Condition Occurrence
Conditions are records 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. Conditions are recorded in different sources and levels of standardization, for example:
- Diagnoses
- Patient self-reported conditions
- EHR collected problem lists
Note that the diagnosis table is not a cohort list. It is simply the recorded states of the patient. Creation of Cohorts is done using the COHORT table. This is created during processing rather than being submitted by the sites.
| Field | Required | Type | FK Table | Description |
|---|---|---|---|---|
| condition_occurrence_id | Yes | bigint | A unique identifier for each Condition Occurrence event. | |
| person_id | Yes | bigint | PERSON | A foreign key identifier to the Person who is experiencing the condition. The demographic details of that Person are stored in the PERSON table. |
| condition_concept_id | Yes | bigint | CONCEPT | A foreign key that refers to the Concept identifier representing the condition. |
| condition_start_date | Yes | date | ||
| condition_start_datetime | No | datetime | ||
| condition_end_date | No | date | ||
| condition_end_datetime | No | datetime | ||
| condition_type_concept_id | Yes | bigint | CONCEPT | The Concept that represents the type of diagnosis this is (e.g. billing, self-reported, problem list). |
| stop_reason | No | varchar(20) | Not used. | |
| provider_id | No | bigint | PROVIDER | Not used. |
| visit_occurrence_id | No | bigint | VISIT_OCCURRENCE | |
| visit_detail_id | No | bigint | VISIT_DETAIL | 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. |
| condition_source_value | No | varchar(50) | Not used. | |
| condition_source_concept_id | No | bigint | CONCEPT | Not used. |
| condition_status_source_value | No | varchar(50) | Not used. | |
| condition_status_concept_id | No | bigint | CONCEPT | The status of the diagnosis. |
| last_updated_datetime | Yes | datetime | Initially this is the time the row was written to OMOP. If the row is subsequently updated, it then becomes the most recent update time. | |
| deleted_datetime | No | datetime | NULL
initially. Set to the time when the row was marked for deletion. A value in this column sent to the central data source will result in this row being deleted (by person_id
) from the combined dataset. Deletions only need to be sent once. |
Conventions
- Valid Condition Concepts belong to the “Condition” domain.
- Condition records are typically inferred from diagnostic codes recorded in the source data. Such code systems like ICD-10, SNOMED, etc., provide a comprehensive coverage of conditions. However, if the diagnostic code in the source does not define a Condition, but rather an Observation or a Procedure, then such information is not stored in the CONDITION_OCCURRENCE table, but in the respective tables instead.