[DM/URSA-CKD] Data Mart for ESRD Start Encounters

Object Description

One record per dialysis parent encounter or hospital inpatient admission with kidney transplantation surgery representing a CKD patient's progression to ESRD.

Metadata

• Table Name: ursa.dm_ursa_ckd_005
• Layer: DATA_MART
• 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

  • 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 Facility Provider ID

• Patient Fields

  • Patient Age Integer -- Patient age, expressed as an integer, as of a reference date or interval.

• Date Fields

  • Encounter Start Date
  • Encounter End Date

• Encounter Fields

  • ESRD Start Type Category
  • Is ESRD Start Type Kidney Transplant
  • Is ESRD Start Type Dialysis Encounter
  • Encounter Setting Category
  • Is Encounter Setting Home
  • Is Encounter Setting Inpatient
  • Is Encounter Setting Outpatient Dialysis Facility
  • Is Encounter Setting Outpatient Non-Dialysis Facility
  • Encounter Qualifying Dialysis Document HCPCS Code
  • Encounter Qualifying Dialysis Document CMS Revenue Center Code
  • Encounter Qualifying Kidney Transplantation Document ICD-10-PCS Code
  • Encounter Qualifying Kidney Transplantation Document HCPCS Code
  • Encounter Qualifying Kidney Transplantation Document MS-DRG Code
  • Encounter CMS Type of Bill Code
  • Encounter CMS Place of Service Code
  • Dialysis Access Type Category
  • Is Dialysis Vascular Access Type Any Catheter
  • Is Dialysis Vascular Access Type Graft Without Catheter
  • Is Dialysis Vascular Access Type Fistula Only
  • Is Hospital Inpatient Admission Encounter
  • Is Emergency Department Visit Parent Encounter
  • Is Observation Stay Parent Encounter
  • Is Encounter Setting Home or Outpatient Dialysis Facility

• Insurance Fields

  • Is Any Current Plan Membership

• Clinical Services Fields

  • Dialysis Modality Category
  • Is Dialysis Modality Hemodialysis
  • Is Dialysis Modality Peritoneal Dialysis

• Metadata Fields

  • Is Medical Claim Data Coverage -- Indicates data coverage for medical claims (i.e., institutional and professional claims) from at least one data source for the patient and time period specified on the record. (See also [URSA-CORE] Data Coverage)
  • Current Continuous Medical Claim Data Coverage Episode Start Date -- The start date of the Continuous Medical Claim Data Coverage Episode in effect as of the (potentially historical) period covered by the record. (See also [URSA-CORE] Continuous Medical Claim Data Coverage Episode)

Foreign Keys

• enc_facility_prov_id → ursa.no_ursa_core_prov_001.prov_id
• pat_id → ursa.no_ursa_core_pat_001.pat_id
• enc_id → ursa.so_ursa_ckd_enc_005.enc_id