[NO/URSA-CORE] Patient Observations

Object Description

One record per patient observation, including lab results, patient questionnaires, imaging studies, etc.

Metadata

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

Published Fields

• Data Model Keys

  • Patient Observation ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Patient Observation (See also [URSA-CORE] Patient Observation)
  • Parent Patient Observation ID
  • 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)
  • 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)
  • 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)
  • Observation-Generating EMR Encounter ID
  • Observation-Generating EMR Encounter Service Line Item ID
  • Observation-Generating Service ID
  • Observation-Generating Service Provider ID
  • Document ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local Patient Observation ID
  • 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)

• 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)
  • Accession Number

• Date Fields

  • Observation-Generating Service Date
  • Observation-Generating Service Datetime
  • Result Finalized Date
  • Result Finalized Datetime

• Metadata Fields

  • 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-Generating Service Description
  • Observation-Generating Service Operational ID
  • Observation-Generating Service HCPCS Code
  • Observation-Generating Service LOINC Code
  • Observation-Generating Service SNOMED CT Code
  • Observation-Generating Service Type Description
  • Is Observation-Generating Service Type Lab
  • Is Observation-Generating Service Type Physical Exam
  • Is Observation-Generating Service Type Imaging
  • Is Observation-Generating Service Type Survey
  • Is Observation-Generating Service Type Device
  • Is Observation-Generating Service Type Procedure
  • Is Observation-Generating Service Type Flowsheet
  • Is Observation-Generating Service Type Other
  • Result Type Description
  • Result Type Operational ID
  • Result Type LOINC Code
  • Result Type SNOMED CT Code
  • Result Status Description
  • Result Status Operational ID
  • Is Result Status Finalized
  • Is Result Status Cancelled
  • Result Description
  • Result Operational ID
  • Result LOINC Code
  • Result SNOMED CT Code
  • Result Numeric
  • Result Units Description
  • Result Ratio Numerator
  • Result Ratio Denominator
  • Result Range Start Value
  • Result Range End Value
  • Reference Range Start Value
  • Reference Range End Value
  • Result Interpretation Description
  • Is Result Interpretation Normal
  • Is Result Interpretation Abnormal
  • Is Result Interpretation Positive
  • Is Result Interpretation Negative
  • Is Result Interpretation Susceptible
  • Is Result Interpretation Intermediate Susceptibility
  • Is Result Interpretation Resistant
  • Is Result Interpretation Non-Susceptible
  • Is Result Interpretation Reactive
  • Is Result Interpretation Non-Reactive

Terms

• Patient Observation: An instance of a documented observation about a patient, such as a lab result, imaging study, assessment tool response, flowchart entry, etc.; a Patient Observation object includes fields capturing the service that was performed to generate the observation, the type of result, and the result value; Patient Observations may also have subordinate Patient Observations representing finer-grained, component results that contribute to a higher-level result.

Foreign Keys

• parent_pat_obs_id → ursa.no_ursa_core_pat_003.pat_obs_id
• pat_id → ursa.no_ursa_core_pat_001.pat_id
• obs_report_id → ursa.no_ursa_core_pat_004.obs_report_id
• observation_generating_emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id
• observation_generating_emr_enc_service_line_item_id → ursa.no_ursa_core_enc_002.emr_enc_service_line_item_id
• observation_generating_service_id → ursa.no_ursa_core_proc_003.service_id
• observation_generating_service_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] Patient Observations, Precursor 1 (All Source Records): One row per patient observation found in a source system