Documentation Index

Fetch the complete documentation index at: https://docs.ursahealth.com/llms.txt

Use this file to discover all available pages before exploring further.

[SO/URSA-CORE] Universal Encounter Document Aggregator

  • Published on Jun 11, 2026
  • 8 minute(s) read
Prev Next

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
    • 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 Hospital Inpatient Admission Encounter
    • Is IRF Inpatient Admission Encounter
    • Is LTCH Inpatient Admission Encounter
    • Is IPF Inpatient Admission Encounter
    • Is Emergency Department Visit Parent Encounter -- Value of "1" if true that the hospital inpatient admission is connected to a Department Visit Parent Encounter during which the patient received care in an emergency room setting; operationally defined by the presence of one or more of the following: (1) a qualifying revenue center code value on an institutional claim or bill; (2) a qualifying HCPCS code on an institutional claim or bill; or (3) an EMR encounter record flagged as an ED visit (i.e., Is Encounter Type ED Visit = 1). Encounters can be nested; that is, one “parent” encounter can contain one or more “child” encounters.
    • Is Hospital Observation Stay Parent Encounter
    • Is Clinician Office Visit
    • Is Urgent Care Visit -- Indicates the encounter had one or more claim document with a HCPCS, Revenue Center Code, or Place of Service Code specific to Urgent Care Facility claim filing.
    • Is Primary Care Clinician Office Visit -- A Clinician Office Visit encounter with a primary care provider or in which primary care services were delivered; operationally defined by the presence of one or more of the following: (1) a service provider or attending provider identified as a primary care provider or with a qualifying primary NUCC taxonomy code; or (2) a qualifying HCPCS code for preventive and/or primary care services. (See also [URSA-CORE] Clinician Office Visit)
    • Is FQHC Primary Care Clinician Office Visit
    • Is RHC Primary Care Clinician Office Visit
    • Is SNF Encounter
    • Is Swing-Bed SNF Encounter -- Indicates a SNF Encounter is a swing-bed SNF encounter, i.e., an encounter in which the patient receives skilled nursing facility-level services within a hospital, typically after being discharged from hospital inpatient status from that same hospital. Swing-bed SNF encounters are identified from institutional claims with Type of Bill codes 18x. SNF Encounters designated as not swing-bed are considered to be Freestanding SNF Encounters, i.e., an encounter in which the patient receives care at a dedicated SNF.
    • Is Ambulatory Surgical Center Encounter
    • Is Hospital Outpatient Surgery Encounter
    • Is Other Hospital Outpatient Encounter
    • Is Birthing Center Encounter
    • Is Home Health Care Visit
    • Is HHA Visit
    • Is Dialysis Facility Encounter
    • Is Other Outpatient Encounter
    • Is FQHC Other Outpatient Encounter
    • Is RHC Other Outpatient Encounter
    • Is Any Hospital Encounter Type -- True if the URSA-CORE meets any of the criteria for one or more of the following encounter types: (1) Emergency Department Visits without Admissions, (2) Hospital Observation Stays without Admission, (3) Hospital Inpatient Admissions, (4) Hospital Outpatient Surgery Encounters, or (5) Other Hospital Outpatient Department Encounters.

  • Metadata Fields

    • Ursa Encounter Type Tier 1 Code -- A short code (e.g., "HIA", "ED", "OBS", "OFFICE", "SNF", "ASC", "HOSURG", "HOME", "DIAL", "OTH", "NONE") identifying the broad clinical encounter type associated with the financial record. Sourced from Ursa encounter-grouping logic, which links claims and service lines to constructed encounters. A value of "NONE" means no encounter was built for the record (e.g., pharmacy claims, which are never encounter-grouped). Unlike Ursa Setting Tier 1 Code, which reflects where a service was rendered based on billing codes, this field reflects the clinical episode context in which the claim participates. Use the Code variant when filtering or joining on specific encounter types. For more granular sub-types, see Ursa Encounter Type Tier 2 Code. (See also [URSA-CORE] Ursa Encounter Type Tier 1 Category, [URSA-CORE] Ursa Encounter Type Tier 1 Description, [URSA-CORE] Ursa Encounter Type Tier 2 Code)
    • Ursa Encounter Type Tier 1 Category -- The numbered, sort-friendly label for the broad encounter type represented by Ursa Encounter Type Tier 1 Code (e.g., "[01] Hospital Inpatient Admission Encounter", "[03] Emergency Department Visit Only"). Resolved via a lookup table keyed on Ursa Encounter Type Tier 1 Code. Use this variant when building visualizations or reports where consistent sort order matters. (See also [URSA-CORE] Ursa Encounter Type Tier 1 Code)
    • Ursa Encounter Type Tier 1 Description -- The plain-English broad encounter type name (e.g., "Hospital Inpatient Admission Encounter", "Emergency Department Visit Only"). Contains the same content as Ursa Encounter Type Tier 1 Category but without the numeric sort prefix. Use this variant for user-facing labels where the bracketed prefix is not desired. (See also [URSA-CORE] Ursa Encounter Type Tier 1 Code, [URSA-CORE] Ursa Encounter Type Tier 1 Category)
    • Ursa Encounter Type Tier 2 Code -- A more granular encounter code that subdivides Ursa Encounter Type Tier 1 Code into specific sub-types (e.g., "HIA/EDOBS" for admission via ED or observation, "HIA/DAC" for direct acute care admission, "HIA/IRF" for inpatient rehabilitation facility, "OFFICE/FQHC" for FQHC visit, "OFFICE/URG" for urgent care, "HOME/HHA" for home health agency visit). Also sourced from the encounter-grouping logic. Provides the most specific encounter classification available in the data model. Use this field when you need to distinguish sub-types within a broad encounter category (e.g., separating urgent care visits from other office visits, or identifying the admission pathway for inpatient stays).
    • Ursa Encounter Type Tier 2 Category -- The numbered, sort-friendly label for the detailed encounter type represented by Ursa Encounter Type Tier 2 Code (e.g., "[01] Direct Acute Care Hospital Inpatient Admission", "[09] Urgent Care Visit"). Resolved via a lookup table keyed on Ursa Encounter Type Tier 2 Code. Use this variant when building visualizations or reports where consistent sort order matters within the more granular encounter classification. (See also [URSA-CORE] Ursa Encounter Type Tier 2 Code)
    • Ursa Encounter Type Tier 2 Description -- The plain-English detailed encounter type name (e.g., "Direct Acute Care Hospital Inpatient Admission", "Urgent Care Visit"). Contains the same content as Ursa Encounter Type Tier 2 Category but without the numeric sort prefix. Use this variant for user-facing labels where the bracketed prefix is not desired. (See also [URSA-CORE] Ursa Encounter Type Tier 2 Code, [URSA-CORE] Ursa Encounter Type Tier 2 Category)
    • Is Surgery Encounter -- Indicates an encounter in which the patient underwent surgery; identified by the presence, among the documents associated with an encounter, of a surgical HCPCS code or a revenue center code for operating room setting care.
    • Ursa Surgery Encounter Type Code -- A short code (e.g., "HIASURG", "HOSURG", "ASCSURG", "ASCNO", "OTHNO", "NONE") classifying the financial record by whether and where a surgical encounter occurred. Derived from the encounter-grouping logic by evaluating whether the associated encounter qualifies as a surgery encounter and, if so, in what setting. Values include: HIASURG (hospital inpatient admission with surgery), HOSURG (hospital outpatient surgery), ASCSURG (ambulatory surgical center encounter with surgery), ASCNO (ASC encounter without surgery), OTHNO (other encounter without surgery), and NONE (no associated Ursa encounter). Use this field to isolate surgical spending by setting or to identify non-surgical claims within surgical encounter types.
    • Ursa Surgery Encounter Type Category -- The numbered, sort-friendly label for the surgery encounter classification represented by Ursa Surgery Encounter Type Code (e.g., "[01] Hospital Inpatient Admission with Surgery", "[03] Ambulatory Surgical Center Encounter with Surgery"). Use this variant when building visualizations or reports where consistent sort order matters for surgical encounter analysis. (See also [URSA-CORE] Ursa Surgery Encounter Type Code)
    • Ursa Surgery Encounter Type Description -- The plain-English surgery encounter type name (e.g., "Hospital Inpatient Admission with Surgery", "Ambulatory Surgical Center Encounter with Surgery"). Contains the same content as Ursa Surgery Encounter Type Category but without the numeric sort prefix. Use this variant for user-facing labels where the bracketed prefix is not desired. (See also [URSA-CORE] Ursa Surgery Encounter Type Code, [URSA-CORE] Ursa Surgery Encounter Type Category)

  • Validation Only Fields

    • 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
    • Other Outpatient Encounter ID

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.