documentation:cdm:visit_occurrence
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
documentation:cdm:visit_occurrence [2017/01/08 18:12] cgreich |
documentation:cdm:visit_occurrence [2017/02/07 03:37] cukarthik |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== VISIT_OCCURRENCE table ===== | ===== VISIT_OCCURRENCE table ===== | ||
| - | This table changed version 5.X of the OMOP CDM. The fields admitting_source_concept_id, discharge_to_concept_id, admitting_source_value and discharge_to_source_value were added. | + | This table changed version 5.1 of the OMOP CDM. The fields visit_start_datetime and visit_end_datetime were added. For 5.0.1, the fields admitting_source_concept_id, discharge_to_concept_id, admitting_source_value and discharge_to_source_value were added. |
| ---- | ---- | ||
| Line 19: | Line 19: | ||
| |admitting_source_concept_id|No|integer|A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the admitting source for a visit.| | |admitting_source_concept_id|No|integer|A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the admitting source for a visit.| | ||
| |discharge_to_concept_id|No|integer|A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the discharge disposition (destination) for a visit.| | |discharge_to_concept_id|No|integer|A foreign key to the predefined concept in the Place of Service Vocabulary reflecting the discharge disposition (destination) for a visit.| | ||
| + | |preceding_visit_occurrence_id|No|integer|A foreign key to the VISIT_OCCURRENCE table record of the visit immediately preceding this visit.| | ||
| |visit_source_value|No|string(50)|The source code for the visit as it appears in the source data.| | |visit_source_value|No|string(50)|The source code for the visit as it appears in the source data.| | ||
| |visit_source_concept_id|No|Integer|A foreign key to a Concept that refers to the code used in the source.| | |visit_source_concept_id|No|Integer|A foreign key to a Concept that refers to the code used in the source.| | ||
| Line 28: | Line 29: | ||
| * A Visit Occurrence is recorded for each visit to a healthcare facility. | * A Visit Occurrence is recorded for each visit to a healthcare facility. | ||
| * Valid Visit Concepts belong to the "Visit" domain. | * Valid Visit Concepts belong to the "Visit" domain. | ||
| - | * Standard Visit Concepts are defined as Inpatient Visit, Outpatient Visit, Emergency Room Visit and Long Term Care Visit. Source Concepts from place of service vocabularies are mapped into these standard visit Concepts in the Standardized Vocabularies. Each Visit is standardized by assigning a corresponding Concept Identifier based on the type of facility visited and the type of services rendered. | + | * Standard Visit Concepts are defined as Inpatient Visit, Outpatient Visit, Emergency Room Visit, Long Term Care Visit and combined ER and Inpatient Visit. The latter is necessary because it is close to impossible to separate the two in many EHR system, treating them interchangeably. To annotate this correctly, the visit concept “Emergency Room and Inpatient Visit” (concept_id=262) should be used. |
| + | * Handling of death: In case when patient died during admission (Visit_Occurrence. discharge_disposition_concept_id = 4216643 ‘Patient died’), a record in the Death table should be created with death_type_concept_id = 44818516 (“EHR discharge status "Expired"). | ||
| + | * Source Concepts from place of service vocabularies are mapped into these standard visit Concepts in the Standardized Vocabularies. | ||
| * At any one day, there could be more than one visit. | * At any one day, there could be more than one visit. | ||
| * One visit may involve multiple providers, in which case the ETL must specify how a single provider id is selected or leave the provider_id field null. | * One visit may involve multiple providers, in which case the ETL must specify how a single provider id is selected or leave the provider_id field null. | ||
| Line 35: | Line 38: | ||
| * Medical Claims include Inpatient Admissions, Outpatient Services, and Emergency Room visits. | * Medical Claims include Inpatient Admissions, Outpatient Services, and Emergency Room visits. | ||
| * Electronic Health Records may capture Person visits as part of the activities recorded depending wether the EHR system is used at the different Care Sites. | * Electronic Health Records may capture Person visits as part of the activities recorded depending wether the EHR system is used at the different Care Sites. | ||
| - | * If applicable, the sequential relationships between Visits within an episode of care may be represented in the FACT_RELATIONSHIP table. | + | * Sequential relationships between Visits within an episode of care are represented through chaining them in the preceding_visit_occurrence_id. |
| - | * Handling of death: In case when patient died during admission (Visit_Occurrence. discharge_disposition_concept_id = 4216643 ‘Patient died’), a record in the Death table should be created with death_type_concept_id = 44818516 (“EHR discharge status "Expired"). | + | |
| - | * Handling of ER visits resulting in hospitalization: Some EMR systems combine emergency room followed by inpatient admission into one visit, and it is close to impossible to separate the two. To annotate this visit type, a new visit type concept “Emergency Room and Inpatient Admission” should be used. | + | |
documentation/cdm/visit_occurrence.txt · Last modified: 2017/09/25 15:00 by clairblacketer
Page Tools
