[SO/URSA-MSSP] Document Aggregator for URSA-MSSP CQM Concepts

  • Published on Aug 21, 2025
  • 10 minute(s) read
Prev Next

Object Description

One record per patient document related to an URSA-MSSP module concept for eCQM measures

Metadata

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

Published Fields

  • Data Model Keys

    • Document ID -- The internal database identifier (used, e.g., for joins and primary keys) for the document. (See also [URSA-CORE] Document)
    • Parent Document ID -- The document ID for the document one level above the current document in the object hierarchy, (See also [URSA-CORE] Document ID)
    • Grandparent Document ID -- The document ID for the document two levels above the current document in the object hierarchy, (See also [URSA-CORE] Document ID)
    • 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)
    • Claim ID -- The internal database identifier (used, e.g., for joins and primary keys) for the claim. (See also [URSA-CORE] Claim)
    • Service Line Number -- The integer-valued ordinal representing the position of a service line item in a claim, bill, encounter, or other master record. May not necessarily match the analogous value in the source data for the same record.
    • Diagnosis Line Number -- The integer-valued ordinal representing the position of a diagnosis on a claim, bill, encounter, or other master record. May not necessarily match the analogous value in the source data for the same record. Typically, the diagnosis in the first position is considered the principal diagnosis, though this is not an absolute rule, and the Is Principal Diagnosis field should be used to identify the principal diagnosis.
    • Procedure Line Number -- The integer-valued ordinal representing the position of a procedure on a claim, bill, encounter, or other master record. May not necessarily match the analogous value in the source data for the same record.
    • Billing Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the billing provider. (See also [URSA-CORE] Billing 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)
    • 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)
    • Source ID -- The identifier for the original source data system from which the current record originated.
    • Master Document ID
    • Encounter ID -- The internal database identifier (used, e.g., for joins and primary keys) for the encounter. (See also [URSA-CORE] Encounter)

  • Date Fields

    • Document Effective Date -- The most appropriate single date that events associated with the document occurred. For documents spanning multiple calendar days, the earliest date is typically used; Document Effective Start Date and Document Effective End Date can be used for a more precise range of dates, if necessary.
    • Document Effective Start Date -- The date that the events associated with the document began.
    • Document Effective End Date -- The last date on which events associated with the document occurred or continued until.
    • Parent Document Effective Start Date -- The date that the events associated with the current document's parent document began.
    • Parent Document Effective End Date -- The last date on which events associated with the current document's parent document occurred or continued until.
    • Encounter Start Date
    • Encounter End Date

  • Encounter Fields

    • Encounter Facility Provider ID
    • Encounter Principal Discharge Diagnosis ICD-10-CM Code
    • Encounter Principal Discharge Diagnosis ICD-10-CM Description
    • Encounter Principal Discharge Diagnosis AHRQ CCS Single-Level Diagnosis Category Code
    • Encounter Principal Discharge Diagnosis AHRQ CCS Single-Level Diagnosis Category Description
    • Encounter CMS Patient Discharge Status Code
    • Encounter CMS Patient Discharge Status Description
    • Is Ursa Encounter Type Hospital Inpatient Admission
    • Is Ursa Encounter Type Clinician Office Visit
    • Is Ursa Encounter Type Primary Care Clinician Office Visit
    • Is Ursa Encounter Type Emergency Department Visit Parent Encounter
    • Is Ursa Encounter Type Hospital Observation Stay Parent Encounter
    • Is Ursa Encounter Type SNF Encounter
    • Is Ursa Encounter Type Ambulatory Surgical Center Encounter
    • Is Ursa Encounter Type Hospital Outpatient Surgery Encounter
    • Is Ursa Encounter Type Other Hospital Outpatient Encounter
    • Is Ursa Encounter Type Dialysis Facility Encounter
    • Is Ursa Encounter Type Home Health Care Visit Encounter
    • Is Ursa Encounter Type Birthing Center Encounter
    • Primary Encounter Ursa Encounter Type Tier 1 Category
    • Primary Encounter Ursa Encounter Type Tier 2 Category
    • Primary Encounter Ursa Surgery Encounter Type Category

  • Clinical Services Fields

    • ICD-10-PCS Code
    • ICD-10-PCS Description
    • ICD-10-PCS AHRQ CCS Single-Level Procedure Category Code
    • ICD-10-PCS AHRQ CCS Single-Level Procedure Category Description
    • HCPCS Code -- The Healthcare Common Procedure Coding System (HCPCS) code associated with a service. Includes both HCPCS Level I codes (commonly called CPT codes) and Level II codes (which includes products, supplies, and services not included in CPT). Level II codes consist of a letter followed by four numeric digits. Current Dental Terminology codes are included in the Level II codes as HCDT. (See also [URSA-CORE] HCPCS Description)
    • HCPCS Description -- The natural language description of a HCPCS code. (See also [URSA-CORE] HCPCS Code)
    • HCPCS Modifier 1 Code -- The 2-character code modifying a HCPCS code.
    • HCPCS Modifier 1 Description -- The natural language description of a HCPCS code modifier. (See also [URSA-CORE] HCPCS Modifier Code)
    • HCPCS Modifier 2 Code
    • HCPCS Modifier 2 Description
    • HCPCS Modifier 3 Code
    • HCPCS Modifier 3 Description
    • HCPCS Modifier 4 Code
    • HCPCS Modifier 4 Description
    • HCPCS Modifier 5 Code
    • HCPCS Modifier 5 Description
    • Service LOINC Code
    • Service SNOMED CT Code
    • CMS Revenue Center Code -- The standard CMS 4-digit Revenue Center code; e.g., 0001 = Total charge, etc. CMS Revenue Center codes should include leading zeros.
    • CMS Revenue Center Description -- The natural language description of a CMS Revenue Center code (See also [URSA-CORE] CMS Revenue Center Code)
    • CMS Place of Service Code -- The standard CMS 2-digit Place of Service code; e.g., 01 = Pharmacy, 02 = Telehealth, etc.
    • CMS Place of Service Description -- The natural language description of a standard CMS Place of Service code (See also [URSA-CORE] CMS Place of Service Code)

  • Medication Fields

    • RxNorm Code -- The standard RxNorm code for medications; e.g., 315253 = acetaminophen 160 MG.
    • Label Description -- Supplies the name given to the product by the manufacturer.
    • Active Ingredients Description -- A natural language description of the medication's biologically active ingredient(s). For medications with multiple active ingredients, the active ingredients should be listed in alphabetical order.
    • AHFS Therapeutic Class Code 6-Digit -- The standard 6-digit AHFS Pharmacologic-Therapeutic Class Code, representing the first 3 tiers of the AHFS Pharmacologic-Therapeutic Classification system. The code is expressed as 6 numbers, without special characters delimiting the tiers, with leading and trailing zeros as needed. (See also [URSA-CORE] AHFS Pharmacologic-Therapeutic Classification System)

  • Diagnosis Fields

    • ICD-10-CM Code
    • ICD-10-CM Description
    • ICD-10-CM AHRQ CCS Single-Level Diagnosis Category Code
    • ICD-10-CM AHRQ CCS Single-Level Diagnosis Category Description
    • Is Admitting Diagnosis -- Indicates that a diagnosis was the admitting diagnosis for an encounter.
    • Is Principal Diagnosis -- Indicates that a diagnosis was documented as the principal diagnosis for the claim, bill, encounter, etc.
    • Diagnosis SNOMED CT Code
    • Diagnosis SNOMED CT Description
    • MS-DRG Code -- The standard 3-digit Medicare Severity Diagnosis Related Group code; MS-DRG codes should include leading zeros.
    • MS-DRG Description -- The natural language description of a standard 3-digit Medicare Severity Diagnosis Related Group code.

  • Billing and Claims Fields

    • CMS Type of Bill Code -- The standard CMS 3-digit Type of Bill (TOB) Code; 111 = Hospital Inpatient Admit Through Discharge, etc.
    • CMS Type of Bill Description -- The natural language description of a standard CMS Type of Bill (TOB) code. (See also [URSA-CORE] CMS Type of Bill Code)

  • Metadata Fields

    • Document Type Description
    • Is Document Type with Uninherited HCPCS
    • Result Type LOINC Code Robust
    • Result Type SNOMED CT Code Robust
    • Diagnosis SNOMED CT Code Robust

  • Validation Only Fields

    • Is Any CQM Q001 (A1C) Document
    • Is Any CQM Q112 (BCS) Document to Spec
    • Is Any CQM Q134 (DEP) Document
    • Is Any CQM Q236 (CBP) Document

  • Patient Observation Fields

    • Result Type Description
    • Result Type LOINC Code
    • Result Type SNOMED CT Code
    • Result Description
    • Result Numeric
    • Observation-Generating EMR Encounter ID
    • Observation-Generating Service Date
    • Is Result Status Finalized

  • Module Fields

    • Is Encounter Principal Discharge ICD10
    • Is Encounter Principal Discharge Single-Level Category Code
    • Is Encounter Principal Discharge Diagnosis Document
    • Is HWR Cardiorespiratory Specialty Cohort Principal Diagnosis Document
    • Is HWR Cardiovascular Specialty Cohort Principal Diagnosis Document
    • Is HWR Medicine Specialty Cohort Principal Diagnosis Document
    • Is HWR Neurology Specialty Cohort Principal Diagnosis Document
    • Is HWR Surgery/Gynecology Specialty Cohort Document
    • Is HWR Medical Treatment of Cancer Exclusion Principal Diagnosis Document
    • Is HWR Rehabilitation Exclusion Principal Diagnosis Document
    • Is HWR Psychiatric Exclusion Principal Diagnosis Document
    • Is HWR Always Planned Procedure Document
    • Is HWR Always Planned Principal Diagnosis Document
    • Is HWR Potentially Planned Procedure Document
    • Is HWR Acute Principal Diagnosis Document
    • Is HWR Covid Principal Diagnosis or Admitting Diagnosis Document
    • Is Ursa Encounter Type Hospital Inpatient Admission Document
    • Is MSSP CQM Frailty Document
    • Is Any MSSP Frailty Document
    • Is MSSP CQM Dementia Medications Document
    • Is Q001 A1C Diabetes Dx Document
    • Is Q001 A1C Encounter Document
    • Is Q001 A1C Denominator Exclusion1 (Hospice) Document
    • Is Q001 A1C Denominator Exclusion2 (Palliative Care) Document
    • Is Q001 A1C Denominator Exclusion3 (SNP) Document
    • Is Q001 A1C Denominator Exclusion4 (Frailty) Document
    • Is Q001 A1C Denominator Exclusion5 (Frailty and Advanced Illness) Document
    • Is Q001 A1C Performance Met Document
    • Is Q001 A1C Performance Not Met Document
    • Is Q112 BCS Encounter Document
    • Is Q112 BCS Denominator Exclusion1 (Bilateral Mastectomy) Document
    • Is Q112 BCS Denominator Exclusion2 (Hospice) Document
    • Is Q112 BCS Denominator Exclusion3 (Palliative Care) Document
    • Is Q112 BCS Denominator Exclusion4 (SNP) Document
    • Is Q112 BCS Denominator Exclusion5 (Frailty) Document
    • Is Q112 BCS Denominator Exclusion6 (Frailty and Advanced Illness) Document
    • Is Q112 BCS Performance Met Document
    • Is Q112 BCS Performance Not Met Document
    • Is Q134 DEP Encounter Document
    • Is Q134 DEP Registry Only Exception Document
    • Is Q134 DEP Denominator Exclusion (Bipolar Disorder) Document
    • Is Q134 DEP Performance Met Document
    • Is Q134 DEP Performance Not Met Document
    • Is Q236 CBP Encounter Document
    • Is Q236 CBP Hypertension Document
    • Is Q236 CBP Denominator Exclusion1 (Hospice) Document
    • Is Q236 CBP Denominator Exclusion2 (Palliative Care) Document
    • Is Q236 CBP Denominator Exclusion3 (ESRD, Dialysis, Renal Transplant, or Pregnancy) Document
    • Is Q236 CBP Denominator Exclusion4 (SNP) Document
    • Is Q236 CBP Denominator Exclusion5 (66+ Frailty) Document
    • Is Q236 CBP Denominator Exclusion6 (Advanced Illness) Document
    • Is Q236 CBP Denominator Exclusion7 (81+ Frailty) Document
    • Is Q236 CBP Systolic Performance Met Document
    • Is Q236 CBP Diastolic Performance Met Document
    • Is Q236 CBP Performance Not Met Document

  • [No Field Group]

    • Is MSSP Finalized PHQ-9 Document
    • Is MSSP Finalized PHQ-2 Document
    • Is POS 81 Laboratory Document
    • Is MSSP Frailty Device Document
    • Is MSSP Frailty Encounter Document
    • Is MSSP Frailty Symptom Document
    • Is MSSP Frailty Diagnosis Document
    • Is MSSP Advanced Illness Document
    • Is Any MSSP Advanced Illness Document
    • Is MSSP Hospice Encounter Document
    • Is MSSP Hospice Intervention Document
    • Is MSSP Hospice Care Ambulatory Document
    • Is MSSP Hospice Diagnosis Document
    • Is MSSP Discharge to Hospice Document
    • Is Any MSSP Hospice Document
    • Is MSSP Palliative Care Encounter Document
    • Is MSSP Palliative Care Diagnosis Document
    • Is MSSP Palliative Care Assessment Document
    • Is MSSP Palliative Care Intervention Document
    • Is Any MSSP Palliative Care Document
    • Is Any MSSP Dementia Medications Document
    • Is MSSP HbA1C Lab Test Document
    • Is MSSP HbA1C Less Than or Equal to 9 Document
    • Is MSSP HbA1C Test Result or Finding Document
    • Is HCPCS Code 3046F Document
    • Is MSSP Mammography Document
    • Is MSSP Bilateral Mastectomy Document
    • Is MSSP History of Bilateral Mastectomy Document
    • Is MSSP Unilateral Mastectomy Document
    • Is MSSP Clinical Unilateral Mastectomy Document
    • Is MSSP eCQM Unilateral Mastectomy, Unspecified Laterality Document
    • Is MSSP Unilateral Mastectomy Left Document
    • Is MSSP Unilateral Mastectomy Right Document
    • Is MSSP Absence of Left Breast Document
    • Is MSSP Absence of Right Breast Document
    • Is Modifier Code 50 Document
    • Is Modifier Code LT Document
    • Is Modifier Code RT Document
    • Is Any MSSP BCS Expanded Document
    • Is MSSP Bipolar Disorder Document
    • Is MSSP Other Bipolar Disorder Document
    • Is MSSP ESRD Diagnosis Document
    • Is MSSP Dialysis Services Document
    • Is MSSP Dialysis Document
    • Is MSSP Dialysis Procedure Document
    • Is MSSP Kidney Transplant Document
    • Is MSSP History of Kidney Transplant Document
    • Is MSSP Kidney Transplant Recipient Document
    • Is MSSP Pregnancy Document
    • Is MSSP Diastolic Blood Pressure Document
    • Is MSSP Diastolic Less Than 90 Document
    • Is MSSP HEDIS Systolic and Diastolic Result Document
    • Is MSSP Systolic Blood Pressure Document
    • Is MSSP HEDIS Systolic Less than 140 Document
    • Is MSSP Systolic Non-Compliant Document
    • Is MSSP Diastolic Non-Compliant Document
    • Is MSSP CQM Systolic Compliant Document
    • Is MSSP CQM Systolic Non-Compliant Document
    • Is MSSP CQM Diastolic Compliant Document
    • Is MSSP CQM Diastolic Non-Compliant Document
    • Snomed Modifier Left or Right Body Site Designation Category