[NO/URSA-CORE] Institutional Bill ICD Procedures

Object Description

One record per institutional bill ICD-9-CM or ICD-10-PCS procedure code.

Metadata

• Table Name: ursa.no_ursa_core_proc_002
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: Bill ID, Procedure Line Number
• Event Date: Bill Covered Start Date
• Primary Key: Bill ID, Procedure Line Number

Published Fields

• Data Model Keys

  • Bill ID -- The identifier for a professional or institutional bill header record; Bill ID values are consistent over the lifetime of a bill, including when a bill is adjusted. On a claim record, this field refers to the bill sent to the plan that originated the claim record.
  • 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.
  • 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)
  • Document ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local Bill ID -- The identifier for the bill in the original source data system. On a claim record, this field refers to the bill sent to the plan that originated the claim record.
  • Source Local Procedure Line Number -- The integer-valued ordinal for a procedure in the original source data system.

• Date Fields

  • Procedure Performed Date -- The date the procedure documented on the current record was performed. For procedures lasting more than one calendar date, this is presumed to be the procedure start date.
  • Bill Covered Start Date
  • Bill Covered End Date

• Clinical Services Fields

  • Procedure ICD-9-CM Code -- The standard 4-digit ICD-9-CM procedure code; e.g., 00.01 = Therapeutic ultrasound of vessels of head and neck. ICD-9-CM procedure codes must include a decimal point after the 2nd digit.
  • Procedure ICD-9-CM Description -- The natural language description of a ICD-9-CM procedure code.
  • Procedure ICD-10-PCS Code -- The standard 7-character ICD-10-PCS code; e.g., 00760ZZ = Dilation of Cerebral Ventricle, Open Approach.
  • Procedure ICD-10-PCS Description -- The natural language description of a ICD-10-PCS code.
  • Is Principal Procedure -- Indicates that a procedure was documented as the principal diagnosis for the claim, bill, encounter, etc.

• Metadata Fields

  • Record Last Updated Datetime -- The date and time the current record was last updated in the original data source.
  • Source Data Effective Datetime -- The "as of" date and time of the original source data system at the moment the current record was extracted. For example, if a snapshot of the data in a production system is taken at 12:05 AM on the first of each month and used to generate a package of flat files that are eventually loaded into the Ursa Studio client database later that month, the Source Data Effective Datetime of all records in that month's package will be 12:05 AM on the first. Not to be confused with Record Last Updated Datetime. (See also [URSA-CORE] Record Last Updated Datetime)

Foreign Keys

• pat_id → ursa.no_ursa_core_pat_001.pat_id

Dedicated Precursors

• [NO/URSA-CORE] Institutional Bill ICD Procedures, Precursor 1 (All Source Records): One record per institutional bill ICD-9-CM or ICD-10-PCS procedure code