URSA-CORE-947: Documents with Non-Standard NPIs

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

Measure Description

Among documents with an NPI, the percentage with a non-standard NPI; non-standard NPIs are those that don't appear in the URSA-CORE NPI reference object.

Metadata

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

Denominator Description

One per document with a non-missing NPI code

Numerator Description

One per qualifying denominator observation with a non-standard NPI; non-standard NPIs are those that don't appear in the URSA-CORE NPI 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)
    • 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)

  • Provider Fields

    • Service Provider Provider NPI
    • Attending Provider Provider NPI
    • Billing Provider Provider NPI
    • Dispensing Provider Provider NPI
    • Facility Provider Provider NPI
    • Ordering Provider Provider NPI
    • Provider Group Provider NPI

  • Diagnosis Fields

    • ICD-10-CM Code
    • ICD-10-CM Description

  • Denominator Fields

    • Is Document with at least one Non-Standard NPI

  • Metadata Fields

    • Document Type Description

  • Validation Only Fields

    • Is Service Provider NPI Missing from NPPES Reference Data
    • Is Attending Provider NPI Missing from NPPES Reference Data
    • Is Billing Provider NPI Missing from NPPES Reference Data
    • Is Dispensing Provider NPI Missing from NPPES Reference Data
    • Is Facility Provider NPI Missing from NPPES Reference Data
    • Is Ordering Provider NPI Missing from NPPES Reference Data
    • Is Provider Group NPI Missing from NPPES Reference Data

  • Measure Fields

    • Denominator