ACCESS Program Support
Prepares Healthie customers participating in CMS's ACCESS payment model to meet its FHIR-based eligibility, alignment, and outcomes-reporting requirements, with the CMS-specific API integration being built by a third-party agency.
Built by Core Engineering
The problem it solves
Organizations accepted into CMS's ACCESS model must integrate with CMS's FHIR-based eligibility, alignment, and outcomes-reporting APIs and establish HIE connectivity — requirements far beyond standard EHR configuration, on a fixed regulatory timeline.
What's included
- Native outcome-data capture (clinical metrics, custom measures, lab tracking) for track-specific measures (BP, HbA1c, weight, PHQ-9/GAD-7, MSK PROMs)
- ONC-certified FHIR R4 API layer (Healthie Cures 1, certified Dec 2022) as the technical foundation
- Native care plan creation, sharing, and milestone documentation
- HIE/bidirectional PCP connectivity support via Zus Health or an equivalent partner
- CMS-specific API integration (eligibility, alignment, and future outcomes reporting) being built by a third-party agency, pending CMS's final reporting spec
How it works
Healthie's existing native capabilities (clinical metrics, forms, care plans, messaging) cover much of ACCESS's documentation and care-coordination requirements out of the box. The CMS-specific integration work — connecting to CMS's $check-eligibility and $align/$unalign FHIR operations, and eventually $report-data once CMS publishes its field-level spec — is being built by a third-party agency rather than in-house. Customers must separately establish HIE connectivity (commonly via Zus Health) within 12 months of their ACCESS model entry date; that relationship is independent of Healthie.
ACCESS Program Support prepares Healthie customers participating in CMS's ACCESS payment model to meet its FHIR-based eligibility, alignment, and reporting requirements. It's for practices enrolled in one of ACCESS's four clinical tracks, and much of the underlying documentation work is already covered by Healthie's native tools. What's being built specifically is the CMS-facing API integration itself, developed in partnership with a third-party agency. Participants must separately establish HIE connectivity within 12 months of their model entry date, which is the customer's own responsibility.
