Hospital Outpatient Surgery Encounter Document Aggregator

Object Description

Collects information about hospital outpatient surgery encounters; contains one record per claim, bill, or EMR encounter record associated with an encounter.

Metadata

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

Relational Diagram

Related Key Concepts

None.

Dedicated Precursors

• [SO/URSA-CORE] Hospital Outpatient Surgery Encounter Document Aggregator, Precursor 1 (Qualifying Documents): One record per professional claim or bill service line item, institutional claim or bill service line item, or EMR encounter record providing qualifying evidence that a hospital outpatient surgery encounter took place; current logic assumes that a single professional bill or claim will contain services for at most a single HOS encounter. NB: rarely, these encounters last more than 1 day; however, the claim covered start and end dates for institutional claims / bills are not reliable for establishing the encounter start and end dates, because the covered periods sometimes includes pre-op testing and other services; so we impute the actual date of surgery from institutional claim service line items with OR setting services, and assume the day of surgery was the first day of the encounter. We also find that professional claims / bills for multi-day encounters seem to overwhelmingly have claim covered start dates on the encounter start date, so we do not attempt to match professional services starting after the encounter start date -- it's not worth the additional computational burden to catch the handful (if any) of these instances.
• [SO/URSA-CORE] Hospital Outpatient Surgery Encounter Document Aggregator, Precursor 2 (All Master Documents): One record per professional claim or bill, institutional claim or bill, or EMR encounter record describing services associated with a hospital outpatient surgery encounter; additionally includes records that would not alone qualify as an encounter of this type, but which match to one that does.

FAQs

None.