The clock on the CMS BALANCE model did not start with a fixed state-by-state schedule. It started when CMS opened the Medicaid application path and said participating state Medicaid agencies can join the model beginning in May 2026 through January 1, 2027. If you run a weight-management practice that plans to take Medicaid coverage when it opens in your state, you have weeks, not quarters, to wire up the eligibility, intake, and prior-authorization workflows that BALANCE expects. Every clinic I have spoken with this month is in some stage of "we should look at that" denial.
Two things to anchor before anything else. Medicaid GLP-1 coverage under BALANCE can begin as early as May 1, 2026 for participating states, with state agreements running through January 1, 2027. Medicare is a separate, evolving track. CMS Part D RFA materials set a conditional January 1, 2027 BALANCE date if enough Part D sponsors applied, while CMS's current Medicare GLP-1 Bridge FAQ says the separate Bridge runs from July 1, 2026 through December 31, 2027. Treating Medicaid BALANCE and Medicare Bridge/Part D planning as one rollout is the most common error I have watched clinic owners make in early-stage planning calls.
I am not going to pretend any of this is settled. The current source stack is the BALANCE Innovation Model page, the State Medicaid RFA, the Part D RFA, and the Medicare GLP-1 Bridge FAQ. What is settled is the clinical-criteria scaffolding clinics will need on day one, regardless of which state opens first. That is what this checklist is built around.
The three timelines you cannot afford to conflate
Most of the early reporting on BALANCE has muddled the dates, and the muddle has trickled into clinic planning conversations. The cleanest mental model:
- May 2026 — Medicaid BALANCE can begin in participating states. State Medicaid agencies apply and execute state agreements in a May 1, 2026 to January 1, 2027 window. Eligibility and PA workflows are state-administered with federal model alignment. This is the timeline that affects bariatric and metabolic clinics serving Medicaid populations now.
- July 1, 2026 — Medicare GLP-1 Bridge. A separate demonstration for eligible Medicare Part D beneficiaries, with a central processor for prior authorization, claims adjudication, and pharmacy payment. It runs outside the normal Part D coverage flow.
- January 1, 2027 — the conditional Part D BALANCE date in RFA materials. CMS's Part D RFA tied the Medicare BALANCE launch to a participation threshold. CMS has since framed Medicare access through the Bridge in its current FAQ, so do not assume broad Part D BALANCE coverage without checking current CMS guidance.
If your clinic mostly sees Medicaid patients, the participating-state Medicaid start window is the one that matters. If it leans Medicare, the Bridge/Part D pathway is a separate operational track. If you serve both, you are running two parallel readiness tracks. None of this is BALANCE-certification material, by the way. There is no software cert; the model is a coverage program, not a vendor stamp. Anyone promising otherwise is selling.
The 11-item readiness checklist
The spine of this article. Each item has a what, a why, and a software question.
Before your first BALANCE-eligible patient walks in:
- 1. Real-time Medicaid eligibility verification at booking. If your clinic still checks the state portal manually, this is the first workflow to harden. By go-live, you want eligibility checking to fire automatically when a patient books, with the result in the chart before the intake nurse sees the appointment. The software question: does your EHR talk to your state Medicaid eligibility API, or is someone in scrubs going to be on hold every Tuesday morning?
- 2. BMI and diagnosis criteria captured as structured data. BALANCE criteria are more specific than the old "BMI 30, or BMI 27 with a comorbidity" shorthand. The State Medicaid RFA uses age, FDA-label fit, BMI at therapy initiation, and diagnosis buckets that include type 2 diabetes, cardiovascular, kidney, sleep-apnea, liver, and prediabetes criteria. Those values cannot live in free-text SOAP prose. They have to be queryable structured fields, because monitoring and PA reviews pull discrete data, not paragraphs.
- 3. A standing prior-authorization packet template. Medicaid PAs are paper-heavy and idiosyncratic by state. Pre-build the packet: H&P, BMI and diagnosis evidence, provider attestation, FDA-label fit, safety screening, patient consent, and clinical reasoning. The bill on every clinic that does not template this in advance is paid in unbillable PA staff hours.
- 4. Structured lifestyle-modification documentation in intake. BALANCE does not create a generic "failed diet first" rule. It pairs GLP-1 access with lifestyle support and prior authorization criteria. The intake form needs structured fields for current lifestyle modification, program referral or engagement, clinical appropriateness, dates, and follow-up owner.
- 5. Contraindication and warning screening as a hard-stop, not a SOAP line. The current Zepbound label lists personal or family history of medullary thyroid carcinoma, MEN2, and serious hypersensitivity as contraindications; pancreatitis and severe gastroparesis are warning/review items, with severe gastroparesis not recommended. The intake flow should stop auto-advancement to prescribing when any safety flag is present and route the chart to clinician review. A polite nudge in the note is not a hard stop.
- 6. Titration tracker tied to dates. Coverage and refill reviews may need to see that patients followed the FDA-approved dose ladder or had a documented clinical reason for deviation. Your chart needs the prior dose, the current dose, the week on the ladder, and the reason for any adjustment, all as discrete data the audit team can extract. (See the [GLP-1 clinic stack walkthrough](/blog/glp1-clinic-ehr-workflow-2026/) for what that looks like in practice.)
- 7. Outcome reporting at defined intervals. BMI, waist circumference, HbA1c, lipid panel — captured longitudinally and visible as a trajectory rather than scattered across notes. CMS says it will monitor model impact on outcomes and may validate clinical records; state PAs may also specify cadence. The EHR should be ordering labs on schedule and surfacing the results back into the metabolic view, not waiting for a clinician to remember.
- 8. De-prescribing and non-response protocols, documented. When a patient does not respond, your clinic needs a documented clinical decision: escalate, switch agent, pause, refer for surgical evaluation, or continue with rationale. Implicit "we'll revisit at week 24" plans do not create an audit-ready record.
- 9. Lifestyle support referral and participation capture. BALANCE pairs drug access with manufacturer-provided lifestyle support. Prescribing or referring is half the work; capturing referral, attestation, engagement status, and coordinator follow-up is the half that makes the record usable for coverage and monitoring. Pick a structured field set now and use it consistently.
- 10. State-by-state rollout tracking. Because Medicaid state agreements can start anytime from May 1, 2026 through January 1, 2027, telehealth practices serving patients across state lines will have different rules per patient through 2026. The EHR should let you tag eligibility on the patient record. The team-side question: who on staff owns the running spreadsheet of which state opened on which date? Software cannot solve this one alone.
- 11. Immutable audit trail on every chart edit and AI-generated note. CMS will monitor compliance and may validate clinical records. Every edit, signature, dose change, and AI-assisted note needs an unalterable log entry — user, timestamp, version, and the unedited original alongside the clinician-reviewed final. If your AI scribe overwrites the draft when the clinician edits it, you are missing the artifact an audit reviewer may need.
That is the spine. Eleven items, none of them new clinical work. Most are things competent metabolic clinics already do informally. The shift BALANCE forces is the move from informal to documented, from prose to structured fields, from "we covered it in the visit" to "we can prove it in the audit pull."
Software versus workflow: which items live where
A common planning mistake is assuming the EHR will handle all eleven. It will not. Some items are software problems with software answers, some are practice-operations problems your team has to own, and a few are honestly both.
| Checklist item | Software (EHR) | Workflow (your team) |
|---|---|---|
| 1. Eligibility verification at booking | Real-time API integration | Front-desk training on the result codes |
| 2. BMI / diagnosis criteria as structured data | Discrete field schema | Consistent capture by intake nurses |
| 3. PA packet template | Templated bundle generator | Owner: who assembles, who submits |
| 4. Lifestyle-modification documentation | Structured intake field | Clinician phrasing during the visit |
| 5. Contraindication / warning hard-stop | Intake-flow logic | Override policy if clinician disagrees |
| 6. Titration tracker | Built-in dose ladder tied to dates | — |
| 7. Outcome reporting at intervals | Lab orders + longitudinal view | Patient outreach for missed labs |
| 8. De-prescribing protocols | Templated decision rationale | Clinical judgment, by definition |
| 9. Lifestyle support referral and participation | Structured adherence fields | Coordinator role for program follow-up |
| 10. State rollout tracking | State-tagged eligibility on chart | Someone owns the rollout calendar |
| 11. Audit trail on edits + AI notes | Immutable log on every output | Audit-readiness drills before go-live |
Of those, Oli handles items 2, 4, 5, 6, 7, and 11 natively today. Items 3 and 9 are partly templated and partly your team's adoption work. Items 1, 8, and 10 land mostly on the practice side. Eligibility integration depends on which state you are in and which clearinghouse you already use. The de-prescribing decision is yours by definition. The rollout calendar is a Tuesday-morning standing meeting nobody can outsource. (For broader context on what an AI-first practice management system covers in metabolic workflows, the bariatric EHR walkthrough is the closer read.)
What scrambling after May costs
Marisol runs a four-clinician metabolic practice in Tampa. She started her BALANCE prep in February: eligibility integration testing with the state Medicaid clearinghouse, intake-form rebuild for structured lifestyle-modification capture, and a one-page audit-readiness drill her team rehearses every other Friday. Her PA packet template was finished by mid-March. She is bored, in the best possible way, by how prepared she is.
The clinic two miles away started looking at this last week. Their owner I spoke with sounded the way owners sound when they realize the runway is shorter than they thought. Eligibility integration can take weeks once you factor in the clearinghouse vendor's queue. Intake-form rebuild usually needs clinical-team review and testing. PA templates take a slow afternoon if you have done one before, longer if you have not. None of this is hard. It is just calendar work, and the calendar is the part you cannot compress.
The clinic that has eligibility, intake, and PA wired before go-live captures coverage when it opens. The clinic that scrambles loses launch-window time to paperwork while patients sit on a waitlist or pay out of pocket. I have watched both versions of this story play out across other CMS coverage rollouts since 2018, and the gap between the two is not skill. It is preparation runway.
Tomorrow's piece walks through a single GLP-1 chart: how titration, plateau, and side-effect tracking sit in one longitudinal view. If you found this checklist useful, the chart walkthrough is the screenshot version of the same argument.
If you are a weight-management clinic preparing for BALANCE and want to see what items 2, 4, 5, 6, 7, and 11 look like inside a working chart, the Oli 30-day free trial runs on real patient data, not a demo sandbox. Take it through one week of real intake and you will know whether the structured-field capture holds up where it has to.
Quick questions
What is the CMS BALANCE model?
BALANCE is a voluntary CMS Innovation Center coverage model that expands access to anti-obesity medications, including GLP-1s, paired with lifestyle-program participation. Per CMS and the State Medicaid RFA, Medicaid GLP-1 coverage can begin for participating states as early as May 2026, with state agreement execution running through January 1, 2027. Medicare access is on a separate Bridge/Part D track.
Does Medicare cover GLP-1s in 2026?
Not under Medicaid BALANCE in 2026. CMS's Medicare GLP-1 Bridge FAQ says eligible Medicare Part D beneficiaries can access certain GLP-1s through a separate Bridge starting July 1, 2026, outside the normal Part D coverage and payment flow. Earlier BALANCE Part D materials targeted January 1, 2027 if a sponsor-participation threshold was met, so Medicare-heavy clinics should follow the current CMS Bridge and Part D guidance rather than the Medicaid rollout calendar. Existing Part D coverage for diabetes and other Part D-covered indications continues unaffected.
What clinical criteria does BALANCE require for GLP-1 coverage?
The State Medicaid RFA lists standardized access criteria and allows states to adopt less restrictive criteria within FDA-approved labeling. Be ready to document adult age, FDA-label fit, BMI at therapy initiation, diagnosis evidence, provider attestation, current lifestyle modification or support when applicable, safety screening, and outcome tracking. Final state-level criteria may vary as Medicaid programs onboard.
Is Oli Health BALANCE-certified?
No software is BALANCE-certified, because there is no software certification under BALANCE. The model is a coverage program for clinics and patients, not a vendor stamp. Any EHR claiming BALANCE certification is misrepresenting the model. What matters operationally is whether the EHR captures the structured data, audit trails, and workflows BALANCE coverage requires, which is what the checklist above covers.
