Guide d'implémentation du GT Standards et Interopérabilité pour les EDS
0.1.0 - ci-build France flag

Guide d'implémentation du GT Standards et Interopérabilité pour les EDS - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Logical Model: OMOPConditionOccurrence - Detailed Descriptions

Draft as of 2024-11-23

Definitions for the OMOPConditionOccurrence logical model.

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

0. OMOPConditionOccurrence
Definition

This table contains records of Events of a Person suggesting the presence of a disease or medical condition stated as a diagnosis, a sign, or a symptom, which is either observed by a Provider or reported by the patient.

ShortCondition Occurrence OMOP Table
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. OMOPConditionOccurrence.condition-occurrence-id
Definition

The unique key given to a condition record for a person. Refer to the ETL for how duplicate conditions during the same visit were handled.

ShortCondition Occurence Identifier
Control1..1
Typeinteger
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. OMOPConditionOccurrence.person-id
Definition

The PERSON_ID of the PERSON for whom the condition is recorded.

ShortPerson
Control1..1
TypeReference(Person OMOP Table)
6. OMOPConditionOccurrence.condition-concept-id
Definition

The CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a condition

ShortCondition
Control1..1
TypeReference(Concept OMOP Table)
8. OMOPConditionOccurrence.condition-start-date
Definition

Use this date to determine the start date of the condition

ShortCondition Start Date
Control1..1
Typedate
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. OMOPConditionOccurrence.condition-start-datetime
Definition

Condition Start Datetime

ShortCondition Start Datetime
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. OMOPConditionOccurrence.condition-end-date
Definition

Use this date to determine the end date of the condition

ShortCondition End Date
Control0..1
Typedate
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
14. OMOPConditionOccurrence.condition-end-datetime
Definition

Condition End Datetime

ShortCondition End Datetime
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
16. OMOPConditionOccurrence.condition-type-concept-id
Definition

This field can be used to determine the provenance of the Condition record, as in whether the condition was from an EHR system, insurance claim, registry, or other sources.

ShortCondition Type
Control1..1
TypeReference(Concept OMOP Table)
18. OMOPConditionOccurrence.condition-status-concept-id
Definition

This concept represents the point during the visit the diagnosis was given (admitting diagnosis, final diagnosis), whether the diagnosis was determined due to laboratory findings, if the diagnosis was exclusionary, or if it was a preliminary diagnosis, among others.

ShortCondition Status
Control0..1
TypeReference(Concept OMOP Table)
20. OMOPConditionOccurrence.stop-reason
Definition

The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring.

ShortStop Reason
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
22. OMOPConditionOccurrence.provider-id
Definition

The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.

ShortProvider
Control0..1
TypeReference(Provider OMOP Table)
24. OMOPConditionOccurrence.visit-occurrence-id
Definition

The visit during which the condition occurred.

ShortVisit Occurrence
Control0..1
TypeReference(Visit Occurrence OMOP Table)
26. OMOPConditionOccurrence.visit-detail-id
Definition

The VISIT_DETAIL record during which the condition occurred. For example, if the person was in the ICU at the time of the diagnosis the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.

ShortVisit Detail
Control0..1
TypeReference(Visit Detail OMOP Table)
28. OMOPConditionOccurrence.condition-source-value
Definition

This field houses the verbatim value from the source data representing the condition that occurred. For example, this could be an ICD10 or Read code.

ShortCondition Source Value
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
30. OMOPConditionOccurrence.condition-source-concept-id
Definition

This is the concept representing the condition source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Condition necessary for a given analytic use case. Consider using CONDITION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.

ShortCondition Source Concept
Control0..1
TypeReference(Concept OMOP Table)
32. OMOPConditionOccurrence.condition-status-source-value
Definition

This field houses the verbatim value from the source data representing the condition status.

ShortCondition Status Source Value
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

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

0. OMOPConditionOccurrence
Definition

This table contains records of Events of a Person suggesting the presence of a disease or medical condition stated as a diagnosis, a sign, or a symptom, which is either observed by a Provider or reported by the patient.

ShortCondition Occurrence OMOP Table
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. OMOPConditionOccurrence.condition-occurrence-id
Definition

The unique key given to a condition record for a person. Refer to the ETL for how duplicate conditions during the same visit were handled.

ShortCondition Occurence Identifier
Control1..1
Typeinteger
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. OMOPConditionOccurrence.person-id
Definition

The PERSON_ID of the PERSON for whom the condition is recorded.

ShortPerson
Control1..1
TypeReference(Person OMOP Table)
6. OMOPConditionOccurrence.condition-concept-id
Definition

The CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a condition

ShortCondition
Control1..1
TypeReference(Concept OMOP Table)
8. OMOPConditionOccurrence.condition-start-date
Definition

Use this date to determine the start date of the condition

ShortCondition Start Date
Control1..1
Typedate
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. OMOPConditionOccurrence.condition-start-datetime
Definition

Condition Start Datetime

ShortCondition Start Datetime
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. OMOPConditionOccurrence.condition-end-date
Definition

Use this date to determine the end date of the condition

ShortCondition End Date
Control0..1
Typedate
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
14. OMOPConditionOccurrence.condition-end-datetime
Definition

Condition End Datetime

ShortCondition End Datetime
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
16. OMOPConditionOccurrence.condition-type-concept-id
Definition

