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

Draft as of 2025-10-23

Definitions for the OMOPVisitDetail 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. OMOPVisitDetail
Définition | The VISIT_DETAIL table is an optional table used to represents details of each record in the parent VISIT_OCCURRENCE table. A good example of this would be the movement between units in a hospital during an inpatient stay or claim lines associated with a one insurance claim. For every record in the VISIT_OCCURRENCE table there may be 0 or more records in the VISIT_DETAIL table with a 1:n relationship where n may be 0. The VISIT_DETAIL table is structurally very similar to VISIT_OCCURRENCE table and belongs to the visit domain.
Short | Visit Detail 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. OMOPVisitDetail.visit-detail-id
Définition | 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 detail.
Short | Visit Detail Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPVisitDetail.person-id
Définition | Person
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPVisitDetail.visit-detail-concept-id
Définition | This field contains a concept id representing the kind of visit detail, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain.
Short | Visit Detail
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPVisitDetail.visit-detail-start-date
Définition | This is the date of the start of the encounter. This may or may not be equal to the date of the Visit the Visit Detail is associated with.
Short | Visit Detail Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPVisitDetail.visit-detail-start-datetime
Définition | Visit Detail Start Datetime
Short | Visit Detail Start Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPVisitDetail.visit-detail-end-date
Définition | This the end date of the patient-provider interaction. 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 | Visit Detail End Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPVisitDetail.visit-detail-end-datetime
Définition | If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_datetime, then set the visit_end_datetime to the datetime of the data pull.
Short | Visit Detail End Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPVisitDetail.visit-detail-type-concept-id
Définition | Use this field to understand the provenance of the visit detail record, or where the record comes from.
Short | Visit Detail Type
Control | 1..1
Type | Reference(Concept OMOP Table)
18. OMOPVisitDetail.provider-id
Définition | There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). This is a typical reason for leveraging the VISIT_DETAIL table as even though each VISIT_DETAIL record can only have one provider, there is no limit to the number of VISIT_DETAIL records that can be associated to a VISIT_OCCURRENCE record.
Short | Provider
Control | 0..1
Type | Reference(Provider OMOP Table)
20. OMOPVisitDetail.care-site-id
Définition | This field provides information about the Care Site where the Visit Detail took place.
Short | Care Site
Control | 0..1
Type | Reference(CareSite OMOP Table)
22. OMOPVisitDetail.visit-detail-source-value
Définition | This field houses the verbatim value from the source data representing the kind of visit detail that took place (inpatient, outpatient, emergency, etc.)
Short | Visit Detail Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
24. OMOPVisitDetail.visit-detail-source-concept-id
Définition | Visit Detail Source Concept
Short | Visit Detail Source Concept
Control | 0..1
Type | Reference(Concept OMOP Table)
26. OMOPVisitDetail.admitted-from-concept-id
Définition | 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
Control | 0..1
Type | Reference(Concept OMOP Table)
28. OMOPVisitDetail.admitted-from-source-value
Définition | 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. OMOPVisitDetail.discharged-to-source-value
Définition | 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
32. OMOPVisitDetail.discharged-to-concept-id
Définition | Use this field to determine where the patient was discharged to after a visit. This concept is part of the visit domain and can indicate if a patient was transferred to another hospital or sent to a long-term care facility, for example. It is assumed that a person is discharged to home therefore there is not a standard concept id for "home". Use concept id = 0 when a person is discharged to home.
Short | Discharged To
Control | 0..1
Type | Reference(Concept OMOP Table)
34. OMOPVisitDetail.preceding-visit-detail-id
Définition | Use this field to find the visit detail that occurred for the person prior to the given visit detail record. There could be a few days or a few years in between.
Short | Preceding Visit
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
36. OMOPVisitDetail.parent-visit-detail-id
Définition | Use this field to find the visit detail that subsumes the given visit detail record. This is used in the case that a visit detail record needs to be nested beyond the VISIT_OCCURRENCE/VISIT_DETAIL relationship.
Short | Parent Visit
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
38. OMOPVisitDetail.visit-occurrence-id
Définition | Use this field to link the VISIT_DETAIL record to its VISIT_OCCURRENCE.
Short | Visit Occurrence
Control | 1..1
Type | Reference(Visit Occurrence OMOP Table)

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

