VisitOccurrence
type: StructureDefinition
node role: treeRoot
id:
  v: VisitOccurrence
language:
  v: en
text:
  status:
    v: extensions
  div:
    v: Generated Narrative: StructureDefinition VisitOccurrence Language: en Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> <a href="StructureDefinition-VisitOccurrence-definitions.html#VisitOccurrence" title="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.">VisitOccurrence 0..* Base Visit Occurrence OMOP Table Instances of this logical model can be the target of a Reference #xD; visit_occurrence_id 1..1 integer Visit Occurrence Identifier #xD; person_id 1..1 Reference(Person OMOP Table) Person #xD; visit_concept_id 1..1 code Visit #xD; visit_start_date 1..1 date Start Date #xD; visit_start_datetime 0..1 dateTime Start Datetime #xD; visit_end_date 1..1 date End Date #xD; visit_end_datetime 0..1 dateTime End Datetime #xD; visit_type_concept_id 1..1 code Visit Type #xD; <a href="StructureDefinition-VisitOccurrence-definitions.html#VisitOccurrence.provider-id" title="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.">provider_id 0..1 Reference(Provider OMOP Table) Provider #xD; care_site_id 0..1 Reference(CareSite OMOP Table) Care Site #xD; visit_source_value 0..1 string Visit Source Value #xD; visit_source_concept_id 0..1 code Visit Source Concept #xD; admitted_f…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-type-characteristics
    l: structuredefinition-type-characteristics
  value: Code
    v: can-be-target
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: brr
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 1
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop
        l: hl7.fhir.uv.omop
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: informative
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop
        l: hl7.fhir.uv.omop
url:
  v: http://hl7.org/fhir/uv/omop/StructureDefinition/VisitOccurrence
  l: VisitOccurrence
version:
  v: 1.0.0
name:
  v: VisitOccurrence
title:
  v: Visit Occurrence OMOP Table
status:
  v: active
date:
  v: 2026-02-12T17:30:34+00:00
publisher:
  v: HL7 International / Biomedical Research and Regulation
contact:
  name:
    v: HL7 International / Biomedical Research and Regulation
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/rcrim
description:
  v: 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.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
fhir version:
  v: 5.0.0
mapping:
  identity:
    v: rim
  uri:
    v: http://hl7.org/v3
    l: v3
  name:
    v: RIM Mapping
kind:
  v: logical
abstract:
  v: false
type:
  v: http://hl7.org/fhir/uv/omop/StructureDefinition/VisitOccurrence
  l: VisitOccurrence
base definition:
  v: http://hl7.org/fhir/StructureDefinition/Base
  l: Base
derivation:
  v: specialization
snapshot:
  extension:
    url:
      v: http://hl7.org/fhir/tools/StructureDefinition/snapshot-base-version
      l: snapshot-base-version
    value: String
      v: 5.0.0
  element:
    id:
      v: VisitOccurrence
    path:
      v: VisitOccurrence
    short:
      v: Visit Occurrence OMOP Table
    definition:
      v: 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.
    min:
      v: 0
    max:
      v: *
    base:
      path:
        v: Base
      min:
        v: 0
      max:
        v: *
    is modifier:
      v: false
    mapping:
      identity:
        v: rim
      map:
        v: n/a
  element:
    id:
      v: VisitOccurrence.visit-occurrence-id
    path:
      v: VisitOccurrence.visit_occurrence_id
    short:
      v: Visit Occurrence Identifier
    definition:
      v: 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.
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: VisitOccurrence.visit_occurrence_id
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: integer
        l: integer
  element:
    id:
      v: VisitOccurrence.person-id
    path:
      v: VisitOccurrence.person_id
    short:
      v: Person
    definition:
      v: Person
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: VisitOccurrence.person_id
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: Reference
        l: Reference
      target profile:
        v: http://hl7.org/fhir/uv/omop/StructureDefinition/Person
        l: Person
  element:
    id:
      v: VisitOccurrence.visit-concept-id
    path:
      v: VisitOccurrence.visit_concept_id
    short:
      v: Visit
    definition:
      v: 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.
    min:
      v: 1
    max:
      v: 1

path:
  v: VisitOccurrence.visit_concept_id
min:
  v: 1
max:
  v: 1

code:
  v: code
  l: code

