I’m looking to test an implementation of parsing OPT v1.4 and examples I’ve found on CKM don’t include T_CONSTRAINT, T_VIEW or FLAT_ARCHETYPE_ONTOLOGY or make use of C_DV_STATE or C_DV_ORDINAL.
Does anyone have any “maximal” examples which make use of / demonstrate the features in OPT v1.4 as defined in Template.xsd?
In the openEHR-SDK we use the all_datatypes OPT for testing constraints in amplitude openEHR-SDK/src/main/resources/opts at master · CaboLabs/openEHR-SDK · GitHub
RIPPLE - Conformance Test template.opt (461.5 KB)
This certainly has DV_ORDINAL . I’m not sure that C_DV_STATE was ever supported in tooling. Not sure about the other constructs
Is there an easy way of knowing what bits of the spec in Template.xsd are not actually used in practice. I can’t find any documentation about them beyond what’s in the schema and they don’t feature in the AOM v1.4
I don’t think we have such thing documented.
Though about C_DV_STATE it was there for the Instruction State Machine, but that ended up being defined by normal C_OBJECTs on ACTION archetypes.