CMS MSSP Connector
The CMS MSSP Connector transforms report tables loaded by the MSSP Pipeline. It includes staging views, typed intermediate facts, and projected benchmark and savings outputs. It also composes the ALR and CCLF connectors for claims mapping.
The published connector chain still resolves to Tuva Core 0.17.2 through the CCLF dependency file. These instructions describe that connector workflow, not a validated Core 1.0 installation. Before adopting 1.0, update the complete dependency graph, migrate its Input Layer mappings, and validate your source with Input Data Quality. Changing a Core version pin alone does not establish connector compatibility.
Source File Coverage
The connector stages participant and provider lists; beneficiary exclusions and MBI crosswalks; MCQM quality files; BEUR, BAIP, and NCBP reports; CCLFA/B files; shadow bundles; and BNMRK, AEXPU, and QEXPU benchmark workbooks.
Model Layers
The staging layer preserves report inputs. Intermediate benchmark models normalize worksheet cells into dimensions such as enrollment type, benchmark year, report period, and delivery; member models retain enrollment type and CMS-provided risk scores.
Final outputs include fct_projected_benchmark_by_enrollment_type and fct_projected_savings. Their full grain retains repeated CMS benchmark deliveries and rows with incomplete inputs. Use the corresponding _current models for the latest calculable delivery; querying all deliveries without a filter can multiply rows. These are projections, not a replacement for CMS reconciliation.
Connector-specific semantic models and benchmark assumptions belong to this repository. They are not part of the standalone Semantic Layer 1.0 package contract. Consult the source model documentation for output grains and configuration.
Configuration and Execution
After loading the raw report tables, configure the root project:
vars:
input_database: "your_database"
input_schema: "your_mssp_schema"
cms_alr_connector: true
Run from the connector checkout with its configured warehouse profile:
dbt deps
dbt build
Review the resolved package lock before building. For Core 1.0, complete the migration described above before using this workflow with the released package set.