Operational Template 2 (OPT2) DEVELOPMENT
The format for a template in ADL 2. A template combines multiple archetypes to define a complete form or document (such as a discharge summary or encounter note); the OPT2 is its fully flattened, self-contained form that clinical systems use at runtime to drive data entry, validation, and storage, with no further archetype resolution required. OPT 1.4 is the predecessor aligned with the ADL 1.4 formalism. Template authors compose it from a root archetype and one or more filler archetypes, specifying slot fillers, value set restrictions, and language selections.
Purpose
This document provides the formal specification of the Operational Template (OPT) for ADL2 artefacts. The OPT is a first generation 'compiled' artefact based on source archetypes and templates, that serves as the starting point for further downstream format generation (e.g. schemas, APIs) as well as the computational format for operational EHR systems using archetypes.
This specification is primarily intended for software developers.
Related Documents
Prerequisite documents for reading this document include:
Related documents include:
Nomenclature
In this document, the term 'attribute' denotes any stored property of a type defined in an object model, including primitive attributes and any kind of relationship such as an association or aggregation. XML 'attributes' are always referred to explicitly as 'XML attributes'.
We also use the word 'archetype' in a broad sense to designate what are commonly understood to be 'archetypes' (specifications of clinical data groups / data constraints) and 'templates' (data sets based on archetypes, since at a technical level, an ADL/AOM 2 template is in fact just an archetype. Accordingly, statements about 'archetypes' in this specification can be always understood to also apply to templates, unless otherwise indicated.
Feedback
Feedback may be provided on the openEHR ADL forum.
Issues may be raised on the specifications Problem Report tracker.
To see changes made due to previously reported issues, see the AM component Change Request tracker.