OpenEHR Base package
0.1.0 - First Draft
OpenEHR Base package, published by openEHR + HL7. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/FHIR/openehr-base-ig/ and changes regularly. See the Directory of published versions
Page standards status: Informative | Maturity Level: 3 |
Definitions for the TERM-MAPPING logical model.
Guidance on how to interpret the contents of this table can be foundhere
0. TERM_MAPPING | |
Definition | Items 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. Base definition for all types defined in FHIR type system. |
Short | Items which are truly boolean dataBase for all types and resources |
Comments | Misuse: The TERM_MAPPING 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. |
Control | 0..* |
Is Modifier | false |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. TERM_MAPPING.match | |
Definition | The relative match of the target term with respect to the mapped text item. Result meanings:
The first three values are taken from the ISO standards 2788 ( Guide to Establishment and development of monolingual thesauri) and 5964 (Guide to Establishment and development of multilingual thesauri). |
Short | > | = | < | ?: The relative match of the target term with respect to the mapped text item |
Control | 1..1 |
Type | string |
Is Modifier | false |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
Invariants | MatchValid: match must be >, =, < or ? ($this = '<' or $this = '=' or $this = '>' or $this = '?' ) |
4. TERM_MAPPING.purpose | |
Definition | Purpose of the mapping e.g. 'automated data mining', 'billing', 'interoperability'. |
Short | Purpose of the mapping |
Control | 0..1 |
Binding | The codes SHALL be taken from Term Mapping Purpose (required to https://specifications.openehr.org/fhir/valueset-term_mapping_purpose ) |
Type | http://openehr.org/fhir/StructureDefinition/DV-CODED-TEXT |
Is Modifier | false |
6. TERM_MAPPING.target | |
Definition | The target term of the mapping. |
Short | The target term of the mapping |
Control | 1..1 |
Type | http://openehr.org/fhir/StructureDefinition/CODE-PHRASE |
Is Modifier | false |
Guidance on how to interpret the contents of this table can be foundhere
0. TERM_MAPPING | |
Definition | Items 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. |
Short | Items which are truly boolean data |
Comments | Misuse: The TERM_MAPPING 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. |
Control | 0..* |
Is Modifier | false |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. TERM_MAPPING.match | |
Definition | The relative match of the target term with respect to the mapped text item. Result meanings:
The first three values are taken from the ISO standards 2788 ( Guide to Establishment and development of monolingual thesauri) and 5964 (Guide to Establishment and development of multilingual thesauri). |
Short | > | = | < | ?: The relative match of the target term with respect to the mapped text item |
Control | 1..1 |
Type | string |
Is Modifier | false |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
Invariants | MatchValid: match must be >, =, < or ? ($this = '<' or $this = '=' or $this = '>' or $this = '?' ) |
4. TERM_MAPPING.purpose | |
Definition | Purpose of the mapping e.g. 'automated data mining', 'billing', 'interoperability'. |
Short | Purpose of the mapping |
Control | 0..1 |
Binding | The codes SHALL be taken from Term Mapping Purpose (required to https://specifications.openehr.org/fhir/valueset-term_mapping_purpose ) |
Type | http://openehr.org/fhir/StructureDefinition/DV-CODED-TEXT |
Is Modifier | false |
6. TERM_MAPPING.target | |
Definition | The target term of the mapping. |
Short | The target term of the mapping |
Control | 1..1 |
Type | http://openehr.org/fhir/StructureDefinition/CODE-PHRASE |
Is Modifier | false |
Guidance on how to interpret the contents of this table can be foundhere
0. TERM_MAPPING | |
Definition | Items 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. |
Short | Items which are truly boolean data |
Comments | Misuse: The TERM_MAPPING 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. |
Control | 0..* |
Is Modifier | false |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. TERM_MAPPING.match | |
Definition | The relative match of the target term with respect to the mapped text item. Result meanings:
The first three values are taken from the ISO standards 2788 ( Guide to Establishment and development of monolingual thesauri) and 5964 (Guide to Establishment and development of multilingual thesauri). |
Short | > | = | < | ?: The relative match of the target term with respect to the mapped text item |
Control | 1..1 |
Type | string |
Is Modifier | false |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
Invariants | MatchValid: match must be >, =, < or ? ($this = '<' or $this = '=' or $this = '>' or $this = '?' ) |
4. TERM_MAPPING.purpose | |
Definition | Purpose of the mapping e.g. 'automated data mining', 'billing', 'interoperability'. |
Short | Purpose of the mapping |
Control | 0..1 |
Binding | The codes SHALL be taken from Term Mapping Purpose (required to https://specifications.openehr.org/fhir/valueset-term_mapping_purpose ) |
Type | http://openehr.org/fhir/StructureDefinition/DV-CODED-TEXT |
Is Modifier | false |
6. TERM_MAPPING.target | |
Definition | The target term of the mapping. |
Short | The target term of the mapping |
Control | 1..1 |
Type | http://openehr.org/fhir/StructureDefinition/CODE-PHRASE |
Is Modifier | false |