[NO/URSA-CORE] Service Orders

Object Description

One record per service order.

Metadata

• Table Name: ursa.no_ursa_core_proc_004
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: Service Order ID
• Event Date: Ordered Date
• Primary Key: Service Order ID

Published Fields

• Data Model Keys

  • Service Order ID -- The internal database identifier (used, e.g., for joins and primary keys) for the service order. (See also [URSA-CORE] Service Order)
  • 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)
  • Service ID -- The internal database identifier (used, e.g., for joins and primary keys) for the service. (See also [URSA-CORE] Service)
  • Ordering Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the ordering provider. (See also [URSA-CORE] Ordering Provider)
  • Receiving Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the receiving provider. (See also [URSA-CORE] Receiving Provider)
  • Originating EMR Encounter ID -- The internal database identifier (used, e.g., for joins and primary keys) for the EMR encounter that is the originating encounter of the given document. (See also [URSA-CORE] EMR Encounter, [URSA-CORE] Originating EMR Encounter)
  • Document ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local Service Order ID -- The internal database identifier for the service order in the source data system this record originated from. (See also [URSA-CORE] Service Order)
  • 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)
  • Source Local Service ID
  • Source Local Ordering Provider ID -- The internal database identifier for the ordering provider in the source data system this record originated from. (See also [URSA-CORE] Ordering Provider)
  • Source Local Receiving Provider ID -- The internal database identifier for the receiving provider in the source data system this record originated from. (See also [URSA-CORE] Receiving Provider)

• Operations Support Fields

  • Order Number -- The unique, user-facing (“real-world”) identifier used by operational systems or staff to identify the service order. (See also [URSA-CORE] Service Order)

• Date Fields

  • Ordered Date -- The calendar date the order was entered into the EMR or otherwise created.
  • Ordered Datetime -- The date and time the order was entered into the EMR or otherwise created.
  • Order Expiration Date -- The calendar date on which the order is considered to have expired.

• Provider Fields

  • Ordering Provider Description
  • Ordering Provider NPI
  • Receiving Provider Description
  • Receiving Provider NPI

• Clinical Services Fields

  • Service Description
  • Is Referral Order -- Indicates that the service order is a referral. (See also [URSA-CORE] Service Order)
  • Is Lab Order -- Indicates that the service order is for a lab-related service. (See also [URSA-CORE] Service Order)
  • Is Imaging Order -- Indicates that the service order is for an imaging-related service. (See also [URSA-CORE] Service Order)

• Diagnosis Fields

  • Primary Indication Description
  • Primary Indication ICD-10-CM Code -- The standard ICD-10-CM code for the order's primary indication. (See also [URSA-CORE] Primary Indication)
  • Primary Indication SNOMED CT Code -- The standard SNOMED CT code for the order's primary indication. (See also [URSA-CORE] Primary Indication)

• Metadata Fields

  • Order Status Description -- The natural language description of the order status. (See also [URSA-CORE] Order Status)
  • Order Status Operational ID -- The unique, user-facing (“real-world”) identifier used by operational systems or staff to identify the order status. (See also [URSA-CORE] Order Status)
  • Is Order Status Draft -- Indicates that the order is in draft form, and not yet issued. (See also [URSA-CORE] Order Status)
  • Is Order Status Issued Only -- Indicates that the order has been finalized and sent to the receiving provider but not yet accepted; nor suspended or cancelled. (See also [URSA-CORE] Order Status)
  • Is Order Status Active -- Indicates that the order has been issued and accepted by the receiving provider, but not completed, cancelled, or suspended. (See also [URSA-CORE] Order Status)
  • Is Order Status Suspended -- Indicates that activities to complete the order have been temporarily stopped, either by request of the ordering provider or some other authority. (See also [URSA-CORE] Order Status)
  • Is Order Status Cancelled -- Indicates that activities to complete the order have been permanently stopped, either by request of the ordering provider or some other authority. In most cases, an order that has been replaced should be considered cancelled. (See also [URSA-CORE] Order Status)
  • Is Order Status Completed -- Indicates that the order has been completed by the receiving provider. (See also [URSA-CORE] Order Status)
  • Is Order Ever Order Status Active -- Indicates that the order reached an order status of active at any point, whether or not it was subsequently accepted, completed, cancelled, or suspended. (See also [URSA-CORE] Is Order Status Active)
  • Other EMR Comments -- Any other annotations or comments associated with the current record entered into the EMR.
  • 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
• medication_id → ursa.no_ursa_core_meds_001.medication_id
• prescribing_prov_id → ursa.no_ursa_core_prov_001.prov_id
• ordering_prov_id → ursa.no_ursa_core_prov_001.prov_id
• receiving_prov_id → ursa.no_ursa_core_prov_001.prov_id
• originating_emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id
• service_id → ursa.no_ursa_core_proc_003.service_id

Dedicated Precursors

• [NO/URSA-CORE] Service Orders, Precursor 1 (All Source Records): One record per service order in a source system