Dv_coded_text_extended

[ian.mcnicoll]

There have been a lot of of conversations on this - basically we can do this already via DV_TEXT/DV_CODED_TEXT but is a bit confusing so we have been looking to introduce the idea of term-binding strength in ADL/AOM2 which is much more explicit.

Addition of required / extensible / preferred / example terminology constraint to AOM and ADL

The openEHR SEC has decided on the addition of the required | extensible | preferred | example ‘binding strength’ constraint modifier, following the model used in HL7 FHIR. The change is documented in openEHR CR SPECAM-68. The change to AOM2 spec looks like this in the UML: [C_terminology_code] We have yet to determine how it should look in ADL2. Currently, the various forms of terminology constraint look as follows in ADL2. ​items matches { ​ELEMENT[id11] occurrences matches {0..1…