TL;DR
In April 2026, CMS proposed a rule reshaping custom EHR architecture with mandatory FHIR Implementation Guides for prior authorization, clinical decision support, and data exchange. The comment period closed June 15, 2026. CMS hasn’t set a final-rule date — expect it in 2027, with most provisions taking effect October 1, 2027. By January 2027, EHR builders and payer integrators must support specific FHIR IGs. Custom EHR developers face three options: build in-house, purchase pre-built accelerators, or implement in phases.
I. What CMS-0062-P Requires (and Why Now)

It’s 3pm on a Wednesday. You’re a CTO at a health-tech startup building a custom EHR for rural clinics. Your compliance team lands in your Slack: “The new CMS rule on prior auth. Do we support it?” You pull up the Federal Register. 91 FR 19890. April 14, 2026. 91 pages. FHIR acronyms stacked three deep. Deadlines. The question is simple: what exactly do you need to do, and when?
Here’s the shape of it.
CMS-0062-P (published April 14, 2026) extends the 2024 interoperability rule (CMS-0057-F) to cover pharmaceutical prior authorization. It applies to Medicare Advantage, state Medicaid FFS and managed care, CHIP, and QHP issuers on federally facilitated exchanges. The mandate is clear: payers must report API endpoints for five specific services to CMS, including a new Prior Authorization API, and they must enforce specific FHIR Implementation Guides that are currently “recommended” but will become required.
That’s the shift. Right now, payers implement FHIR IGs at their own pace. Your EHR can work with or without them, and things mostly still work. Under CMS-0062-P, that optional becomes mandatory. Not optional for payers. Mandatory for anyone building software that connects to payers.
The compliance window is phased. Based on the CMS-0057-F pattern, expect January 2027 for most APIs (Patient Access, Provider Directory, Provider Access, Payer-to-Payer). Prior auth drugs likely follow in January 2028. Manufacturers must report implementation status to CMS. Miss the deadline, civil monetary penalties apply.
Here’s why this matters now. The comment period closed June 15, 2026, and that window is gone. CMS hasn’t published a final rule, and isn’t expected to until 2027, with most provisions taking effect October 1, 2027. That’s a real deadline, not an open one — the question to settle now is whether you build FHIR IG support yourself, buy a pre-built stack, or phase it in.
II. Which FHIR Implementation Guides You Actually Need

Get Your Custom EHR Ready for FHIR IG Mandates Now!
IV. Three Build-Path Decisions for Your Roadmap

You have roughly six months from now until the CMS-0062-P final rule to decide your build path. Six months to pick between three options.
PATH A: PRE-BUILT ACCELERATOR (8-12 weeks)
Use a pre-built FHIR IG stack connect health. It’s FHIR IG certified. Tested against 15+ payers in production. It handles CRD, DTR, and PAS across FHIR R4 and upcoming versions. When a new FHIR IG version ships, the vendor updates it. You don’t chase spec changes every quarter.
Timeline: 8-12 weeks (integration + testing, not building the layers from scratch)
Cost: $200K-500K (license fees + custom integration work)
Risk profile: Low — compliance risk is on the vendor
Pick this when: You need fast time-to-compliance. Your team’s strengths are clinical features, not interop plumbing.
PATH B: CUSTOM BUILD WITH EXTERNAL STACK (16-24 weeks)
Pick a FHIR middleware (Medplum, SmileCDR, Aidbox). FHIR-first platforms built to implement IG specs quickly. You build your EHR’s prior auth logic on top of their FHIR layer. You own the CRD decision engine. They own the FHIR spec compliance.
Timeline: 16-24 weeks (spec learning + design + integration + payer testing)
Cost: $500K-1.5M (middleware license $50-100K/year + custom development)
Risk profile: Medium you own the integration layer, vendor owns IG compliance
Pick this when you need workflow control. Your team has FHIR engineers. You don’t mind a vendor dependency for spec updates.
PATH C: IN-HOUSE BUILD, PHASED (24-36 weeks)
Build FHIR IG support in-house. January 2027: launch CRD only. January 2028, add PAS. It’s a phased approach because full prior auth support is complex, and you’re learning the spec as you build.
Timeline: 6 months for CRD (Jan 2027 go-live), then 6 months for full PAS suite
Cost: $1M-3M fully loaded (FHIR engineers + ongoing maintenance + spec-chasing)
Risk profile: High you own everything, including every IG version update
Pick this when: You have a deep FHIR team. Prior auth is your long-term competitive moat. You have budget runway for a multi-year program.
The decision tree is simple. Speed + budget: Path A. Control + engineering depth: Path B. Long-term platform: Path C.
Most builders I talk to underestimate Path C. In-house FHIR development sounds cheaper upfront. It’s not. By month 18, you’ve rewritten the auth decision engine twice, rebuilt security once, and you’re still not at parity with a vendor who had 30 customers before you started.
V. Common Pitfalls: What Custom EHR Builders Often Miss

