Support 'dose units' in DV_QUANTITY
Description
Attachments
PR is addressed in
is duplicated by
Activity
Ian McNicoll March 4, 2024 at 3:21 PM
This can be closed - implemented in RM 1.1.0 with units_system attribute
Severin Kohler March 4, 2024 at 2:00 PM
push, see Thomas comment below.
Thomas Beale May 24, 2022 at 2:01 PM
can you confirm that this PR is also solved by SPECRM-65?
Ian McNicoll January 29, 2019 at 12:50 PM
This would actually be addressed by SPECRM-65. https://openehr.atlassian.net/browse/SPECRM-65
Pablo Pazos July 23, 2018 at 9:13 PM
This was a recent email (July 13th 2018) to the SEC that generated a nice review of this topic. Just for the record:
Subject "Constraints of current DV_QUANTITY.units"
I'm playing around with FHIR resources and found that they use UCUM units but considered as a coded value, so it can use other terminologies for the units, or even use custom units.
On the other hand, seen some forced archetype modeling trying use the current units that we have on DV_QUANTITY that are UCUM only, adding some extra nodes to model custom units.
Basically, we are stuck with UCUM because DV_QUANTITY.units is String, not CODE_PHRASE.
I think that change would simplify modeling, and with modeling, will simplifying storing, querying, etc.
Personally I like the idea of being able to use other units when needed, and control the terminology used for the units.
At present it is not possible to use 'dose units' e.g 'tablets', 'drops' 'puffs' in DV_QUANTITY which makes it impossible to record medication amounts within a single element i.e needing an element for amount and one for 'units'.
This seems clumsy for a reference model attuned to clinical care where medication amounts are ubiquitous.
One solution might be to allow non-UCUM terms as 'units'.