id:
  v: VisitOccurrence.visit-start-date
path:
  v: VisitOccurrence.visit_start_date
short:
  v: Start Date
definition:
  v: For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same.
min:
  v: 1
max:
  v: 1
base:
  path:
    v: VisitOccurrence.visit_start_date
  min:
    v: 1
  max:
    v: 1
type:
  code:
    v: date
    l: date

id:
  v: VisitOccurrence.visit-start-datetime
path:
  v: VisitOccurrence.visit_start_datetime
short:
  v: Start Datetime
definition:
  v: Start Datetime
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.visit_start_datetime
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: dateTime
    l: dateTime

id:
  v: VisitOccurrence.visit-end-date
path:
  v: VisitOccurrence.visit_end_date
short:
  v: End Date
definition:
  v: 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.
min:
  v: 1
max:
  v: 1
base:
  path:
    v: VisitOccurrence.visit_end_date
  min:
    v: 1
  max:
    v: 1
type:
  code:
    v: date
    l: date

id:
  v: VisitOccurrence.visit-end-datetime
path:
  v: VisitOccurrence.visit_end_datetime
short:
  v: End Datetime
definition:
  v: End Datetime
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.visit_end_datetime
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: dateTime
    l: dateTime

id:
  v: VisitOccurrence.visit-type-concept-id
path:
  v: VisitOccurrence.visit_type_concept_id
short:
  v: Visit Type
definition:
  v: Use this field to understand the provenance of the visit record, or where the record comes from.
min:
  v: 1
max:
  v: 1
base:
  path:
    v: VisitOccurrence.visit_type_concept_id
  min:
    v: 1
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: VisitOccurrence.provider-id
path:
  v: VisitOccurrence.provider_id
short:
  v: Provider
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.provider_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
    l: Reference
  target profile:
    v: http://hl7.org/fhir/uv/omop/StructureDefinition/Provider
    l: Provider

id:
  v: VisitOccurrence.care-site-id
path:
  v: VisitOccurrence.care_site_id
short:
  v: Care Site
definition:
  v: This field provides information about the Care Site where the Visit took place.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.care_site_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
    l: Reference
  target profile:
    v: http://hl7.org/fhir/uv/omop/StructureDefinition/CareSite
    l: CareSite

id:
  v: VisitOccurrence.visit-source-value
path:
  v: VisitOccurrence.visit_source_value
short:
  v: Visit Source Value
definition:
  v: This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.)
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.visit_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

id:
  v: VisitOccurrence.visit-source-concept-id
path:
  v: VisitOccurrence.visit_source_concept_id
short:
  v: Visit Source Concept
definition:
  v: Visit Source Concept
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.visit_source_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: VisitOccurrence.admitted-from-concept-id
path:
  v: VisitOccurrence.admitted_from_concept_id
short:
  v: Admitted From Concept
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.admitted_from_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: VisitOccurrence.admitted-from-source-value
path:
  v: VisitOccurrence.admitted_from_source_value
short:
  v: Admitted From Source Value
definition:
  v: Admitted From Source Value
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.admitted_from_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

id:
  v: VisitOccurrence.discharged-to-concept-id
path:
  v: VisitOccurrence.discharged_to_concept_id
short:
  v: Discharged To Concept
definition:
  v: Discharged To Concept
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.discharged_to_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: VisitOccurrence.discharged-to-source-value
path:
  v: VisitOccurrence.discharged_to_source_value
short:
  v: Discharged To Source Value
definition:
  v: Discharged To Source Value
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.discharged_to_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

id:
  v: VisitOccurrence.preceding-visit-occurrence-id
path:
  v: VisitOccurrence.preceding_visit_occurrence_id
short:
  v: Preceding Visit Occurrence
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: VisitOccurrence.preceding_visit_occurrence_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
    l: Reference
  target profile:
    v: http://hl7.org/fhir/uv/omop/StructureDefinition/VisitOccurrence
    l: VisitOccurrence

element:
  id:
    v: VisitOccurrence
  path:
    v: VisitOccurrence
  short:
    v: Visit Occurrence OMOP Table
  definition:
    v: 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.
element:
  id:
    v: VisitOccurrence.visit-occurrence-id
  path:
    v: VisitOccurrence.visit_occurrence_id
  short:
    v: Visit Occurrence Identifier
  definition:
    v: 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.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: integer
      l: integer
