I would like to pick up a discusssion we started in the ADL2 meeting last year in Braunschweig: We had another request (this time from HiGHmed) to support open/extensible set of codes in a DV_CODED_TEXT. In this case, the reason is that they cannot standardise all codes across the various sites, b…

Further to today’s discussion, and @ian.mcnicoll 's worry about whether local code-sets can be ‘broken’ in a specialisation by adding a new code, not just restricting (as per standard constraint logic), well, this can be done, if you assume that the parent code set has this new marker of extensible …

Also, just to be clear on why value-set constraints are just the same as any other constraint in a machine-processing sense: the universal rule we have is that the data created according to any archetype will be a valid instance of any parent of that archetype. If that is not the case, archetypes do…

[image] thomas.beale: data created according to any archetype will be a valid instance of any parent of that archetype Well, this isn’t true if we let create new nodes derived from RM classes in specialization/templates, and this is the exact same thing but with data types.

So-called ‘new’ nodes can only be created if the archetype permits it. By default, container attributes do allow such nodes, unless specifically prohibited using an exclusion node. See here . However, the value range of a leaf type, i.e. Integer, String, Date, Terminology_code etc is not a set of ch…

Just to illustrate with a timely example from the Covid-19 modelling. We created a specialization of the health risk evaluation archetype. The purpose of this was to model the Covid-19 risk factors. It was great to use the archetype for such purposes regarding the translations into different langua…

Yeah, I was referring to creating new DV_TEXT/DV_CODED_TEXT which are actually objects. Domain types kind of hide it a little, but it’s just a RM specific way of defining alternatives. I would disagree in having garbage, you will have an actual archetype/template that governs your data, it wouldn’t…

[image] bna: Later in the epidemic situation new risk factors where added. Some might even be national or regional. We wanted a way to add more terms into the archetype. So I would assume this corresponds to the need to mark the term constraint as either preferred or maybe extensible as per o…

[image] yampeku: it wouldn’t be strictly a specialization, but neither are now with the ‘open unless specifically prohibited’ Well actually, strictly speaking, so-called ‘added’ nodes like ELEMENT and so on are proper specialisations, since they still fit the data space defined by the RM (e.g…

last bit was related to your second paragraph, explicit id4 specializations could be created, and even id4 be prohibited. This would also give some actual meaning to the occurrences in DV (i.e. if it is defined as alternatives of 1…1 objects it wouldn’t be able to remove “terms” from the subset, but…

DV_CODED_TEXT with open/extensible set of codes (value set)

Specifications ADL

sebastian.garde (Sebastian Garde) 12 March 2020 13:27 2

For cross-reference - see https://openehr.atlassian.net/browse/SPECPR-70 (an older, closely related, PR).

Topic		Replies	Views
Option to record free text as choice against DV_CODED_TEXT - do we need DV_PLAIN_TEXT ADL adl , archetype	72	2672	5 January 2023
FHIR-like terminology 'binding strengths'? Technical (archive)	9	56	17 April 2019
A case for hierarchical value sets Specifications archetype	18	1457	22 February 2021
Coding element and event names Specifications template	59	1447	28 August 2026
Addition of required / extensible / preferred / example terminology constraint to AOM and ADL ADL	21	2097	20 March 2023
Why is value not optional for DvCodedText RM	27	1101	20 October 2021
Text, descriptions and comments for value set items - mandatory or optional? Clinical	40	2370	3 June 2020
New ADL/AOM proposals to solve some old problems Technical (archive)	15	59	29 April 2013
Storing codes of two external terminologies Terminology	37	1987	19 July 2024
Modelling and behavior of of the data type DV_ORDINAL Specifications	42	2343	18 March 2021

DV_CODED_TEXT with open/extensible set of codes (value set)

Related topics