7.22.26 Medicare Plan Finder Information Session

  • Created  []
  • Updated  []

1. Medicare Plan Finder Phase 2 Overview

  • Final rule basis: CMS final rule 4208, released last September, requires all Medicare Advantage (MA) plans to supply provider directory data directly to CMS starting in Contract Year 2027, to populate the Medicare Plan Finder tool used by Medicare beneficiaries and caregivers.
  • How RevSpring supports it: RevSpring provides data to CMS via FHIR based JSON files. Clients make their data available to RevSpring, RevSpring generates a URL, the client populates that URL in HPMS, and CMS crawls the URL daily to validate results and update Medicare Plan Finder.
  • Division of responsibility: RevSpring owns the technical work to generate the URLs, but health plans remain responsible for the submission itself and for the annual attestation to CMS.

2. CMS Key Dates and Timeline

  • CMS testing window: Open May 2026 through the end of August 2026. Plans submit files and receive validation results, which can be routed to RevSpring for troubleshooting.
  • July 10, 2026: Milestone to populate MPF provider directory URLs in HPMS (UAT). This date has passed, and every client RevSpring is working with hit it. The underlying data and the URLs themselves can still change after this date.
  • September 1, 2026: Attestation deadline in HPMS. This is owned directly by each client's team.
  • September 18, 2026: Production URLs must be entered in HPMS. From this date, CMS loads everything submitted and attested into Medicare Plan Finder ahead of the October 1 go live.
  • October 1, 2026: Target production release date for Medicare Plan Finder, ahead of open enrollment.

3. Production Cutover Steps

  • Status: RevSpring is in active testing with all clients who have supplied crosswalks, and is working through CMS validation feedback with them. Clients should keep sending errors, feedback, or validation results they'd like help with.
  • August 15, 2026: Deadline for RevSpring to receive production level crosswalks from all clients, so production URLs can be generated in time for launch. This mirrors the earlier UAT crosswalk exercise.
    • Not a hard cutoff: CY2027 contracting is still in flux for some clients, so keep sending updated files as more information becomes available.
  • The four production cutover steps: Submit finalized production data to RevSpring, RevSpring generates the URL and returns it to you, you update that URL in HPMS, and you complete attestation, sharing any validation findings along the way.
  • Ongoing communication: Info sessions will continue for any major updates, date changes, or new CMS learnings, alongside regular communication through Customer Success partners and Data Operations leads.

4. Known Issues and Validation Updates

  • Omitted ContractID error (CMS error N30006): At least three clients on the call had received this error even though the field was populated. CMS has confirmed the fix and expects it to ship in this Friday's (7/24) release.
    • If the error persists after Friday, note any other error codes appearing alongside N30006 and send them to RevSpring so CMS can continue root causing it.
  • HPMS URL submission errors: At least one client experienced a save or validation error entering a URL into HPMS. This remains open with CMS and under investigation. Report it to RevSpring if you're experiencing this so it can be escalated.
  • URL access validation message: A validation message has appeared for some clients at submission even when the URL is valid and reachable. CMS has confirmed this does not block them from crawling the URL, and pushed a fix on July 9. If you're still seeing it, resubmitting the URL should self resolve.

5. FHIR Provider Directory API (CMS-9115-F Compliance)

  • Background: CMS-9115-F, the Interoperability and Patient Access final rule, went live in 2020 to improve how health plan data is shared, including making MA, Medicaid, and CHIP directories available to the public via APIs.
  • June 24, 2026 update: CMS released updated guidance supporting the 2020 rule, creating an immediate compliance requirement. Organizations without a compliant endpoint today can use RevSpring's FHIR Provider Directory API to get there.
  • January 1, 2027 deadline: A new rule requires the FHIR provider directory API to be upgraded to a newer standard. RevSpring is upgrading its API to meet the new Da Vinci PDex Plan Net 1.2 spec, targeting an October 2026 go live to leave room for testing.
    • Clients already on RevSpring's FHIR API don't need to do anything, it will update automatically. Interested clients should contact their Customer Success partner.
  • What the API includes: CMS conformant (HL7 FHIR R4 and Da Vinci specs), covers all CMS mandated fields plus extras like languages, credentials, and geo coordinates, requires no login or app registration, and can be built per brand for clients with multiple lines of business.
    • Built on the same provider directory data that powers member facing search, for a consistent experience, and supports capability statement conformance for third party app access.

6. Looking Ahead: MPF Phase 3 and Rule 0057

  • MPF Phase 3: Expected to leverage the same FHIR endpoints to support CMS's national provider directory. Clients already on RevSpring's FHIR Provider Directory API will likely already be positioned for this work. CMS has not yet shared timing or requirements, RevSpring will share updates as they learn more.
  • Final rule 0057: Introduces CMS "secret shopper" accuracy audits comparing FHIR API data to what's published on plan member websites, reinforcing state and federal expectations around data accuracy.
  • Q3 2026 investment: RevSpring is investing in performance upgrades to its FHIR Provider Directory API to support increased usage and these upcoming CMS mandates.

7. Immediate Action Items

  • Keep sharing CMS validation feedback: From UAT now, and from production later, send validation reports or feedback to your Customer Success partner or Data Operations lead for triage.
  • Submit production ready crosswalk data by August 15: Send this to RevSpring by email, the same way you did for UAT. Notify RevSpring in advance if you expect to miss this date, along with your expected timeline.
  • Upload your new production URL to HPMS: Once RevSpring provides it, upload it in HPMS ahead of the September 18 deadline.
  • Register for the next info session: Scheduled for Wednesday, September 9, 2026 at 3:00 PM ET. 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request