It was removed in 2004. We need to discuss if it needs to be reintroduced into RM.
Isn’t this solved with tuples:
value matches {
DV_QUANTITY[id12] matches {
[magnitude, units] matches {
[{|0.0..1000.0|}, {"mg/dL"}],
[{|0.0..20.0|}, {"mmol/L"}]
}
}
}
Or do you need to leave the units “open” at the archetype level? The above example could be further constrained in templates to include only one of the units (or whatever makes clinical sense).
If DV_QUANTITY.property is reintroduced, it introduces a two-level constraining pattern between two RM attributes. Would this be the only such usage?
TERM/latest/SupportTerminology.html#_property does not specify the units. This means they still have to be specified in the archetypes (as supported by AD) or we would need a mapping table for the property codes to the actual units codes (openEHR unit list).
There are posts here and here that point out that the openEHR unit list is a pain point.
Don’t we solve the issue with the openEHR unit list if we agree that DV_QUANTITY.property was removed 20+ years ago?