Is a set of constraints over the RM that defines a maximal data model for one specific domain concept, for
instance Blood Pressure, Body Temperature, Service Request, etc.
Clinical Data Repository
In the openEHR RM, is the class that represents a document or data structure that can be individually added
to an EHR (data contained in a Composition can't be added to an EHR without a containing Composition)
Demographic Data Repository
Implementation Technology Specification
openEHR RM class that is the parent of all archetypable and versionable objects
Operational Template (OPT)
An OPT is the final form of a template, that is used on a concrete system. Atomik uses OPTs for everything, from data
definition and indexing, to data validation and querying.
openEHR Reference Model, contains the definitions of all the classes that define concepts like EHR, COMPOSITION,
VERSION, etc. which enable information management.
Represents a full document, folder, or actor, defined by using existing archetypes. It can be seen as a big archetype,
designed to be used in a specific context. Unlike archetypes, a template doesn't include every single node of the
archetypes they reference, jsut the parts that are needed by the specific context. So templates are not maximal data
Template Object Model, is the model that defines the templates. This is not a formal model in the openEHR specifications
but a de-facto one that surged from a useful implementation technology.