0. OMOPVisitDetail
Définition | The VISIT_DETAIL table is an optional table used to represents details of each record in the parent VISIT_OCCURRENCE table. A good example of this would be the movement between units in a hospital during an inpatient stay or claim lines associated with a one insurance claim. For every record in the VISIT_OCCURRENCE table there may be 0 or more records in the VISIT_DETAIL table with a 1:n relationship where n may be 0. The VISIT_DETAIL table is structurally very similar to VISIT_OCCURRENCE table and belongs to the visit domain.
Short | Visit Detail OMOP Table
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. OMOPVisitDetail.visit-detail-id
Définition | 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 detail.
Short | Visit Detail Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPVisitDetail.person-id
Définition | Person
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPVisitDetail.visit-detail-concept-id
Définition | This field contains a concept id representing the kind of visit detail, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain.
Short | Visit Detail
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPVisitDetail.visit-detail-start-date
Définition | This is the date of the start of the encounter. This may or may not be equal to the date of the Visit the Visit Detail is associated with.
Short | Visit Detail Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPVisitDetail.visit-detail-start-datetime
Définition | Visit Detail Start Datetime
Short | Visit Detail Start Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPVisitDetail.visit-detail-end-date
Définition | This the end date of the patient-provider interaction. 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 | Visit Detail End Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPVisitDetail.visit-detail-end-datetime
Définition | If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_datetime, then set the visit_end_datetime to the datetime of the data pull.
Short | Visit Detail End Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPVisitDetail.visit-detail-type-concept-id
Définition | Use this field to understand the provenance of the visit detail record, or where the record comes from.
Short | Visit Detail Type
Control | 1..1
Type | Reference(Concept OMOP Table)
18. OMOPVisitDetail.provider-id
Définition | There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). This is a typical reason for leveraging the VISIT_DETAIL table as even though each VISIT_DETAIL record can only have one provider, there is no limit to the number of VISIT_DETAIL records that can be associated to a VISIT_OCCURRENCE record.
Short | Provider
Control | 0..1
Type | Reference(Provider OMOP Table)
20. OMOPVisitDetail.care-site-id
Définition | This field provides information about the Care Site where the Visit Detail took place.
Short | Care Site
Control | 0..1
Type | Reference(CareSite OMOP Table)
22. OMOPVisitDetail.visit-detail-source-value
Définition | This field houses the verbatim value from the source data representing the kind of visit detail that took place (inpatient, outpatient, emergency, etc.)
Short | Visit Detail Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
24. OMOPVisitDetail.visit-detail-source-concept-id
Définition | Visit Detail Source Concept
Short | Visit Detail Source Concept
Control | 0..1
Type | Reference(Concept OMOP Table)
26. OMOPVisitDetail.admitted-from-concept-id
Définition | 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
Control | 0..1
Type | Reference(Concept OMOP Table)
28. OMOPVisitDetail.admitted-from-source-value
Définition | 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. OMOPVisitDetail.discharged-to-source-value
Définition | 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
32. OMOPVisitDetail.discharged-to-concept-id
Définition | Use this field to determine where the patient was discharged to after a visit. This concept is part of the visit domain and can indicate if a patient was transferred to another hospital or sent to a long-term care facility, for example. It is assumed that a person is discharged to home therefore there is not a standard concept id for "home". Use concept id = 0 when a person is discharged to home.
Short | Discharged To
Control | 0..1
Type | Reference(Concept OMOP Table)
34. OMOPVisitDetail.preceding-visit-detail-id
Définition | Use this field to find the visit detail that occurred for the person prior to the given visit detail record. There could be a few days or a few years in between.
Short | Preceding Visit
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
36. OMOPVisitDetail.parent-visit-detail-id
Définition | Use this field to find the visit detail that subsumes the given visit detail record. This is used in the case that a visit detail record needs to be nested beyond the VISIT_OCCURRENCE/VISIT_DETAIL relationship.
Short | Parent Visit
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
38. OMOPVisitDetail.visit-occurrence-id
Définition | Use this field to link the VISIT_DETAIL record to its VISIT_OCCURRENCE.
Short | Visit Occurrence
Control | 1..1
Type | Reference(Visit Occurrence OMOP Table)

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

