Data Management with FHIR
0.1.0 - ci-build

Data Management with FHIR - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## Logical Model: OMOPConcept - Detailed Descriptions

Draft as of 2025-10-23

Definitions for the OMOPConcept logical model.

- Key Elements Table
- Differential Elements Table
- Snapshot Elements Table

Guidance on how to interpret the contents of this table can be foundhere

0. OMOPConcept
Définition | The Standardized Vocabularies contains records, or Concepts, that uniquely identify each fundamental unit of meaning used to express clinical information in all domain tables of the CDM. Concepts are derived from vocabularies, which represent clinical information across a domain (e.g. conditions, drugs, procedures) through the use of codes and associated descriptions. Some Concepts are designated Standard Concepts, meaning these Concepts can be used as normative expressions of a clinical entity within the OMOP Common Data Model and within standardized analytics. Each Standard Concept belongs to one domain, which defines the location where the Concept would be expected to occur within data tables of the CDM. Concepts can represent broad categories (like "Cardiovascular disease"), detailed clinical elements ("Myocardial infarction of the anterolateral wall") or modifying characteristics and attributes that define Concepts at various levels of detail (severity of a disease, associated morphology, etc.). Records in the Standardized Vocabularies tables are derived from national or international vocabularies such as SNOMED-CT, RxNorm, and LOINC, or custom Concepts defined to cover various aspects of observational data analysis.
Short | Concept OMOP Table
Control | 0..*
Is Modifier | false
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. OMOPConcept.concept-id
Définition | A unique identifier for each Concept across all domains.
Short | A unique identifier for each Concept across all domains.
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPConcept.concept-name
Définition | An unambiguous, meaningful and descriptive name for the Concept.
Short | An unambiguous, meaningful and descriptive name for the Concept.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
6. OMOPConcept.domain-id
Définition | A foreign key to the DOMAIN table the Concept belongs to.
Short | A foreign key to the DOMAIN table the Concept belongs to.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
8. OMOPConcept.vocabulary-id
Définition | A foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.
Short | A foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPConcept.concept-class-id
Définition | The attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.
Short | The attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPConcept.standard-concept
Définition | This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowable values are "S" (Standard Concept) and "C" (Classification Concept), otherwise the content is NULL.
Short | This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowable values are "S" (Standard Concept) and "C" (Classification Concept), otherwise the content is NULL.
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPConcept.concept-code
Définition | The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies.
Short | The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPConcept.valid-start-date
Définition | The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
Short | The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
18. OMOPConcept.valid-end-date
Définition | The date when the Concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099, meaning, the Concept is valid until it becomes deprecated.
Short | The date when the Concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099, meaning, the Concept is valid until it becomes deprecated.
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
20. OMOPConcept.invalid-reason
Définition | Reason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
Short | Reason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. OMOPConcept
Définition | The Standardized Vocabularies contains records, or Concepts, that uniquely identify each fundamental unit of meaning used to express clinical information in all domain tables of the CDM. Concepts are derived from vocabularies, which represent clinical information across a domain (e.g. conditions, drugs, procedures) through the use of codes and associated descriptions. Some Concepts are designated Standard Concepts, meaning these Concepts can be used as normative expressions of a clinical entity within the OMOP Common Data Model and within standardized analytics. Each Standard Concept belongs to one domain, which defines the location where the Concept would be expected to occur within data tables of the CDM. Concepts can represent broad categories (like "Cardiovascular disease"), detailed clinical elements ("Myocardial infarction of the anterolateral wall") or modifying characteristics and attributes that define Concepts at various levels of detail (severity of a disease, associated morphology, etc.). Records in the Standardized Vocabularies tables are derived from national or international vocabularies such as SNOMED-CT, RxNorm, and LOINC, or custom Concepts defined to cover various aspects of observational data analysis.
Short | Concept OMOP Table
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. OMOPConcept.concept-id
Définition | A unique identifier for each Concept across all domains.
Short | A unique identifier for each Concept across all domains.
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPConcept.concept-name
Définition | An unambiguous, meaningful and descriptive name for the Concept.
Short | An unambiguous, meaningful and descriptive name for the Concept.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
6. OMOPConcept.domain-id
Définition | A foreign key to the DOMAIN table the Concept belongs to.
Short | A foreign key to the DOMAIN table the Concept belongs to.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
8. OMOPConcept.vocabulary-id
Définition | A foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.
Short | A foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPConcept.concept-class-id
Définition | The attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.
Short | The attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPConcept.standard-concept
Définition | This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowable values are "S" (Standard Concept) and "C" (Classification Concept), otherwise the content is NULL.
Short | This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowable values are "S" (Standard Concept) and "C" (Classification Concept), otherwise the content is NULL.
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPConcept.concept-code
Définition | The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies.
Short | The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPConcept.valid-start-date
Définition | The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
Short | The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
18. OMOPConcept.valid-end-date
Définition | The date when the Concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099, meaning, the Concept is valid until it becomes deprecated.
Short | The date when the Concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099, meaning, the Concept is valid until it becomes deprecated.
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
20. OMOPConcept.invalid-reason
Définition | Reason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
Short | Reason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. OMOPConcept
Définition | The Standardized Vocabularies contains records, or Concepts, that uniquely identify each fundamental unit of meaning used to express clinical information in all domain tables of the CDM. Concepts are derived from vocabularies, which represent clinical information across a domain (e.g. conditions, drugs, procedures) through the use of codes and associated descriptions. Some Concepts are designated Standard Concepts, meaning these Concepts can be used as normative expressions of a clinical entity within the OMOP Common Data Model and within standardized analytics. Each Standard Concept belongs to one domain, which defines the location where the Concept would be expected to occur within data tables of the CDM. Concepts can represent broad categories (like "Cardiovascular disease"), detailed clinical elements ("Myocardial infarction of the anterolateral wall") or modifying characteristics and attributes that define Concepts at various levels of detail (severity of a disease, associated morphology, etc.). Records in the Standardized Vocabularies tables are derived from national or international vocabularies such as SNOMED-CT, RxNorm, and LOINC, or custom Concepts defined to cover various aspects of observational data analysis.
Short | Concept OMOP Table
Control | 0..*
Is Modifier | false
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. OMOPConcept.concept-id
Définition | A unique identifier for each Concept across all domains.
Short | A unique identifier for each Concept across all domains.
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPConcept.concept-name
Définition | An unambiguous, meaningful and descriptive name for the Concept.
Short | An unambiguous, meaningful and descriptive name for the Concept.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
6. OMOPConcept.domain-id
Définition | A foreign key to the DOMAIN table the Concept belongs to.
Short | A foreign key to the DOMAIN table the Concept belongs to.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
8. OMOPConcept.vocabulary-id
Définition | A foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.
Short | A foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPConcept.concept-class-id
Définition | The attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.
Short | The attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPConcept.standard-concept
Définition | This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowable values are "S" (Standard Concept) and "C" (Classification Concept), otherwise the content is NULL.
Short | This flag determines where a Concept is a Standard Concept, i.e. is used in the data, a Classification Concept, or a non-standard Source Concept. The allowable values are "S" (Standard Concept) and "C" (Classification Concept), otherwise the content is NULL.
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPConcept.concept-code
Définition | The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies.
Short | The concept code represents the identifier of the Concept in the source vocabulary, such as SNOMED-CT concept IDs, RxNorm RXCUIs etc. Note that concept codes are not unique across vocabularies.
Control | 1..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPConcept.valid-start-date
Définition | The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
Short | The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
18. OMOPConcept.valid-end-date
Définition | The date when the Concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099, meaning, the Concept is valid until it becomes deprecated.
Short | The date when the Concept became invalid because it was deleted or superseded (updated) by a new concept. The default value is 31-Dec-2099, meaning, the Concept is valid until it becomes deprecated.
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
20. OMOPConcept.invalid-reason
Définition | Reason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
Short | Reason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension