Glossary
A
- ADL
- Archetype Definition Language
- AOM
- Archetype Object Model
- Archetype
- 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.
C
- CDR
- Clinical Data Repository
- Composition
- 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)
D
- DDR
- Demographic Data Repository
I
- ITS
- Implementation Technology Specification
L
- Locatable
- openEHR RM class that is the parent of all archetypable and versionable objects
O
- 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.
R
- RM
- openEHR Reference Model, contains the definitions of all the classes that define concepts like EHR, COMPOSITION, VERSION, etc. which enable information management.
T
- Template
- 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 models.
- TOM
- 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.