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: OMOPConditionOccurrence - Detailed Descriptions

Draft as of 2025-10-23

Definitions for the OMOPConditionOccurrence 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. OMOPConditionOccurrence
Définition | 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.
Short | Condition Occurrence 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. OMOPConditionOccurrence.condition-occurrence-id
Définition | 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.
Short | Condition Occurence Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPConditionOccurrence.person-id
Définition | The PERSON_ID of the PERSON for whom the condition is recorded.
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPConditionOccurrence.condition-concept-id
Définition | 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
Short | Condition
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPConditionOccurrence.condition-start-date
Définition | Use this date to determine the start date of the condition
Short | Condition Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPConditionOccurrence.condition-start-datetime
Définition | Condition Start Datetime
Short | Condition Start Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPConditionOccurrence.condition-end-date
Définition | Use this date to determine the end date of the condition
Short | Condition End Date
Control | 0..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPConditionOccurrence.condition-end-datetime
Définition | Condition End Datetime
Short | Condition End Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPConditionOccurrence.condition-type-concept-id
Définition | 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.
Short | Condition Type
Control | 1..1
Type | Reference(Concept OMOP Table)
18. OMOPConditionOccurrence.condition-status-concept-id
Définition | 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.
Short | Condition Status
Control | 0..1
Type | Reference(Concept OMOP Table)
20. OMOPConditionOccurrence.stop-reason
Définition | 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.
Short | Stop Reason
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
22. OMOPConditionOccurrence.provider-id
Définition | The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.
Short | Provider
Control | 0..1
Type | Reference(Provider OMOP Table)
24. OMOPConditionOccurrence.visit-occurrence-id
Définition | The visit during which the condition occurred.
Short | Visit Occurrence
Control | 0..1
Type | Reference(Visit Occurrence OMOP Table)
26. OMOPConditionOccurrence.visit-detail-id
Définition | 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.
Short | Visit Detail
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
28. OMOPConditionOccurrence.condition-source-value
Définition | 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.
Short | Condition Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
30. OMOPConditionOccurrence.condition-source-concept-id
Définition | 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.
Short | Condition Source Concept
Control | 0..1
Type | Reference(Concept OMOP Table)
32. OMOPConditionOccurrence.condition-status-source-value
Définition | This field houses the verbatim value from the source data representing the condition status.
Short | Condition Status Source 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. OMOPConditionOccurrence
Définition | 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.
Short | Condition Occurrence OMOP Table
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. OMOPConditionOccurrence.condition-occurrence-id
Définition | 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.
Short | Condition Occurence Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPConditionOccurrence.person-id
Définition | The PERSON_ID of the PERSON for whom the condition is recorded.
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPConditionOccurrence.condition-concept-id
Définition | 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
Short | Condition
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPConditionOccurrence.condition-start-date
Définition | Use this date to determine the start date of the condition
Short | Condition Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPConditionOccurrence.condition-start-datetime
Définition | Condition Start Datetime
Short | Condition Start Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPConditionOccurrence.condition-end-date
Définition | Use this date to determine the end date of the condition
Short | Condition End Date
Control | 0..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPConditionOccurrence.condition-end-datetime
Définition | Condition End Datetime
Short | Condition End Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPConditionOccurrence.condition-type-concept-id
Définition | 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.
Short | Condition Type
Control | 1..1
Type | Reference(Concept OMOP Table)
18. OMOPConditionOccurrence.condition-status-concept-id
Définition | 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.
Short | Condition Status
Control | 0..1
Type | Reference(Concept OMOP Table)
20. OMOPConditionOccurrence.stop-reason
Définition | 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.
Short | Stop Reason
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
22. OMOPConditionOccurrence.provider-id
Définition | The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.
Short | Provider
Control | 0..1
Type | Reference(Provider OMOP Table)
24. OMOPConditionOccurrence.visit-occurrence-id
Définition | The visit during which the condition occurred.
Short | Visit Occurrence
Control | 0..1
Type | Reference(Visit Occurrence OMOP Table)
26. OMOPConditionOccurrence.visit-detail-id
Définition | 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.
Short | Visit Detail
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
28. OMOPConditionOccurrence.condition-source-value
Définition | 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.
Short | Condition Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
30. OMOPConditionOccurrence.condition-source-concept-id
Définition | 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.
Short | Condition Source Concept
Control | 0..1
Type | Reference(Concept OMOP Table)
32. OMOPConditionOccurrence.condition-status-source-value
Définition | This field houses the verbatim value from the source data representing the condition status.
Short | Condition Status Source 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. OMOPConditionOccurrence
Définition | 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.
Short | Condition Occurrence 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. OMOPConditionOccurrence.condition-occurrence-id
Définition | 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.
Short | Condition Occurence Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPConditionOccurrence.person-id
Définition | The PERSON_ID of the PERSON for whom the condition is recorded.
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPConditionOccurrence.condition-concept-id
Définition | 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
Short | Condition
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPConditionOccurrence.condition-start-date
Définition | Use this date to determine the start date of the condition
Short | Condition Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPConditionOccurrence.condition-start-datetime
Définition | Condition Start Datetime
Short | Condition Start Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPConditionOccurrence.condition-end-date
Définition | Use this date to determine the end date of the condition
Short | Condition End Date
Control | 0..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPConditionOccurrence.condition-end-datetime
Définition | Condition End Datetime
Short | Condition End Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPConditionOccurrence.condition-type-concept-id
Définition | 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.
Short | Condition Type
Control | 1..1
Type | Reference(Concept OMOP Table)
18. OMOPConditionOccurrence.condition-status-concept-id
Définition | 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.
Short | Condition Status
Control | 0..1
Type | Reference(Concept OMOP Table)
20. OMOPConditionOccurrence.stop-reason
Définition | 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.
Short | Stop Reason
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
22. OMOPConditionOccurrence.provider-id
Définition | The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.
Short | Provider
Control | 0..1
Type | Reference(Provider OMOP Table)
24. OMOPConditionOccurrence.visit-occurrence-id
Définition | The visit during which the condition occurred.
Short | Visit Occurrence
Control | 0..1
Type | Reference(Visit Occurrence OMOP Table)
26. OMOPConditionOccurrence.visit-detail-id
Définition | 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.
Short | Visit Detail
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
28. OMOPConditionOccurrence.condition-source-value
Définition | 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.
Short | Condition Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
30. OMOPConditionOccurrence.condition-source-concept-id
Définition | 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.
Short | Condition Source Concept
Control | 0..1
Type | Reference(Concept OMOP Table)
32. OMOPConditionOccurrence.condition-status-source-value
Définition | This field houses the verbatim value from the source data representing the condition status.
Short | Condition Status Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension