Press CTRL+K to open search

[NO/URSA-CORE] Institutional Claim Transaction ICD Procedures

  • Published on Sep 2, 2026
  • 4 minute(s) read
Prev Next

Object Description

One record per institutional claim transaction ICD-10-PCS procedure code.

Metadata

  • Table Name: ursa.no_ursa_core_proc_005
  • Layer: NATURAL_OBJECT
  • Object Type: Single Stack
  • Case ID: Transaction Header ID, Procedure Line Number
  • Primary Key: Transaction Header ID, Procedure Line Number

Published Fields

  • Data Model Keys

    • Transaction Header ID
    • 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.
    • Claim ID -- The internal database identifier (used, e.g., for joins and primary keys) for the claim. (See also [URSA-CORE] Claim)
    • 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 -- The internal database identifier (used, e.g., for joins and primary keys) for the document. (See also [URSA-CORE] Document)
    • Source ID -- The identifier for the original source data system from which the current record originated.

  • Source Local Keys

    • Source Local Transaction Header ID -- The internal database identifier for the transaction header in the source data system this record originated from. (This field, along with Source Local Transaction Service Line Item ID, can be used when integrating data from source systems containing both header- and service-line-item-level transactions, to avoid conflating the two.) (See also [URSA-CORE] Claim or Billing Transaction)
    • Source Local Procedure Line Number -- The integer-valued ordinal for a procedure in the original source data system.
    • Source Local Claim ID -- The internal database identifier for the claim in the source data system this record originated from. (See also [URSA-CORE] Claim)
    • Source Local Patient ID -- The internal database identifier for the patient in the source data system this record originated from. (See also [URSA-CORE] Patient)

  • 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.
    • Transaction Effective Date -- The date or datetime the transaction was considered to take effect in the original source system. Often useful in determining the order in which a series of transactions within the same transaction family should be evaluated.
    • Claim Covered Start Date -- The start date of services covered by a claim.
    • Claim Covered End Date -- The end date of services covered by a claim.
    • Admit Date -- The date the patient was admitted to a care facility; note that "admission" typically implies the initiation of inpatient status, but not always, so this term should not necessarily be interpreted in that way.
    • Discharge Date -- The date the patient was discharged from a care facility.
    • Payor Incurred Date -- The date the payor considers the services associated with the record to be incurred for accounting purposes.

  • Clinical Services Fields

    • 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)
    • Source Data Loaded Datetime -- The date and time that the record was loaded into the current database environment. For systems that track the start and end datetimes of these loads, this value is meant to represent the end datetime (i.e., when the record or records have finished loading).
    • Source Data Filename -- The filename of the file that originally contained the current record; by convention, Source Data Filename values should not include the file path, but should include an extension, if it exists.

Foreign Keys

  • pat_id → ursa.no_ursa_core_pat_001.pat_id
  • claim_id → ursa.no_ursa_core_fin_001.claim_id
  • trx_header_id → ursa.no_ursa_core_fin_006.trx_header_id

Dedicated Precursors

  • [NO/URSA-CORE] Institutional Claim Transaction ICD Procedures, Precursor 1 (All Source Records): One record per ICD procedure code associated with an institutional claim transaction header record.