[SO/URSA-CORE] Patient-Plan Months with Active Membership

  • Published on Nov 19, 2025
  • 3 minute(s) read
Prev Next

Object Description

One record per patient-plan-month triple for patients with an active membership at any time during that month in any (integrated) source data membership file, regardless of attributed status. Note that the same patient might have multiple records for the same month (associated with different concurrent plan memberships).

Metadata

  • Table Name: ursa.so_ursa_core_fin_002
  • Layer: SYNTHETIC_OBJECT
  • Object Type: Single Stack
  • Temporal Class: Interval (Timeline)
  • Case ID: Patient ID, Plan ID
  • Interval Start Date: Month Start Date
  • Interval End Date: Month End Date
  • Primary Key: Patient ID, Plan ID, Month Start Date, Month 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)
    • Plan ID -- The identifier for a particular health insurance plan product offered by a payor.
    • Payor ID -- The identifier for the health insurance organization associated with the current record.
    • Plan Attributee Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Plan Attributee Provider. (See also [URSA-CORE] Plan Attributee Provider)
    • Plan Attributee Individual Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Plan Attributee Individual Provider. (See also [URSA-CORE] Plan Attributee Individual Provider)
    • Plan Attributee Provider Group Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Plan Attributee Provider Group. (See also [URSA-CORE] Plan Attributee Provider Group)
    • Plan Attributee Provider Contract ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Plan Attributee Provider Contract. (See also [URSA-CORE] Plan Attributee Provider Contract)
    • Risk Program Entity ID
    • Provider Partner ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Provider Partner. (See also [URSA-CORE] Provider Partner)
    • 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)

  • Operations Support Fields

    • Plan Attributee Provider Contract Operational ID

  • Patient Fields

    • Member MBI

  • Date Fields

    • Month Start Date -- The start date (e.g., January 1, February 1, etc.) of the month in the patient's life described by the current record.
    • Month End Date
    • First Membership Date in Month
    • Last Membership Date in Month

  • Insurance Fields

    • Payor Description
    • Plan Description
    • Plan CMS Contract Number
    • Plan CMS PBP Number
    • Plan CMS Segment Number
    • Group Operational ID
    • Subgroup Operational ID
    • Is Patient Attributed -- Indicates the patient is, during the period specified by the current record, considered attributed to the Ursa client organization.
    • Is Patient Attributed with Risk -- Indicates the patient is, during the period specified by the current record, considered attributed to the Ursa client organization, and, additionally, considered qualified for inclusion in risk-based payment model calculations.
    • Risk Program Entity Operational ID
    • Is SNP Membership According to Source Data
    • Is C-SNP Membership According to Source Data
    • Is D-SNP Membership According to Source Data
    • Is I-SNP Membership According to Source Data

  • Metadata Fields

    • Membership Rank Within Patient-Month
    • Membership Days as Fraction of Month

  • Validation Only Fields

    • Is Multiple Contracts Within Member-Month
    • Individual Provider TIN for Business Entity Identification
    • Individual Provider NPI for Business Entity Identification
    • Provider Group TIN for Business Entity Identification
    • Provider Group NPI for Business Entity Identification

Foreign Keys

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