OpenEHR Base package
0.1.0 - First Draft International flag

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

Logical Model: TERM_MAPPING - Detailed Descriptions

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.

ShortItems 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.

Control0..*
Is Modifierfalse
Logical ModelInstances 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 mapping is to a broader term e.g. orginal text = arbovirus infection , target = viral infection
  • '=': the mapping is to a (supposedly) equivalent to the original item
  • '<': the mapping is to a narrower term. e.g. original text = diabetes , mapping = diabetes mellitus.
  • '?': the kind of mapping is unknown.

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
Control1..1
Typestring
Is Modifierfalse
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
InvariantsMatchValid: 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'.

ShortPurpose of the mapping
Control0..1
BindingThe codes SHALL be taken from Term Mapping Purpose
(required to https://specifications.openehr.org/fhir/valueset-term_mapping_purpose)
Typehttp://openehr.org/fhir/StructureDefinition/DV-CODED-TEXT
Is Modifierfalse
6. TERM_MAPPING.target
Definition

The target term of the mapping.

ShortThe target term of the mapping
Control1..1
Typehttp://openehr.org/fhir/StructureDefinition/CODE-PHRASE
Is Modifierfalse

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.

ShortItems 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.

Control0..*
Is Modifierfalse
Logical ModelInstances 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 mapping is to a broader term e.g. orginal text = arbovirus infection , target = viral infection
  • '=': the mapping is to a (supposedly) equivalent to the original item
  • '<': the mapping is to a narrower term. e.g. original text = diabetes , mapping = diabetes mellitus.
  • '?': the kind of mapping is unknown.

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
Control1..1
Typestring
Is Modifierfalse
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
InvariantsMatchValid: 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'.

ShortPurpose of the mapping
Control0..1
BindingThe codes SHALL be taken from Term Mapping Purpose
(required to https://specifications.openehr.org/fhir/valueset-term_mapping_purpose)
Typehttp://openehr.org/fhir/StructureDefinition/DV-CODED-TEXT
Is Modifierfalse
6. TERM_MAPPING.target
Definition

The target term of the mapping.

ShortThe target term of the mapping
Control1..1
Typehttp://openehr.org/fhir/StructureDefinition/CODE-PHRASE
Is Modifierfalse

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.

ShortItems 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.

Control0..*
Is Modifierfalse
Logical ModelInstances 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 mapping is to a broader term e.g. orginal text = arbovirus infection , target = viral infection
  • '=': the mapping is to a (supposedly) equivalent to the original item
  • '<': the mapping is to a narrower term. e.g. original text = diabetes , mapping = diabetes mellitus.
  • '?': the kind of mapping is unknown.

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
Control1..1
Typestring
Is Modifierfalse
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
InvariantsMatchValid: 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'.

ShortPurpose of the mapping
Control0..1
BindingThe codes SHALL be taken from Term Mapping Purpose
(required to https://specifications.openehr.org/fhir/valueset-term_mapping_purpose)
Typehttp://openehr.org/fhir/StructureDefinition/DV-CODED-TEXT
Is Modifierfalse
6. TERM_MAPPING.target
Definition

The target term of the mapping.

ShortThe target term of the mapping
Control1..1
Typehttp://openehr.org/fhir/StructureDefinition/CODE-PHRASE
Is Modifierfalse