--- title: "[SO/URSA-HCC] Patient Timelines of Standard Final Run CMS-HCC Results" slug: "so-ursa-hcc-patient-timelines-of-standard-final-run-cms-hcc-results" updated: 2026-11-04T20:51:38Z published: 2026-11-04T20:51:38Z canonical: "docs.ursahealth.com/so-ursa-hcc-patient-timelines-of-standard-final-run-cms-hcc-results" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.ursahealth.com/llms.txt > Use this file to discover all available pages before exploring further. # [SO/URSA-HCC] Patient Timelines of Standard Final Run CMS-HCC Results ## Object Description One record per period in which the patient qualified for either the version 24 or version 28 CMS-HCC model under the Standard Final Run scenario; the blended RAF score is generated using the appropriate blending ratio for the calendar year of the period. ## Metadata - **Table Name**: ursa.so_ursa_hcc_pat_024 - **Layer**: SYNTHETIC_OBJECT - **Object Type**: Complex 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) - **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). - **Module Fields** - CMS-HCC RAF Score - CMS-HCC Raw RAF Score - CMS-HCC Demographic Component RAF Score - CMS-HCC Disease Component RAF Score - CMS-HCC RAF Score Using 2024 Blend -- The CMS-HCC RAF score generated using diagnoses and other input data as of the time period on the current record but using the model blend of 2024 (i.e., 67% from v24 and 33% from v28). - CMS-HCC RAF Score Using 2025 Blend -- The CMS-HCC RAF score generated using diagnoses and other input data as of the time period on the current record but using the model blend of 2025 (i.e., 33% from v24 and 67% from v28). - CMS-HCC v24 RAF Score - CMS-HCC v24 Raw RAF Score - CMS-HCC v28 RAF Score - CMS-HCC v28 Raw RAF Score - CMS-HCC v24 Demographic Component RAF Score - CMS-HCC v24 Demographic Component Raw RAF Score - CMS-HCC v28 Demographic Component RAF Score - CMS-HCC v28 Demographic Component Raw RAF Score - CMS-HCC v24 All Outputs Summary - CMS-HCC v28 All Outputs Summary - CMS-HCC v24 Model Output 1 Code - CMS-HCC v24 Model Output 1 Description - CMS-HCC v24 Model Output 2 Code - CMS-HCC v24 Model Output 2 Description - CMS-HCC v24 Model Output 3 Code - CMS-HCC v24 Model Output 3 Description - CMS-HCC v24 Model Output 4 Code - CMS-HCC v24 Model Output 4 Description - CMS-HCC v24 Model Output 5 Code - CMS-HCC v24 Model Output 5 Description - CMS-HCC v24 Model Output 6 Code - CMS-HCC v24 Model Output 6 Description - CMS-HCC v24 Model Output 7 Code - CMS-HCC v24 Model Output 7 Description - CMS-HCC v24 Model Output 8 Code - CMS-HCC v24 Model Output 8 Description - CMS-HCC v24 Model Output 9 Code - CMS-HCC v24 Model Output 9 Description - CMS-HCC v24 Model Output 10 Code - CMS-HCC v24 Model Output 10 Description - CMS-HCC v28 Model Output 1 Code - CMS-HCC v28 Model Output 1 Description - CMS-HCC v28 Model Output 2 Code - CMS-HCC v28 Model Output 2 Description - CMS-HCC v28 Model Output 3 Code - CMS-HCC v28 Model Output 3 Description - CMS-HCC v28 Model Output 4 Code - CMS-HCC v28 Model Output 4 Description - CMS-HCC v28 Model Output 5 Code - CMS-HCC v28 Model Output 5 Description - CMS-HCC v28 Model Output 6 Code - CMS-HCC v28 Model Output 6 Description - CMS-HCC v28 Model Output 7 Code - CMS-HCC v28 Model Output 7 Description - CMS-HCC v28 Model Output 8 Code - CMS-HCC v28 Model Output 8 Description - CMS-HCC v28 Model Output 9 Code - CMS-HCC v28 Model Output 9 Description - CMS-HCC v28 Model Output 10 Code - CMS-HCC v28 Model Output 10 Description - CMS-HCC v24 Model Output 11 Code - CMS-HCC v24 Model Output 12 Code - CMS-HCC v24 Model Output 13 Code - CMS-HCC v24 Model Output 14 Code - CMS-HCC v24 Model Output 15 Code - CMS-HCC v24 Model Output 16 Code - CMS-HCC v24 Model Output 17 Code - CMS-HCC v24 Model Output 18 Code - CMS-HCC v24 Model Output 19 Code - CMS-HCC v24 Model Output 20 Code - CMS-HCC v24 Model Output 11 Description - CMS-HCC v24 Model Output 12 Description - CMS-HCC v24 Model Output 13 Description - CMS-HCC v24 Model Output 14 Description - CMS-HCC v24 Model Output 15 Description - CMS-HCC v24 Model Output 16 Description - CMS-HCC v24 Model Output 17 Description - CMS-HCC v24 Model Output 18 Description - CMS-HCC v24 Model Output 19 Description - CMS-HCC v24 Model Output 20 Description - CMS-HCC v28 Model Output 11 Code - CMS-HCC v28 Model Output 12 Code - CMS-HCC v28 Model Output 13 Code - CMS-HCC v28 Model Output 14 Code - CMS-HCC v28 Model Output 15 Code - CMS-HCC v28 Model Output 16 Code - CMS-HCC v28 Model Output 17 Code - CMS-HCC v28 Model Output 18 Code - CMS-HCC v28 Model Output 19 Code - CMS-HCC v28 Model Output 20 Code - CMS-HCC v28 Model Output 11 Description - CMS-HCC v28 Model Output 12 Description - CMS-HCC v28 Model Output 13 Description - CMS-HCC v28 Model Output 14 Description - CMS-HCC v28 Model Output 15 Description - CMS-HCC v28 Model Output 16 Description - CMS-HCC v28 Model Output 17 Description - CMS-HCC v28 Model Output 18 Description - CMS-HCC v28 Model Output 19 Description - CMS-HCC v28 Model Output 20 Description ## Dedicated Precursors - **[SO/URSA-HCC] Patient Timelines of Standard Final Run CMS-HCC Results, Precursor 1 (Demographic Model Input Periods)**: One record per patient-period during which the patient was covered by a "Final Run" MMR record (effectively, all covered months, since we want to report final run results for all patients, even those without a change to RAF, who will therefore not have an updated MMR transaction record in the following year). The Simple Timeline object is used to merge contiguous periods in the same calendar year together when the CMS-HCC demographic component values are identical, reducing the record volume sent to the model. - **[SO/URSA-HCC] Patient Timelines of Standard Final Run CMS-HCC Results, Precursor 2 (Model Inputs)**: One record per distinct patient-period (for patients with no qualifying diagnoses in the Final Run catchment period) or per patient-period-diagnosis (for patients with qualifying diagnoses); this unusual grain size is the required format for inputs sent to the CMS-HCC model. Patients with a qualifying membership but without any qualifying diagnosis codes will have a single record for that period, with a diagnosis code value of NULL. - **[SO/URSA-HCC] Patient Timelines of Standard Final Run CMS-HCC Results, Precursor 3 (Version 24 Model Output)**: - **[SO/URSA-HCC] Patient Timelines of Standard Final Run CMS-HCC Results, Precursor 4 (Version 28 Model Output)**: