[NO/URSA-CORE] Tasks

Object Description

One record per task.

Metadata

• Table Name: ursa.no_ursa_core_ops_001
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: Task ID
• Event Date: Task Completed Date
• Primary Key: Task ID

Published Fields

• Data Model Keys

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

• Source Local Keys

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

• Operations Support Fields

  • Task Operational ID -- The unique, user-facing (“real-world”) identifier used by operational systems or staff to identify the Task. (See also [URSA-CORE] Task)
  • Child Task Ordinal Number
  • Task Type Description
  • Task Type Operational ID
  • Requested Activity Description
  • Performed Activity Description
  • Task Priority Description
  • Task Priority Operational ID
  • Task Status Description
  • Task Status Operational ID
  • Is Task Status Draft
  • Is Task Status Ready
  • Is Task Status In Progress
  • Is Task Status Suspended
  • Is Task Status Cancelled
  • Is Task Status Completed
  • 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.

• Date Fields

  • Task Target Start Date
  • Task Target Start Datetime
  • Task Target Completion Date
  • Task Target Completion Datetime
  • Task Started Date
  • Task Started Datetime
  • Task Completed Date
  • Task Completed 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)

Foreign Keys

• pat_id → ursa.no_ursa_core_pat_001.pat_id
• requesting_prov_id → ursa.no_ursa_core_prov_001.prov_id
• performing_prov_id → ursa.no_ursa_core_prov_001.prov_id
• originating_service_order_id → ursa.no_ursa_core_proc_004.service_order_id
• originating_medication_order_id → ursa.no_ursa_core_meds_002.medication_order_id
• originating_emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id
• performing_emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id

Dedicated Precursors

• [NO/URSA-CORE] Tasks, Precursor 1 (All Source Records): One record per task