D

NameKindDescription
dataattributeThe data of the Entry; modelled in archetypes.
dataattributeThe actual data found at uri, if supplied inline.
dataattributeThe data of this evaluation, in the form of a spatial data structure.
datarelationThe data of this event.
dataattributeThe data' from the source message or record.

** SHOULD BE of Type ITEM_TREE **
dataoperationData of wrapped ORIGINAL_VERSION.
dataattributeThe data of this observation, in the form of a history of values which
may be of any complexity.
datarelationThe data being versioned. If not present, this corresponds to logical deletion.
dataoperationOriginal content of this Version.
DATA_STRUCTUREclassAbstract parent class of all data structure types. Includes the as_hierarchy function
which can generate the equivalent CEN EN13606 single hierarchy for each
subtype's physical representation. For example, the physical representation of an
ITEM_LIST is List<ELEMENT>; its implementation of as_hierarchy will generate a
CLUSTER containing the set of ELEMENT nodes from the list.
DATA_STRUCTUREartifact
data_structurespackageIn most openEHR information models, generic data structures are used for expressing
content whose particular structure will be defined by archetypes. The generic structures
are as follows.
Single: single items, used to contain any single value, such as a height or weight.
List: linear lists of named items, such as many pathology test results.
Table: tabular data, including unlimited and limited length tables with named and
ordered columns, and potentially named rows.
Tree: tree-shaped data, which may be conceptually a list of lists, or other deep structure.
History: time-series structures, where each time-point can be an entire data structure
of any complexity, described by one of the above structure types. Point and interval
samples are supported.
data_structures_class_diag (rm)class diagram
data_structures_cvclass view
data_structures_dvdeployment view
data_typespackage
data_typespackageA set of clearly defined data types underlies all other models, and provides a number of general and clinically specific types required for all kinds of health information. The following categories of data types are defined in the data types reference model.
Text: plain text, coded text, paragraphs.
Quantities: any ordered type including ordinal values (used for representing symbolic ordered
values such as + , ++ , +++ ), measured quantities with values and units, and so on.
Date/times: date, time, date-time types, and partial date/time types.
Encapsulated data: multimedia, parsable content.
Basic types: boolean, state variable.
DATA_VALUEclassServes as a common ancestor of all data value types in openEHR models.
DATA_VALUEartifact
date_timepackage
date_time_cvclass view
date_time_dvdeployment view
day_validityattributeValidity of day in constrained date.
day_validityattributeValidity of day in constrained date.
days_allowedattributeTrue if days are allowed in the constrained Duration.
default_valueoperationGenerate a default value from this constraint object.
default_valueoperationGenerate a default value from this constraint object.
default_valueattribute
defining_coderelationThe term which the value' attribute is the textual rendition (i.e. rubric) of.
definitionrelation
Root node of this archetype.
definitionattribute
definitionpackageThe rm.support.definition package defines symbolic definitions used by the
openEHR models. Only a small number are currently defined.
definitionrelation
definition_class_diag (rm)class diagramClasses in the rm.support.definition package.
Includes OPENEHR_DEFINITIONS, BASIC_DEFINITIONS.
definition_cvclass view
definition_dvdeployment view
demographicpackageThe demographic model defines generic concepts of PARTY, ROLE and related details such as contact addresses. The archetype model defines the semantics of constraint on PARTYs, allowing archetypes for any type of person, organisation, role and role relationship to be described. This approach provides a flexible way of including the arbitrary demographic attributes allowed in the OMG HDTF
PIDS standard.
demographicpackage
denominatorattributedenominator of ratio.
descriptionattributeDescription of the activity to be performed, in the form of an
archetyped structure.
descriptionattributeDescription of the activity, in the form of an archetyped structure.
descriptionattributeReason for committal.
descriptionrelationDescription and lifecycle information of the resource.
detailsrelationDetails of all parts of resource description that are natural language-dependent,
keyed by language code.
diffoperationDifference of two quantities.
diffoperationDifference of two temporal quantities.
diffoperationDifference of two temporal quantities.
directorypackageThe rm.common.directory package provides a simple abstraction of a versioned
folder structure.
directoryattributeOptional directory structure for this EHR.
directory_class_diag (rm)class diagram
directory_cvclass view
directory_dvdeployment view
disallowedattributeConstant to indicate disallowed presence of something.
domain_conceptoperationName of the concept represented by this archetype, including specialisation, e.g.
Biochemistry_result-cholesterol .
durationattributeDuration of the entire History; either corresponds to the duration of all the events,
and/or the duration represented by the summary, if it exists.
DV_ABSOLUTE_QUANTITYclassAbstract class defining the concept of quantified entities whose values are absolute with
respect to an origin. Dates and Times are the main example.
DV_ABSOLUTE_QUANTITYartifact
DV_AMOUNTclassAbstract class defining the concept of relative quantified amounts'. For relative quantities,
the +' and -' operators are defined (unlike descendants of DV_ABSOLUTE_QUANTITY,
such as the date/time types).
DV_AMOUNTartifact
DV_BOOLEANclassItems which are truly boolean data, such as true/false or yes/no answers.
For such data, it is important to devise the meanings (usually questions in subjective data)
carefully, so that the only allowed results are in fact true or false.
The DV_BOOLEAN class should not be used as a replacement for naively modelled
enumerated types such as male/female etc. Such values should be coded, and in
any case the enumeration often has more than two values.
DV_BOOLEANartifact
DV_CODED_TEXTclassA text item whose value must be the rubric from a controlled terminology, the
key (i.e. the code') of which is the defining_code attribute. In other words: a
DV_CODED_TEXT is a combination of a CODE_PHRASE (effectively a code) and
the rubric of that term, from a terminology service, in the language in which the
data was authored.

Since DV_CODED_TEXT is a subtype of DV_TEXT, it can be used in place of it,
effectively allowing the type DV_TEXT to mean a text item, which may option-
ally be coded .

If the intention is to represent a term code attached in some way to a fragment of
plain text, DV_CODED_TEXT should not be used; instead use a DV_TEXT and a
TERM_MAPPING to a CODE_PHRASE.
DV_CODED_TEXTartifact
DV_COUNTclassCountable quantities.
Used for countable types such as pregnancies and steps (taken by a physiotherapy
patient), number of cigarettes smoked in a day.
Not to be used for amounts of physical entities (which all have units)
DV_COUNTartifact
DV_DATEclassRepresents an absolute point in time, as measured on the Gregorian calendar, and
specified only to the day. Semantics defined by ISO 8601.
Used for recording dates in real world time. The partial form is used for
approximate birth dates, dates of death, etc.
DV_DATEartifact
DV_DATE_TIMEclassRepresents an absolute point in time, specified to the second. Semantics defined
by ISO 8601.
Used for recording a precise point in real world time, and for approximate time
stamps, e.g. the origin of a HISTORY in an OBSERVATION which is only partially
known.
DV_DATE_TIMEartifact
DV_DURATIONclassRepresents a period of time with respect to a notional point in time, which is not
specified. A sign may be used to indicate the duration is backwards in time
rather than forwards.

NOTE: a deviation from ISO8601 is supported, allowing the W' designator to
be mixed with other designators. See assumed types section in the Support IM.

Used for recording the duration of something in the real world, particularly when
there is a need a) to represent the duration in customary format, i.e. days, hours,
minutes etc, and b) if it will be used in computational operations with date/time
quantities, i.e. additions, subtractions etc.
Durations cannot be used to represent points in time, or intervals of time.
DV_DURATIONartifact
DV_EHR_URIclassA DV_EHR_URI is a DV_URI which has the scheme name ehr , and which can
only reference elements in EHRs.
Used to reference elements in an EHR, which may be the current one, or another.
DV_EHR_URIartifact
DV_ENCAPSULATEDartifact
DV_ENCAPSULATEDclassAbstract class defining the common meta-data of all types of encapsulated data.
DV_GENERAL_TIME_SPECIFICATIONclassSpecifies points in time in a general syntax. Based on the HL7v3 GTS data type.
DV_GENERAL_TIME_SPECIFICATIONartifact
DV_IDENTIFIERclassType for representing identifiers of real-world entities. Typical identifiers include
drivers licence number, social security number, veterans affairs number, prescription id,
order id, and so on.

