[SO/URSA-CORE] Dialysis Facility Encounters

  • Published on Apr 10, 2026
  • 2 minute(s) read
Prev Next

Object Description

One record per Dialysis Facility Encounter; this object executes the logic to generate the final encounter-level properties based on the full set of documents related to the encounter collected in the aggregator object.

Metadata

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

Published Fields

  • Data Model Keys

    • Encounter ID -- The internal database identifier (used, e.g., for joins and primary keys) for the encounter. (See also [URSA-CORE] Encounter)
    • 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)
    • Encounter Primary Payor ID -- Data model key for the primary payor documented in the billing for an encounter.
    • Encounter Primary Plan ID -- Data model key for the primary plan documented in the billing for an encounter.
    • Facility Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the facility provider. (See also [URSA-CORE] Facility Provider)
    • Service Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the service provider. (See also [URSA-CORE] Service Provider)
    • Attending Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the attending provider. (See also [URSA-CORE] Attending Provider)
    • Provider Group Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the provider group. (See also [URSA-CORE] Provider Group)
    • Primary HCPCS Procedure Provider ID

  • Date Fields

    • Encounter Date

  • Encounter Fields

    • Qualifying Document HCPCS Code
    • Qualifying Document CMS Revenue Center Code
    • Qualifying Document CMS Type of Bill Code
    • Qualifying Document EMR Encounter Type Description

  • Clinical Services Fields

    • Primary HCPCS Procedure HCPCS Code

  • Diagnosis Fields

    • Principal Diagnosis ICD-10-CM Code -- The ICD-10-CM diagnosis code documented as the principal diagnosis for a claim, bill, encounter, etc.
    • Principal Diagnosis ICD-10-CM Description -- The natural language description of the Principal Diagnosis ICD-10-CM Code. (See also [URSA-CORE] Principal Diagnosis ICD-10-CM Code)

  • Billing and Claims Fields

    • CMS Admission Type Code -- The standard CMS 1-digit Admission Type code; 1 = Emergency, 2 = Urgent, etc.
    • CMS Admit Source Code -- The standard 1-character CMS Admit Source code; e.g., 1 = Physician Referral, 2 = Clinic Referral, etc.
    • CMS Patient Discharge Status Code -- The standard 2-digit CMS Patient Discharge Status code; 01 = Discharged to Home or Self Care, etc. Patient Discharge Status codes should include leading zeros.
    • CMS Place of Service Code -- The standard CMS 2-digit Place of Service code; e.g., 01 = Pharmacy, 02 = Telehealth, etc.

Foreign Keys

  • pat_id → ursa.no_ursa_core_pat_001.pat_id
  • enc_primary_payor_id → ursa.no_ursa_core_struct_004.payor_id
  • enc_primary_plan_id → ursa.no_ursa_core_struct_005.plan_id
  • facility_prov_id → ursa.no_ursa_core_prov_001.prov_id
  • service_prov_id → ursa.no_ursa_core_prov_001.prov_id
  • attending_prov_id → ursa.no_ursa_core_prov_001.prov_id
  • prov_group_prov_id → ursa.no_ursa_core_prov_001.prov_id