Normal range/reference ranges for text data type

Ian McNicoll ian at freshehr.com
Wed Sep 28 10:57:09 EDT 2016


Thanks Thomas,

Good suggestion.

@karsten. The reference range guidance element could be made computable by
using a coded text and controlled terminology, rather than just plain text.

Ian
On Wed, 28 Sep 2016 at 15:43, Thomas Beale <thomas.beale at openehr.org> wrote:

>
> Normally this is done with the Ordinal (DV_ORDINAL) data type, which is a
> kind of DV_ORDERED
> <http://www.openehr.org/releases/RM/latest/docs/data_types/data_types.html#_quantity_package>,
> which has normal_range and reference_ranges defined.
>
> - thomas
>
> On 28/09/2016 14:25, Karsten Hilbert wrote:
>
> On Wed, Sep 28, 2016 at 01:23:00PM +0100, Ian McNicoll wrote:
>
>
> If a result is expressed as normal/ abnormal or high/normal/low,
> surely the 'normalcy range' is self-defining.
>
> If there is a need for the lab to assert some kind of textual normalcy
> rangeThe 'reference range guidance' element  in the Lab panel
> archetype is intended for this purpose and essentially equates to
> referenceRange/text in the FHIR Observation.
>
>
> I think Silje was asking about a way to define reference
> ranges for textual results in a computable fashion.
>
> Karsten
>
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20160928/47ee640b/attachment-0002.html>


More information about the openEHR-clinical mailing list