[SO/URSA-CORE] Patient Timelines of Primary Plan Membership

  • Published on Apr 10, 2026
  • 1 minute(s) read
Prev Next

Object Description

One record per patient timeline period in which the patient has at least one active insurance plan coverage, with attribution to the primary plan; primary plan is determined based on the following criteria, evaluated in this order (1) the plan identified as primary in the membership record or had provider-side risk; (2) the plan with any attribution to a provider; (3) the plan with a non-reversed MMR record in that month; (4) the plan that is not a Medicaid plan; (5) the plan with the lowest Plan ID (tiebreaker).

Metadata

  • Table Name: ursa.so_ursa_core_fin_005
  • Layer: SYNTHETIC_OBJECT
  • Object Type: Attribution 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)
    • Primary Plan ID -- The identifier for the health insurance plan product that is the first party responsible for payment.

  • Date Fields

    • Period Start Date -- The date identifying the start of a period of time. Period Start Date values are inclusive; e.g., a period with Period Start Date = January 1 would begin be considered to begin at 00:00 on January 1.
    • Period End Date -- The date identifying the end of an period of time. Period End Date values are exclusive; e.g., a period with Period End Date = January 1 would begin be considered to end at precisely 00:00 on January 1 (meaning that the period did not include any time on January 1).

  • Validation Only Fields

    • Is Plan Designated Primary or with Provider-Side Risk
    • Is Plan with Any Attribution
    • Count MMR Member-Months

Foreign Keys

  • pat_id → ursa.no_ursa_core_pat_001.pat_id
  • primary_plan_id → ursa.no_ursa_core_struct_005.plan_id