What Does the CMS ACCESS Model Require From Your Software?
Key Takeaways
- The CMS ACCESS Model pays $180 to $420 per patient for the first year, by track, and withholds half the Medicare portion until outcomes are reconciled.
- Every clinical outcome goes to CMS through a FHIR-based Reporting API, and a patient is unaligned if valid baseline measures don’t arrive within 60 days.
- Care updates must reach the patient’s primary care clinician through Direct messaging, an HIE, or a CMS Aligned Network; your own portal doesn’t count.
- Under the FFS Exclusion, you can’t bill RPM or CCM codes for an aligned patient, so per-patient software and device costs have to fit inside the ACCESS payment.
- Adding ACCESS reporting to an existing RPM or virtual care product typically runs $40K–90K over 8–14 weeks; a new single-track platform runs $150K–300K.
CMS ACCESS marks the first Original Medicare payment model designed for tech-enabled chronic care that rewards actual recovery. Most commentary will frame this as a simple reimbursement shift, but engineers will see a detailed software requirements document.
CMS dictates very precisely which endpoints you touch, the clinical metrics you track, tight delivery windows, and who must get automated care summaries the moment a patient reaches a required treatment milestone.
The model started on July 5, 2026, with more than 160 participating organizations, and it runs until June 30, 2036. CMS takes applications on a rolling basis through 2033. Five new tracks (heart failure, COPD, substance use disorder, tobacco cessation and a follow-on chronic MSK pain track) open on April 1, 2027.
Plenty of teams already have most of the pieces. A product built on solid remote patient monitoring software development collects readings, flags gaps and keeps an audit trail. What’s missing is usually the CMS-facing layer, plus the clinician-to-clinician messaging that ACCESS treats as mandatory.Â
Tech Exactly works on these builds as a healthcare app development company, and what follows is our read of what that layer involves and what it costs, drawn from the ACCESS Model RFA (Request for Applications), the payment amounts document and CMS’s technical FAQ.
What Is the CMS ACCESS Model?
ACCESS, short for Advancing Chronic Care with Effective, Scalable Solutions, is CMMI’s voluntary 10-year model piloting Outcome-Aligned Payments (OAPs) in Original Medicare. Whether you call it the Medicare ACCESS or CMMI ACCESS model, participating entities collect regular management fees per qualified patient.
However, retaining the full financial rate will demand verifiable clinical recovery: a predefined percentage of your cohort must reach target metrics, such as lowering systolic blood pressure by 15 mmHg or demonstrating defined threshold gains on PHQ-9 assessments.
Participants have to be Medicare Part B-enrolled providers or suppliers (DME and lab suppliers are excluded). They also need an active TIN, a physician Medical Director, and status as a HIPAA-covered entity.
Individuals onboard through direct sign-ups or physician referrals, while CMS logs risk-stratified outcome data in a public provider registry. Medicare Advantage remains outside the program’s scope, though commercial insurers covering over 165 million Americans have already promised to launch complementary payment programs aligned with ACCESS standards.
The four initial tracks group conditions that are usually treated the same way:
| Track | Qualifying conditions | What counts as success |
|---|---|---|
| eCKM (early cardio-kidney-metabolic) | Hypertension, or two or more of dyslipidemia, obesity/overweight with central obesity, prediabetes | Control or minimum improvement in BP, lipids, weight and HbA1c |
| CKM (cardio-kidney-metabolic) | Diabetes, CKD stage 3a/3b, or ASCVD | Same measures as eCKM, plus eGFR and UACR submission for CKD and diabetes |
| MSK (musculoskeletal) | Chronic MSK pain lasting more than three months | Minimum improvement in pain intensity, interference and function on a validated PROM |
| BH (behavioral health) | Depression or anxiety | Minimum improvement on PHQ-9 or GAD-7, plus WHODAS 2.0 (12-item) submission |
Your product is responsible for every qualifying condition in a track. You can’t run a hypertension-only program in eCKM and leave a patient’s prediabetes to someone else.
How Does ACCESS Model Payment Work for Your Platform?
Annual allowable payments per beneficiary encompass both Medicare’s 80% liability and the individual’s 20% coinsurance obligation. Under an established CMS safe harbor, participating entities are permitted to waive patient fees completely, as long as the decision applies universally across every enrolled case.
The figures below cover July 5, 2026 to December 31, 2027 and come from the ACCESS payment amounts and performance targets published by CMS:
| Track | Initial period (12 months) | Follow-on period | Device assumed in rate |
|---|---|---|---|
| eCKM | $360 | $180 | Cellular blood pressure cuff |
| CKM | $420 | $210 | Cellular blood pressure cuff |
| MSK | $180 | None | None |
| BH | $180 | $90 | None |
Rural eCKM and CKM patients add a fixed $15 to cover device distribution. When one patient is enrolled in two tracks with the same participant, CMS takes 5% off the cheaper track for the months they overlap.
Monthly revenue cycles process through designated G-code claims submitted directly to your Medicare Administrative Contractor. Interim disbursements are held at 50% of the federal Medicare share, leaving the second half escrowed until the full 12-month treatment cycle concludes. CMS then reconciles that withheld balance against documented clinical targets and substitute spending (ancillary Medicare outlays for managing that condition).
For the initial 18-month rollout, clearing the 50% Outcome Attainment Threshold unlocks complete funding. Performance below that mark triggers a proportional haircut—achieving 40% success delivers 80% of total revenue, though overall deductions cannot exceed 50% of your gross allowable amount.
A patient only counts as a success if every required measure was reported on time and every target was met, so one late HbA1c costs you the whole patient. And the FFS Exclusion stops you, and any affiliated entity, from billing Medicare fee-for-service for other services to an aligned patient.
For an eCKM patient, the most you can collect in a year is $360, and RPM codes like 99454 and 99457 are off the table. Device logistics, clinician time and software all have to fit inside that number.
What Data Does the ACCESS Model Make You Report?
CMS has built the model around four APIs, and your platform will talk to all of them:
- Eligibility API. Confirm the patient is in Original Medicare and qualifies for the track before you enroll them.
- Alignment API. Formally connects the patient to your organization for a track. Each patient can align with just one participant per track and can change after 90 days.
- Reporting API (FHIR-based). Receives every outcome measure. The RFA points to the HL7 Person-Centered Outcomes (PCO) FHIR Implementation Guide for the profiles, and CMS has said a detailed implementation guide is coming.
- BCDA API. The Beneficiary Claims Data API gives you Part A, B, and D claims for aligned patients—helpful for coordinating care and tracking substitute spend.
The reporting calendar is strict, and it should drive your data model:
- Baseline: valid baseline measures within 60 days of alignment, or the patient is unaligned and you have to start over through the Alignment API.
- Quarterly: Space each subsequent reporting transmission 70 to 110 days apart. These quarterly readings never determine payment, but missing a cycle terminates the active-care standing required for uninterrupted billing.
- End of period: no later than day 425 after alignment. Early success reporting is allowed up to 90 days before day 365 for eCKM and CKM, and 180 days before for BH and MSK.
- Validity windows: every measure has a maximum gap between the collection date and the submission date. An HbA1c can be up to 24 months old as a baseline for an eCKM patient without prediabetes.
Every submitted value needs its data source, collection date, and method. Capture provenance with each reading from the start. A cuff reading and a nurse‑typed value use different FHIR Observation metadata, and fixing that afterward is tough.
CMS also asks participants to implement standardized patient and population services APIs that meet the ONC certification criteria under 45 CFR 170.315(g)(10). If your product has never had to expose a certified FHIR API, plan for it as its own workstream.
How Do ACCESS Model Care Updates Reach Primary Care?
ACCESS assumes you are augmenting, not replacing, the patient’s primary care ecosystem. Teams must take proactive steps to confirm the patient’s PCP and referring physician, routing standardized clinical progress notes at treatment initiation, completion, and key events. Accepted channels include Direct Secure Messaging.
HIE push/subscription mechanisms, and HIPAA-compliant e-fax. Merely hosting updates in your proprietary portal fails to meet requirements without embedded clinician integrations. Come July 2027, connecting to an HIE, CMS Aligned Network, or comparable federated network becomes a hard mandate.
Most chronic care management software, including almost every chronic care management platform sold to practices, never had to solve this routing problem. The same building blocks show up in care coordination software: a recipient directory, message templates tied to clinical events, retry logic and a delivery log. If the receiving practice runs an older EHR, expect some HL7 integration work as well, because plenty of HIE feeds still arrive as v2 messages.
External clinicians actually benefit from reviewing incoming transmissions. Any PCP who reads an ACCESS update and notes an intervention in their EHR qualifies for a ~$30 co-management G-code, alongside a ~$10 initial intake reimbursement, maxing out at roughly $100 per patient, track, and year, entirely exempt from patient coinsurance.
Which ACCESS Model Tracks Fit Your Product?
Track choice decides most of the build, and the four tracks split into two very different products.
eCKM and CKM are device-and-lab products. The rates assume a cellular-connected blood pressure cuff, which spares older patients the Bluetooth pairing step that sinks many home monitoring programs. You also need lab results for HbA1c and LDL-C, and for CKM patients with CKD or diabetes, eGFR and UACR submissions.
Your platform requires device ingestion layers, inbound/outbound lab interfaces, medication titration workflows, and real-time clinical threshold notifications. Engineering teams with remote patient monitoring experience already possess these core primitives. The actual engineering challenge lies in mapping existing telemetry cleanly to CMS ACCESS measure specifications and rigid submission timetables.
BH and MSK are questionnaire products. Success depends on validated PROMs: PHQ-9, GAD-7 and WHODAS 2.0 for behavioral health, and a pain and function instrument for MSK. That shifts the engineering toward survey scheduling, reminders, accessible forms for older users and safety escalation when a PHQ-9 answer flags risk.
Existing behavioral health software usually handles the questionnaires but not the CMS reporting or the PCP updates. Video visits fit naturally here too, and teams that have done telemedicine app development can reuse the scheduling and visit flow.
The April 2027 heart failure and COPD rollouts primarily lean on device hardware. Meanwhile, substance use disorder must navigate DEA telemedicine controlled-substance rules, whose temporary exceptions terminate on December 31, 2026, without further intervention.
What Does FDA Require From ACCESS Model Devices and Apps?
ACCESS provides zero relief from FDA scrutiny. Enrolled entities must confirm that every integrated device and algorithmic capability carries legitimate marketing authorization or meets established enforcement discretion criteria. Basic administrative infrastructure and passive storage engines avoid device status.
However, software recommending medication titration, interpreting patient streams to drive clinical care, or administering active software therapies almost certainly qualifies.
The FDA TEMPO pilot (Technology-Enabled Meaningful Patient Outcomes) is the model’s release valve. A manufacturer whose digital health device would normally need premarket authorization can ask FDA to exercise enforcement discretion when the device is used in ACCESS, provided it follows an agreed plan for risk mitigation and real-world performance data.
FDA limits TEMPO to 10 US-based manufacturers per clinical track. Patients using a TEMPO device have to give enhanced consent, and the data you send to FDA goes beyond normal ACCESS reporting.
If any part of your product is regulated, design controls, risk files and verification evidence under IEC 62304 take months to put in place after the fact. Our IEC 62304-compliant mobile app for test interpretation is a good example of the documentation load. Teams that need help scoping that work can talk to TE’s medical device software development group early, before the clinical workflow is locked.
What It Costs to Build an ACCESS Model Platform
These are Tech Exactly’s planning ranges for US‑facing builds, based on a HIPAA‑ready cloud setup and a clinical team capable of approving workflows. They’re not quotes—HIE or HISP fees, device hardware, and FDA submission costs are extra.
| Build scope | Typical cost | Timeline | What’s included |
|---|---|---|---|
| ACCESS reporting add-on for an existing RPM or virtual care product | $40K–90K | 8–14 weeks | Eligibility and Alignment API clients, FHIR Reporting API submission, measure provenance, validity and deadline tracking, G-code claim export |
| Care-update pipeline | $15K–40K | 4–8 weeks | PCP and referrer lookup, Direct or HIE delivery, milestone templates, delivery log |
| New single-track platform (eCKM or BH) | $150K–300K | 5–8 months | Patient app, clinician dashboard, device or PROM capture, ACCESS reporting, care updates |
| Multi-track platform (CKM, BH and MSK) | $300K–600K+ | 8–12 months | Shared patient record across tracks, lab integration, multi-track discount logic, BCDA claims analytics |
With annual rates between $180 and $420 per head, automation isn’t optional—no model survives paying clinical staff to chase late telemetry. Your most cost-effective early asset is an intelligent deadline engine tracking per-patient submission windows across every measure and calculating the downstream financial hits of missed cycles.
The healthcare app development cost of the patient-facing app is usually the smaller line item. The reporting and coordination layer is where budgets overrun.
Where Do ACCESS Model Builds Lose Payment?
We expect a large share of lost ACCESS payments to trace back to operational slips the software could have caught, and patients who failed to improve will account for less of it than most teams assume.
- Late baselines. Miss the 60-day window and the patient is unaligned. Build enrollment so a patient can’t reach “active” until the baseline set is complete.
- One missing measure. A patient may have perfect blood pressure, but if the end‑of‑period LDL‑C is missing, it’s still a failure. Measure completeness by patient, not by metric.
- Missing provenance. Values without source, date and method can be rejected. Store provenance at capture, including for manually entered readings.
- Accidental FFS billing. An affiliated practice billing a 99214 for an aligned patient breaks the FFS Exclusion. Your billing export needs an ACCESS-aligned flag that every connected billing system respects.
- Updates that never arrive. A Direct message to an outdated address fails the care‑coordination rule. Record delivery confirmations and flag when a PCP isn’t reachable.
- Track overlap mistakes. A patient can’t sit in eCKM and CKM at the same time. Enforce track rules at alignment rather than cleaning up after the fact.
- Unvalidated hypertension. CMS allows eCKM alignment on a reported hypertension diagnosis but monitors for white‑coat cases. Capture confirmation readings and keep the rate of non‑qualifying alignments low.
A HIPAA-compliant app foundation (audit logs, access controls, BAAs with every vendor touching PHI) is the floor here. ACCESS adds outcome bookkeeping on top of it.
Who Should Build for the CMS ACCESS Model, and When?
The ACCESS framework rewards digital health operators ready to move past stacking monthly time-based codes for Medicare reimbursement. But if your margins depend on recurring RPM claims for these same individuals, walk away: the FFS Exclusion rule enforces a zero-sum, mutually exclusive boundary across both programs per beneficiary.
Start with Medicare enrollment, since CMS can’t approve an ACCESS application until PECOS enrollment is complete, and that can take months. Applications received after April 1 and before October 1, 2026 were considered for the January 1, 2027 cohort, and later cohorts start on a rolling basis through July 1, 2033.
CMS publishes participants’ risk-adjusted outcomes starting in winter 2028, so the first full year of data will be public and comparable. The ACCESS technical FAQ is the most current source on requirements and is worth checking before each build milestone, since CMS is still releasing guidance.
Frequently Asked Questions
This decade-long Medicare framework pays digital health providers recurring management fees across hypertension, diabetes, depression, and pain. Securing your full compensation requires a set share of enrolled patients to hit verified clinical endpoints.
For July 2026 through December 2027, the annual allowed amount per patient is $360 for eCKM, $420 for CKM, $180 for MSK, and $180 for BH in the initial 12-month period. Follow-on periods pay half, and MSK has no follow-on period.
Absolutely not. The FFS Exclusion prevents participating providers and related billing entities from submitting traditional Medicare claims for aligned members across their treatment term. All platform revenue for that patient relies strictly on ACCESS G-codes.
The Eligibility API, the Alignment API, the FHIR-based Reporting API for outcome measures, and optionally the BCDA API for claims data. Participants also need a HIPAA-compliant way to send care updates to primary care clinicians.
Functionality drives regulatory status. Archival repositories and operational back-office tools avoid device classification. However, systems steering clinical treatment decisions typically mandate 510(k) clearance unless covered by specific FDA enforcement discretion under TEMPO initiatives.
Medicare Part B-enrolled providers and suppliers other than DME and lab suppliers, with an active TIN, a physician Medical Director, and HIPAA covered-entity status. CMS accepts applications on a rolling basis through 2033.
