Sam, for me the point was not having an OpenEhr property but an UCUM property which has also conversion routines for units within that property boundary available, so that it does not matter if the dataset contains Fahrenheit or Celsius when property "temperature" was constrained, because UCUM can tell the data validating/interpretating software how to understand the value and how to convert to another unit if desired.
This needs a redesign of the DvQuantity, see the example Diego described a few days ago. Best regards Bert Op 28 jan. 2018 22:32 schreef "Sam Heard" <sam.he...@oceaninformatics.com>: > Hi All > > The ‘property’ editor is available with the archetype editor. Has anyone > had a look at adding the required type and then the whatever bit can be in > all the tools. > > Cheers, Sam > > > > *From:* openEHR-technical [mailto:openehr-technical- > boun...@lists.openehr.org] *On Behalf Of *Sebastian Garde > *Sent:* Thursday, 25 January 2018 7:33 PM > *To:* For openEHR technical discussions <openehr-technical@lists. > openehr.org> > *Subject:* AW: Quantities of arbitrary units in openEHR > > > > This sender failed our fraud detection checks and may not > be who they appear to be. Learn about spoofing > <http://aka.ms/LearnAboutSpoofing> > > Feedback <http://aka.ms/SafetyTipsFeedback> > > Hi Silje, > > > > I think this may ‘just’ be a modelling tooling issue, openEHR itself > supports this ok. > > > > Speaking for CKM, if you upload an archetype with this to CKM, it should > validate the UCUM unit correctly for [arb'U]{whatever}. > > However, [arb‘*u*]{whatever} or similar is (very slightly) incorrect in > my understanding: > > > > 1. Use the completely vertical ' not ‘ or similar (at least that is my > understanding). > 2. openEHR uses (implicitly I think, but it may be hidden somewhere in > the spec), the case-sensitive version of UCUM – therefore the U needs to be > upper case, see e.g. http://unitsofmeasure.org/ucum.html#para-45 > > > > Regards > > Sebastian > > > > *Von:* openEHR-technical [mailto:openehr-technical- > boun...@lists.openehr.org <openehr-technical-boun...@lists.openehr.org>] *Im > Auftrag von *Thomas Beale > *Gesendet:* Donnerstag, 25. Januar 2018 10:25 > *An:* openehr-technical@lists.openehr.org > *Betreff:* Re: Quantities of arbitrary units in openEHR > > > > Hi Silje, > > I don't understand how adding an 'Arbitrary' term to the openEHR > terminology helps things. DV_QUANTITY.units is a UCUM String field. Won't > the strange units just turn up in the String form you quoted for UCUM > arbitrary units in that field? > > (BTW, to ask for a new terminology term, just create a new issue on the PR > tracker with component=New Term Request - choose this from the dropdown). > > Setting property and not units makes sense - and if we had a proper, > standardised units service, a runtime archetype evaluator would use it to > limit the actual units for property = pressure (say) to only pressure > units. I think we need to define such a service properly.... > > - thomas > > > > On 24/01/2018 09:52, Bakke, Silje Ljosland wrote: > > Hi all, > > > > I’m working on representing medication strengths in archetypes at the > moment. Most medications are thankfully measured in SI units such as mg/ml > or mg/{dose unit}, but others use arbitrary units that are not derived from > any other physical dimensional units. Examples of these are standardized > quality units (SQ-U), focus forming units (FFU), European and American > pharmacopoeia units, anti factor Xa units, or international units (IU). > There are seemingly an unlimited number of these units, and they apparently > make up new ones as they go along (ref: SQ-T and SQ-HDM). See > http://unitsofmeasure.org/ucum.html#para-45 for more. > > > > UCUM has a generic way of representing these, as “[arb’u]{whatever}” > (arbitrary unit, name of the unit), but openEHR doesn’t seem to have a > property in its Quantity data type for them. Could it be a possibility to > add an “Arbitrary” property to the openEHR support terminology for unit > properties? > > > > Also, is it ok to model Quantity elements with a property set but the > units left unconstrained? I’ve just started trying to add these units to an > archetype (as a concentration, so got around the property issue), and it’s > just a never ending task. > > > > Kind regards, > *Silje Ljosland Bakke* > > > > Information Architect, RN > > Coordinator, National Editorial Board for Archetypes > Nasjonal IKT HF, Norway > > Tel. +47 40203298 <+47%20402%2003%20298> > > Web: http://arketyper.no / Twitter: @arketyper_no > <https://twitter.com/arketyper_no> > > > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical@lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > -- > Thomas Beale > Principal, Ars Semantica <http://www.arssemantica.com> > Consultant, ABD Team, Intermountain Healthcare > <https://intermountainhealthcare.org/> > Management Board, Specifications Program Lead, openEHR Foundation > <http://www.openehr.org> > Chartered IT Professional Fellow, BCS, British Computer Society > <http://www.bcs.org/category/6044> > Health IT blog <http://wolandscat.net/> | Culture blog > <http://wolandsothercat.net/> > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