This field can be used to determine the provenance of the Condition record, as in whether the condition was from an EHR system, insurance claim, registry, or other sources.

ShortCondition Type
Control1..1
TypeReference(Concept OMOP Table)
18. OMOPConditionOccurrence.condition-status-concept-id
Definition

This concept represents the point during the visit the diagnosis was given (admitting diagnosis, final diagnosis), whether the diagnosis was determined due to laboratory findings, if the diagnosis was exclusionary, or if it was a preliminary diagnosis, among others.

ShortCondition Status
Control0..1
TypeReference(Concept OMOP Table)
20. OMOPConditionOccurrence.stop-reason
Definition

The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring.

ShortStop Reason
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
22. OMOPConditionOccurrence.provider-id
Definition

The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.

ShortProvider
Control0..1
TypeReference(Provider OMOP Table)
24. OMOPConditionOccurrence.visit-occurrence-id
Definition

The visit during which the condition occurred.

ShortVisit Occurrence
Control0..1
TypeReference(Visit Occurrence OMOP Table)
26. OMOPConditionOccurrence.visit-detail-id
Definition

The VISIT_DETAIL record during which the condition occurred. For example, if the person was in the ICU at the time of the diagnosis the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.

ShortVisit Detail
Control0..1
TypeReference(Visit Detail OMOP Table)
28. OMOPConditionOccurrence.condition-source-value
Definition

This field houses the verbatim value from the source data representing the condition that occurred. For example, this could be an ICD10 or Read code.

ShortCondition Source Value
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
30. OMOPConditionOccurrence.condition-source-concept-id
Definition

This is the concept representing the condition source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Condition necessary for a given analytic use case. Consider using CONDITION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.

ShortCondition Source Concept
Control0..1
TypeReference(Concept OMOP Table)
32. OMOPConditionOccurrence.condition-status-source-value
Definition

This field houses the verbatim value from the source data representing the condition status.

ShortCondition Status Source Value
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

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

0. OMOPConditionOccurrence
Definition

This table contains records of Events of a Person suggesting the presence of a disease or medical condition stated as a diagnosis, a sign, or a symptom, which is either observed by a Provider or reported by the patient.

ShortCondition Occurrence OMOP Table
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. OMOPConditionOccurrence.condition-occurrence-id
Definition

The unique key given to a condition record for a person. Refer to the ETL for how duplicate conditions during the same visit were handled.

ShortCondition Occurence Identifier
Control1..1
Typeinteger
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. OMOPConditionOccurrence.person-id
Definition

The PERSON_ID of the PERSON for whom the condition is recorded.

ShortPerson
Control1..1
TypeReference(Person OMOP Table)
6. OMOPConditionOccurrence.condition-concept-id
Definition

The CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a condition

ShortCondition
Control1..1
TypeReference(Concept OMOP Table)
8. OMOPConditionOccurrence.condition-start-date
Definition

Use this date to determine the start date of the condition

ShortCondition Start Date
Control1..1
Typedate
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. OMOPConditionOccurrence.condition-start-datetime
Definition

Condition Start Datetime

ShortCondition Start Datetime
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. OMOPConditionOccurrence.condition-end-date
Definition

Use this date to determine the end date of the condition

ShortCondition End Date
Control0..1
Typedate
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
14. OMOPConditionOccurrence.condition-end-datetime
Definition

Condition End Datetime

ShortCondition End Datetime
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
16. OMOPConditionOccurrence.condition-type-concept-id
Definition

This field can be used to determine the provenance of the Condition record, as in whether the condition was from an EHR system, insurance claim, registry, or other sources.

ShortCondition Type
Control1..1
TypeReference(Concept OMOP Table)
18. OMOPConditionOccurrence.condition-status-concept-id
Definition

This concept represents the point during the visit the diagnosis was given (admitting diagnosis, final diagnosis), whether the diagnosis was determined due to laboratory findings, if the diagnosis was exclusionary, or if it was a preliminary diagnosis, among others.

ShortCondition Status
Control0..1
TypeReference(Concept OMOP Table)
20. OMOPConditionOccurrence.stop-reason
Definition

The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring.

ShortStop Reason
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
22. OMOPConditionOccurrence.provider-id
Definition

The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.

ShortProvider
Control0..1
TypeReference(Provider OMOP Table)
24. OMOPConditionOccurrence.visit-occurrence-id
Definition

The visit during which the condition occurred.

ShortVisit Occurrence
Control0..1
TypeReference(Visit Occurrence OMOP Table)
26. OMOPConditionOccurrence.visit-detail-id
Definition

The VISIT_DETAIL record during which the condition occurred. For example, if the person was in the ICU at the time of the diagnosis the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.

ShortVisit Detail
Control0..1
TypeReference(Visit Detail OMOP Table)
28. OMOPConditionOccurrence.condition-source-value
Definition

This field houses the verbatim value from the source data representing the condition that occurred. For example, this could be an ICD10 or Read code.

ShortCondition Source Value
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
30. OMOPConditionOccurrence.condition-source-concept-id
Definition

This is the concept representing the condition source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Condition necessary for a given analytic use case. Consider using CONDITION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.

ShortCondition Source Concept
Control0..1
TypeReference(Concept OMOP Table)
32. OMOPConditionOccurrence.condition-status-source-value
Definition

This field houses the verbatim value from the source data representing the condition status.

ShortCondition Status Source Value
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension