[NO/URSA-CORE] Patient-Source Timelines of Data Coverage

Object Description

One record per patient-source timeline period during which at least one of the flagged data types for that patient would be included in the imported files from that data source if such records existed. NB: Input data to this object from each source should already be non-overlapping within a patient, and therefore the union of those should also be non-overlapping within a patient-source pair; using a Simple Timeline here represents a fail-safe that guarantees this non-overlapping structure.

Metadata

• Table Name: ursa.no_ursa_core_pat_002
• Layer: NATURAL_OBJECT
• Object Type: Simple Timeline
• Temporal Class: Interval (Timeline)
• Case ID: Patient ID, Source ID
• Interval Start Date: Period Start Date
• Interval End Date: Period End Date
• Primary Key: Patient ID, Source 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)
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Date Fields

  • Period Start Date
  • Period End Date

• Metadata Fields

  • Is Institutional Claim Data Coverage -- Indicates data coverage for institutional claims from at least one data source for the patient and time period specified on the record. (See also [URSA-CORE] Data Coverage)
  • Is Institutional Claim Paid Amount Data Coverage -- Indicates data coverage for institutional claims, with plan paid amounts populated at least at the claim header level, from at least one data source for the patient and time period specified on the record. (See also [URSA-CORE] Data Coverage)
  • Is Institutional Claim Service Line Item Paid Amount Data Coverage -- Indicates data coverage for institutional claims, with plan paid amounts populated at the claim service line item level, from at least one data source for the patient and time period specified on the record. (Having line-level paid amounts allows finer-grained analyses than those possible when paid amounts are only available at the header-level.) (See also [URSA-CORE] Data Coverage)
  • Is Professional Claim Data Coverage -- Indicates data coverage for professional claims from at least one data source for the patient and time period specified on the record. (See also [URSA-CORE] Data Coverage)
  • Is Professional Claim Paid Amount Data Coverage -- Indicates data coverage for professional claims, with plan paid amounts populated at least at the claim header level, from at least one data source for the patient and time period specified on the record. (See also [URSA-CORE] Data Coverage)
  • Is Professional Claim Service Line Item Paid Amount Data Coverage -- Indicates data coverage for professional claims, with plan paid amounts populated at the claim service line item level, from at least one data source for the patient and time period specified on the record. (Having line-level paid amounts allows finer-grained analyses than those possible when paid amounts are only available at the header-level.) (See also [URSA-CORE] Data Coverage)
  • Is Pharmacy Claim Data Coverage -- Indicates data coverage for pharmacy claims from at least one data source for the patient and time period specified on the record. (See also [URSA-CORE] Data Coverage)
  • Is Pharmacy Claim Paid Amount Data Coverage -- Indicates data coverage for pharmacy claims, with plan paid amounts populated, from at least one data source for the patient and time period specified on the record. (See also [URSA-CORE] Data Coverage)
  • 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)

Dedicated Precursors

• [NO/URSA-CORE] Patient-Source Timelines of Data Coverage, Precursor 1 (All Source Records): One record per patient-source timeline period during which at least one of the flagged data types for that patient would be included in the imported files from that data source if such records existed.