[NO/URSA-CORE] Patient Timelines of Time-Varying Features

Object Description

One record per patient timeline period in which a targeted time-varying patient feature is known.

Metadata

• Table Name: ursa.no_ursa_core_pat_010
• Layer: NATURAL_OBJECT
• Object Type: Complex Timeline
• Temporal Class: Interval (Timeline)
• Case ID: Patient ID
• Interval Start Date: Period Start Date
• Interval End Date: Period End Date
• Primary Key: Patient ID, Period Start Date, Period End Date

Published Fields

• Data Model Keys

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

• Patient Fields

  • Risk Score
  • Risk Category Operational ID
  • Risk Category Description
  • Is Active Patient
  • Engagement Category Operational ID
  • Engagement Category Description

• Date Fields

  • Period Start Date
  • Period End Date

Foreign Keys

• pat_id → ursa.no_ursa_core_pat_001.pat_id

Dedicated Precursors

• [NO/URSA-CORE] Patient Timelines of Time-Varying Features, Precursor 1 (All Source Records): One record per patient period in which a targeted time-varying feature is known. Each stack in this integrator should (1) contain only records from a single source (as usual); and (2) conform to the non-overlappingness characteristics of a timeline with respect to other records within that stack.
• [NO/URSA-CORE] Patient Timelines of Time-Varying Features, Precursor 2 (Patient-Field Block Timelines): One record per patient-field block timeline period. Effectively, this object acts to ensure that the data submitted through the first precursor conforms to the necessary timeline format of non-overlappingness within a patient-field block combination (even when, potentially, records originate in different sources).