Currently, the last main blockers in getting ADL2 over the line, are various issues around DV_CODED_TEXT constraints that are required and variably supported in .oet.
One of the options in .oet is to be able to define an inline external terminology valueset e.g.
Looking at AOM2, it feels as if we might usefully open up the valueset to include non-local terms, and indeed consider some other features in FHIR such as a simple way of nesting terms with in the valueset. Not having nesting has led to us (IMO) havesome rather mangled models - e.g. there is wel established pattern oin documenting pulse rythm of
Regular Irregular regularly irregular Irregularly irregular
with some people wanting to stick at the top-level only, others preferring second-level detail for irregualr.
Flattening out the list was felt the wrong thing to do so we currently have 2 datapoints one for Regular/Irregular, the other for Type of Irregularity.
Is there even an argument for aligning our valueset with the helpful features in the FHIR valueset, so that becomes pretty well identical whether constrained locally or as an external rtef