View:Hide Browser | Browser on the left | Browser on the right
Index: | A | B | C | D | E | F | G | H | I | K | L | M | N | O | P | Q | R | S | T | U | V | W | Y | Symbol | Unnamed | 

Dictionary

 
A
access_control   Package  from Package security     
ACCESS_CONTROL_SETTINGS   Class  from Package access_control     
ACCESS_GROUP_REF   Class  from Package identification  Reference to access group in an access control service.   
Accuracy_is_percent_validity   Constraint  from Package quantity     
Accuracy_validity   Constraint  from Package quantity     
ACTION   Class  from Package entry  Used to record a clinical action that has been performed, which may have been ad hoc, or due to the execution of an Activity in an Instruction workflow. Every Action corresponds to a careflow step of some kind or another.   
Action_archteype_id_valid   Constraint  from Package ehr     
Action_valid   Constraint  from Package basic     
activities   AssociationEnd  from Association <unnamed>     
Activities_valid   Constraint  from Package ehr     
ACTIVITY   Class  from Package entry     
Activity_path_valid   Constraint  from Package ehr     
ACTOR   Class  from Package demographic  Ancestor of all real-world types, including people and organisations. An actor is any real-world entity capable of taking on a role.   
ADDRESS   Class  from Package demographic  Address of contact, which may be electronic or geographic.   
addresses   AssociationEnd  from Association <unnamed>     
Addresses_exists   Constraint  from Package demographic     
ADMIN_ENTRY   Class  from Package entry  Entry subtype for administrative information, i.e. information about setting up the clinical process, but not itself clinically relevant. Archetypes will define contained information.   
AGENT   Class  from Package demographic  Generic concept of any kind of agent, including devices, software systems, but not humans or organisations.   
Aggregate   Class  from Package assumed_types  Abstract parent of of the aggregate types List, Set, Array and Hash.   
all_version_ids_valid   Constraint  from Package change_control     
all_versions_valid   Constraint  from Package change_control     
alternatives_exists   Constraint  from Package constraint_model     
am   Package      
am.archetype   Class Diagram      
am.archetype.assertion   Class Diagram      
am.archetype.constraint_model   Class Diagram      
am.archetype.constraint_model. <...>   Class Diagram      
am.archetype.ontology   Class Diagram      
am.openehr_profile   Class Diagram      
am.openehr_profile.data_types. <...>   Class Diagram      
am.openehr_profile.data_types. <...>   Class Diagram      
am.openehr_profile.data_types. <...>   Class Diagram      
am.packages   Class Diagram      
am.packages_with_classes   Class Diagram      
Any   Class  from Package TypesUML     
Any_allowed_validity   Constraint  from Package text     
ARCHETYPE   Class  from Package archetype  Archetype equivalent to ARCHETYPED class in Common reference model. Defines semantics of identfication, lifecycle, versioning, composition and specialisation.   
archetype   Package  from Package am  The model of an archetype is straightforward at an abstract level, mimicking the structure of an archetype document as defined in the openEHR Archetype Definition Language (ADL) document. An archetype is a modelled as a particular kind of AUTHORED_RESOURCE, and as such, includes descriptive meta-data, language information and revision history. The ARCHETYPE class adds identifying information, a definition - expressed in terms of constraints on instances of an object model, and an ontology. The archetype definition, the ‘main’ part of an archetype, is an instance of a C_COMPLEX_OBJECT, which is to say, the root of the constraint structure of an archetype always takes the form of a constraint on a non-primitive object type. The last section of an archetype, the ontology, is represented by its own class, and is what allows the archetypes to be natural language-and terminology-neutral. A utility class, VALIDITY_KIND is also included in the Archetype package. This class contains one integer attribute and three constant definitions, and is intended to be used as the type of any attribute in this constraint model whose value is logically ‘mandatory’, ‘optional’, or ‘disallowed’. It is used in this model in the classes C_Date, C_Time and C_Date_Time.   
ARCHETYPE_CONSTRAINT   Class  from Package constraint_model  Archetype equivalent to LOCATABLE class in openEHR Common reference model. Defines common constraints for any inheritor of LOCATABLE in any reference model.   
archetype_details   AssociationEnd  from Association <unnamed>     
ARCHETYPE_ID   Class  from Package identification  Identifier for archetypes.   
archetype_id_valid   Constraint  from Package archetyped     
archetype_id_validity   Constraint  from Package archetype     
ARCHETYPE_INTERNAL_REF   Class  from Package constraint_model  A constraint defined by proxy, using a reference to an object constraint defined elsewhere in the same archetype. Note that since this object refers to another node, there are two objects with available occurrences values. The local occurrences value on an ARCHETYPE_INTERNAL_REF should always be used; when setting this from a serialised form, if no occurrences is mentioned, the target occurrences should be used (not the standard default of {1..1}); otherwise the locally specified occurrences should be used as normal. When serialising out, if the occurrences is the same as that of the target, it can be left out.   
Archetype_node_id_valid   Constraint  from Package ehr     
Archetype_node_id_valid   Constraint  from Package archetyped     
ARCHETYPE_ONTOLOGY   Class  from Package ontology  Local ontology of an archetype.   
Archetype_root_point   Constraint  from Package entry     
ARCHETYPE_SLOT   Class  from Package constraint_model  Constraint describing a `slot' where another archetype can occur.   
ARCHETYPE_TERM   Class  from Package ontology  Representation of any coded entity (term or constraint) in the archetype ontology.   
ARCHETYPED   Class  from Package archetyped  Archetypes act as the configuration basis for the particular structures of instances defined by the reference model. To enable archetypes to be used to create valid data, key classes in the reference model act as “root” points for archetyping; accordingly, these classes have the archetype_details attribute set. An instance of the class ARCHETYPED contains the relevant archetype identification information, allowing generating archetypes to be matched up with data instances   
archetyped   Package  from Package common     
Archetyped_valid   Constraint  from Package archetyped     
Array   Class  from Package assumed_types  Container whose storage is assumed to be contiguous   
ASSERTION   Class  from Package assertion  Structural model of a typed first order predicate logic assertion, in the form of an expression tree, including optional variable definitions.   
assertion   Package  from Package archetype  Assertions are expressed in archetypes in typed first-order predicate logic (FOL). They are used in two places: to express archetype slot constraints, and to express invariants in complex object constraints. In both of these places, their role is to constrain something inside the archetype. Constraints on external resources such as terminologies are expressed in the constraint binding part of the archetype ontology, described in the Ontology Package The concrete syntax of assertion statements in archetypes is designed to be compatible with the OMG Object Constraint Language (OCL). Archetype assertions are essentially statements that contain the following elements: • variables, which are attribute names, or ADL paths terminating in attribute names (i.e. equivalent of referencing class feature in a programming language); • manifest constants of any primitive type, plus date/time types • arithmetic operators: +, *, -, /, ^ (exponent) • relational operators: >, <, >=, <=, =, !=, matches • Boolean operators: not, and, or, xor • quantifiers applied to container variables: for_all, exists The package described here is currently designed to allow the representation of a general-purpose binary expression tree, as would be generated by a parser. This may be replaced in the future by a more specific model, if needed.    
ASSERTION_VARIABLE   Class  from Package assertion  Definition of a named variable used in an assertion expression. Note: the definition of named variables may change; still under development in ADL2.   
assigner_valid   Constraint  from Package basic     
assumed_library_types   Class Diagram      
assumed_types   Class Diagram      
assumed_types   Package   This package provides models for common generic and container types not directly supported in UML.   
assumed_types_date_time   Class Diagram      
assumed_types_date_time_summar <...>   Class Diagram      
assumed_types_primitive_detail <...>   Class Diagram      
assumed_types_primitive_outlin <...>   Class Diagram      
Assumed_value_valid   Constraint  from Package constraint_model     
Assumed_value_valid   Constraint  from Package constraint_model     
Assumed_value_valid   Constraint  from Package constraint_model     
attestations   AssociationEnd  from Association <unnamed>     
attributes   AssociationEnd  from Association <unnamed>     
attributes_valid   Constraint  from Package constraint_model     
audit   AssociationEnd  from Association <unnamed>     
Audit_valid   Constraint  from Package generic     
audit_valid   Constraint  from Package generic     
audit_validmed2   Constraint  from Package change_control     
audits   AssociationEnd  from Association <unnamed>     
Author_valid   Constraint  from Package change_control     
AUTHORED_RESOURCE   Class  from Package resource  Abstract idea of an online resource created by a human author.   
 
 
B
basic   Package  from Package data_types     
basic   Package  from Package data_types     
BASIC_DEFINITIONS   Class  from Package definition  Defines globally-used constant values.   
binary_consistency   Constraint  from Package primitive     
BINARY_QUERY_NODE   Class  from Package sm     
Branch_number_valid   Constraint  from Package identification     
Branch_validity   Constraint  from Package identification     
Branch_version_valid   Constraint  from Package identification     
 
 
C
C_ATTRIBUTE   Class  from Package constraint_model  Abstract model of constraint on any kind of attribute node.   
C_BOOLEAN   Class  from Package primitive  Constraint on instances of Boolean . Both attributes cannot be set to False, since this would mean that the Boolean value being constrained cannot be True or False.   
C_CODE_PHRASE   Class  from Package text  Express constraints on instances of CODE_PHRASE. The terminology_id attribute may be specified on its own to indicate any term from a specified terminology; the code_list attribute may be used to limit the codes to a specific list.   
C_COMPLEX_OBJECT   Class  from Package constraint_model  Constraint on complex objects, i.e. any object that consists of other object constraints.   
C_DATE   Class  from Package primitive  ISO 8601-compatible constraint on instances of Date in the form either of a set of validity values, or an actual date range. There is no validity flag for ‘year’, since it must always be by definition mandatory in order to have a sensible date at all. Syntax expressions of instances of this class include “YYYY-??-??” (date with optional month and day).   
C_DATE_TIME   Class  from Package primitive  ISO 8601-compatible constraint on instances of Date_Time. There is no validity flag for ‘year’, since it must always be by definition mandatory in order to have a sensible date/time at all. Syntax expressions of instances of this class include “YYYY-MM-DDT??:??:??” (date/time ith optional time) and “YYYY-MMDDTHH: MM:xx” (date/time, seconds not allowed).   
C_DEFINED_OBJECT   Class  from Package constraint_model  Abstract parent type of C_OBJECT subtypes that are defined by value, i.e. whosedefinitions are actually in the archetype rather than being by reference.   
C_DOMAIN_TYPE   Class  from Package constraint_model  Abstract parent type of domain-specific constrainer types, to be defined in external packages.   
C_DURATION   Class  from Package primitive  ISO 8601-compatible constraint on instances of Duration. In ISO 8601 terms, constraints might are of the form “PWD” (weeks and/or days), “PDTHMS” (days, hours, minutes, seconds) and so on. In official ISO 8601:2004, the ‘W’ (week) designator cannot be mixed in; allowing it is an openEHR-wide exception.   
C_DV_ORDINAL   Class  from Package quantity  Class specifying constraints on instances of DV_ORDINAL. Custom constrainer type for instances of DV_ORDINAL.   
C_DV_QUANTITY   Class  from Package quantity  Constrain instances of DV_QUANTITY.   
C_DV_STATE   Class  from Package basic  Constrainer type for DV_STATE instances. The attribute c_value defines a state/event table which constrains the allowed values of the attribute value in a DV_STATE instance, as well as the order of transitions between values.   
C_INTEGER   Class  from Package primitive  Constraint on instances of Integer .   
C_MULTIPLE_ATTRIBUTE   Class  from Package constraint_model  Abstract model of constraint on any kind of attribute node.   
C_OBJECT   Class  from Package constraint_model  Abstract model of constraint on any kind of object node.   
C_PRIMITIVE   Class  from Package primitive     
C_PRIMITIVE_OBJECT   Class  from Package constraint_model  Constraint on a primitive type.   
C_QUANTITY_ITEM   Class  from Package quantity  Constrain instances of DV_QUANTITY.   
C_REAL   Class  from Package primitive  Constraint on instances of Real .   
C_REFERENCE_OBJECT   Class  from Package constraint_model  Abstract parent type of C_OBJECT subtypes that are defined by reference.   
C_SINGLE_ATTRIBUTE   Class  from Package constraint_model  Concrete model of constraint on a single-valued attribute node. The meaning of the inherited children attribute is that they are alternatives.   
C_STRING   Class  from Package primitive  Constraint on instances of STRING .   
C_TIME   Class  from Package primitive  ISO 8601-compatible constraint on instances of Time. There is no validity flag for ‘hour’, since it must always be by definition mandatory in order to have a sensible time at all. Syntax xpressions of instances of this class include “HH:??:xx” (time with optional minutes and seconds not allowed).   
c_value_exists   Constraint  from Package basic     
capabilities   AssociationEnd  from Association <unnamed>     
Capabilities_valid   Constraint  from Package demographic     
CAPABILITY   Class  from Package demographic  Capability of a role, such as “ehr modifier”, “health care provider”. Capability should be backed up by credentials.   
CARDINALITY   Class  from Package constraint_model  Expresses constraints on the cardinality of container objects which are the values of multiply-valued attributes, including uniqueness and ordering, providing the means to state that a container acts like a logical list, set or bag. The cardinality cannot contradict the cardinality of the corresponding attribute within the relevant reference model.   
cardinality   AssociationEnd  from Association <unnamed>     
cardinality_validity   Constraint  from Package constraint_model     
CARE_ENTRY   Class  from Package entry  The abstract parent of all clinical ENTRY subtypes. A CARE_ENTRY defines protocol and guideline attributes for all clinical Entry subtypes.   
Category_validity   Constraint  from Package composition     
change_control   Package  from Package common  In various openEHR reference models, the semantics of formal change control are required. There are two architectural aspects of managing changes to data. The first is the concept of a complex information object, being versioned in time, meaning that its creation and all subsequent modifications cause new “versions” to be created, rather than literally overwriting the existing data. Each version includes an audit trail, typically containing the dentity of a user, the date/time of the change, and a reason for the change. The second aspect recognises that repositories are made up of complex information objects, and that changes are not in fact just made to individual objects, but to the respository itself. Any change by a user may change more than one versioned object in the repository, and the set of such changes - a “change-set” - constitutes the logical unit of change to the repository, taking it from one valid state to the next.   
Change_type_valid   Constraint  from Package generic     
Charset_valid   Constraint  from Package encapsulated     
children   AssociationEnd  from Association <unnamed>     
children_validity   Constraint  from Package constraint_model     
CLUSTER   Class  from Package representation  The grouping variant of ITEM, which may contain further instances of ITEM, in an ordered list.   
CODE_PHRASE   Class  from Package text  A fully coordinated (i.e. all “coordination” has been performed) term from a terminology service (as distinct from a particular terminology).   
CODE_SET_ACCESS   Class  from Package terminology  Defines an object providing proxy access to a code_set.   
Code_string_exists   Constraint  from Package text     
code_valid   Constraint  from Package ontology     
Column_names_valid   Constraint  from Package item_structure     
commit_audit   AssociationEnd  from Association <unnamed>     
Commit_audit_valid   Constraint  from Package change_control     
committer   AssociationEnd  from Association <unnamed>     
Committer_valid   Constraint  from Package generic     
common   Package  from Package rm     
commutative   Constraint  from Package assumed_types     
commutative   Constraint  from Package assumed_types     
completeness   Constraint  from Package support     
composer   AssociationEnd  from Association <unnamed>     
composer   AssociationEnd  from Association <unnamed>     
Composer_valid   Constraint  from Package composition     
COMPOSITION   Class  from Package composition  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.   
composition   Package  from Package rm  The Composition is the primary ‘data container’ in the openEHR EHR and is the root point of clinical content. Instances of the Composition class can be considered as self-standing data aggregations, or documents in a document-oriented system (similar to HL7 CDA Documents). The key information in a COMPOSITION is found in its content, context, and composer attributes. The majority of the use of paths in openEHR is likely to be within Compositions.   
Compositions_valid   Constraint  from Package ehr     
Compression_algorithm_validity   Constraint  from Package encapsulated     
concept_code_valid   Constraint  from Package ontology     
concept_valid   Constraint  from Package archetype     
Consistency   Constraint  from Package constraint_model     
consistency   Constraint  from Package constraint_model     
consistency   Constraint  from Package primitive     
consistency   Constraint  from Package primitive     
consistency   Constraint  from Package primitive     
consistent_with_semi_strict   Constraint  from Package assumed_types     
constraint_bindings_exists   Constraint  from Package ontology     
constraint_codes_exists   Constraint  from Package ontology      
constraint_model   Package  from Package archetype  The following statements summarise the main features of this package. Any archetype definition is an instance of a C_COMPLEX_OBJECT, which can be thought of as expressing constraints on a object that is of some particular type (recorded in the attribute rm_type_name ) in a reference model, and which is larger than a simple instance of a primitive type such as String or Integer. A C_COMPLEX_OBJECT consists of attributes of type C_ATTRIBUTE, which are constraints on the attributes (i.e. any property, including relationships) of the reference model type. Accordingly, each C_ATTRIBUTE records the name of the constrained attribute (in rm_attr_name), the existence and cardinality expressed by the constraint (depending on whether the attribute it constrains is a multiple or single relationship), and the constraint on the object to which this C_ATTRIBUTE refers via its children attribute (according to its reference model) in the form of further C_OBJECTs. The key subtypes of C_OBJECT, are C_COMPLEX_OBJECT (described above) C_PRIMITIVE_OBJECT (constraints on instances of primitive types such as String, Integer, Boolean and Date). The other subtypes of C_OBJECT, namely, ARCHETYPE_SLOT, ARCHETYPE_INTERNAL_REF and CONSTRAINT_REF are used to express, respectively, a `slot' where further archetypes can be used to continue describing constraints; a reference to a part of the current archetype that expresses exactly the same constraints needed at another point; and a reference to a constraint on a constraint defined in the archetype ontology, which in turn points to an external knowledge resource, such as a terminology. All nodes in an archetype constraint structure are instances of the supertype ARCHETYPE_CONSTRAINT, which provides a number of important common features to all nodes.    
CONSTRAINT_REF   Class  from Package constraint_model  Reference to a constraint described in the same archetype, but outside the main constraint structure. This is used to refer to constraints expressed in terms of external resources, such as constraints on terminology value sets.   
CONTACT   Class  from Package demographic  Description of a means of contact of a party. Actual structure is archetyped.   
contacts   AssociationEnd  from Association <unnamed>     
Contacts_valid   Constraint  from Package demographic     
content   AssociationEnd  from Association <unnamed>     
content   Package  from Package composition     
CONTENT_ITEM   Class  from Package content  Abstract ancestor of all concrete content types.   
Content_valid   Constraint  from Package composition     
context   AssociationEnd  from Association <unnamed>     
CONTRIBUTION   Class  from Package change_control  Documents a contribution of one or more versions added to a change-controlled repository.   
Contribution_valid   Constraint  from Package change_control     
Contributions_valid   Constraint  from Package ehr     
copyright_valid   Constraint  from Package change_control     
Create_audit_valid   Constraint  from Package change_control     
Create_audit_valid   Constraint  from Package change_control     
creating_system_id   Constraint  from Package identification     
Credentials_exists   Constraint  from Package demographic     
Current_revision_valid   Constraint  from Package change_control     
Current_state_valid   Constraint  from Package ehr     
 
 
D
data   AssociationEnd  from Association <unnamed>     
data   AssociationEnd  from Association <unnamed>     
Data_exists   Constraint  from Package item_structure     
DATA_STRUCTURE   Class  from Package data_structures     
data_structures   Package  from Package rm     
data_types   Package  from Package rm     
data_types   Package  from Package openehr_profile  This data type specification constitutes the lowest level of technical specification of openEHR, and describes a set of types suitable for use in clinical and related information structures. In order for such types to exist, a set of primitive types is assumed, namely Integer, Real, Boolean, Character, String, List, Set, and Array. These have standard definitions in the OMG object model used in UML, OCL, and are available in almost all type systems. The exact assumptions are described in the openEHR Support Reference Model. A number of symbolic definitions (similar to constants in programming) are also described in the Support RM. The data types described here are named with the class prefix “DV_”, and inherit from the class DATA_VALUE. They have two distinct uses in reference models. Firstly, they may be used as “data values” in reference model structures wherever the DATA_VALUE class appears, for example, in the EHR Reference Model via the ELEMENT.value attribute. Additionally, specific subtypes of the data types described here can also be used as attribute types in other classes in reference models, such as date/times, coded terms and so on. The difference is that in the former case, only subtypes of DATA_VALUE may be used, whilst in the latter case, other types may be used as well, from the assumed set of basic types.   
Data_valid   Constraint  from Package ehr     
Data_valid   Constraint  from Package ehr     
Data_valid   Constraint  from Package ehr     
Data_valid   Constraint  from Package change_control     
data_valid   Constraint  from Package change_control     
DATA_VALUE   Class  from Package basic  Serves as a common ancestor of all data value types in openEHR models.   
date_time   Package  from Package quantity  The data_types.quantity.date_time package includes three absolute date/time concepts: DV_DATE, DV_TIME, DV_DATE_TIME, a relative concept: DV_DURATION, and the concept of partial dates and times, via DV_PARTIAL_DATE, DV_PARTIAL_TIME.   
date_valid   Constraint  from Package date_time     
Day_known_validity   Constraint  from Package date_time     
Day_valid   Constraint  from Package assumed_types     
day_validity_disallowed    Constraint  from Package primitive     
day_validity_optional    Constraint  from Package primitive     
days_vlid   Constraint  from Package assumed_types     
de_morgan   Constraint  from Package assumed_types     
de_morgan   Constraint  from Package assumed_types     
Default_value_consistency   Constraint  from Package primitive     
defining_code   AssociationEnd  from Association <unnamed>     
definition   AssociationEnd  from Association <unnamed>     
definition   Constraint  from Package assumed_types     
definition   Package  from Package support  The definition package describes symbolic definitions used by the openEHR models.   
Definition_exists   Constraint  from Package text     
definition_exists   Constraint  from Package archetype      
Definition_valid   Constraint  from Package assertion     
demographic   Package  from Package rm  This document describes the architecture of the openEHR Demographic Information Model. The semantics are drawn from previous work in GEHR, existing models in CEN 13606 and the HL7v3 RIM, and other work done in Australia. The intended audience includes: • Standards bodies producing health informatics standards; • Software development groups using openEHR; • Academic groups using openEHR; • The open source healthcare community; • Medical informaticians and clinicians intersted in health information; • Health data managers.   
Denominator_exists   Constraint  from Package quantity     
description   AssociationEnd  from Association <unnamed>     
description_exists   Constraint  from Package archetype      
Description_valid   Constraint  from Package ehr     
Description_valid   Constraint  from Package ehr     
Description_valid   Constraint  from Package change_control     
Description_valid   Constraint  from Package common     
details   AssociationEnd  from Association <unnamed>     
Details_exists   Constraint  from Package demographic     
Details_exists   Constraint  from Package demographic     
Details_valid   Constraint  from Package change_control     
directory   Package  from Package common  The directory package provides a simple abstraction of a versioned folder structure. The VERSIONED_FOLDER class is the binding of VERSIONED_OBJECT to FOLDER, i.e. it is a VERSIONED_OBJECT. This means that each of its versions is a FOLDER structure. It provides a means of versioning FOLDER structures over time, which is useful in the EHR, Demographics service or anywhere else where Folders are used to group things.   
Directory_valid   Constraint  from Package ehr     
Domain_concept_valided2   Constraint  from Package support     
DV_ABSOLUTE_QUANTITY   Class  from Package quantity  Abstract class defining the concept of quantified entities whose values are absolute with respect to an origin. Dates and Times are the main example.   
DV_AMOUNT   Class  from Package quantity  Abstract 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_BOOLEAN   Class  from Package basic  Items which are truly boolean data, such as true/false or yes/no answers.   
DV_CODED_TEXT   Class  from Package text  A 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.   
DV_COUNT   Class  from Package quantity  Countable quantities.   
DV_DATE   Class  from Package date_time  Represents an absolute point in time, as measured on the Gregorian calendar, and specified only to the day. Semantics defined by ISO 8601.   
DV_DATE_TIME   Class  from Package date_time  Represents an absolute point in time, specified to the second. Semantics defined by ISO 8601.   
DV_DURATION   Class  from Package date_time  

