Data Management with FHIR
0.1.0 - ci-build France flag

Data Management with FHIR - version de développement local (intégration continue v0.1.0) construite par les outils de publication FHIR (HL7® FHIR® Standard). Voir le répertoire des versions publiées

Logical Model: OMOPConcept - Detailed Descriptions

Draft as of 2026-02-05

Definitions for the OMOPConcept logical model.

Des conseils sur l'interprétation du contenu de ce tableau peuvent être trouvésici

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.

CourtConcept OMOP Table
Contrôle0..*
Est modificateurfalse
Modèle logiqueLes instances de ce modèle logique ne sont pas marquées pour être la cible d'une référence
2. OMOPConcept.concept-id
Définition

A unique identifier for each Concept across all domains.

CourtA unique identifier for each Concept across all domains.
Contrôle1..1
Typeinteger
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
4. OMOPConcept.concept-name
Définition

An unambiguous, meaningful and descriptive name for the Concept.

CourtAn unambiguous, meaningful and descriptive name for the Concept.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
6. OMOPConcept.domain-id
Définition

A foreign key to the DOMAIN table the Concept belongs to.

CourtA foreign key to the DOMAIN table the Concept belongs to.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
8. OMOPConcept.vocabulary-id
Définition

A foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.

CourtA foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
10. OMOPConcept.concept-class-id
Définition

The attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.

CourtThe attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThis 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.
Contrôle0..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThe 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.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThe date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
Contrôle1..1
Typedate
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThe 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.
Contrôle1..1
Typedate
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtReason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
Contrôle0..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension

Des conseils sur l'interprétation du contenu de ce tableau peuvent être trouvésici

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.

CourtConcept OMOP Table
Modèle logiqueLes instances de ce modèle logique ne sont pas marquées pour être la cible d'une référence
2. OMOPConcept.concept-id
Définition

A unique identifier for each Concept across all domains.

CourtA unique identifier for each Concept across all domains.
Contrôle1..1
Typeinteger
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
4. OMOPConcept.concept-name
Définition

An unambiguous, meaningful and descriptive name for the Concept.

CourtAn unambiguous, meaningful and descriptive name for the Concept.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
6. OMOPConcept.domain-id
Définition

A foreign key to the DOMAIN table the Concept belongs to.

CourtA foreign key to the DOMAIN table the Concept belongs to.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
8. OMOPConcept.vocabulary-id
Définition

A foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.

CourtA foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
10. OMOPConcept.concept-class-id
Définition

The attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.

CourtThe attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThis 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.
Contrôle0..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThe 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.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThe date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
Contrôle1..1
Typedate
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThe 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.
Contrôle1..1
Typedate
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtReason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
Contrôle0..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension

Des conseils sur l'interprétation du contenu de ce tableau peuvent être trouvésici

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.

CourtConcept OMOP Table
Contrôle0..*
Est modificateurfalse
Modèle logiqueLes instances de ce modèle logique ne sont pas marquées pour être la cible d'une référence
2. OMOPConcept.concept-id
Définition

A unique identifier for each Concept across all domains.

CourtA unique identifier for each Concept across all domains.
Contrôle1..1
Typeinteger
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
4. OMOPConcept.concept-name
Définition

An unambiguous, meaningful and descriptive name for the Concept.

CourtAn unambiguous, meaningful and descriptive name for the Concept.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
6. OMOPConcept.domain-id
Définition

A foreign key to the DOMAIN table the Concept belongs to.

CourtA foreign key to the DOMAIN table the Concept belongs to.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
8. OMOPConcept.vocabulary-id
Définition

A foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.

CourtA foreign key to the VOCABULARY table indicating from which source the Concept has been adapted.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension
10. OMOPConcept.concept-class-id
Définition

The attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.

CourtThe attribute or concept class of the Concept. Examples are "Clinical Drug", "Ingredient", "Clinical Finding" etc.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThis 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.
Contrôle0..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThe 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.
Contrôle1..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThe date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
Contrôle1..1
Typedate
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtThe 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.
Contrôle1..1
Typedate
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une 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.

CourtReason the Concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.
Contrôle0..1
Typestring
Valeur primitiveCet élément primitif peut être présent, absent ou remplacé par une extension