Hi, I’ve got a use case where we need to represent a time duration (of a symptom), which can be for example <24H or >3M. Is it possible to represent this using the DV_DURATION data type, like you can do with DV_QUANTITY and magnitude_status? If not, what should we do? Kind regards, Silje Ljosland…

Not sure if this is already in the RM version you use and not sure if ADL 1.4 supports this, but can this be a DV_INTERVAL of DV_DURATION? Regards, Pieter Bos

Yeah, it is supported in 1.4. However, I’m not sure that that Durations are the way to go here, as all the duration is constraint as string, which means string lists or regex in best case scenario, which IMO makes pretty difficult to represent the “<” or “>”. Personally I would go with an alternativ…

Hi Diego, Does DV_DURATION not inherit magnitude_status as a separate attribute from the RM? https://www.openehr.org/releases/trunk/UML/#Architecture___18_1_83e026d_1433773264460_352968_7042 Not sure it would work in archetyping constraint but in data it would/should just be value: “P24H” magni…

I’ve never understood the usefulness of that attribute: Seems strange to populate an attribute that will end up in data with a value that could provoke misunderstandings

I’m not really sure that it even means what we need in this case

Indeed it does, as may be verified with the ADL Workbench [image]

It was added to the RM years ago to support quantities in lab results, which are sometimes of the form <X, >Y etc. If I had my time again, I would have moved the date/time types out a bit so they did not inherit this attribute. Usually it is Void. - thomas

yeah, I can see to be useful for that, but seems weird to constraint it in any way

Hi Diego, We have certainly had to use it in some lab test integrations. I would normally agree that it might be risky to carry this kind of modifier as a separate attribute, which could easily be missed in queries, but these are gnerally imprecise values (as in Silje’s use-case) or out-of-range on…

But the meaning is for this attribute is to be be used in measures like lab result to express things that are probably barely measurable, not to express that in modelling time the other defined constraint is meant to be the upper (or lower) part of a range

DV_DURATION and magnitude_status?

Technical (archive)

system (system) 25 September 2018 09:24 17

Hi Slije,

Duration should support magnitude_status - it is alreqady defined as such in the RM. The issue is about how to archetype this, not represent in data.

However … I am not exactly sure if current CDRs support storing magnitude_status for Duration. Suggest you give it a go!!

Ian

Topic		Replies	Views
rm_type_name for the DV_DURATIONs primitive object in XML Technical (archive)	11	5	18 March 2016
Duration data type RM datatypes	12	987	1 May 2020
DV_DATE_TIME and DV_DATE RM	15	1058	26 September 2022
DV_DURATION as ranges Technical (archive)	3	9	30 January 2012
Tool support of DV_DURATION Specifications adl , archetype	4	914	11 February 2021
Recording of estimates using reference model attributes Clinical (archive)	4	5	1 December 2014
Missing "magnitude" for DV_QUANTITY constraint ADL	6	530	31 January 2022
DV_QUANTITY or DV_DURATION? Technical (archive)	3	5	23 December 2010
CDR implementation of partial DV_TEMPORALs Implementation	9	110	29 April 2026
Runtime name suggestions? Technical (archive)	8	3	18 January 2017

DV_DURATION and magnitude_status?

Related topics