E

Name	Kind	Description
EHR	class	The EHR object is the root object and access point of an EHR for a subject of care.
EHR	artifact
ehr	package	The EHR IM defines the containment and context semantics of the concepts EHR, COMPOSITION, SECTION, and ENTRY. These classes are the major coarse-grained components of the EHR, and correspond directly to the classes of the same names in CEN EN13606:2005 and fairly closely to the levels of the same names in the HL7 Clinical Document Architecture (CDA) release 2.0.
ehr	package	The EHR service model defines the coarse-grained interface to electronic health record service. The level of granularity is openEHR Contributions and Compositions, i.e. a version-control / change-set interface. Part of the model defines the semantics of server-side querying, i.e. queries which cause large amounts of data to be processed, generally returning small aggregated answers, such as averages, or sets of ids of patients matching a particular criterion.
ehr_access	attribute	Reference to EHR_ACCESS object for this EHR.
EHR_ACCESS	class	EHR-wide access contol object. All access decisions to data in the EHR must be made in accordance with the policies and rules in this object.
EHR_ACCESS	artifact
ehr_class_diag (rm)	class diagram	Class diagram for the openEHR rm.ehr package.
ehr_cv	class view	Class view for rm.ehr package.
ehr_dv	deployment view
ehr_extract	package	The EHR Extract IM defines how an EHR extract is built from COMPOSITIONs, demographic, and access control information from the EHR. A number of Extract variations are supported, including full openEHR , a simplified form for integration with CEN EN13606, and an openEHR/openEHR synchronisation Extract.
ehr_id	attribute	The id of this EHR.
ehr_status	attribute	Reference to EHR_STATUS object for this EHR.
EHR_STATUS	class	Single object per EHR giving various EHR-wide information.
EHR_STATUS	artifact
ELEMENT	class	The leaf variant of ITEM, to which a DATA_VALUE instance is attached.
ELEMENT	artifact
element_at_path	operation	Return the leaf element at the path a_path'.
encapsulatd_class_diag	class diagram	Classes in the rm.data_types.encapsulated package. Includes DV_ENCAPSULATED, DV_MULTIMEDIA, DV_PARSABLE.
encapsulated	package	The data_types.encapsulated package contains classes representing data values whose internal structure is defined outside the EHR model, such as multimedia and parsable data.
encapsulated_deploy	deployment diagram	Shows testing module layout for rm.data_types.encapsulated package.
encapsulated_dv	deployment view
encapsulated_test	artifact	A module for testing the rm.datatypes.encapsulated package.
encoding	relation	Name of character encoding scheme in which this value is encoded. Coded from openEHR Code Set character sets . Unicode is the default assumption in openEHR, with UTF-8 being the assumed encoding. This attribute allows for variations from these assumptions.
encoding	attribute	Name of character set in which text values in this Entry are encoded. Coded from openEHR Code Set character sets .
encpsulated_cv	class view
end_time	attribute	Optional end time of the clinical session.
entry	package	The rm.composition.content.entry package. All information which is created in the openEHR health record is expressed as an instance of a class in the entry package, containing the ENTRY class and a number of descendants. An ENTRY instance is logically a single clinical statement', and may be a single short narrative phrase, but may also contain a significant amount of data, e.g. an entire microbiology result, a psychiatric examination, a complex prescription. In terms of actual content, the Entry classes are the most important in the openEHR EHR Information Model, since they define the semantics of all the hard' information in the record. They are intended to be archetyped, and in fact, archetypes for Entries make up the vast majority of important clinical archetypes defined.
ENTRY	class	The abstract parent of all ENTRY subtypes. An ENTRY is the root of a logical item of hard clinical information created in the clinical statement context, within a clinical session. There can be numerous such contexts in a clinical session. Observations and other Entry types only ever document information captured/created in the event documented by the enclosing Composition. An ENTRY is also the minimal unit of information any query should return, since a whole ENTRY (including subparts) records spatial structure, timing information, and contextual information, as well as the subject and generator of the information.
ENTRY	artifact
entry_class_diag (rm)	class diagram	Class diagram for the rm.composition.content.entry package. Includes abstract ENTRY class and the primary entry classes OBSERVATION, EVALUATION, INSTRUCTION, ACTION.
entry_cv	class view
entry_dv	deployment view
EVALUATION	class	Entry type for evaluation statements. Used for all kinds of statements which evaluate other information, such as interpretations of obvservations, diagnoses, differential diagnoses, hypotheses, risk assessments, goals and plans. Should not be used for actionable statements such as medication orders - these are represented using the INSTRUCTION type.
EVALUATION	artifact
EVENT	class	Defines the abstract notion of a single event in a series. This class is generic, allowing types to be generated which are locked to particular spatial types, such as EVENT<ITEM_LIST>. Subtypes express point or intveral data.
EVENT	artifact
event	attribute	Event which fires this transition.
event_alignment	operation	Event alignment extracted from value.
event_alignment	operation	Event alignment extracted from value.
event_alignment	operation	Indicates what real-world event the specification is aligned to if any. Extracted from the value' attribute.
EVENT_CONTEXT	class	Documents the context information of a healthcare event involving the subject of care and the health system. The context information recorded here are independent of the attributes recorded in the version audit, which document the system interaction context, i.e. the context of a user interacting with the health record system. Healthcare events include patient contacts, and any other business activity, such as pathology investigations which take place on behalf of the patient.
events	relation	The events in the series.
excludes	attribute	List of constraints defining other archetypes that cannot be included at this point.
existence	attribute	Constraint on every attribute, regardless of whether it is singular or of a container type, which indicates whether its target object exists or not (i.e. is mandatory or not).
existence	attribute
expiry_time	attribute	Optional expiry date/time to assist determination of when an Instruction can be assumed to have expired. This helps prevent false listing of Instructions as Active when they clearly must have been terminated in some way or other.
EXPR_BINARY_OPERATOR	class
EXPR_BINARY_OPERATOR	artifact
EXPR_ITEM	class
EXPR_ITEM	artifact
EXPR_LEAF	class
EXPR_LEAF	artifact
EXPR_OPERATOR	class
EXPR_OPERATOR	artifact
EXPR_UNARY_OPERATOR	class
EXPR_UNARY_OPERATOR	artifact
expression	relation	Root of expression tree.
extension	operation	Optional local identifier of the object within the context of the root identifier. Returns the part to the right of the first ::' separator if any, or else any empty String.
EXTERNAL_ENVIRONMENT_ACCESS	class	A mixin class providing access to services in the external environment.
external_ref	relation	Optional reference to more detailed demographic or identification information for this party, in an external system.