I’ve sat through seven custom EHR prior auth implementations. The same stumbles come up.
PITFALL 1: API VERSIONING DRIFT
You build to da Vinci CRD v2.0. Six months later, v2.1 ships. It changes the decision tree format slightly. Not backward-compatible. Payer A updates to v2.1 on January 15, 2027. You don’t. January 16, their CRD endpoint rejects your v2.0 requests. Clinic staff get an error. You’re down until you patch.
Lesson: version your FHIR adapters. Build version-detection into your payer discovery. Test against 2+ versions in sandbox before production.
PITFALL 2: PATIENT CONSENT FLOWS AREN’T COVERED BY FHIR
The FHIR spec defines the data format. It doesn’t define the consent model. You still have to: (1) ask the patient for permission to share with the payer, (2) document that consent, (3) handle consent revocation, (4) audit it all. Most builders assume FHIR IG compliance covers it. It doesn’t.
Lesson: build a separate consent engine. You need a patient-facing form: “Is it okay if we send your clinical info to Blue Cross to check prior auth?” That’s not in the FHIR spec. You have to design it.
PITFALL 3: ERROR HANDLING AND FALLBACK WORKFLOWS
What happens when the payer’s CRD endpoint times out? What if PAS submission fails? Most builders don’t plan for this. Clinic staff hits “submit prior auth,” gets an error and is stuck. No fallback. No retry logic. No manual escalation path.
Lesson: design for failure. CRD times out? Show a manual auth entry form. PAS fails? Queue it for async retry + notify the clinic staff. Pay down? Route to a clinical escalation workflow. Build this into your MVP, not as a Phase 2.
PITFALL 4: USCDI V3 DATA COMPLETENESS
You implement CRD and PAS beautifully. But your EHR’s clinical data is incomplete on USCDI v3 fields. Maybe your problem list is sparse. Maybe medication entries lack dose/frequency. CRD decision logic depends on complete data. If the payer asks “what other therapies has the patient tried?” and your EHR has no medication history, the auth request fails.
Lesson: audit your USCDI v3 data completeness before prior auth workflows. Fix data quality first. Implement prior auth after.
PITFALL 5: ENCRYPTION AND AUDIT LOGGING UNDERESTIMATED
Most builders spend 1-2 weeks on security. It usually needs 3-4 weeks of dedicated work. If you miss this, you’re not HIPAA-compliant, and CMS will flag you.
Lesson: plan 25-30% of your FHIR build timeline for security and audit infrastructure. Build it first, not as an afterthought.
Related Read: Custom Software Development Services a Complete Guide
VI. Testing Your FHIR IG Implementation Against CMS-0062-P
Before you go live, compliance means real testing. Against real payer sandboxes.
Each major payer (UnitedHealth, Anthem, Aetna, Medicaid MCOs) runs a sandbox. You register, get test credentials, and run your CRD/DTR/PAS flows end-to-end. Expect 2-4 weeks per payer. You submit a CRD query, the payer sandbox returns a decision, and you verify your code parses it correctly. Submit a PAS request, verify the approval notification lands in your system.
After payer sandboxes: conformance testing. Da Vinci/Argonaut conformance test suites. Your implementation submits test payloads. The test suite validates that your FHIR resources are spec-compliant. They must pass before you claim CMS compliance.
Then volume and latency testing. Fire 100 CRD queries per second. Can your system handle it? CMS compliance includes SLA adherence: CRD response under 1 second, PAS decision within 7 days standard / 72 hours expedited. If you can’t hit those SLAs in testing, you won’t have in production.
Cross-payer interoperability testing is the piece most builders skip. One payer’s CRD implementation differs subtly from others. They interpret the FHIR spec slightly differently. Test against 3-5 major payers in sandbox, not just one.
Finally: audit logging and access control testing. Verify the audit log captured the prior auth exchange. Verify only authorized users can access patient data. Verify consent revocation is logged. Table stakes for HIPAA compliance.
VII. Timeline: From Now Through Compliance
Here’s what’s ahead
Comment period closed (June 15, 2026): CMS reviewed 900+ comments. No final rule yet.
Final rule (expected 2027): CMS publishes compliance dates, mandatory FHIR IGs, and enforcement mechanisms. Exact month isn’t set don’t build a launch plan around a specific week until it drops.
Most provisions effective (October 1, 2027): This is CMS’s own stated target for the bulk of the rule’s requirements. Treat earlier dates circulating as unconfirmed until the final rule names them.
Your build timeline depends on your path:
Once the final rule publishes, you’ll have a fixed runway to the compliance date (most provisions effective October 1, 2027). Three ways to use that runway: build FHIR IG support yourself, buy a pre-built accelerator, or phase it in (CRD first, PAS later). A pre-built stack compresses integration to weeks instead of months if the final rule lands with a tight runway, that gap matters
Prepare Now Before the Compliance Clock Starts
CMS-0062-P may still be in the proposal stage, but waiting for the final rule before acting could leave custom EHR teams with little room for architecture changes, payer testing, security validation, and FHIR version updates. The priority now is to assess the current interoperability stack, identify gaps across CRD, PAS, USCDI v3, consent, and audit logging, and select a realistic build path based on available time, budget, and internal FHIR expertise.
Whether the organization chooses a pre-built accelerator, an external FHIR stack, or a phased in-house build, early planning will reduce compliance risk and prevent expensive rework later. The teams that start readiness assessments now will be better positioned to adapt when CMS confirms the final Implementation Guides, versions, and enforcement dates.








BLOGS
NEWSROOM
CASE STUDIES
WEBINARS
PODCASTS
ASSET HUB
EVENT CALENDAR 



