0. OMOPVisitDetail
Définition | The VISIT_DETAIL table is an optional table used to represents details of each record in the parent VISIT_OCCURRENCE table. A good example of this would be the movement between units in a hospital during an inpatient stay or claim lines associated with a one insurance claim. For every record in the VISIT_OCCURRENCE table there may be 0 or more records in the VISIT_DETAIL table with a 1:n relationship where n may be 0. The VISIT_DETAIL table is structurally very similar to VISIT_OCCURRENCE table and belongs to the visit domain.
Short | Visit Detail 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. OMOPVisitDetail.visit-detail-id
Définition | 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 detail.
Short | Visit Detail Identifier
Control | 1..1
Type | integer
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
4. OMOPVisitDetail.person-id
Définition | Person
Short | Person
Control | 1..1
Type | Reference(Person OMOP Table)
6. OMOPVisitDetail.visit-detail-concept-id
Définition | This field contains a concept id representing the kind of visit detail, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain.
Short | Visit Detail
Control | 1..1
Type | Reference(Concept OMOP Table)
8. OMOPVisitDetail.visit-detail-start-date
Définition | This is the date of the start of the encounter. This may or may not be equal to the date of the Visit the Visit Detail is associated with.
Short | Visit Detail Start Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
10. OMOPVisitDetail.visit-detail-start-datetime
Définition | Visit Detail Start Datetime
Short | Visit Detail Start Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. OMOPVisitDetail.visit-detail-end-date
Définition | This the end date of the patient-provider interaction. 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 | Visit Detail End Date
Control | 1..1
Type | date
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. OMOPVisitDetail.visit-detail-end-datetime
Définition | If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_datetime, then set the visit_end_datetime to the datetime of the data pull.
Short | Visit Detail End Datetime
Control | 0..1
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
16. OMOPVisitDetail.visit-detail-type-concept-id
Définition | Use this field to understand the provenance of the visit detail record, or where the record comes from.
Short | Visit Detail Type
Control | 1..1
Type | Reference(Concept OMOP Table)
18. OMOPVisitDetail.provider-id
Définition | There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). This is a typical reason for leveraging the VISIT_DETAIL table as even though each VISIT_DETAIL record can only have one provider, there is no limit to the number of VISIT_DETAIL records that can be associated to a VISIT_OCCURRENCE record.
Short | Provider
Control | 0..1
Type | Reference(Provider OMOP Table)
20. OMOPVisitDetail.care-site-id
Définition | This field provides information about the Care Site where the Visit Detail took place.
Short | Care Site
Control | 0..1
Type | Reference(CareSite OMOP Table)
22. OMOPVisitDetail.visit-detail-source-value
Définition | This field houses the verbatim value from the source data representing the kind of visit detail that took place (inpatient, outpatient, emergency, etc.)
Short | Visit Detail Source Value
Control | 0..1
Type | string
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
24. OMOPVisitDetail.visit-detail-source-concept-id
Définition | Visit Detail Source Concept
Short | Visit Detail Source Concept
Control | 0..1
Type | Reference(Concept OMOP Table)
26. OMOPVisitDetail.admitted-from-concept-id
Définition | 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
Control | 0..1
Type | Reference(Concept OMOP Table)
28. OMOPVisitDetail.admitted-from-source-value
Définition | 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. OMOPVisitDetail.discharged-to-source-value
Définition | 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
32. OMOPVisitDetail.discharged-to-concept-id
Définition | Use this field to determine where the patient was discharged to after a visit. This concept is part of the visit domain and can indicate if a patient was transferred to another hospital or sent to a long-term care facility, for example. It is assumed that a person is discharged to home therefore there is not a standard concept id for "home". Use concept id = 0 when a person is discharged to home.
Short | Discharged To
Control | 0..1
Type | Reference(Concept OMOP Table)
34. OMOPVisitDetail.preceding-visit-detail-id
Définition | Use this field to find the visit detail that occurred for the person prior to the given visit detail record. There could be a few days or a few years in between.
Short | Preceding Visit
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
36. OMOPVisitDetail.parent-visit-detail-id
Définition | Use this field to find the visit detail that subsumes the given visit detail record. This is used in the case that a visit detail record needs to be nested beyond the VISIT_OCCURRENCE/VISIT_DETAIL relationship.
Short | Parent Visit
Control | 0..1
Type | Reference(Visit Detail OMOP Table)
38. OMOPVisitDetail.visit-occurrence-id
Définition | Use this field to link the VISIT_DETAIL record to its VISIT_OCCURRENCE.
Short | Visit Occurrence
Control | 1..1
Type | Reference(Visit Occurrence OMOP Table)