Representing a Real value in openEHR

Diego Boscá yampeku at gmail.com
Tue Mar 17 07:02:28 EDT 2015


So it would be stored as {1}? (as they are supposed to be UCUM). Empty
units doesn't feel like valid UCUM units either.

2015-03-17 11:55 GMT+01:00 Daniel Karlsson <daniel.karlsson at liu.se>:
> Hi,
> what about the unit 1 (uno) for dimensionless quantities?
> http://goldbook.iupac.org/D01742.html
>
> /Daniel
>
>
> On tis, 2015-03-17 at 11:43 +0100, Diego Boscá wrote:
>> Qualified Real is a property from the domain type, not the type
>> itself, I thought the idea was to get rid of domain types in the
>> future.
>>
>> 2015-03-17 11:23 GMT+01:00 Ian McNicoll <ian at freshehr.com>:
>> > Hi David,
>> >
>> > Qualified Real is the current preferred option (for me anyway). I think we
>> > have flagged up in the spec CRs that proper support for Real would be
>> > helpful as Qualified real is somewhat obscure.
>> >
>> > So - agree with your request.
>> >
>> > Ian
>> >
>> >
>> >
>> > Dr Ian McNicoll
>> > mobile +44 (0)775 209 7859
>> > office +44 (0)1536 414994
>> > skype: ianmcnicoll
>> > email: ian at freshehr.com
>> > twitter: @ianmcnicoll
>> >
>> > Director, freshEHR Clinical Informatics
>> > Director, openEHR Foundation
>> > Director, HANDIHealth CIC
>> > Hon. Senior Research Associate, CHIME, UCL
>> >
>> > On 17 March 2015 at 10:09, David Moner <damoca at gmail.com> wrote:
>> >>
>> >> Hello,
>> >>
>> >> It might seem a very basic question, but I couldn't find an appropriate
>> >> answer anywhere. Which is the best way to model a single Real number in
>> >> openEHR? For example, a result of a score.
>> >>
>> >> I have found two possible options:
>> >>
>> >> - Use a DV_QUANTITY, with the "Qualified Real" property, that sets the
>> >> units to an empty String. This approach is used in the "Harris Hip Score"
>> >> archetype (http://www.openehr.org/ckm/#showArchetype_1013.1.1873)
>> >>
>> >> - Use a DV_PROPORTION, with the PROPORTION_KIND set to Unitary. This
>> >> approach is used in the "Waist and hip circumference" archetype
>> >> (http://www.openehr.org/ckm/#showArchetype_1013.1.332)
>> >>
>> >> In both cases, it seems we are forcing to use a data type that does not
>> >> really fit for purpose. Why don't we have something similar as the DV_COUNT,
>> >> but representing a real number and not an integer? Something equivalent to
>> >> the REAL data type in ISO 21090
>> >>
>> >> David
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> David Moner Cano
>> >> Grupo de Informática Biomédica - IBIME
>> >> Instituto ITACA
>> >> http://www.ibime.upv.es
>> >> http://www.linkedin.com/in/davidmoner
>> >>
>> >> Universidad Politécnica de Valencia (UPV)
>> >> Camino de Vera, s/n, Edificio G-8, Acceso B, 3ª planta
>> >> Valencia – 46022 (España)
>> >>
>> >> _______________________________________________
>> >> openEHR-clinical mailing list
>> >> openEHR-clinical at lists.openehr.org
>> >>
>> >> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>> >
>> >
>> >
>> > _______________________________________________
>> > openEHR-clinical mailing list
>> > openEHR-clinical at lists.openehr.org
>> > http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>>
>> _______________________________________________
>> openEHR-clinical mailing list
>> openEHR-clinical at lists.openehr.org
>> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org




More information about the openEHR-clinical mailing list