Measure Description
Among institutional claim or bill ICD procedure records, the percentage with at least one unpopulated critical field; critical fields are: ICD-10-PCS Code and Procedure Line Number.
Metadata
- Measure Identifier: URSA-CORE-945
- Measure Type: Rate Measure
- Temporal Structure: Event
- Component Class: Normal-Form
- Denominator Case Field: Document ID
- Target Direction: Down
Denominator Description
One per institutional claim or bill ICD procedure record.
Numerator Description
One per qualifying denominator observation with at least one unpopulated critical field; critical fields are: ICD-10-PCS Code and Procedure Line Number.
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)
- 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.
- 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
- Is ICD-10-PCS Code NULL
- Is Procedure Line Number NULL
-
Metadata Fields
- Document Type Description
-
Measure Fields
- Denominator