Cut Paperwork, Not Care
Four actions to turn the January 1, 2027 federal prior-authorization deadline — and your RHTP award — into lasting relief for your state’s providers and patients.
Download the playbook (PDF, 9 pages, July 2026) →The decision on one page. Every impacted payer in your market will invest in CMS-0057 capability by January 1, 2027 — that investment is unavoidable. Your state chooses what it becomes: another set of disconnected portals, or one shared path your providers and patients can actually use. Joining takes four actions — Join · Activate the Market · Connect State-Sponsored Health Plans · Accelerate Provider Adoption (optional, RHTP-funded) — and January means a first ready production cohort, not statewide saturation. Decision requested now: name an executive sponsor and an implementation lead.
1 · The problem
American healthcare still sends nine billion faxes a year. “Dr. Jones — we’d love to approve your prior authorization request. Can you fax us the clinical notes?”
Administrative burden is crushing providers — financially, and through burnout — and it lands hardest where margins are thinnest. A large health system amortizes that paperwork across whole departments; a small or rural practice absorbs the same burden at a front desk of one, with no prior-authorization department, no IT staff, and no spare capacity. Prior authorization is the most burdensome of all: it costs too much, delays care, and leaves patients in the dark — decisions made about them, without them. Every provider in your state pays this tax; the providers least able to carry it pay the most. For rural providers, cutting paperwork is protecting access to care — and protecting the scarce resources that keep their doors open.
In a recorded Delaware prior-authorization call this spring, a physician — now the state’s Surgeon General — learned mid-appeal that the payer had never received his clinical note:
Physician: “You don’t have my note. You have no clinical information on this patient?”
Reviewer: “I have nothing attached to this patient’s claim. We didn’t have the documentation — which was what was in the denial rationale.”
Physician: “So it was denied without asking for additional information?”
The note wasn’t missing. The bridge was.
The fix is already required — and already promised. Federal law mandates it: CMS-0057 requires impacted payers to stand up standardized, FHIR-based Prior Authorization APIs by January 1, 2027. The industry has pledged it: the AHIP prior-authorization commitments, including real-time responses for most electronic approvals. And the states have been legislating the same direction for three years running, with prior-authorization laws now on the books in some forty states and more advancing every session. Federal requirements, state legislatures, and the industry all agree — every impacted payer in your market must move. The only question a state decides is how — separately, or together.
But if every payer complies separately, compliance won’t solve the problem — it will perpetuate it: more portals, more one-off integrations, more unfunded work pushed onto the practices least equipped to absorb it. Every payer in your market can comply perfectly, and your providers would still face a separate portal, credential, and integration for each of them. Fragmented APIs are just fax machines in modern clothing.
The deadline creates a one-time market-design opportunity — too good to waste. Every impacted plan will spend real money between now and January 1 — no matter what you do. The only question is whether those required capabilities remain fragmented at the provider edge — or become reachable through shared rails the whole market can use. The federal government sets payer obligations; payers build APIs; the state is the only actor positioned to point all of that mandatory motion toward a common destination. Miss the window and the money gets spent anyway — on the fragmented version, which then hardens for years and grows only more expensive to maintain.
And the same window answers a second question every state must answer: what did your RHTP award visibly do for rural providers? Aim your RHTP dollars at the infrastructure that sustains rural practices and their patients. Leverage the prior-authorization requirements every payer must meet anyway. The paperwork will kill these practices otherwise. The result is proof in production — rural practices connected at no charge, turnaround times measured, administrative hours returned to care — funded by leveraging payer compliance investment rather than asking the state to finance every underlying payer build. Delaware is running exactly this play (Axios, July 6, 2026: “Rural health funds to fix prior authorization”; Delaware DHSS announcement).
2 · The answer
Other industries use shared networks rather than requiring every participant to build directly to every other participant — card networks like Visa are the familiar example. Smart Health Network brings the same structure to providers, payers, and patients: shared rails with real accountability and measured results. From N-by-N to N-by-1 — connect once, reach every enabled, authorized counterparty on the network.
What the network is. Smart Health Network is a Public Benefit Corporation operating a payload-blind routing network: registered mail, not a warehouse. Clinical and administrative payloads remain encrypted between sender and recipient; SHN routes, tracks, and records the transaction evidence needed for delivery, status, audit, and accountability — and does not operate as a clinical data warehouse. Participants connect once to reach every authorized counterparty; that single connection upgrades over time without rebuilding separate integrations. Prior authorization is the first use case; additional transactions follow on the same connection under the same published utility terms — each new transaction type a decision, not a project.
This is not a big IT project. The network exists and is operating in synthetic-data testing. There is no new platform for your state to design, build, or operate: payers and providers connect on the technology they already run — standards-based APIs — and can begin testing today under the network’s standard testing terms, synthetic data only, no negotiated agreement required. Delaware first, not Delaware only: your state joins a network with payers already testing, published terms, and a state activation playbook running live in Delaware now. Your state doesn’t build this — it joins a network already operating in test.
The patient dividend. Every prior authorization is about a patient — and today the patient is the only party in the transaction who can’t see it: decisions made about them, without them, on a timeline they can’t watch. Because the network records standardized status for every routed transaction, patients can be given the ability to view and track the transactions about their own care — submitted, received, decided, like tracking a package — surfaced through participating tools they already use as identity and payer integrations are enabled. Patient access carries no SHN network fee under the published Open Access terms. Most interoperability projects are invisible to the public; a parent watching their child’s prior authorization move is not.
What the state gets by joining
- One common connection path for providers across participating payers, instead of a portal and integration per payer
- A coordinated production launch on a common timeline, instead of disconnected payer deadlines
- Common participation, conformance, security, and accountability rules across the market
- Measurable, production-tracked administrative-burden results — compliance is the floor; relief is the goal
- Reusable infrastructure for later transactions and state affordability priorities
- A way to enable rural providers — without building a new state-owned platform or replacing core state systems
- A health-IT result constituents can directly see: a staged path to patient-visible prior-authorization status
What SHN is not: the state’s MMIS; a clinical data warehouse; a payer’s utilization-management engine; the maker of any coverage or medical-necessity decision; a replacement for an HIE or EHR; or a state registry or source system.
Why one national network beats fifty state hubs. National and multistate payers integrate once rather than state by state; EHR vendors and onboarding partners build to one specification across markets; published national terms replace bespoke contracting; state HIEs and vendors operate certified roles on the network rather than being displaced; shared governance and permanent independence protections prevent control by any single payer, vendor, or state; and each state retains control of its funds, its programs, and its source data. A state-built hub solves one state’s fragmentation by adding one more incompatible network to the nation’s.
For a payer already building CMS-0057, participation reuses that work — it does not repeat it: connect or authorize access to the same standards-based endpoints the rule requires; complete SHN security, conformance, and participation requirements; map authorized counterparties through the network; participate in production testing; and retain full utilization-management rules and decision authority. The network is a distribution layer for the compliance investment the payer is already making.
3 · Four state actions
| Action | What it requires | Likely state lead | Illustrative budget* |
|---|---|---|---|
| 1 · Join | Nonbinding public commitment to the launch-cohort planning process — no contract, no expenditure | Governor, Secretary of Health, or designated executive sponsor | $0 |
| 2 · Activate the Market | State leadership convening + Connectathon satellite | Secretary of Health + Insurance Commissioner + Medicaid Director | No network fee; ordinary state convening costs as applicable |
| 3 · Connect State-Sponsored Health Plans | Medicaid FFS and/or MCO participation under published terms; state employee plans as applicable | Medicaid agency; state employee benefits office | $0.25 PMPM launch rate (≈$3/member/year; ~$750K/year per 250K covered lives) |
| 4 · Accelerate Provider Adoption (optional — “RHTP states”) | State Program Contract + statements of work; RHTP as the federally supported startup funding pathway | State program office or designated intermediary | State-specific program budget; Delaware reference model in Appendix 2 |
*Illustrative, based on the Delaware program for approximately 1 million residents. These are state actions, not a rigid sequence — convening in particular begins early and continues through launch.
Action 1 — Join
The state announces its intent to participate in the launch-cohort planning process and to pursue a shared statewide pathway for prior authorization. The commitment is nonbinding and requires no contract or expenditure. It gives payers, providers, HIEs, and EHR vendors the focal point they need to plan, and signals the state will quarterback provider connection so the market captures the relief together.
Action 2 — Activate the Market
The state’s most powerful contribution is its convening authority — no individual market participant has the state’s authority and neutrality to convene the full market. State leadership convenes payers, providers, and implementation partners around implementation timing, readiness expectations, and participation pathways; regular testing events (a state satellite of the national Connectathon cadence, payer-provider roundtables, monthly accountability check-ins) maintain momentum. Delaware’s July 2026 payer convening, chaired by the state, is the model. Each payer makes its own independent participation decision.
Action 3 — Connect State-Sponsored Health Plans
The state’s covered lives join under the same published participation terms as every other payer. In many states, the fastest path starts with the MCOs: they already carry CMS-0057 compliance obligations, so joining the network is a reuse of work they must do anyway, and states can use their existing contracts and oversight mechanisms to encourage or require participation, as state law permits. Medicaid FFS follows, keeping the systems it has: a network gateway sits beside the MMIS — no MMIS replacement, no core-platform redesign — and deeper vendor integration can come later, on the state’s own schedule. State employee plans (often among the largest books in the market), universities, and other state-sponsored programs can join through existing issuer and TPA relationships.
Action 4 — Accelerate Provider Adoption (optional)
Compliance is the floor; relief is the goal — and relief arrives only when providers are connected. Action 4 is how a state accelerates provider connection using RHTP as the startup funding pathway: a State Program Contract (directly or through a state-designated intermediary) governing statements of work for program management, provider enablement, market activation, and evaluation, with escrowed milestone-based payments under state-chaired governance. Providers are not charged for state-funded onboarding and connection work; Certified Onboarding Partners — organizations providers already work with — do it, and are paid only when the connection is verified complete. Rural providers get connected first — and rural results get measured. A rural practice’s authorizations travel to statewide and national payers, so delivering rural relief means connecting the market the practice actually transacts with. The program reports rural outcomes in production — activation rates, prior-authorization turnaround, administrative hours returned to care, share of transactions completed electronically. States that skip Action 4 still join the network fully; their providers connect as the market adopts the network through ordinary operating cycles rather than on a state-accelerated schedule.
4 · What launches in January
January 2027 means, at minimum: the state — or its designated participant — has executed its participation agreement; designated launch payers’ endpoints are reachable through the network; the first named provider-payer cohort can transact prior authorization in production; a defined onboarding path exists for providers not yet integrated; additional payers, providers, and transaction types join continuously after launch. Launch is a beginning, not a saturation event.
January is the first production cohort, not statewide saturation. Launch scope is defined by the participants that complete agreements, credentials, conformance, and readiness checks. Cohort scope is defined by executed participation agreements — the payers and providers signed by November 30 are what launch in January — and each participant activates as its security, legal, and production-readiness gates complete. Delaware is operating against this same launch sequence: the state announced its statewide initiative July 6, the July 13 launch and Connectathon drew more than 200 participants in person and online with the first health plan connected to the test network and testing, and the national Connectathon convenes October 14 with a Delaware satellite.
| Date | Action | What it means |
|---|---|---|
| September 1, 2026 | Join | Nonbinding public commitment to the launch-cohort planning process. |
| September 30, 2026 | State Program Contract (RHTP states only) | Framework for RHTP-funded enablement and program activities. |
| November 30, 2026 | Participation agreements complete | Executed agreements define January cohort scope. |
| January 1, 2027 | Launch | Minimum launch conditions above; continuous expansion thereafter. |
5 · State pathways and economics
Two lanes, so a state can raise its hand before it can do everything:
Public commitment; named executive sponsor and implementation lead; participation in convenings and testing; candidate payers and providers identified; diligence completed; launch pricing preserved by signing participation agreements by December 31, 2026.
All of the above, plus executed state-sponsored payer participation, RHTP-funded provider enablement, and state governance and reporting under a State Program Contract.
The economics, in three parts. Network participation (payer): a flat published utility fee — $0.25 PMPM at the launch rate, $0.50 standard — with unlimited volume across every enabled transaction type; no tiers, no negotiated deals. For a 250,000-life program, roughly $750,000 per year, weighed against the ongoing cost of fragmented portals, interfaces, status operations, and payer-by-payer provider connectivity. The savings are money the market already spends. Provider participation: connection, onboarding, and conformance testing carry no SHN fees; future provider transaction fees follow published terms on a phased schedule. Optional state activation (RHTP states): a separate, milestone-gated program budget for provider enablement and market activation — RHTP and other existing sources may support some or all of it, subject to state and federal approval.
6 · Decision and next steps
Join by September 1, 2026 — or as soon after as readiness allows — and your state has a spot in the January cohort planning process. Name an executive sponsor and implementation lead. Participation agreements by November 30 define what launches; RHTP states execute the State Program Contract by September 30. States not positioned for January may join a future cohort — and any state that signs participation agreements by December 31, 2026 locks launch pricing, even into a later cohort.
Decision requested:
- Name an executive sponsor
- Name an implementation lead
- Authorize launch-cohort diligence
- Identify candidate state-sponsored payers and the first provider-payer cohort
- Decide whether to evaluate RHTP-funded provider acceleration
The commitment package — a model public statement, the participation agreements, the fund-sizing worksheet keyed to your provider counts, and diligence materials — is available on request, and SHN will walk your team through it in an initial working session. And nothing waits on paperwork to be proven: any payer or provider in your market can start testing against the network with synthetic data today, under the network’s standard testing terms — no negotiated agreement required.
Every impacted payer in your market will spend compliance money by January 1 whether or not you act. Acting means that spend converges into rails your providers can actually use, your RHTP award produces rural relief you can measure and show, and your state creates a path for patients to gain visibility into the process that decides their care. This alignment of federal deadline, payer investment, and rural funding will not recur. Use it to cut paperwork, not care.
Appendices
Appendix 1 · Published network terms
Payer utility fee: $0.25 PMPM Launch Participant (agreements by 12/31/26; locked through 2029 with production certification by 12/31/27 per market) · $0.50 PMPM standard. Provider connection, onboarding, and conformance testing: no SHN fee on either track. Provider routed-claims utility fee: $0 through 2028 → 0.025% in 2029 → published standard 0.05% of aggregate routed paid-claim volume from January 1, 2030. Open Access track (patient access, eligibility, public-health reporting, onboarding, conformance testing): no SHN network fee under the published Open Access terms. Payer membership pricing is a flat PMPM with unlimited transaction volume across every enabled transaction type. “Free” throughout refers to SHN network fees; EHR-vendor, integrator, and internal participant costs remain the participant’s. Full pricing →
Appendix 2 · The RHTP program — governance, funding controls, and budget
Two distinct governance spheres — kept separate by design. The Program Executive Committee (PEC) — chaired by a senior state health official, with final state authority — governs the state program: scope, state funds, statements of work, subcontractor approval, milestones, reporting. Network governance — the SHN governance bodies — governs the network: rules, technical standards, certification and conformance, national participation terms. State program authority does not extend to network rules or other participants; that separation is what keeps the utility neutral for every state that joins. Funding controls: payments only upon demonstrated, verified milestones (disputes withhold only the disputed amount); quarterly reporting; audit and clawback rights; exit rights; the Delaware framework intended as a contractor relationship under 2 C.F.R. 200 (not subrecipient), subject to state and counsel review. Budget reference (Delaware model): a $200K/month program-management budget funding a defined scope — program office, market activation, onboarding management, technical coordination, governance support, reporting, evaluation coordination, and Connectathon operations — with state-specific budgets scoped via the fund-sizing worksheet.
Appendix 3 · RHTP provider enablement — reference design (Delaware-derived)
Providers receive an Enablement Voucher and select a Certified Onboarding Partner through the network registry — one funded enablement per practice location, lapse and duplicate-funding controls statewide. Reference funding schedule: $5,000 per clinician for the first 10 clinicians in an organization; $2,000 per clinician for clinicians 11–50; $500 beyond 50; $750,000 maximum per organization — states determine how, what, and whom to fund against this reference, and may weight it toward rural and rural-serving providers. Payment milestones (reference): 50% at gateway green-light and production-ready certification; 25% at verified prior-authorization production capability; 25% at a state-selected sustainment milestone. Payment only for completed work — never tied to transaction volume, claims value, or migration share. Each milestone produces a machine-verifiable connection certificate; escrow disburses directly to the partner on state approval; verification is checked against authoritative state records under the Data Sharing Agreement. SHN’s administration fee is a defined, disclosed, flat fee — never a percentage of the fund; SHN takes no share of partner delivery revenue and never holds claim proceeds.
Appendix 4 · Connecting Medicaid systems
The default is the simplest: a network gateway runs beside the MMIS/MES, communicating through the interfaces the environment already exposes — APIs, files, or queues. No MMIS replacement or core-system rebuild is required; deeper vendor integration can follow later, on the state’s schedule, without redoing the launch configuration. SHN and the MMIS/MES vendor can support APD documentation; some activities may be eligible for federal financial participation, subject to CMS review.
Appendix 5 · Required documentation summary
Join: none — public statement. Activate the Market: none to convene (RHTP states memorialize convening roles in a statement of work). Connect State-Sponsored Health Plans: Network Participation Agreements; approved MCO/TPA participation mechanisms as applicable; a State Systems Integration Workplan where MMIS/MES integration is in scope. Accelerate Provider Adoption (RHTP states): State Program Contract + statements of work; Data Sharing Agreement covering the verification feeds used for enablement-payment checks.
References to CMS, HHS, RHTP, or CMS-0057 describe federal programs and requirements. Smart Health Network is not endorsed by CMS or HHS. State participation and funding decisions remain with each state. State Playbook · July 2026 · Descriptive, not contractual.