[NO/URSA-CORE] Professional Bill ICD Diagnoses

Object Description

One record per diagnosis (expressed as ICD-9-CM and/or ICD-10-CM code) associated with a professional bill service line item.

Metadata

• Table Name: ursa.no_ursa_core_cond_004
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: Bill Service Line Item ID, Diagnosis Line Number
• Event Date: Service Start Date
• Primary Key: Bill Service Line Item ID, Diagnosis 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.
  • Bill Service Line Item ID -- The identifier for a service line item on an institutional or professional bill.
  • Service Line Number -- The integer-valued ordinal representing the position of a service line item in a claim, bill, encounter, or other master record. May not necessarily match the analogous value in the source data for the same record.
  • Diagnosis Line Number -- The integer-valued ordinal representing the position of a diagnosis on a claim, bill, encounter, or other master record. May not necessarily match the analogous value in the source data for the same record. Typically, the diagnosis in the first position is considered the principal diagnosis, though this is not an absolute rule, and the Is Principal Diagnosis field should be used to identify the principal diagnosis.
  • 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 Bill Service Line Item ID -- The identifier for the bill service line item 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 Service Line Number -- The integer-valued ordinal for a service line item in the original source data system.
  • Source Local Diagnosis Line Number -- The integer-valued ordinal for a diagnosis in the original source data system.

• Date Fields

  • Bill Covered Start Date
  • Bill Covered End Date
  • Service Start Date -- The first calendar date a service was delivered.
  • Service End Date -- The last calendar date a service was delivered.

• Diagnosis Fields

  • Diagnosis ICD-9-CM Code -- The standard ICD-9-CM diagnosis code; e.g., 001.0 = Cholera due to vibrio cholerae. ICD-9-CM diagnosis codes longer than 3 digits must include a decimal point after the 3rd digit.
  • Diagnosis ICD-9-CM Description -- The natural language description of a ICD-9-CM diagnosis code. (See also [URSA-CORE] Diagnosis ICD-9-CM Code)
  • Diagnosis ICD-10-CM Code -- The standard ICD-10-CM diagnosis code; e.g., A00 = Cholera. ICD-10-CM diagnosis codes longer than 3 digits must include a decimal point after the 3rd digit.
  • Diagnosis ICD-10-CM Description -- The natural language description of a ICD-10-CM diagnosis code. (See also [URSA-CORE] Diagnosis ICD-10-CM Code)
  • Is Principal Diagnosis -- Indicates that a diagnosis 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
• bill_id → ursa.no_ursa_core_fin_013.bill_id
• bill_service_line_item_id → ursa.no_ursa_core_fin_013.bill_service_line_item_id

Dedicated Precursors

• [NO/URSA-CORE] Professional Bill ICD Diagnoses, Precursor 1 (All Source Records): One record per diagnosis (expressed as ICD-9-CM and/or ICD-10-CM code) associated with a professional bill service line item