Hi Silje, This seems a bit odd to me. Do labs normally
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. see http://openehr.org/ckm/#showArchetype_1013.1.2192 Does that work? Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com twitter: @ianmcnicoll Co-Chair, openEHR Foundation ian.mcnic...@openehr.org Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 28 September 2016 at 12:56, Karsten Hilbert <karsten.hilb...@gmx.net> wrote: > On Wed, Sep 28, 2016 at 11:27:18AM +0000, Bakke, Silje Ljosland wrote: > >> We're working on requirements for labs results, and have >> bumped into a potential problem. Some results are >> textual/non-quantitative in nature, for example >> "positive/negative", "+/++/+++", >> "negative/borderline/positive". These results also need a >> kind of "normal range" for the receiving system to be able to >> mark or emphasise it in the UI. The text data type however >> doesn't have any normal range/reference ranges attributes in >> the reference model like the quantity, count and ordinal data >> types do. We can't have several different places where the >> normality information is kept for different data types, as >> this would be very complex to handle. How should this be >> handled? > > Often, the lab will provide a field denoting in-rangeness of > such results. Other than that, a human on the receiving side > may have to manually set the property when reviewing / > paraphing the result. > > Some programmatic smarts can be added to applications to > auto-set the property to "not-any-known-normal" where > "known-normal" consists of a suitably restricted regular > expression defined per test type. > > Karsten > -- > GPG key ID E4071346 @ eu.pool.sks-keyservers.net > E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 > > _______________________________________________ > openEHR-clinical mailing list > openEHR-clinical@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org _______________________________________________ openEHR-clinical mailing list openEHR-clinical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
