From 3ac7884fde998533afbf538340528ff1502b19ee Mon Sep 17 00:00:00 2001 From: Severin Kohler Date: Wed, 21 May 2025 16:30:38 +0200 Subject: [PATCH] Changed Reconstitutability --- docs/Identification/master07-referencing.adoc | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/Identification/master07-referencing.adoc b/docs/Identification/master07-referencing.adoc index 288c7617..dfc3e5ca 100755 --- a/docs/Identification/master07-referencing.adoc +++ b/docs/Identification/master07-referencing.adoc @@ -351,8 +351,13 @@ With the more sophisticated identification system described here, these archetyp `org.openehr::openEHR-EHR-EVALUATION.diagnosis.*v1.29.0*` -References with no namespace will remain legal, since there should be no computational impediment to using uncontrolled archetypes and templates, e.g. in an experimental situation. The lack of minor and patch level version numbers should also be legal for non-namespaced identifiers, and be interpreted as meaning `0` in both cases, i.e. `.v1` means `.v1.0.0`. +References with no namespace will remain legal, since there should be no computational impediment to using uncontrolled archetypes, e.g. in an experimental situation. The lack of minor and patch level version numbers should also be legal for non-namespaced identifiers, and be interpreted as meaning `0` in both cases, i.e. `.v1` means `.v1.0.0`. +`org.openehr::openEHR-EHR-COMPOSITION.SomeTemplateName.v1.29.0` + +For template IDs, the link:https://specifications.openehr.org/releases/AM/development/AOM2.html#_archetype_identification[HRID format] is mandatory. Older formats that omit the namespace and version are deprecated but still supported for legacy data. + +This requirement is introduced to allow compositions to clearly reference a specific version of the template and to facilitate transformation to ADL2. The template ID must be provided at the point of composition validation. === Supporting Archetype-based Querying Querying of data in openEHR systems is assumed to be based on archetype 'path-sets', i.e. the set of paths extracted from an operational (flat-form) archetype. The paths are a slight simplification of standard X-paths. Two querying methods have been described to date, AQL and a-path, both making this assumption (see {openehr_query_aql}[The Archetype Querying Language (AQL)^] ).