Last Updated: 2026-03-01
Status: ✅ Complete
Spec: PM-25 Value-Based Payment & APM Tracking
Constitution Reference: Section 1.2 (Core Independence), Section 1.3 (Integration Patterns)
Overview
PM-25 adds value-based payment (VBP) and alternative payment model (APM) tracking: programs, quality measures, performance levels, and incentive payments. It integrates with PM-11 (analytics/dashboards), CL-10 (outcomes data for measure numerators/denominators), CL-15 (quality measures and reporting), and PM-02/PM-01 (member/patient attribution).Integration Points (from spec)
Data Source Tables (PM-25)
Platform Layer Usage
- PM-11: Reads
pm_vbp_*tables for VBP widgets, incentive forecasting, and gap reports. No new event contracts; same-core data access. - CL-10 / CL-15: Gap identification (patients due for measures) may consume outcomes and quality data via platform integration layer or shared reporting; exact contract TBD in implementation (see spec Clarifications C-1, C-2).
- Permissions:
pm.vbp.view,pm.vbp.managegate UI; RLS enforces tenant isolation.
Event / API Contracts
- PM-11: Data only; no new events. Dashboard queries pm_vbp_*.
- CL-10 / CL-15: Integration for gap identification to be documented when implementation approach is chosen (manual list vs attribution table vs shared reporting layer).