Archetypes

Archetype

An archetype is a data specification for a single clinical concept.

Usually designed with to be inclusive of all possible data points that might be relevant for that specific clinical concept:

Maximal data set
Universal use case

Design principle: incorporate minimal constraints to ensure broadest possible use and to maximise interoperability

Archetype classes

Archetypes are separated into five different major types that reflect the different clinical or data-specific purpose.

The Classes are:

COMPOSITION
SECTION
ENTRY
CLUSTER
ELEMENT

When constructing archetypes, it is important to consider how the data will be used and select an archetype from the appropriate class for use.

COMPOSITION

A COMPOSITION is a container class of archetype.

It is the unit of contribution (and therefore committal and communication) to an electronic health record (EHR).

Remember: "You cannot save less than a Composition”

All openEHR data is transferred between EHRs as Compositions.

Set of entries comprising a clinical care session or document. This can be used to gather multiple concepts together and is typically used to describe clinical care or represent a clinical document. A composition archetype is a container for other classes of archetypes used for that clinical encounter. For example consultation note, health report or prescription.

A COMPOSITION can contain SECTION and ENTRY archetypes.

Examples: Consultation note, Prescription, Care Plan, Medication List

SECTION

A SECTION is a navigation class of archetype. It has no inherent semantic meaning but is used to support human navigation:

for content designers
for content reviewers

ENTRY

OBSERVATION

EVALUATION

INSTRUCTION

ACTION

CLUSTER

ELEMENT

General

Maximal data set

blah

Archetype		A single clinical content specification for a single clinical concept. Usually designed with the intent of being a maximal data set and universal use case, thus inclusive of all data elements frelevant for that clinical concept. Data elements are gathered by reflecting upon a broad scope of clinical data required to provide clear, unambiguous care for patients and which is applicable to all clinical situations (otherwise known as a maximal data set). Archetypes include data elements that will not change over time, (universal constraints
Composition	Archetype class
Section	Archetype class
Entry	Archetype class
Observation	Archetype class
Evaluation	Archetype class
Instruction	Archetype class
Action	Archetype class
Admin Entry	Archetype class
Cluster	Archetype class
Element	Archetype class
Clinical Knowledge Manager (CKM)		For information on the terms used related to the Clinical Knowledge Manager tool: CKM Glossary
History/Event Model
Maximal data set
Protocol
Reference Model
Slot
Specialisation
State Model
Template
Terminology
Universal use case
Value set

NOTE: For information on the terms used related to the Clinical Knowledge Manager tool: CKM Glossary

Archetypes are separated into five classes which provide flexibility for use and reuse irrespective of clinical application. When constructing archetypes, it is important to consider the end use for the archetype during the draft phase and select the most appropriate “category” suitable for long term, sustainable use of data.

openEHR Clinical Modelling Glossary

Archetypes

General