Press CTRL+K to open search

[SO/URSA-CKD] Kidney Transplantation Surgery Encounter

  • Published on Oct 8, 2026
  • 3 minute(s) read
Prev Next

Object Description

One record per hospital inpatient admission encounter with a kidney transplantation surgery.

Metadata

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

Published Fields

  • Data Model Keys

    • 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 ID -- The internal database identifier (used, e.g., for joins and primary keys) for the encounter. (See also [URSA-CORE] 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)
    • 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)

  • Date Fields

    • Encounter Start Date
    • Encounter End Date

  • Encounter Fields

    • 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 Observation Stay Parent Encounter -- Indicates the patient received care in a hospital observation setting. In the context of Hospital Inpatient Admission Encounters, this field will identify IP Admits that came from an observation stay as a part of the Hospital Inpatient Admission Encounter (True = "1"). (See also [URSA-CORE] Encounter)
    • Encounter Qualifying Document ICD-10-PCS Code
    • Encounter Qualifying Document HCPCS Code
    • Encounter Qualifying Document MS-DRG Code
    • CMS Admit Type Code -- The standard single-digit CMS inpatient admission type code found on Inpatient and Skilled Nursing Facility claims; ; 1 = Emergency, 2 = Urgent, 3 = Elective, 4 = Newborn, 5 = Trauma Center, 9 = Information Not Available.
    • 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.

  • Diagnosis Fields

    • Principal Discharge Diagnosis ICD-10-CM Code
    • Principal Discharge Diagnosis ICD-10-CM Description

  • Financial Fields

    • Primary Plan Allowed Amount -- The maximum amount that the payor agrees to pay the provider for a service or product, typically governed by a contract. The Allowed Amount for a claim or billing record is calculated by adding the Contractual Adjustment Amount (which is typically negative) to the Charge Amount. Adding the total Non-Contractual Adjustment Amount to the Allowed Amount yields the Total Due Amount. On billing records, which may identify up to three plans responsible for payment, the Primary Plan Allowed Amount, Secondary Plan Allowed Amount, and Tertiary Plan Allowed Amount fields identify the amounts paid by the primary, secondary, and tertiary plans listed on the bill, respectively. (See also [URSA-CORE] Charge Amount, [URSA-CORE] Contractual Adjustment Amount, [URSA-CORE] Non-Contractual Adjustment Amount, [URSA-CORE] Total Due Amount)
    • Primary Plan Paid Amount -- The amount actually paid by the health plan to the provider for a service or product. Subtracting the plan paid amount from the total due amount typically yields the patient responsibility amount. On billing records, which may identify up to three plans responsible for payment, the Primary Plan Paid Amount, Secondary Plan Paid Amount, and Tertiary Plan Paid Amount fields identify the amounts paid by the primary, secondary, and tertiary plans listed on the bill, respectively; the total paid by any and all plans on a bill is identified by the Any Plan Paid Amount field.
    • Total Plan Paid Amount from All Plans
    • Patient Paid Amount -- The amount paid by the patient to the provider for health care services or products.

Terms

  • Kidney Transplantation Surgery Encounter: An encounter with a kidney transplantation surgery performed. The surgery is identified via MS-DRG, ICD-10-PCS, or CPT/HCPCS procedure code associated with a hospital inpatient admission encounter.

Foreign Keys

  • pat_id → ursa.no_ursa_core_pat_001.pat_id
  • enc_id → ursa.so_ursa_core_enc_001.enc_id
  • facility_prov_id → ursa.no_ursa_core_prov_001.prov_id
  • attending_prov_id → ursa.no_ursa_core_prov_001.prov_id