# Remove DV\_QUANTITY.property attribute in BMM files

**URL:** <https://discourse.openehr.org/t/remove-dv-quantity-property-attribute-in-bmm-files/6779>\
**Category:** BMM/Expressions\
**Created:** [8 May 2025 08:10 UTC](https://discourse.openehr.org/t/remove-dv-quantity-property-attribute-in-bmm-files/6779 "2025-05-08T08:10:19Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sebastian.garde](https://discourse.openehr.org/user_avatar/discourse.openehr.org/sebastian.garde/32/3070_2.png) [@sebastian.garde](https://discourse.openehr.org/u/sebastian.garde)\
**Post date:** [8 May 2025 09:59 UTC](https://discourse.openehr.org/t/remove-dv-quantity-property-attribute-in-bmm-files/6779/3 "2025-05-08T09:59:57Z")

</div>

Hmmm - interesting topic.

See this discussion from 2022, which seems to be related.

> [@General modeling question for DV\_QUANTITY with multiple properties](https://discourse.openehr.org/t/general-modeling-question-for-dv-quantity-with-multiple-properties/2647/):
>
> I was creating some examples for my clinical modeling students, and one example that I wanted to create was to allow recording different units for different physical properties in the same DV\_QUANTITY, then realized the Archetype Editor didn’t allow multiple “properties” in the same DV\_QUANTITY. Spec-wise, in general, without considering any specific use case, would it be possible to create such archetype / ADL? I think it’s not possible if using the archetype\_profile class C\_DV\_QUANTITY since…

@pablo’s conclusion from there was:

> That kind of breaks the `normal` way of constraining, because `property` is not a physical attribute in the RM but an implicit concept behind the `units`. 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:

1. 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](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.
2. Archie also keeps it when converting an archetype from 1.4 to 2.x
3. @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](https://github.com/openEHR/adl-archetypes/blob/master/ADL2-reference/features/aom_structures/tuples/openEHR-EHR-CLUSTER.lab_analyte-triglycerides.v0.0.1.adls)
4. It may not be useful within data, but for constraining a quantity to e.g. pressure (of any unit) it makes sense to have.
5. How this is currently backed in any way by the specs - beyond the archetype profile - I don’t understand.

---

_[View the full topic](https://discourse.openehr.org/t/remove-dv-quantity-property-attribute-in-bmm-files/6779)._