As Medicaid requirements expand, provider organizations operating in a payer role are now expected to meet payer-level compliance — exposing gaps clinical systems weren't designed to handle.
Community mental health centers, county behavioral health plans, prepaid mental health plans, Local Mental Health Authorities, and LME-MCOs across the country share a common profile: they deliver direct clinical services, their primary technology is a behavioral health EHR, and they hold a Medicaid prepaid or managed care contract that may subject them to payer-level requirements under CMS-0057-F, depending on how their role is defined by the state.
CMS-0057-F applies based on how an organization functions within Medicaid — not how it identifies itself — meaning entities operating in a payer role may be subject to these requirements.
Behavioral health EHR systems are generally not designed to deliver the payer-grade FHIR APIs required by CMS-0057-F.
The gap isn't a feature request to your EHR vendor. It's a category mismatch. While some EHR vendors support FHIR capabilities, payer-specific APIs aligned to CMS-0057-F are typically outside the scope of clinical system design and roadmaps.
CMS-0057-F rolls out in two phases. Phase 1 is already in effect. Phase 2 introduces additional FHIR API requirements — each requiring distinct technical capabilities — by January 1, 2027.
⚠ If your current PA workflow is manual or EHR-only, maintaining consistent compliance becomes significantly more difficult.
⏱ These APIs require payer-side infrastructure that extends beyond traditional EHR capabilities.
Each of CMS-0057-F's FHIR APIs is a distinct technical build. Each requires payer-side infrastructure that clinical documentation systems were never designed to provide.
Members can access their own claims history, PA decisions, encounter data, and clinical information via authorized third-party apps. Required to support member access through third-party applications authorized by the patient.
In-network providers can query member attribution, prior authorization status, claims history, and encounter data. Reduces duplicative authorization requests and improves care coordination across the network.
When a member transitions to a new plan, the prior payer must make up to five years of clinical data and claims history available to the receiving payer. Ensures continuity and prevents care gaps on plan transitions.
Providers submit PA requests, check status, and receive decisions electronically via FHIR — eliminating fax and portal-based submission. Plans must accept FHIR-based PA requests and return structured decisions.
A fully integrated payer workflow in a single platform — from member enrollment through claims adjudication — with CMS-0057-F requirements embedded across authorization, reporting, and interoperability workflows.
Incedo was designed specifically for behavioral health managed care — not retrofitted from a general EHR or adapted from a medical MCO platform.
A structured implementation gets your plan to full Phase 1 compliance within 120 days. FHIR API certification follows in months 6–8 — well ahead of the January 2027 deadline.
Full CMS-0057-F compliance — FHIR APIs live — before the January 1, 2027 federal deadline. Organizations that begin now will certify on time. Organizations that wait until Q3 or Q4 2026 face a very different calculation.
Start with a conversation. Two quick steps help us understand your current setup and show you exactly how Incedo addresses the gap — then step three gets you moving.
Every day without a payer compliance layer is a day of exposure. Incedo closes the gap — without replacing your EHR, without requiring your IT team to build FHIR APIs, and on a timeline that works before January 2027.
Request a demo or needs assessment — we'll be in touch within one business day.