Represents 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 that a deviation from ISO8601 is supported, allowing the ‘W’ designator to

be mixed with other designators. See assumed types section in the Support IM.

   
DV_EHR_URI   Class  from Package uri  A DV_EHR_URI is a DV_URI which has the scheme name “ehr”, and which can only reference elements in EHRs   
DV_ENCAPSULATED   Class  from Package encapsulated  Abstract class defining the common meta-data of all types of encapsulated data.   
DV_GENERAL_TIME_SPECIFICATION   Class  from Package time_specification     
DV_IDENTIFIER   Class  from Package basic  Type for representing identifiers of real-world entities. Typical identifiers include drivers licence number, social security number, vertans affairs number, prescription id, order id, and so on.   
DV_INTERVAL   Class  from Package date_time  Generic class defining an interval (i.e. range) of a comparable type. An interval is a contiguous subrange of a comparable base type.   
DV_INTERVAL<DV_DATE_TIME>   Class  from Package quantity     
DV_MULTIMEDIA   Class  from Package encapsulated  A specialisation of DV_ENCAPSULATED for audiovisual and biosignal types. Includes further metadata relating to multimedia types which are not applicable t other subtypes of DV_ENCAPSULATED.   
DV_ORDERED   Class  from Package quantity  Abstract 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 class.   
DV_ORDINAL   Class  from Package quantity  Models 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 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 {neg, trace, small, moderate, large}.   
DV_PARAGRAPH   Class  from Package text  A 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_PARSABLE   Class  from Package encapsulated  Encapsulated data expressed as a parsable String. The internal model of the data item is not described in the openEHR model in common with other encapsulated 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_SPECIFICATION   Class  from Package time_specification     
DV_PROPORTION   Class  from Package quantity  Models a ratio of values, i.e. where the numerator and denominator are both pure numbers.   
DV_QUANTIFIED   Class  from Package quantity  Abstract class defining the concept of true quantified values, i.e. values which are not only ordered, but which have a precise magnitude.   
DV_QUANTITY   Class  from Package quantity  Quantitified 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_STATE   Class  from Package basic  For representing state values which obey a defined state machine, such as a variable representing the states of an instruction or care process.   
DV_TEMPORAL   Class  from Package date_time  Specialised temporal variant of DV_ABSOLUTE_QUANTITY whose diff type is DV_DURATION.   
DV_TEXT   Class  from Package text  A plain 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). Any DV_TEXT may be “coded” by adding mappings to it.   
DV_TIME   Class  from Package date_time  Represents 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.   
DV_TIME_SPECIFICATION   Class  from Package time_specification     
DV_URI   Class  from Package uri  A 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.   
 
 
E
EHR   Class  from Package ehr  The EHR object is the root object and access point of an EHR for a subject of care.   
ehr   Package  from Package rm     
Ehr_acces_valid   Constraint  from Package ehr     
EHR_ACCESS   Class  from Package ehr  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_id_valid   Constraint  from Package ehr     
EHR_STATUS   Class  from Package