One version in a VERSIONED_COMPOSITION. A composition is considered the
unit of modification of the record, the unit of transmission in record extracts, and
the unit of attestation by authorising clinicians. In this latter sense, it may be
considered equivalent to a signed document.
Declaration :
Relation context (<directional composition>) |
The clinical session context of this Composition, i.e. the contextual attributes of
the clinical session.
Declaration :
Relation composer (<directional composition>) |
The person primarily responsible for the content of the Composition
(but not necessarily its committal into the EHR system). This is the
identifier which should appear on the screen. It may or may not
be the person who entered the data. When it is the patient, the special
self instance of PARTY_PROXY will be used.
Declaration :
Attribut language |
Mandatory indicator of the localised language in which this Composition
is written. Coded from openEHR Code Set languages . The language of an
Entry if different from the Composition is indicated in ENTRY.language.
Declaration :
Attribut territory |
Name of territory in which this Composition was written. Coded from
openEHR countries code set, which is an expression of the ISO 3166 standard.
Declaration :
Attribut category |
Indicates what broad category this Composition is belogs to, e.g.
persistent - of longitudinal validity, event , process etc.
Declaration :
Operation is_persistent |
True if category is a persistent type, False otherwise. Useful for finding
Compositions in an EHR which are guaranteed to be of interest to most users.
Declaration :
Relation <directional composition> |
Declaration :
Relation content (<directional composition>) |
The content of this Composition.
Declaration :
All public operations : concept , is_archetype_root , is_persistent , item_at_path , items_at_path , parent , path_exists , path_of_item , path_unique