DV_IDENTIFIER is used to represent any identifier of a real thing, issued by
some authority or agency.

DV_IDENTIFIER is not used to express identifiers generated by the infrastructure to
refer to information items; the types OBJECT_ID and OBJECT_REF and subtypes are
defined for this purpose.
DV_IDENTIFIERartifact
DV_INTERVALclassGeneric class defining an interval (i.e. range) of a comparable type. An interval is
a contiguous subrange of a comparable base type. Used to define intervals of dates,
times, quantities (whose units match) and so on.
The type parameter, T, must be a descendant of the type DV_ORDERED, which is
necessary (but not sufficient) for instances to be compared (strictly_comparable is
also needed).
Without the DV_INTERVAL class, quite a few more DV_ classes would be needed to
express logical intervals, namely interval versions of all the date/time classes, and
of quantity classes. Further, it allows the semantics of intervals to be stated in one
place unequivocally, including the conditions for strict comparison.

The basic semantics are derived from the class INTERVAL<T>, described in the
support RM.
DV_INTERVALartifact
DV_MULTIMEDIAartifact
DV_MULTIMEDIAclassA specialisation of DV_ENCAPSULATED for audiovisual and biosignal types.
Includes further metadata relating to multimedia types which are not applicable to
other subtypes of DV_ENCAPSULATED.
DV_ORDEREDclassAbstract class defining the concept of ordered values, which includes ordinals as well as
true quantities. It defines the functions <' and is_strictly_comparable_to, the latter of
which must evaluate to True for instances being compared with the <' function, or
used as limits in the DV_INTERVAL<T> class.

