Re: Normal range/reference ranges for text data type

2016-09-30 Thread GF
I agree that they do not fit in a Data Type. It had better be handled using archetypes. It is too complex for a DV_Ordinal Data Type The reason why I wrote what I wrote is that Archetype must do more than the bare essentials. Leaving more to the implicit knowledge of humans or value sets stored

Re: Normal range/reference ranges for text data type

2016-09-30 Thread Bert Verhees
On 30-09-16 10:46, GF wrote: The ERS system needs to be able to represent faithfully that what was shown on a screen. This is what the HcProvider signs off/attests. See the requirements imposed on ERS systems in ISO 18308. Therefor I’m of the opinion that the archetype used to store data in,

Re: Normal range/reference ranges for text data type

2016-09-30 Thread GF
The ERS system needs to be able to represent faithfully that what was shown on a screen. This is what the HcProvider signs off/attests. See the requirements imposed on ERS systems in ISO 18308. Therefor I’m of the opinion that the archetype used to store data in, and retrieve data from, the

Re: Normal range/reference ranges for text data type

2016-09-30 Thread Thomas Beale
On 29/09/2016 13:31, GF wrote: Each entry in the classification needs: - a screen representation (‘+++') - a description (‘moderate') in theory these two come from DV_ORDINAL.symbol, which is a DV_CODED_TEXT. That assumes a text value of '+++' and either a description or synonym (or both)

Re: Normal range/reference ranges for text data type

2016-09-30 Thread Bert Verhees
On 29-09-16 14:31, GF wrote: Each entry in the classification needs: - a screen representation (‘+++') - a description (‘moderate') - an expression defining the inclusion criteria ('Lower Limit' < ‘Value' < 'Higher limit' - an expression defining the exclusion criteria ('no diagnosis of xyz')

Re: Normal range/reference ranges for text data type

2016-09-29 Thread GF
Each entry in the classification needs: - a screen representation (‘+++') - a description (‘moderate') - an expression defining the inclusion criteria ('Lower Limit' < ‘Value' < 'Higher limit' - an expression defining the exclusion criteria ('no diagnosis of xyz') And perhaps each entry needs:

Aw: Re: Normal range/reference ranges for text data type

2016-09-29 Thread Karsten Hilbert
> Yes. That is how this should work but I'm still not sure exactly what the > requirement is. > > Can you give a couple of examples of the result values and associated > reference ranges? Assuming I correctly understood the OP I think an example would be: Blood in urine dipstick: reference

Re: Normal range/reference ranges for text data type

2016-09-29 Thread GF
Is possible to define inclusion and exclusion criteria in the DV-Ordinal? GF > On 29 Sep 2016, at 09:00, Bakke, Silje Ljosland > wrote: > > Thanks for your replies everyone! > > Can the Any data type be constrained to DV_ORDINAL and populated with values

Re: Normal range/reference ranges for text data type

2016-09-29 Thread Ian McNicoll
openehr.org] *On Behalf Of *Thomas Beale > *Sent:* Wednesday, September 28, 2016 4:44 PM > *To:* openehr-clinical@lists.openehr.org > *Subject:* Re: Normal range/reference ranges for text data type > > > > > > Normally this is done with the Ordinal (DV_ORDINAL) data type, which

RE: Normal range/reference ranges for text data type

2016-09-29 Thread Bakke, Silje Ljosland
:44 PM To: openehr-clinical@lists.openehr.org Subject: Re: Normal range/reference ranges for text data type 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_pack

Re: Normal range/reference ranges for text data type

2016-09-28 Thread Ian McNicoll
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 wrote: > > Normally this is done with

Re: Normal range/reference ranges for text data type

2016-09-28 Thread Thomas Beale
Normally this is done with the Ordinal (DV_ORDINAL) data type, which is a kind of DV_ORDERED , which has normal_range and reference_ranges defined. - thomas On 28/09/2016 14:25, Karsten Hilbert

Re: Normal range/reference ranges for text data type

2016-09-28 Thread Karsten Hilbert
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'

Re: Normal range/reference ranges for text data type

2016-09-28 Thread Ian McNicoll
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

Re: Normal range/reference ranges for text data type

2016-09-28 Thread Karsten Hilbert
On Wed, Sep 28, 2016 at 11:27:18AM +, 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", "+/++/+++", >

Re: Normal range/reference ranges for text data type

2016-09-28 Thread Diego Boscá
Hello Silje, We had a little discussion on the matter in the questions part of the wiki this year https://openehr.atlassian.net/wiki/questions/30900242/how-to-model-meta-archetypes Regards 2016-09-28 13:27 GMT+02:00 Bakke, Silje Ljosland : > Hi everyone, > >