[NO/URSA-CORE] Problem List Entries

Object Description

One record per problem list entry.

Metadata

• Table Name: ursa.no_ursa_core_cond_006
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Interval
• Case ID: Problem List Entry ID
• Interval Start Date: Active Start Date
• Interval End Date: Active End Date
• Primary Key: Problem List Entry ID

Published Fields

• Data Model Keys

  • Problem List Entry 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)
  • Documenting Provider 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)
  • Document ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local Problem List Entry 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)
  • Source Local Documenting Provider ID

• Operations Support Fields

  • Is Active Condition -- Indicates the condition is currently unresolved as of the source data effective date.

• Date Fields

  • Documented Date
  • Active Start Date
  • Active End Date

• Diagnosis Fields

  • Condition Description
  • Condition Operational ID
  • Condition ICD-10-CM Code
  • Condition SNOMED CT Code
  • Verification Status Description -- The natural language description of the Verification Status, typically in the original language found in the source system. (See also [URSA-CORE] Verification Status)
  • Is Verification Status Pre-Confirmation -- Indicates a level of evidence insufficient to conclude whether or not the patient has or had the condition or allergy / intolerance. (See also [URSA-CORE] Verification Status)
  • Is Verification Status Confirmed -- Indicates a clinical conclusion that the patient has or had the condition or allergy / intolerance. (See also [URSA-CORE] Verification Status)
  • Is Verification Status Refuted -- Indicates a clinical conclusion that the patient does not have or did not have the condition or allergy / intolerance. (See also [URSA-CORE] Verification Status)

• 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
• documenting_prov_id → ursa.no_ursa_core_prov_001.prov_id
• originating_emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id

Dedicated Precursors

• [NO/URSA-CORE] Problem List Entries, Precursor 1 (All Source Records): One record per problem list entry