Data value types which are to be used as limits in the DV_INTERVAL<T> class must
inherit from this class, and implement the function is_strictly_comparable_to to ensure
that instances compare meaningfully. For example, instances of DV_QUANTITY can only
be compared if they measure the same kind of physical quantity.
DV_ORDEREDartifact
DV_ORDINALclassModels rankings and scores, e.g. pain, Apgar values, etc, where there is a) implied ordering,
b) no implication that the distance between each value is constant, and c) the total number
of values is finite. Note that although the term ordinal' in mathematics means natural
numbers only, here any integer is allowed, since negative and zero values are often used
by medical professionals for values around a neutral point. Examples of sets of ordinal values:
-3, -2, -1, 0, 1, 2, 3 -- reflex response values
0, 1, 2 -- Apgar values

This class is used for recording any clinical datum which is customarily recorded using
symbolic values. Example: the results on a urinalysis strip, e.g. {neg, trace, +, ++, +++} are
used for leucocytes, protein, nitrites etc; for non-haemolysed blood {neg, trace, moderate};
for haemolysed blood small, moderate, large}.
DV_ORDINALartifact
DV_PARAGRAPHclassA logical composite text value consisting of a series of DV_TEXTs, i.e. plain text
(optionally coded) potentially with simple formatting, to form a larger tract of
prose, which may be interpreted for display purposes as a paragraph.

DV_PARAGRAPH is the standard way for constructing longer text items in summaries,
reports and so on.
DV_PARAGRAPHartifact
DV_PARSABLEartifact
DV_PARSABLEclassEncapsulated data expressed as a parsable String. The internal model of the
data item is not described in the openEHR model in common with other encapsu-
lated types, but in this case, the form of the data is assumed to be plaintext, rather
than compressed or other types of large binary data.
DV_PERIODIC_TIME_SPECIFICATIONclassSpecifies periodic points in time, linked to the calendar (phase-linked), or a real
world repeating event, such as breakfast (event-linked). Based on the HL7v3
data types PIVL<T> and EIVL<T>.
Used in therapeutic prescriptions, expressed as INSTRUCTIONs in the openEHR
model.
DV_PERIODIC_TIME_SPECIFICATIONartifact
DV_PROPORTIONoperationClass constructor
DV_PROPORTIONoperationcopy constructor
DV_PROPORTIONclassModels a ratio of values, i.e. where the numerator and denominator are both pure
numbers.
Used for recording titers (e.g. 1:128), concentration ratios, e.g. Na:K (unitary
denominator), albumin:creatinine ratio, and percentages, e.g. red cell distirbution
width (RDW).

Should not be used to represent things like blood pressure which are often written
using a /' character, giving the misleading impression that the item is a ratio,
when in fact it is a structured value. E.g. visual acuity 6/24 is not a ratio.
Should not be used for formulations.
DV_PROPORTIONartifact
DV_QUANTIFIEDclassAbstract class defining the concept of true quantified values, i.e. values which
are not only ordered, but which have a precise magnitude.
DV_QUANTIFIEDartifact
DV_QUANTITYclassQuantitified type representing scientific quantities, i.e. quantities expressed as a
magnitude and units. Units were inspired by the Unified Code for Units of Measure
(UCUM), developed by Gunther Schadow and Clement J. McDonald of The Regenstrief
Institute.
Can also be used for time durations, where it is more convenient to treat these as
simply a number of seconds rather than days, months, years.
DV_QUANTITYartifact
DV_STATEclassFor representing state values which obey a defined state machine, such as a variable
representing the states of an instruction or care process.

DV_STATE is expressed as a String but its values are driven by archetype-defined
state machines. This provides a powerful way of capturing stateful complex processes
in simple data.
DV_STATEartifact
DV_TEMPORALclassSpecialised temporal variant of DV_ABSOLUTE_QUANTITY whose diff type is DV_DURATION.
DV_TEMPORALartifact
DV_TEXTclassA text item, which may contain any amount of legal characters arranged as e.g. words,
sentences etc (i.e. one DV_TEXT may be more than one word). Visual formatting and
hyperlinks may be included.

A DV_TEXT can be coded by adding mappings to it.
DV_TEXTartifact
DV_TIMEclassRepresents an absolute point in time from an origin usually interpreted as
meaning the start of the current day, specified to the second. Semantics
defined by ISO 8601.
Used for recording real world times, rather than scientifically measured fine
amounts of time. The partial form is used for approximate times of events and
substance administrations.
DV_TIMEartifact
DV_TIME_SPECIFICATIONclassThis is an abstract class of which all timing specifications are specialisations.
Specifies points in time, possibly linked to the calendar, or a real world repeating
event, such as breakfast .
DV_TIME_SPECIFICATIONartifact
DV_URIclassA reference to an object which conforms to the Universal Resource Identifier (URI) standard, as defined by W3C RFC 2936.
See "Universal Resource Identifiers in WWW" by Tim Berners-Lee at http://www.ietf.org/rfc/rfc2396.txt.
This is a World-Wide Web RFC for global identification of resources.
See http://www.w3.org/Addressing for a starting point on URIs.
See http://www.ietf.org/rfc/rfc2806.txt for new URI types like telephone, fax and modem numbers.
DV_URIartifact