element:
  id:
    v: VisitOccurrence.person-id
  path:
    v: VisitOccurrence.person_id
  short:
    v: Person
  definition:
    v: Person
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: Reference
      l: Reference
    target profile:
      v: http://hl7.org/fhir/uv/omop/StructureDefinition/Person
      l: Person
element:
  id:
    v: VisitOccurrence.visit-concept-id
  path:
    v: VisitOccurrence.visit_concept_id
  short:
    v: Visit
  definition:
    v: 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.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: VisitOccurrence.visit-start-date
  path:
    v: VisitOccurrence.visit_start_date
  short:
    v: Start Date
  definition:
    v: For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: date
      l: date
element:
  id:
    v: VisitOccurrence.visit-start-datetime
  path:
    v: VisitOccurrence.visit_start_datetime
  short:
    v: Start Datetime
  definition:
    v: Start Datetime
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: dateTime
      l: dateTime
element:
  id:
    v: VisitOccurrence.visit-end-date
  path:
    v: VisitOccurrence.visit_end_date
  short:
    v: End Date
  definition:
    v: 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.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: date
      l: date
element:
  id:
    v: VisitOccurrence.visit-end-datetime
  path:
    v: VisitOccurrence.visit_end_datetime
  short:
    v: End Datetime
  definition:
    v: End Datetime
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: dateTime
      l: dateTime
element:
  id:
    v: VisitOccurrence.visit-type-concept-id
  path:
    v: VisitOccurrence.visit_type_concept_id
  short:
    v: Visit Type
  definition:
    v: Use this field to understand the provenance of the visit record, or where the record comes from.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: VisitOccurrence.provider-id
  path:
    v: VisitOccurrence.provider_id
  short:
    v: Provider
  definition:
    v: 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.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: Reference
      l: Reference
    target profile:
      v: http://hl7.org/fhir/uv/omop/StructureDefinition/Provider
      l: Provider
element:
  id:
    v: VisitOccurrence.care-site-id
  path:
    v: VisitOccurrence.care_site_id
  short:
    v: Care Site
  definition:
    v: This field provides information about the Care Site where the Visit took place.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: Reference
      l: Reference
    target profile:
      v: http://hl7.org/fhir/uv/omop/StructureDefinition/CareSite
      l: CareSite
element:
  id:
    v: VisitOccurrence.visit-source-value
  path:
    v: VisitOccurrence.visit_source_value
  short:
    v: Visit Source Value
  definition:
    v: This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.)
  min:
    v: 0
  max:
    v: 1

code:
  v: string
  l: string

id:
  v: VisitOccurrence.visit-source-concept-id
path:
  v: VisitOccurrence.visit_source_concept_id
short:
  v: Visit Source Concept
definition:
  v: Visit Source Concept
min:
  v: 0
max:
  v: 1
type:
  code:
    v: code
    l: code

id:
  v: VisitOccurrence.admitted-from-concept-id
path:
  v: VisitOccurrence.admitted_from_concept_id
short:
  v: Admitted From Concept
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: code
    l: code

id:
  v: VisitOccurrence.admitted-from-source-value
path:
  v: VisitOccurrence.admitted_from_source_value
short:
  v: Admitted From Source Value
definition:
  v: Admitted From Source Value
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string
    l: string

id:
  v: VisitOccurrence.discharged-to-concept-id
path:
  v: VisitOccurrence.discharged_to_concept_id
short:
  v: Discharged To Concept
definition:
  v: Discharged To Concept
min:
  v: 0
max:
  v: 1
type:
  code:
    v: code
    l: code

id:
  v: VisitOccurrence.discharged-to-source-value
path:
  v: VisitOccurrence.discharged_to_source_value
short:
  v: Discharged To Source Value
definition:
  v: Discharged To Source Value
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string
    l: string

id:
  v: VisitOccurrence.preceding-visit-occurrence-id
path:
  v: VisitOccurrence.preceding_visit_occurrence_id
short:
  v: Preceding Visit Occurrence
definition:
  v: 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.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: Reference
    l: Reference
  target profile:
    v: http://hl7.org/fhir/uv/omop/StructureDefinition/VisitOccurrence
    l: VisitOccurrence