[NO/URSA-CORE] Observation Reports

Object Description

One record per observation report.

Metadata

• Table Name: ursa.no_ursa_core_pat_004
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: Observation Report ID
• Event Date: Report Finalized Date
• Primary Key: Observation Report ID

Published Fields

• Data Model Keys

  • Observation Report ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Observation Report (See also [URSA-CORE] Observation Report)
  • 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 Order ID -- The internal database identifier (used, e.g., for joins and primary keys) for the service order. (See also [URSA-CORE] Service Order)
  • Authoring Provider ID
  • Source ID -- The identifier for the original source data system from which the current record originated.
  • Document ID

• Source Local Keys

  • Source Local Observation Report ID -- The internal database identifier for the Observation Report in the source data system this record originated from. (See also [URSA-CORE] Observation Report)
  • 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 Authoring Provider ID

• Operations Support Fields

  • Observation Report Operational ID
  • 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

  • Report Finalized Date
  • Report Finalized Datetime

• Metadata Fields

  • Observation Report Status Description
  • Observation Report Status Operational ID
  • Is Observation Report Status Finalized
  • Is Observation Report Status Cancelled
  • 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)

• Patient Observation Fields

  • Observation Report Type Description
  • Observation Report Type Operational ID
  • Narrative Text
  • Conclusion Description -- The natural language description of the results of activity, such as a task or instance of communication, whether it was completed successfully or not.
  • Conclusion Operational ID -- The "real-life" identifier for the results of activity, such as a task or instance of communication, whether it was completed successfully or not.
  • Conclusion Primary ICD-10-CM Code
  • Conclusion Primary SNOMED CT Code

Foreign Keys

• pat_id → ursa.no_ursa_core_pat_001.pat_id
• authoring_prov_id → ursa.no_ursa_core_prov_001.prov_id
• service_order_id → ursa.no_ursa_core_proc_004.service_order_id

Dedicated Precursors

• [NO/URSA-CORE] Observation Reports, Precursor 1 (All Source Records): One record per observation report