[SO/URSA-CORE] Continuous CMS Hospice Status Episodes
  • 28 Jun 2025
  • 1 Minute to read
  • Dark
    Light

[SO/URSA-CORE] Continuous CMS Hospice Status Episodes

  • Dark
    Light

Article summary

Object Description

One record per continuous episode of CMS hospice status.

Metadata

  • Table Name: ursa.so_ursa_core_episode_004
  • Layer: SYNTHETIC_OBJECT
  • Object Type: Single Stack
  • Temporal Class: Interval
  • Case ID: Episode ID
  • Interval Start Date: Episode Start Date
  • Interval End Date: Episode End Date
  • Primary Key: Episode ID

Published Fields

  • Data Model Keys

    • Episode ID
    • 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

    • Patient Date of Death
  • Date Fields

    • Episode Start Date
    • Episode End Date

Foreign Keys

  • pat_id → ursa.no_ursa_core_pat_001.pat_id

Dedicated Precursors

  • [SO/URSA-CORE] Continuous CMS Hospice Status Episodes, Precursor 1 (Episode Component Intervals): One row per membership period with CMS hospice status.

Was this article helpful?