[SO/URSA-CORE] Universal Encounter Document Aggregator

Object Description

One record per document that is associated with at least one of the URSA-CORE encounter types.

Metadata

• Table Name: ursa.so_ursa_core_enc_120
• Layer: SYNTHETIC_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: Document ID
• Event Date: Document Effective Date
• Primary Key: Document ID

Published Fields

• Data Model Keys

  • Document ID -- The internal database identifier (used, e.g., for joins and primary keys) for the document. (See also [URSA-CORE] Document)
  • Parent Document ID -- The document ID for the document one level above the current document in the object hierarchy, (See also [URSA-CORE] Document ID)
  • Grandparent Document ID -- The document ID for the document two levels above the current document in the object hierarchy, (See also [URSA-CORE] Document ID)
  • Patient ID -- The internal database identifier (used, e.g., for joins and primary keys) for the patient. This value is typically mastered, i.e., all records for the same patient, regardless of the source data system from which that record originated, should have the same Patient ID value. (Note that while the mastered Patient ID value might resemble a local identifier used in one of the upstream data sources, this does not indicate any special priority of that source system in determining the characteristics of the patient.) (See also [URSA-CORE] Patient)
  • Primary Encounter ID
  • Hospital Inpatient Admission Encounter ID
  • Clinician Office Visit Encounter ID
  • Emergency Department Visit Parent Encounter ID
  • Hospital Observation Stay Parent Encounter ID
  • SNF Encounter ID
  • Ambulatory Surgical Center Encounter ID
  • Hospital Outpatient Surgery Encounter ID
  • Other Hospital Outpatient Encounter ID
  • Dialysis Facility Encounter ID
  • Home Health Care Visit Encounter ID
  • Birthing Center Encounter ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Date Fields

  • Document Effective Date -- The most appropriate single date that events associated with the document occurred. For documents spanning multiple calendar days, the earliest date is typically used; Document Effective Start Date and Document Effective End Date can be used for a more precise range of dates, if necessary.
  • Document Effective Start Date -- The date that the events associated with the document began.
  • Document Effective End Date -- The last date on which events associated with the document occurred or continued until.
  • Primary Encounter Start Date
  • Primary Encounter End Date

• Encounter Fields

  • Is Ursa Encounter Type Hospital Inpatient Admission
  • Is Ursa Encounter Type Clinician Office Visit
  • Is Ursa Encounter Type Primary Care Clinician Office Visit
  • Is Ursa Encounter Type Emergency Department Visit Parent Encounter
  • Is Ursa Encounter Type Hospital Observation Stay Parent Encounter
  • Is Ursa Encounter Type SNF Encounter
  • Is Ursa Encounter Type Ambulatory Surgical Center Encounter
  • Is Ursa Encounter Type Hospital Outpatient Surgery Encounter
  • Is Ursa Encounter Type Other Hospital Outpatient Encounter
  • Is Ursa Encounter Type Dialysis Facility Encounter
  • Is Ursa Encounter Type Home Health Care Visit Encounter
  • Is Ursa Encounter Type Birthing Center Encounter
  • Primary Encounter Ursa Encounter Type Tier 1 Category
  • Primary Encounter Ursa Encounter Type Tier 2 Category
  • Primary Encounter Ursa Surgery Encounter Type Category
  • Is Primary Encounter Surgery Encounter
  • Is Primary Encounter Urgent Care Visit
  • Is Primary Encounter Any Hospital Encounter Type

Dedicated Precursors

• [SO/URSA-CORE] Universal Encounter Document Aggregator, Precursor 1 (All Encounter Documents): One record per document-encounter pair; the same document can appear multiple times. These duplicates are resolved in the terminal object.