Thank you for joining our recent office hours session covering Phase 2 of the Medicare Plan Finder initiative. We appreciate the thoughtful engagement and wanted to provide a summary of the key questions discussed to help your team prepare for upcoming milestones.

As a reminder, Phase 2 moves toward a dual-option solution for Contract Year 2027, requiring health plans to supply provider directory data via machine-readable JSON or FHIR-based JSON files. RevSpring is committed to supporting our clients through this transition by providing the necessary URLs and generating compliant files to be hosted within your HPMS system.

Below is a recap of the frequently asked questions from the session:

Testing and Validation

Q: Will RevSpring assist with the plan testing period? A: Yes. RevSpring will assist in generating FHIR-based JSON files and providing the necessary URLs for your HPMS. We will work with you to ensure the data supplied is accurate and compliant with CMS requirements. Testing is expected to begin in May 2026.

Q: Who will validate the data prior to sending it to CMS? A: RevSpring will validate that the data being transferred meets CMS technical requirements. However, plans remain responsible for ensuring the accuracy of the underlying provider data provided to RevSpring.

Q: What exactly is being validated? A: CMS has not yet fully defined the validation criteria. They are expected to publish a validation inventory prior to the test period (likely this month). We will update you as soon as more details are available.

Technical Implementation

Q: Will RevSpring be creating index files or a live FHIR API? A: For Phase 2, we are explicitly generating FHIR-based JSON files (flattened bundles conforming to the PlanNet 1.2 standard). We are providing URLs that link to these pre-processed files rather than exposing a live API endpoint.

Q: Do we need to map Contract IDs to the Product Code or the Provider Network Code? A: You should map Contract IDs to the Provider Network Code that you are sending in your provider files, rather than the product code.

Q: What additional data do we need to send to RevSpring? A: If you are already working with us for provider directory services, we likely have much of what is needed. However, we require a supplemental "Network Crosswalk" file that links your network information to specific CMS Plan Identifiers.

Attestation and Timeline

Q: Who oversees the attestation process? A: A designated signatory at your organization (typically a CEO, CFO, or COO) must complete the annual attestation in HPMS by September 1, 2026.

Q: What are the key dates we should keep in mind?

• May – August 2026: Plan testing period.

• September 1, 2026: Deadline for CY 2027 attestation.

• September 18, 2026: Target deadline for production-ready data.

• October 1, 2026: Production release of the CY 2027 Medicare Plan Finder.

Next Steps

If you are interested in RevSpring supporting your Phase 2 compliance at no additional charge (available to current Provider Directory subscribers), please reach out to your Customer Success Partner. They will coordinate with our data operations team to get your files set up.