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.
integer
Yes
No
person_id*
integer
No
Yes
PERSON
visit_detail_
concept_id*
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.
integer
No
Yes
CONCEPT
visit_detail_start_date*
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.
date
No
No
visit_detail_start_datetime
datetime
No
No
visit_detail_end_
date*
This the end date of the patient-provider interaction.
date
No
No
visit_detail_end_
datetime
datetime
No
No
visit_detail_type_
concept_id*
Use this field to understand the provenance of the visit detail
record, or where the record comes from.
integer
No
Yes
CONCEPT
provider_id
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.
integer
No
Yes
PROVIDER
care_site_id
This field provides information about the Care Site where the Visit
Detail took place.
integer
No
Yes
CARE_SITE
visit_detail_
source_value
This field houses the verbatim value from the source data
representing the kind of visit detail that took place (inpatient,
outpatient, emergency, etc.)
varchar(50)
No
No
visit_detail_source_concept_id
Integer
No
Yes
CONCEPT
preceding_visit_detail_id
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.
integer
No
Yes
VISIT_DETAIL
visit_detail_parent_id
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.
integer
No
Yes
VISIT_DETAIL
visit_occurrence_id*
Use this field to link the VISIT_DETAIL record to its
VISIT_OCCURRENCE.