Hmmm - interesting topic.
See this discussion from 2022, which seems to be related.
@pablo’s conclusion from there was:
That kind of breaks the
normalway of constraining, becausepropertyis not a physical attribute in the RM but an implicit concept behind theunits. I’m guessing that is why this pattern is actually defined in the Archetype Profile model and not in the AOM itself, because the AOM only works over physical/explicit attributes of the RM (declared in a RM class).
I certainly find this odd as well and not sure what to make of it, but a few comments from my end:
- Even if not a physical attribute, its usage is certainly still backed for 1.4 archetypes via the definition of C_DV_QUANTITY from the archetype profile, see
https://specifications.openehr.org/releases/1.0.1/architecture/am/openehr_archetype_profile.pdf
So, I don’t think we should modify existing archetypes using this. - Archie also keeps it when converting an archetype from 1.4 to 2.x
- @thomas.beale 's example from the discussion above contains property for adl2 as well: adl-archetypes/ADL2-reference/features/aom_structures/tuples/openEHR-EHR-CLUSTER.lab_analyte-triglycerides.v0.0.1.adls at master · openEHR/adl-archetypes · GitHub
- It may not be useful within data, but for constraining a quantity to e.g. pressure (of any unit) it makes sense to have.
- How this is currently backed in any way by the specs - beyond the archetype profile - I don’t understand.