Contents x
    Hospital Inpatient Admission Encounter Document Aggregator
    • 24 Apr 2023
    • 1 Minute to read
    • Print
    • Dark
      Light
    Contents

    Hospital Inpatient Admission Encounter Document Aggregator

    • Updated on 24 Apr 2023
    • 1 Minute to read
    • Print
    • Dark
      Light
    Article Summary

    Object Description

    One record per document associated with a hospital inpatient admission, including all children of master documents; master document types for this encounter type are: institutional claim or bill headers; EMR encounters; and professional claim or bill headers.

    Metadata

    • Table Name: ursa.so_ursa_core_enc_101
    • Layer: Synthetic Object
    • Object Type: Integrator
    • Temporal Class: Event
    • Case ID: Document ID
    • Event Date: Encounter Start Date
    • Primary Key: Document ID

    Relational Diagram

    Hospital Inpatient Admission Encounter Document Aggregator.png

    None.

    Dedicated Precursors

    • [SO/URSA-CORE] Hospital Inpatient Admission Encounter Document Aggregator, Precursor 1 (Qualifying Documents): One record per qualifying document; qualifying document types for this encounter type are: institutional claim or bill headers; or EMR encounters.
    • [SO/URSA-CORE] Hospital Inpatient Admission Encounter Document Aggregator, Precursor 2 (Qualifying Document Matching): One record per qualifying document; qualifying document types for this encounter type are: institutional claim or bill headers; or EMR encounters. This precursor implements logic to group multiple qualifying master records for the same admission, using the structure of an episode to represent an admission.
    • [SO/URSA-CORE] Hospital Inpatient Admission Encounter Document Aggregator, Precursor 3 (All Master Documents): One record per master document; master document types for this encounter type are: institutional claim or bills, EMR encounters, and professional claims and bills.

    FAQs

    None.

    Was this article helpful?
    What's Next