Re: UCUM code in body temperature archetype

An alternative for dealing with semantic in archetypes is dealing with semantics in coding systems like SNOMED. The consequence is that SNOMED must be a complete Medicinal Product Formulary. I have doubts whether this is a good idea. Many countries have different specific formularies. I like to

Re: UCUM code in body temperature archetype

In 2012 a number of ISO standards were published on the “Identification of medicinal products” When I recall correctly there is one that deals with the representation of dose forms, units of presentation and route of administration. Jan Talmon > On 19 mei 2016, at 10:19, Gerard Freriks

Re: UCUM code in body temperature archetype

Hi Gerard, "The consequence is that SNOMED must be a complete Medicinal Product Formulary. I have doubts whether this is a good idea.' dm+d is a UK health-service managed dictionary based on SNOMED CT and using the UK national namespace i.e. it is not managed internationally. It is a complete

Re: UCUM code in body temperature archetype

Here in Spain there is an official terminology for medication dispensation. It is partially mapped to snomed (and the remaining ones will be part of snomed national extension) In my opinion, it makes perfect sense to allow the specification of 'units' from other (non-ucum) terminologies, such as

Re: UCUM code in body temperature archetype

On 19/05/2016 08:26, Ian McNicoll wrote: Hi Thomas, I appreciate that the Quantity classes add computability such as the +,-,=, diff operators etc but computability (or at least safe/sensible computability) is not a given even when the two operands share the same unit. it might not be

Re: UCUM code in body temperature archetype

I agree with Thomas. Speaking as someone who has had to help with quality control of large amounts of user entered concomitant medication data for clinical trials, ‘tablet’ , ‘capsule’, and similar are not ‘units’ unless they are associated with other reference data. ‘Tablet' is a description

Re: openEHR draft Expression spec

Hello Thomas, I had already noticed the expressions part and based my experimental implementation on that. This email got quite long, so let’s start with a summary: Summary: - The current spec is quite similar to XPath. We can keep this even closer by referencing to the XPath specification in

Re: AW: Archie version 0.1.0 released

It certainly does validate specs. In fact, it already has caused some corrections to both the specs and the ANTLR-grammar. And we already found a few more issues in the specs. I’ll soon file an issue report about the rules section, to specify how to handle operators on multiple-valued path

openEHR draft Expression spec

Pieter, With respect to the 'rules' bit of ADL, and also GDL, there is a new draft 'Expressions' spec in the BASE component . This is a working draft, and partly lifted from ADL/AOMs specs (those now just include this one), plus some

Re: openEHR-technical Digest, Vol 51, Issue 24

William, I think the question is /how/ they use UCUM. If it's just a question of expressing '5 mg', that works out of the box. I would imagine that here you are talking about the manufactured dose of one tablet / capsule / etc, i.e. the manufacturer's point of view (what's printed on the

RE: openEHR-technical Digest, Vol 51, Issue 24

__ openEHR-technical mailing list openEHR-technical@lists.openehr.org<mailto:openEHR-technical@lists.openehr.org> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- next part -- An HTML attachment was scrubbed... URL: <http://lists.op

RE: openEHR-technical Digest, Vol 51, Issue 26

commendations can only be to adjust to the UCUM, or if you find > something awkward to adjust UCUM via the open community. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20160519/096d77d0/

Re: UCUM code in body temperature archetype

Thomas, All are Units of a different kind. SI defines: Units of Measure, and Units of Quantity in the scientific domain. There are also Units of Time: minute, hour, etc. When I think of tablets, capsule, etc. we will call these Units of Medicinal Product Dose. Isn’t in UCUM this an example of

Re: UCUM code in body temperature archetype

Hi Gerard, they actually could be, but whenever this discussion comes up, no-one proposes it. I'm not sure if I would either, because these arbitrary units are still not computable in general, but 'dose units' can be made computable but only with some extra data fields, i.e. you need both the

Re: UCUM code in body temperature archetype

Hi Thomas, In the UK (and ? Aus/NZ), we would not use arbitrary units in UCUM for dose units because the latter are expressed as SNOMED terms, and are used in conjunction with the SNOMED-based dm+d (or AMT) drug dictionary to compute actual doses/amounts where possible. e.g. 318421004 |

Re: UCUM code in body temperature archetype

Hi Thomas, I appreciate that the Quantity classes add computability such as the +,-,=, diff operators etc but computability (or at least safe/sensible computability) is not a given even when the two operands share the same unit. Nor does the fact that a unit is non-scientific invalidate the use

Re: UCUM code in body temperature archetype

Two reactions: 1- There is a difference between the world of semantic interpretability in system interfaces and the real word of users looking at screens, and typing on keyboards In one world we can/must use as much as possible SI units via UCUM and strife for as detailed as possible reducing