[DM/URSA-QUALITY] History of Data Mart for Chase List Measure Results
  • 18 Jul 2025
  • 2 Minutes to read
  • Dark
    Light

[DM/URSA-QUALITY] History of Data Mart for Chase List Measure Results

  • Dark
    Light

Article summary

Object Description

One record per record present in the Data Mart for Chase List Measure Results table when this object was run.

Metadata

  • Table Name: ursa.dm_ursa_quality_002_history
  • Layer: DATA_MART
  • Object Type: Single Stack
  • Case ID: Patient ID
  • Primary Key: Patient 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)
    • Primary Payor ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Primary Payor. (See also [URSA-CORE] Primary Payor)
    • Primary Plan ID -- The identifier for the health insurance plan product that is the first party responsible for payment.
    • Primary Plan Attributee Provider ID
  • Operations Support Fields

    • Measure ID
    • Measure Name
  • Date Fields

    • Snapshot Date -- The date, evaluated at 00:00:00 AM, giving the moment the state of the world will be set to for the purposes of an analysis. The snapshot date does not represent the freshness of the data, or the date in real time at which an analysis was executed.
    • Current Performance Year Start Date
    • Current Performance Year End Date
  • Measure Fields

    • Is Snapshot Date in Current Performance Year
    • Is Denominator Excluded
    • Denominator
    • Is Numerator Qualifying Using Standard End-of-Year Timing
    • Numerator Component Using Standard End-of-Year Timing
  • Denominator Fields

    • Is Continuous Membership Criterion Met
    • Is Event Criterion Met
    • Is Any Required Exclusion
    • Denominator Excluded Reasons Description
    • Denominator Qualifying Event Date
  • Numerator Fields

    • Is Numerator Met Using Rolling Performance Period Timing
    • Numerator Document ID
  • Patient Fields

    • Patient Operational ID -- The user-facing value used by staff used to uniquely identify the Patient in their administrative systems and/or day-to-day operations. (See also [URSA-CORE] Patient)
    • Patient MBI -- The patient's Medicare Beneficiary Identifier (MBI). On the Patients Natural Object, this reflects the most recent MBI known for the patient; on the Patient-Plan Timelines of Plan Membership Natural Object, this reflects the contemporaneous MBI during the respective timeline period.
    • Zus Patient ID
    • Primary Payor Description
    • Primary Plan Description
    • Primary Plan Financial Class Description
    • Primary Plan Attributee Provider Description
    • Current Continuous Primary Payor Membership Episode Start Date -- The start date of the Continuous Primary Payor Membership Episode in effect as of the (potentially historical) period covered by the record. (See also [URSA-CORE] Continuous Primary Payor Membership Episode)
  • Provider Fields

    • Primary Plan Attributee Provider NPI
  • [No Field Group]

    • Denominator Event Window End Date
    • Is Measure Event Based
    • Is Measure Inverse Performance

Was this article helpful?