Here is a comprehensive summary of the Medicare Plan Finder Phase 2 Info Session meeting based on the video presentation:
Overview
The session, hosted by Pat Rockwell on Wednesday, June 24, 2026, outlined the program details, implementation timelines, and respective responsibilities for the Medicare Plan Finder (MPF) Phase 2 rollout. This program mandates all payers offering Medicare Advantage (MA) plans to submit provider directory data to CMS via a FHIR-based JSON API for display on the MPF tool starting Contract Year (CY) 2027.
Key Timelines & Milestones
The speaker highlighted several key dates for both CMS and RevSpring-specific deliverables:
May – August 2026: Plan testing period using machine-readable and FHIR-based JSON API files.
August 15, 2026: Deadline for clients to submit the finalized CY 2027 Network Crosswalk data to RevSpring to ensure production readiness.
August 31, 2026: Conclusion of the MPF Phase 2 testing phase.
September 1, 2026: Deadline for completing the CY 2027 attestation in HPMS.
Early September 2026: Plan preview window opens for reviewing data in the MPF system.
September 18, 2026: Target deadline to have production-ready CY 2027 data available to CMS.
October 1, 2026: Production release and live go-of the CY 2027 Medicare Plan Finder.
Roles and Responsibilities
The success of the implementation relies on specific shared actions between RevSpring and its clients:
RevSpring Responsibilities
Artifact Generation: Generating index URLs, index files, and FHIR-based JSON files per contract year and contract ID based on provided data.
Compliance & Hosting: Ensuring all index URLs are functional and publicly accessible to CMS, and that files adhere to CMS technical specifications.
Data Maintenance: Updating the FHIR-based JSON files at least every 30 days.
Communication: Distributing index URLs to client business and technical contacts and providing feedback on data issues.
Client Responsibilities
Network Crosswalk: Providing the initial network crosswalk file to RevSpring for testing and production.
NPI Inclusion: Ensuring provider directory data contains required National Provider Identifiers (NPIs).
HPMS Configuration: Entering the RevSpring-provided index URLs into the HPMS Contract Management module and explicitly setting the file type to "FHIR-based JSON files."
Validation Review: Monitoring CMS validation feedback within HPMS and sharing error reports with RevSpring for quick resolution.
CMS Testing and Validation Process
CMS uses an automated nightly crawl (typically executed during low-traffic hours) to ingest and validate the data, a process taking roughly two hours. Results are posted by mid-to-late morning in the HPMS MPF Provider Directory module.
CMS categorizes findings into three testing levels:
Level 1 – Fatal Errors: Structural issues or malformed JSON syntax. This results in the rejection of the entire dataset. RevSpring holds primary responsibility for correcting these issues.
Level 2 – Record-Level Errors: Specific invalid or incomplete record fields. The rest of the dataset is processed, but the flagged record is withheld from MPF. Clients must share these details with RevSpring to coordinate a fix.
Level 3 – Informational Warnings: Potential issues that do not stop record processing but should be reviewed and updated quickly.
Q&A Highlights
Test Version Visibility: A participant asked if there would be a preview version of the MPF to see how data populates. The speaker confirmed that CMS—not RevSpring—controls this, and it is scheduled to be available during the plan preview window from September 1 through September 17.
Error Report Sharing: The speaker clarified that the best way to share CMS error reports with RevSpring is via email directly to the client's designated Customer Success Partner and Data Operations Lead.
Future Contract Years (CY 2028): In response to a query about future contract year switchovers, the speaker noted that CMS has not yet finalized this cadence and guidance is not expected until early 2027.
Immediate Action Items
Now: Clients need to input their current RevSpring-provided index URLs into HPMS and pass any validation feedback from early testing along to RevSpring.
Now: Clients who haven't yet done so must submit their testing network crosswalks.
Upcoming (August 15): Submit final finalized CY 2027 production network crosswalks. If negotiations with CMS will push past this deadline, clients must notify their RevSpring Customer Success Partner immediately to adjust planning.