[NO/URSA-CORE] Patient-Program Entity Affiliation Timelines

Object Description

One record per timeline period of affiliation between a patient and a program entity.

Metadata

• Table Name: ursa.no_ursa_core_pat_011
• Layer: NATURAL_OBJECT
• Object Type: Simple Timeline
• Temporal Class: Interval (Timeline)
• Case ID: Patient ID, Affiliated Program Entity ID
• Interval Start Date: Period Start Date
• Interval End Date: Period End Date
• Primary Key: Patient ID, Affiliated Program Entity 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)
  • Affiliated Program Entity ID -- The internal database identifier (used, e.g., for joins and primary keys) for the affiliated program entity of the reference patient or provider. (See also [URSA-CORE] Affiliated Program Entity)
  • Affiliated Program Entity Provider ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • 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 Affiliated Program Entity ID
  • Source Local Affiliated Program Entity Provider ID

• Operations Support Fields

  • Patient Operational ID -- The user-facing value used by staff used to uniquely identify the Patient in their administrative systems and/or day-to-day operations. (See also [URSA-CORE] Patient)
  • Program Entity Operational ID
  • Program Operational ID

• Date Fields

  • Period Start Date
  • Period End Date

• Metadata Fields

  • 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
• affiliated_program_entity_id → ursa.no_ursa_core_struct_003.program_entity_id
• affiliated_program_entity_prov_id → ursa.no_ursa_core_prov_001.prov_id

Dedicated Precursors

• [NO/URSA-CORE] Patient-Program Entity Affiliation Timelines, Precursor 1 (All Source Records): One record per timeline period of affiliation between a patient and a program entity.