[DM/URSA-MSSP] Data Mart for MSSP CQM Documents

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

Object Description

One row per MSSP CQM document

Metadata

  • Table Name: ursa.sm_ursa_mssp_cqm_002
  • Layer: DATA_MART
  • 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)
    • 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)
    • Source ID -- The identifier for the original source data system from which the current record originated.

  • 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.

  • Denominator Fields

    • Is Any Encounter Document
    • Encounter Criteria Met Category Description
    • Is Any Inclusionary Dx Document
    • Inclusionary Diagnosis Category Description
    • Is Any Required Exclusion Document
    • Required Exclusion Category Description

  • 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)
    • Result Type Description
    • Result Type LOINC Code
    • Result Type SNOMED CT Code
    • Result Description
    • Result Numeric
    • Snomed Modifier Left or Right Body Site Designation Category

  • 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
    • 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.

  • Provider Fields

    • 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)

  • 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