URSA-CORE-914: Documents with Non-Standard Revenue Center Code

  • Published on Apr 10, 2026
  • 2 minute(s) read
Prev Next

Measure Description

Among documents with a CMS revenue center code, the percentage with a non-standard value. Positive values indicate a likely illegal code, or a legal value with improper formatting (e.g., without a leading zero).

Metadata

  • Measure Identifier: URSA-CORE-914
  • Measure Type: Rate Measure
  • Temporal Structure: Event
  • Component Class: Normal-Form
  • Denominator Case Field: Document ID
  • Target Direction: Down

Denominator Description

Documents with a naturally occurring CMS Revenue Center Code.

Numerator Description

Denominator observations for which the CMS Revenue Center Code does not appear in the URSA-CORE CMS Revenue Center Code reference object.

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)
    • 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)
    • Payor ID -- The identifier for the health insurance organization associated with the current record.
    • 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.
    • Segment Start Date -- The start date of the reporting segment. (See also [URSA-CORE] Reporting Segment)
    • Segment End Date -- The end date of the reporting segment. (See also [URSA-CORE] Reporting Segment)

  • Denominator 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)
    • EMR Encounter Type Operational ID
    • EMR Encounter Type Description
    • 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)
    • Revenue Center Code Document Type Category

  • Metadata Fields

    • Document Type Description

  • Measure Fields

    • Denominator