Guide d'implémentation du GT Standards et Interopérabilité pour les EDS
0.1.0 - ci-build
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
Draft as of 2024-11-23 |
Definitions for the OMOPVisitOccurrence logical model.
Guidance on how to interpret the contents of this table can be found here
0. OMOPVisitOccurrence | |
Definition | This table contains Events where Persons engage with the healthcare system for a duration of time. They are often also called "Encounters". Visits are defined by a configuration of circumstances under which they occur, such as (i) whether the patient comes to a healthcare institution, the other way around, or the interaction is remote, (ii) whether and what kind of trained medical staff is delivering the service during the Visit, and (iii) whether the Visit is transient or for a longer period involving a stay in bed. |
Short | Visit Occurrence OMOP Table |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. OMOPVisitOccurrence.visit-occurrence-id | |
Definition | Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit. |
Short | Visit Occurrence Identifier |
Control | 1..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
4. OMOPVisitOccurrence.person-id | |
Definition | Person |
Short | Person |
Control | 1..1 |
Type | Reference(Person OMOP Table) |
6. OMOPVisitOccurrence.visit-concept-id | |
Definition | This field contains a concept id representing the kind of visit, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain. |
Short | Visit |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
8. OMOPVisitOccurrence.visit-start-date | |
Definition | For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same. |
Short | Start Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
10. OMOPVisitOccurrence.visit-start-datetime | |
Definition | Start Datetime |
Short | Start Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
12. OMOPVisitOccurrence.visit-end-date | |
Definition | For inpatient visits the end date is typically the discharge date. If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_date, then set the visit_end_date to the date of the data pull. |
Short | End Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
14. OMOPVisitOccurrence.visit-end-datetime | |
Definition | End Datetime |
Short | End Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
16. OMOPVisitOccurrence.visit-type-concept-id | |
Definition | Use this field to understand the provenance of the visit record, or where the record comes from. |
Short | Visit Type |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
18. OMOPVisitOccurrence.provider-id | |
Definition | There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). If there are multiple providers associated with a visit in the source, this can be reflected in the event tables (CONDITION_OCCURRENCE, PROCEDURE_OCCURRENCE, etc.) or in the VISIT_DETAIL table. |
Short | Provider |
Control | 0..1 |
Type | Reference(Provider OMOP Table) |
20. OMOPVisitOccurrence.care-site-id | |
Definition | This field provides information about the Care Site where the Visit took place. |
Short | Care Site |
Control | 0..1 |
Type | Reference(CareSite OMOP Table) |
22. OMOPVisitOccurrence.visit-source-value | |
Definition | This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.) |
Short | Visit Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
24. OMOPVisitOccurrence.visit-source-concept-id | |
Definition | Visit Source Concept |
Short | Visit Source Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
26. OMOPVisitOccurrence.admitted-from-concept-id | |
Definition | Use this field to determine where the patient was admitted from. This concept is part of the visit domain and can indicate if a patient was admitted to the hospital from a long-term care facility, for example. |
Short | Admitted From Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
28. OMOPVisitOccurrence.admitted-from-source-value | |
Definition | Admitted From Source Value |
Short | Admitted From Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
30. OMOPVisitOccurrence.discharged-to-concept-id | |
Definition | Discharged To Concept |
Short | Discharged To Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
32. OMOPVisitOccurrence.discharged-to-source-value | |
Definition | Discharged To Source Value |
Short | Discharged To Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
34. OMOPVisitOccurrence.preceding-visit-occurrence-id | |
Definition | Use this field to find the visit that occurred for the person prior to the given visit. There could be a few days or a few years in between. |
Short | Preceding Visit Occurrence |
Control | 0..1 |
Type | Reference(Visit Occurrence OMOP Table) |
Guidance on how to interpret the contents of this table can be found here
0. OMOPVisitOccurrence | |
Definition | This table contains Events where Persons engage with the healthcare system for a duration of time. They are often also called "Encounters". Visits are defined by a configuration of circumstances under which they occur, such as (i) whether the patient comes to a healthcare institution, the other way around, or the interaction is remote, (ii) whether and what kind of trained medical staff is delivering the service during the Visit, and (iii) whether the Visit is transient or for a longer period involving a stay in bed. |
Short | Visit 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. OMOPVisitOccurrence.visit-occurrence-id | |
Definition | Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit. |
Short | Visit Occurrence Identifier |
Control | 1..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
4. OMOPVisitOccurrence.person-id | |
Definition | Person |
Short | Person |
Control | 1..1 |
Type | Reference(Person OMOP Table) |
6. OMOPVisitOccurrence.visit-concept-id | |
Definition | This field contains a concept id representing the kind of visit, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain. |
Short | Visit |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
8. OMOPVisitOccurrence.visit-start-date | |
Definition | For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same. |
Short | Start Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
10. OMOPVisitOccurrence.visit-start-datetime | |
Definition | Start Datetime |
Short | Start Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
12. OMOPVisitOccurrence.visit-end-date | |
Definition | For inpatient visits the end date is typically the discharge date. If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_date, then set the visit_end_date to the date of the data pull. |
Short | End Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
14. OMOPVisitOccurrence.visit-end-datetime | |
Definition | End Datetime |
Short | End Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
16. OMOPVisitOccurrence.visit-type-concept-id | |
Definition | Use this field to understand the provenance of the visit record, or where the record comes from. |
Short | Visit Type |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
18. OMOPVisitOccurrence.provider-id | |
Definition | There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). If there are multiple providers associated with a visit in the source, this can be reflected in the event tables (CONDITION_OCCURRENCE, PROCEDURE_OCCURRENCE, etc.) or in the VISIT_DETAIL table. |
Short | Provider |
Control | 0..1 |
Type | Reference(Provider OMOP Table) |
20. OMOPVisitOccurrence.care-site-id | |
Definition | This field provides information about the Care Site where the Visit took place. |
Short | Care Site |
Control | 0..1 |
Type | Reference(CareSite OMOP Table) |
22. OMOPVisitOccurrence.visit-source-value | |
Definition | This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.) |
Short | Visit Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
24. OMOPVisitOccurrence.visit-source-concept-id | |
Definition | Visit Source Concept |
Short | Visit Source Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
26. OMOPVisitOccurrence.admitted-from-concept-id | |
Definition | Use this field to determine where the patient was admitted from. This concept is part of the visit domain and can indicate if a patient was admitted to the hospital from a long-term care facility, for example. |
Short | Admitted From Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
28. OMOPVisitOccurrence.admitted-from-source-value | |
Definition | Admitted From Source Value |
Short | Admitted From Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
30. OMOPVisitOccurrence.discharged-to-concept-id | |
Definition | Discharged To Concept |
Short | Discharged To Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
32. OMOPVisitOccurrence.discharged-to-source-value | |
Definition | Discharged To Source Value |
Short | Discharged To Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
34. OMOPVisitOccurrence.preceding-visit-occurrence-id | |
Definition | Use this field to find the visit that occurred for the person prior to the given visit. There could be a few days or a few years in between. |
Short | Preceding Visit Occurrence |
Control | 0..1 |
Type | Reference(Visit Occurrence OMOP Table) |
Guidance on how to interpret the contents of this table can be found here
0. OMOPVisitOccurrence | |
Definition | This table contains Events where Persons engage with the healthcare system for a duration of time. They are often also called "Encounters". Visits are defined by a configuration of circumstances under which they occur, such as (i) whether the patient comes to a healthcare institution, the other way around, or the interaction is remote, (ii) whether and what kind of trained medical staff is delivering the service during the Visit, and (iii) whether the Visit is transient or for a longer period involving a stay in bed. |
Short | Visit 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. OMOPVisitOccurrence.visit-occurrence-id | |
Definition | Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit. |
Short | Visit Occurrence Identifier |
Control | 1..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
4. OMOPVisitOccurrence.person-id | |
Definition | Person |
Short | Person |
Control | 1..1 |
Type | Reference(Person OMOP Table) |
6. OMOPVisitOccurrence.visit-concept-id | |
Definition | This field contains a concept id representing the kind of visit, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain. |
Short | Visit |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
8. OMOPVisitOccurrence.visit-start-date | |
Definition | For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same. |
Short | Start Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
10. OMOPVisitOccurrence.visit-start-datetime | |
Definition | Start Datetime |
Short | Start Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
12. OMOPVisitOccurrence.visit-end-date | |
Definition | For inpatient visits the end date is typically the discharge date. If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_date, then set the visit_end_date to the date of the data pull. |
Short | End Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
14. OMOPVisitOccurrence.visit-end-datetime | |
Definition | End Datetime |
Short | End Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
16. OMOPVisitOccurrence.visit-type-concept-id | |
Definition | Use this field to understand the provenance of the visit record, or where the record comes from. |
Short | Visit Type |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
18. OMOPVisitOccurrence.provider-id | |
Definition | There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). If there are multiple providers associated with a visit in the source, this can be reflected in the event tables (CONDITION_OCCURRENCE, PROCEDURE_OCCURRENCE, etc.) or in the VISIT_DETAIL table. |
Short | Provider |
Control | 0..1 |
Type | Reference(Provider OMOP Table) |
20. OMOPVisitOccurrence.care-site-id | |
Definition | This field provides information about the Care Site where the Visit took place. |
Short | Care Site |
Control | 0..1 |
Type | Reference(CareSite OMOP Table) |
22. OMOPVisitOccurrence.visit-source-value | |
Definition | This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.) |
Short | Visit Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
24. OMOPVisitOccurrence.visit-source-concept-id | |
Definition | Visit Source Concept |
Short | Visit Source Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
26. OMOPVisitOccurrence.admitted-from-concept-id | |
Definition | Use this field to determine where the patient was admitted from. This concept is part of the visit domain and can indicate if a patient was admitted to the hospital from a long-term care facility, for example. |
Short | Admitted From Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
28. OMOPVisitOccurrence.admitted-from-source-value | |
Definition | Admitted From Source Value |
Short | Admitted From Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
30. OMOPVisitOccurrence.discharged-to-concept-id | |
Definition | Discharged To Concept |
Short | Discharged To Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
32. OMOPVisitOccurrence.discharged-to-source-value | |
Definition | Discharged To Source Value |
Short | Discharged To Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
34. OMOPVisitOccurrence.preceding-visit-occurrence-id | |
Definition | Use this field to find the visit that occurred for the person prior to the given visit. There could be a few days or a few years in between. |
Short | Preceding Visit Occurrence |
Control | 0..1 |
Type | Reference(Visit Occurrence OMOP Table) |