openEHR Foundation Types specification
Issuer: openEHR Specification Program | |
---|---|
Release: BASE Release-1.1.0 |
Status: STABLE |
Revision: [latest_issue] |
Date: [latest_issue_date] |
Keywords: openehr, identifiers, types |
© 2017 - 2019 The openEHR Foundation | |
---|---|
The openEHR Foundation is an independent, non-profit community organisation, facilitating the sharing of health records by consumers and clinicians via open standards-based implementations. |
|
Licence |
Creative Commons Attribution-NoDerivs 3.0 Unported. https://creativecommons.org/licenses/by-nd/3.0/ |
Support |
Issues: Problem Reports |
Amendment Record
Issue | Details | Raiser | Completed |
---|---|---|---|
BASE Release 1.1.0 |
|||
SPECRM-72: Add guidance on date/time formatting, recommending extended ISO8601 format. |
B Lah |
||
SPECBASE-15. Add foundation types specification to BASE component. |
T Beale |
19 Jul 2018 |
|
SPECPUB-6. Correct UML package nesting and paths in documents; insert |
T Beale |
27 Nov 2017 |
|
0.7.6 |
Re-organise heading structure. Remove references to ISO 11404. Rename to 'Foundation types'; |
T Beale |
17 Aug 2017 |
0.7.0 |
Initial Writing. Taken from openEHR RM Release 1.0.3 Support Model |
T Beale |
20 May 2016 |
The Amendment history relevant to the original content in this specification can be found here (a fully hyper-linked version may be found on the working baseline).
Acknowledgements
Contributors
This specification has benefited from formal and informal input from the openEHR and wider health informatics community.
Trademarks
-
'openEHR' is a registered trademark of the openEHR Foundation
1. Preface
1.1. Purpose
This document describes the openEHR Foundation Types, a collection of built-in and library types whose semantics are assumed by all other openEHR specifications.
The intended audience includes:
-
Standards bodies producing health informatics standards;
-
Research groups using openEHR, ISO 13606, archetypes and related technologies;
-
The open source healthcare community;
-
Solution vendors.
1.3. Status
This specification is in the STABLE state. The development version of this document can be found at https://specifications.openehr.org/releases/BASE/latest/foundation_types.html.
Known omissions or questions are indicated in the text with a 'to be determined' paragraph, as follows:
TBD: (example To Be Determined paragraph)
1.4. Feedback
Feedback may be provided on the technical mailing list.
Issues may be raised on the specifications Problem Report tracker.
To see changes made due to previously reported issues, see the BASE component Change Request tracker.
1.5. Previous Versions
This specification is based on the types orginally defined in the openEHR Support Information Model from Release 1.0.3 of the Reference Model. Some changes have been made as follows.
1.5.1. Interval types
The additional types Point_interval
and Proper_interval
have been added, to support the common need for a point value and a proper interval to be specified as substitutable types. The types Multiplicity_interval
and Cardinality
have been added, from the AOM2 specification.
2. Overview
The openEHR Foundation Types (org.openehr.base.foundation_types
package) consists of generic low level types assumed by and used throughout the openEHR components and specifications. The types described here are specified in order to establish the names and minimal semantics of typical standard classes, as used by all other openEHR specifications, and to provide a mapping point into implementation technologies.
The set of types chosen here is based on a common set derived from various published sources, including:
-
Major interoperability formalisms, including OMG IDL, W3C XML-schema;
-
Major typed programming languages, including Java, C#, C++, etc.
The package structure is illustrated below.
base.foundation_types
PackageThe primitive_types
, structures
and time
packages describe types assumed by the openEHR specifcations to exist in any implementation technology, such as a programming language, schema language or database environment.
The functional
package includes types enabling functional programming primitives to be expressed in the openEHR modelling environment, i.e. functions-as-objects and 'lambda' expressions.
The types are described in this specification are typically of two kinds: built-in types, which are those built in to a type system of the development language, and library types, which are assumed to be available in a (class) library defined in the formalism. Thus, the type Boolean
is always assumed to exist in a formalism, while the type Array<T>
is assumed to be available in a library. For practical purposes, these two categories do not matter too much - whether String
is really a library class (the usual case) or an inbuilt type doesn’t make much difference to the programmer. They are shown separately here mainly as an explanatory convenience.
The assumptions that openEHR makes about existing types are documented below in terms of interface definitions. Each of these definitions contains only the assumptions required for the given type to be used in the openEHR Reference Model - it is not by any means a complete interface definition. The name and semantics of any function used here for an assumed type might not be identical to those found in some implementation technologies. Any mapping required should be stated in the relevant implementation technology specification (ITS). To give a concrete example, where the assumed Set<T>
type defined below has an operation has (item: T): Boolean
which is used throughout the openEHR specifications, Java has the method contains()
on its Set<T>
class. In a Java implementation, the contains()
method should then be used throughout the openEHR classes as expressed in Java, in place of the has ()
method.
2.1. The Any Class
Within all object-oriented and most other modern programming and modelling environment exists an ultimate ancestor type to which all others conform. In this specification, we assume the type Any
, which defines a bare minimum of operators, and stands for the real Any
or Object
type found in real technologies.
2.2. openEHR Leaf Types
The sections below provide formal definitions of all the foundation types used in openEHR. A subset of these can be understood as terminal or leaf types, typically used as terminal value types in other information models. The following diagram provides an aide memoire for the leaf types.
2.3. Class Definitions
2.3.1. Any Class
Class |
Any (abstract) |
|||
---|---|---|---|---|
Description |
Abstract supertype. Usually maps to a type like Any or Object in an object-oriented technology. Defined here to provide value and reference equality semantics. |
|||
Functions |
Signature |
Meaning |
||
(abstract) |
is_equal ( |
Value equality. |
||
infix = ( |
Reference equality. Parameters
|
|||
instance_of ( |
Create new instance of a type. |
|||
type_of ( |
Type name of an object as a string. May include generic parameters, as in "Interval<Time>". |
3. Primitive Types
3.1. Overview
This section describes primitive types assumed by all openEHR models. These are types supported directly by most programing languages, and usually visible via either a class interface and/or a built-in raw value type. The following table lists the primitive types assumed by openEHR.
Type name in openEHR |
Description |
---|---|
|
a type whose value is an 8-bit value. |
|
a type whose value is a member of an 8-bit character-set (ISO: "repertoire"). |
|
logical True/False values; usually physically represented as an integer, but need not be. |
|
32-bit integers. |
|
64-bit integers. |
|
32-bit real numbers in any interoperable representation, including single-width IEEE floating point. |
|
64-bit real numbers, in any interoperable representation including double-precision IEEE floating point. |
|
represents unicode-enabled strings. |
The figure below illustrates these types. Simple inheritance relationships are shown which facilitate the type descriptions below. Actual inheritance from or subsitutability for an Any
class is not assumed, and is shown only for convenience (e.g. to indicate that the '=' operator is available on any type). The type Ordered_numeric
is on the other hand is used to indicate assumed substitutability of numeric types, and is intended to be mapped to an equivalent type in a real type system (e.g. in Java, java.lang.Number
). Data-oriented implementation type systems such as XML-schema do not have such operations.
base.foundation_types.primitive_types
Package3.2. Unicode
It is assumed in the openEHR specifications that Unicode is supported by the type String
. Unicode is needed for all Asian, Arabic and other script languages, for both data values (particularly plain text and coded text) and for many predefined string attributes of the classes in the openEHR Reference Model. It encompasses all existing character sets. In openEHR, UTF-8 encoding is assumed.
3.3. Class Definitions
3.3.1. Boolean Class
Class |
Boolean |
|
---|---|---|
Description |
Class representing minimal interface of standard Boolean type. |
|
Inherit |
|
|
Functions |
Signature |
Meaning |
infix and ( |
Logical conjunction |
|
infix and_then ( |
Boolean semi-strict conjunction with other |
|
infix or ( |
Boolean disjunction with other. |
|
infix or_else ( |
Boolean semi-strict disjunction with `other'. |
|
infix xor ( |
Boolean exclusive or with `other'. |
|
infix implies ( |
Boolean implication of `other' (semi-strict) |
|
Invariants |
Involutive_negation: |
|
Non_contradiction: |
||
Completeness: |
3.3.2. Ordered Class
Class |
Ordered (abstract) |
|
---|---|---|
Description |
Abstract notional parent class of ordered, types i.e. types on which the ‘<‘ operator is defined. |
|
Inherit |
|
|
Functions |
Signature |
Meaning |
(abstract) |
infix < ( |
Arithmetic comparison. In conjunction with ‘=’, enables the definition of the operators ‘>’, ‘>=’, ‘<=’, ‘<>’. In real type systems, this operator might be defined on another class for comparability. |
3.3.5. String Class
Class |
String |
|
---|---|---|
Description |
Strings of characters, as used to represent textual data in any natural or formal language. |
|
Inherit |
|
|
Functions |
Signature |
Meaning |
infix + ( |
Concatenation operator - causes ‘other’ to be appended to this string. |
|
is_empty (): |
True if string is empty, i.e. equal to "". |
|
is_integer (): |
True if string can be parsed as an integer. |
|
as_integer (): |
Return the integer corresponding to the integer value represented in this string. |
3.3.7. Numeric Class
Class |
Numeric (abstract) |
|
---|---|---|
Description |
Abstract notional parent class of numeric types, which are types which have various arithmetic and comparison operators defined. |
|
Inherit |
|
|
Functions |
Signature |
Meaning |
(abstract) |
infix * ( |
Product by `other'. Actual type of result depends on arithmetic balancing rules. |
(abstract) |
infix + ( |
Sum with `other' (commutative). Actual type of result depends on arithmetic balancing rules. |
(abstract) |
infix - ( |
Result of subtracting `other'. Actual type of result depends on arithmetic balancing rules. |
3.3.8. Ordered_Numeric Class
Class |
Ordered_Numeric (abstract) |
|
---|---|---|
Description |
Abstract notional parent class of ordered, numeric types, which are types with ‘<‘ and arithmetic operators defined. |
|
Inherit |
|
3.3.9. Integer Class
Class |
Integer |
|
---|---|---|
Description |
Class representing minimal interface of standard Integer type. |
|
Inherit |
|
3.3.10. Integer64 Class
Class |
Integer64 |
|
---|---|---|
Description |
Class representing minimal interface of standard Integer64 type. |
|
Inherit |
|
4. Structure Types
4.1. Overview
The types described in this section are basic data structures assumed to be standardly available in implementation technologies. The following types consititute the minimum set of structure types assumed by openEHR of an implementation environment.
Type name in openEHR |
Description |
---|---|
|
physical container of items indexed by number |
|
container of items, implied order, non-unique membership |
|
container of items, no order, unique membership |
|
a table of values of any type V, keyed by values of any |
The following UML diagram illustrates the base.foundation_types.structures
package. As with the primitive types, inheritance and abstract classes are used for convenience of the definitions in openEHR models, but are not assumed to exist in exactly the same way within implementation technologies. Hence, in an implementation, various workarounds or equivalences may be needed to obtain the defined semantics.
base.foundation_types.structures
package4.2. Class Definitions
4.2.1. Container Class
Class |
Container (abstract) |
|
---|---|---|
Description |
Abstract ancestor of container types whose items are addressable in some way. |
|
Inherit |
|
|
Functions |
Signature |
Meaning |
(abstract) |
has ( |
Test for membership of a value. |
(abstract) |
count (): |
Number of items in container. |
(abstract) |
is_empty (): |
True if container is empty. |
4.2.2. List Class
Class |
List |
|
---|---|---|
Description |
Ordered container that may contain duplicates. |
|
Inherit |
|
|
Functions |
Signature |
Meaning |
first (): |
Return first element. |
|
last (): |
Return last element. |
|
Invariants |
First_validity: |
|
Last_validity: |
4.2.3. Set Class
Class |
Set |
|
---|---|---|
Description |
Unordered container that may not contain duplicates. |
|
Inherit |
|
5. Interval
5.1. Overview
Another kind of structure commonly needed in rich data is the interval. The definition of the Interval<T>
class here is an intensional one, i.e. it states its members by implication from its limits, rather than enumerating them. To support the common need for defining times in models that could be either a fixed point in time or a time interval, the classes Point_interval<T>
and Proper_interval<T>
are provided. If Interval<X>
is defined as the type of a feature in a class in an openEHR model, where X
is some descendant of Ordered
, then at runtime, either a Point_interval
or Proper_interval
may be attached.
In addition to the generic interval types, the derived types Multiplicity_interval
and Cardinality
are provided, for use in models to represent multiplicity, optionality, and cardinality.
The following UML diagram illustrates the interval
package.
base.foundation_types.interval
package5.2. Class Definitions
5.2.1. Interval Class
Class |
Interval |
|
---|---|---|
Description |
Interval abstraction, featuring upper and lower limits that may be open or closed, included or not included. Interval of ordered items. |
|
Inherit |
|
|
Attributes |
Signature |
Meaning |
0..1 |
lower: |
Lower bound. lower bound. |
0..1 |
upper: |
Upper bound. Upper bound. |
1..1 |
lower_unbounded: |
|
1..1 |
upper_unbounded: |
|
1..1 |
lower_included: |
|
1..1 |
upper_included: |
|
Functions |
Signature |
Meaning |
has ( |
True if |
|
intersects ( |
True if there is any overlap between intervals represented by Current and `other'. True if at least one limit of other is strictly inside the limits of this interval. |
|
contains ( |
True if current interval properly contains |
|
(effected) |
is_equal ( |
True if current object’s interval is semantically same as |
Invariants |
Lower_included_valid: |
|
Upper_included_valid: |
||
Limits_consistent: |
||
Limits_comparable: |
5.2.2. Point_interval Class
Class |
Point_interval |
|
---|---|---|
Description |
Type representing an Interval that happens to be a point value. Provides an efficient representation that is substitutable for |
|
Inherit |
|
|
Attributes |
Signature |
Meaning |
1..1 |
lower_unbounded: |
lower boundary open (i.e. = -infinity) |
1..1 |
upper_unbounded: |
upper boundary open (i.e. = +infinity) |
1..1 |
lower_included: |
lower boundary value included in range if not lower_unbounded. |
1..1 |
upper_included: |
upper boundary value included in range if not upper_unbounded. |
Invariants |
Inv_point: |
5.2.3. Proper_interval Class
Class |
Proper_interval |
|
---|---|---|
Description |
Type representing a 'proper' Interval, i.e. any two-sided or one-sided interval. |
|
Inherit |
|
|
Invariants |
Inv_not_point: |
5.2.4. Multiplicity_interval Class
Class |
Multiplicity_interval |
|
---|---|---|
Description |
An Interval of Integer, used to represent multiplicity, cardinality and optionality in models. |
|
Inherit |
|
|
Constants |
Signature |
Meaning |
1..1 |
Multiplicity_range_marker: |
Marker to use in string form of interval between limits. |
1..1 |
Multiplicity_unbounded_marker: |
Symbol to use to indicate upper limit unbounded. |
Functions |
Signature |
Meaning |
is_open (): |
True if this interval imposes no constraints, i.e. is set to |
|
is_optional (): |
True if this interval expresses optionality, i.e. |
|
is_mandatory (): |
True if this interval expresses mandation, i.e. |
|
is_prohibited (): |
True if this interval is set to |
5.2.5. Cardinality Class
Class |
Cardinality |
|
---|---|---|
Description |
Express 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. |
|
Attributes |
Signature |
Meaning |
1..1 |
interval: |
The interval of this cardinality. |
1..1 |
is_ordered: |
True if the members of the container attribute to which this cardinality refers are ordered. |
1..1 |
is_unique: |
True if the members of the container attribute to which this cardinality refers are unique. |
Functions |
Signature |
Meaning |
is_bag (): |
True if the semantics of this cardinality represent a bag, i.e. unordered, non-unique membership. |
|
is_list (): |
True if the semantics of this cardinality represent a list, i.e. ordered, non-unique membership. |
|
is_set (): |
True if the semantics of this cardinality represent a set, i.e. unordered, unique membership. |
6. Time Types
6.1. Overview
The primitive Date/Time types used in openEHR are represented by classes defined in the package base.foundation_types.time
. These are concrete types based on the ISO 8601 (2004) date/time standard semantics, which supports partial dates, times, and complex durations, all of which are needed in the biomedical and clinical domains. These classes have a String
physical representation. and are assumed to exist in close to the form specified here, because they are specified in other openEHR specifications.
The time
package is shown below.
base.foundation_types.time
package6.2. Primitive Time Types
The set of ISO 8601 based types define dates and times with a String
representation (as per ISO 8601), and the ISO 8601 'partial' and 'extended' semantics. They are defined as descendents of the native types described above, and add the necessary elements required for ISO 8601.
Note
|
class names of the form Iso8601_xxx have been used here to clearly identify these classes where used elsewhere in the openEHR specifications. In real implementations, other class names may be used as convenient, just as for the other primitive types.
|
Note
|
For reasons of readability in data, it is strongly recommended that the 'extended' form of date and time strings be used when writing and displaying data, rather than the compact form. An extended date has the form yyyy-mm-dd rather than yyyymmdd , and an extended time has the form hh:mm:ss rather than hhmmss . Nevertheless, both forms should be supported so that openEHR-based systems that use 'straight-through' processing on legacy data that may be in the compact form remain conformant to the specifications.
|
ISO 8601 semantics not included in these types include:
-
'expanded' dates, which have year numbers of greater than 4 digits, and may be negative; in openEHR, only 4-digit year numbers are assumed;
-
the
YYYY-WW-DD
method of expressing dates (since this is imprecise and difficult to compute with due to variable week starting dates, and not required in health); -
partial date/times with fractional minutes or hours, e.g.
hh,hhh
ormm,mm
; in openEHR, only fractional seconds are supported; -
the interval syntax. Intervals of date/times are supported in openEHR, but their syntax form is defined by ADL, and is standardised across all comparable types, not just dates and times.
Deviations from the published standard include the following:
-
durations are supposed to take the form of
PnnW
orPnnYnnMnnDTnnHnnMnnS
, but in openEHR, the W (week) designator can be used in combination with the other designators, since it is very common to state durations of pregnancy as some combination of weeks and days. -
partial variants of
Iso8601_date_time
can include missing hours, days and months, whereas ISO 8601:2004 (section 4.3.3 c) only allows missing seconds and minutes. The reasons for this deviation are:-
the same deviation is used in HL7v2 and HL7v3 TS (timestamp) type, i.e. there are data in existing clinical systems matching this specification;
-
in a typed object model, this deviation is more sensible anyway; the ISO 8601 rule is most likely a limitation of the purely syntactic means of expression. In real systems where a timestamp/date-time is specified in a screen form, it makes sense to allow it to be as partial as possible, rather than artifically restricted to only missing seconds and minutes.
-
-
the time
24:00:00
(or240000
) is not allowed anywhere, whereas in ISO 8601:2004 it appears to be legal at least for pure times. This deviation is also appears to be used in HL7v2 and HL7v3 (where midnight is defined as the time00:00:00
), and is preferable to the documented standard, since a date/time with time of24:00:00
is really the next day, i.e. the date part is then incorrect.
See ISO 8601 and the official ISO 8601 standard for details. Note that in the date, time and date_time formats shown below, 'Z' and 'T' are literals. In the duration class shown below, 'P', 'Y', 'M', 'W', 'D', 'H', 'S' and 'T' are literals.
6.3. Derived Interval / Time Types
A number of useful types may be generated from the Date/time classes and the Interval classes. These are shown in blue on the following diagram.
6.4. Class Definitions
6.4.1. Time_Definitions Class
Class |
Time_Definitions |
|||||
---|---|---|---|---|---|---|
Description |
Definitions for date/time classes. Note that the timezone limits are set by where the international dateline is. Thus, time in New Zealand is quoted using |
|||||
Constants |
Signature |
Meaning |
||||
1..1 |
Seconds_in_minute: |
|||||
1..1 |
Minutes_in_hour: |
|||||
1..1 |
Hours_in_day: |
|||||
1..1 |
Nominal_days_in_month: |
Used for conversions of durations containing months to days and / or seconds. |
||||
1..1 |
Max_days_in_month: |
|||||
1..1 |
Days_in_year: |
|||||
1..1 |
Days_in_leap_year: |
|||||
1..1 |
Max_days_in_year: |
|||||
1..1 |
Nominal_days_in_year: |
Used for conversions of durations containing years to days and / or seconds. |
||||
1..1 |
Days_in_week: |
|||||
1..1 |
Months_in_year: |
|||||
1..1 |
Min_timezone_hour: |
Minimum hour value of a timezone (note that the -ve sign is supplied in the ISO8601_TIMEZONE class). |
||||
1..1 |
Max_timezone_hour: |
|||||
Functions |
Signature |
Meaning |
||||
valid_year ( |
||||||
valid_month ( |
||||||
valid_day ( |
True if d >= 1 and d <= days_in_month (m, y) |
|||||
valid_hour ( |
True if (h >= 0 and h < Hours_in_day) or (h = Hours_in_day and m = 0 and s = 0) |
|||||
valid_minute ( |
True if m >= 0 and m < Minutes_in_hour. |
|||||
valid_second ( |
True if s >= 0 and s < Seconds_in_minute . |
|||||
valid_fractional_second ( |
True if fs >= 0.0 and fs < 1.0 . |
|||||
valid_iso8601_date ( |
String is a valid ISO 8601 date, i.e. takes the complete form:
Where:
The combinations of |
|||||
valid_iso8601_time ( |
String is a valid ISO 8601 date, i.e. takes the form:
with an additional optional timezone indicator of:
Where:
|
|||||
valid_iso8601_date_time ( |
String is a valid ISO 8601 date-time, i.e. takes the form:
|
|||||
valid_iso8601_duration ( |
String is a valid ISO 8601 duration, i.e. takes the form:
Where each nn represents a number of years, months, etc. nnW represents a number of 7-day weeks. Note: allowing the Parameters
Where each
|
6.4.2. Temporal Class
Class |
Temporal (abstract) |
|
---|---|---|
Description |
Abstract ancestor of time-related classes. |
|
Inherit |
|
6.4.3. Iso8601_type Class
Class |
Iso8601_type (abstract) |
|
---|---|---|
Description |
Abstract ancestor type of ISO 8601 types, defining interface for 'extended' and 'partial' concepts from ISO 8601. |
|
Inherit |
|
|
Attributes |
Signature |
Meaning |
1..1 |
value: |
Representation of all descendants is a single String. |
Functions |
Signature |
Meaning |
(abstract) |
is_partial (): |
True if this date time is partial, i.e. if trailing end (right hand) value(s) is/are missing. |
(abstract) |
is_extended (): |
True if this ISO8601 string is in the 'extended' form, i.e. uses ‘-’ and / or ‘:’ separators. This is the preferred format. |
6.4.4. Iso8601_date Class
Class |
Iso8601_date |
|
---|---|---|
Description |
Represents an ISO 8601 date, including partial and extended forms. Value may be:
See |
|
Inherit |
|
|
Functions |
Signature |
Meaning |
year (): |
Year. |
|
month (): |
Month in year. |
|
day (): |
Day in month. |
|
timezone (): |
Timezone; may be Void. |
|
month_unknown (): |
Indicates whether month in year is unknown. If so, the date is of the form |
|
day_unknown (): |
Indicates whether day in month is unknown. If so, and month is known, the date is of the form |
|
(effected) |
is_partial (): |
True if this date is partial, i.e. if days or more is missing. |
(effected) |
is_extended (): |
True if this date uses |
as_string (): |
Return string value in extended format. |
|
Invariants |
Year_valid: |
|
Month_valid: |
||
Day_valid: |
||
Partial_validity: |
6.4.5. Iso8601_time Class
Class |
Iso8601_time |
|||
---|---|---|---|---|
Description |
Represents an ISO 8601 time, including partial and extended forms. Value may be:
See
|
|||
Inherit |
|
|||
Functions |
Signature |
Meaning |
||
hour (): |
Hour in day, in 24-hour time. |
|||
minute (): |
Minute in hour. |
|||
second (): |
Second in minute. |
|||
fractional_second (): |
Fractional seconds. |
|||
timezone (): |
Timezone; may be Void. |
|||
minute_unknown (): |
Indicates whether minute is unknown. If so, the time is of the form “hh”. |
|||
second_unknown (): |
Indicates whether second is unknown. If so and month is known, the time is of the form |
|||
is_decimal_sign_comma (): |
True if this time has a decimal part indicated by ‘,’ (comma) rather than ‘.’ (period). |
|||
(effected) |
is_partial (): |
True if this time is partial, i.e. if seconds or more is missing. |
||
(effected) |
is_extended (): |
True if this time uses ‘-’, ‘:’ separators. |
||
has_fractional_second (): |
True if the fractional_second part is signficant (i.e. even if = 0.0). |
|||
as_string (): |
Return string value in extended format. |
|||
Invariants |
Hour_valid: |
|||
Minute_valid: |
||||
Second_valid: |
||||
Fractional_second_valid: |
||||
Partial_validity: |
6.4.6. Iso8601_date_time Class
Class |
Iso8601_date_time |
|
---|---|---|
Description |
Represents an ISO 8601 date/time, including partial and extended forms. Value may be:
See Note that this class includes 2 deviations from ISO 8601:2004:
|
|
Inherit |
|
|
Functions |
Signature |
Meaning |
year (): |
Year. |
|
month (): |
Month in year. |
|
day (): |
Day in month. |
|
hour (): |
Hour in day. |
|
minute (): |
Minute in hour. |
|
second (): |
Second in minute. |
|
fractional_second (): |
Fractional seconds. |
|
timezone (): |
Timezone; may be Void. |
|
month_unknown (): |
Indicates whether month in year is unknown. |
|
day_unknown (): |
Indicates whether day in month is unknown. |
|
minute_unknown (): |
Indicates whether minute in hour is known. |
|
second_unknown (): |
Indicates whether minute in hour is known. |
|
is_decimal_sign_comma (): |
True if this time has a decimal part indicated by ‘,’ (comma) rather than ‘.’ (period). |
|
(effected) |
is_partial (): |
True if this date time is partial, i.e. if seconds or more is missing. |
(effected) |
is_extended (): |
True if this date/time uses ‘-’, ‘:’ separators. |
has_fractional_second (): |
True if the fractional_second part is signficant (i.e. even if = 0.0). |
|
as_string (): |
Return the string value in extended format. |
|
Invariants |
Year_valid: |
|
Month_valid: |
||
Day_valid: |
||
Hour_valid: |
||
Minute_valid: |
||
Second_valid: |
||
Fractional_second_valid: |
||
Partial_validity_year: |
||
Partial_validity_month: |
||
Partial_validity_day: |
||
Partial_validity_hour: |
||
Partial_validity_minute: |
6.4.7. Iso8601_duration Class
Class |
Iso8601_duration |
|
---|---|---|
Description |
Represents an ISO 8601 duration, which may have multiple parts from years down to seconds. Value is in format:
|
|
Inherit |
|
|
Functions |
Signature |
Meaning |
seconds (): |
Number of seconds. |
|
fractional_seconds (): |
Fractional seconds. |
|
is_decimal_sign_comma (): |
True if this time has a decimal part indicated by ',' (comma) rather than '.' (period). |
|
(effected) |
is_partial (): |
Returns False. |
(effected) |
is_extended (): |
Returns True. |
months (): |
Number of months. |
|
years (): |
Number of years of nominal 365-day length. |
|
weeks (): |
Number of 7 day weeks. |
|
to_seconds (): |
Total number of seconds equivalent (including fractional) of entire duration. |
|
minutes (): |
Number of 60 second minutes. |
|
hours (): |
Number of 60 minute hours. |
|
days (): |
Number of 24 hour days. |
|
as_string (): |
Return the duration string value. |
|
Invariants |
Years_valid: |
|
Months_valid: |
||
Weeks_valid: |
||
Days_valid: |
||
Hours_valid: |
||
Minutes_valid: |
||
Seconds_valid: |
||
Fractional_second_valid: |
6.4.8. Iso8601_timezone Class
Class |
Iso8601_timezone |
|
---|---|---|
Description |
ISO8601 timezone string, in format:
where:
|
|
Inherit |
|
|
Functions |
Signature |
Meaning |
hour (): |
Hour part of timezone - in the range 00 - 13. |
|
minute (): |
Minute part of timezone. Generally 00 or 30. |
|
sign (): |
Direction of timezone expresssed as +1 or -1. |
|
minute_unknown (): |
Indicates whether minute part known. |
|
(effected) |
is_partial (): |
True if this time zone is partial, i.e. if minutes is missing. |
(effected) |
is_extended (): |
True if this time-zone uses ‘:’ separators. |
is_gmt (): |
True if timezone is UTC, i.e. +0000. |
|
as_string (): |
Return timezone string. |
|
Invariants |
Min_hour_valid: |
|
Max_hour_valid: |
||
Minute_valid: |
||
Sign_valid: |
7. Terminology Package
7.1. Overview
The base.foundation_types.terminology
package provides leaf types used to represent a terminology code, i.e. a code within a terminology, and a term, which is the combination of a code and one rubric (natural language) string associated with it. Terminology codes are sometimes called concept codes among terminology experts, and when used as references, concept references.
An instance of Terminology_code
is a reference to any referenceable entity within a terminology or ontology, which may be:
-
a single term, for which a rubric(s) and potentially relationships (at least the
IS-A
relationship) are defined; -
a value set i.e. a set of single terms, possibly in a tree or other structure corresponding to relationships between the member terms;
-
any other terminological entity referencable with a code.
An instance of Terminology_term
provides a way to record a terminology code and the rubric used in some operational context, allowing the receiver or reader of the data to avoid having to perform a terminology lookup to obtain the rubric, e.g. for display purposes.
base.foundation_types.terminology
package7.2. Class Definitions
7.2.1. Terminology_term Class
Class |
Terminology_term |
|
---|---|---|
Description |
Leaf type representing a term from a terminology, which consists of the term text and the code, i.e. a concept reference. |
|
Inherit |
|
|
Attributes |
Signature |
Meaning |
1..1 |
concept: |
Refrence to the terminology concept formally representing this term. |
1..1 |
text: |
Text of term. |
7.2.2. Terminology_code Class
Class |
Terminology_code |
|
---|---|---|
Description |
Logically primitive type representing a reference to a terminology concept, in the form of a terminology identifier, optional version, and a code or code string from the terminology. |
|
Inherit |
|
|
Attributes |
Signature |
Meaning |
1..1 |
terminology_id: |
The archetype environment namespace identifier used to identify a terminology. Typically a value like |
0..1 |
terminology_version: |
Optional string value representing terminology version, typically a date or dotted numeric. |
1..1 |
code_string: |
A terminology code or post-coordinated code expression, if supported by the terminology. The code may refer to a single term, a value set consisting of multiple terms, or some other entity representable within the terminology. |
0..1 |
uri: |
The URI reference that may be used as a concrete key into a notional terminology service for queries that can obtain the term text, definition, and other associated elements. |
8. Functional Meta-types
8.1. Overview
A small number of meta-types are defined that correspond to functional programming primitives, otherwise known as 'closures', 'lambda expressions' and so on. These concepts are supported in most modern programming languages now, and the types defined here are intended to provide a minimal formal basis to enable other openEHR specification to defined function-related elements. Since UML does not contain native functional elements, the semantics here are approximated using normal class facilities.
The following illustrates the functional
package.
Two key abstractions are required, namely 'function as a type', and 'tuple', which enables arguments to be formalised. To provide a 'function' type, a 'routine' type is also required. For completeness, a 'procedure' type is also defined. The 'tuple' type is defined as a generic meta-type whose descendants may additionally define any number of generic parameter types, corresponding to a type list.
8.1.2. ROUTINE Class
Class |
ROUTINE |
|
---|---|---|
Description |
Type representing a function with a return type and 0 or more arguments represented as a TUPLE. |
8.1.3. FUNCTION Class
Class |
FUNCTION |
|
---|---|---|
Description |
Type representing a function with a return type and 0 or more arguments represented as a TUPLE. |
|
Inherit |
|
8.1.4. PROCEDURE Class
Class |
PROCEDURE |
|
---|---|---|
Description |
Type representing a procedure with 0 or more arguments represented as a TUPLE. |
|
Inherit |
|
9. Type Cross-Reference
The following table provides a cross-reference from openEHR foundation types to their equivalents in common implementation formalisms. Where there is no equivalent listed, a specific library may still exist, or an implementation may be required of the openEHR specification.
Type name in openEHR |
Description | XML | Java | C# |
---|---|---|---|---|
|
8-bit value. |
- |
|
|
|
a member of an 8-bit character-set. |
|
|
|
|
logical True/False values. |
`boolean |
|
|
|
32-bit integers. |
`decimal |
|
|
|
64-bit integers. |
`decimal |
|
|
|
32-bit real numbers |
|
|
|
|
64-bit real numbers |
|
|
|
|
Unicode-enabled strings. |
|
|
|
|
Contiguous Array. |
|
|
|
|
Ordered List. |
|
|
|
|
Unordered, unique membership container. |
|
|
|
|
Unique-keyed map. |
(various) |
|
|
|
Interval of ordered types. |
- |
- |
|
|
Native date type. |
|
|
|
|
Native time type. |
|
|
|
|
Native date/time type. |
|
|
|
|
Native duration type. |
|
|
|
|
ISO8601-encoded date type. |
|
use |
(use formatted string) |
|
ISO8601-encoded time type. |
|
use j`ava.text.SimpleDateFormat` |
(use formatted string) |
|
ISO8601-encoded date/time type. |
|
use |
(use formatted string) |
|
ISO8601-encoded duration type. |
|
use |
(use formatted string) |
|
Interval of Integer. |
- |
(various) |
- |
|
Interval of Date. |
- |
(various) |
- |
|
Interval of Time. |
- |
(various) |
- |
|
Interval of DateTime. |
- |
(various) |
- |