URSA-CORE-902: Service Line Items Not Starting at Line Number 1

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

Measure Description

Among EMR encounters or medical claims or bills with at least one service line item, the percentage with a starting service line number other than 1. (Any measure result other than 0 should be addressed immediately, since some URSA-CORE data model logic depends on the existence of a service line item with line number of 1.)

Metadata

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

Denominator Description

One per EMR encounter or medical claims or bills with at least one service line item.

Numerator Description

One per qualifying denominator observation with a starting service line number other than 1.

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)
    • Plan ID -- The identifier for a particular health insurance plan product offered by a payor.
    • 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)

  • Numerator Fields

    • Lowest Service Line Number

  • Measure Fields

    • Denominator