1. What You're Entering, and Why

CMS requires two pieces of information to be entered in HPMS. These come from two different CMS rules and serve two different purposes — it's important not to confuse them.  To keep them separate, this document will focus on the MPF Provider Directory URL.

A. MPF Provider Directory URL

This is a URL RevSpring generates for you. It points to an index file listing the flattened, FHIR-based JSON files that make up your complete provider directory for a given CMS contract Number/Contract Year. CMS crawls this URL daily to pull data into Medicare Plan Finder.

• Governed by: CMS-4208-F2 (the MPF provider directory final rule)
• Entered in: the “Manage MPF Provider Directory URLs” page in the HPMS MPF Provider Directory module
• RevSpring Support: Part of the Provider Directory offering and requires clients to opt-in for RevSpring to manage.  
• Who provides the URL: RevSpring generates and sends it

Note: Must be completed in HPMS by July 10, 2026, per the CMS memo issued June 24, 2026 — even if the underlying JSON files behind the MPF Provider Directory URL are not yet complete. CMS has confirmed the URL itself must exist and be entered on time, but it can change at a later date; full data population can follow.

2. Step-by-Step: Entering the MPF Provider Directory URL

1.  Wait to receive your MPF Provider Direcotry URL(s) from RevSpring. RevSpring generates one URL per CMS contract number, per contract year, once your Network Crosswalk File has been processed.

2.  Log in to HPMS and navigate to the MPF Provider Directory module.

3.  Open the “Manage MPF Provider Directory URLs” page.

4.  For each contract number / contract year combination, enter the exact URL provided by RevSpring.

5.  Set the file type indicator to FHIR-based JSON files (RevSpring does not use the machine-readable JSON option).

6.  Save your entries. Confirm every individual (non employer-only) plan/segment you offer has a corresponding URL entered.

7.  Repeat step 4–6 for any additional contract numbers as new URLs are provided by RevSpring (e.g., new contracts, or the production URL refresh ahead of the September 18, 2026 target).

be able to access it without any of these barriers.

3. Responsibilities: RevSpring vs. Client

The table below outlines who owns each activity across the lifecycle of the MPF Phase II engagement.

During Onboarding & Testing

During Production Cutover

Ongoing (Post-Production)

Note: For shared items: RevSpring resolves issues stemming from file generation, formatting, or hosting; the client resolves issues stemming from the underlying source data (e.g., a missing NPI, incorrect address, or provider no longer in-network).

5. Key Reminders

• Each MPF Provider Directory URL must represent exactly one CMS contract number for one contract year — never combine multiple contract numbers or years behind a single URL.
• The URL entered in HPMS must point to the index.json file itself, not a live FHIR endpoint or API base URL.
• The index file must list only the constituent JSON files for that same contract number / contract year combination.
• Report the MPF Provider Directory URL in HPMS even if the underlying JSON files aren't fully populated yet — the URL must exist by the deadline regardless.
• Keep URLs up to date in HPMS at all times; CMS crawls daily and will flag stale or unreachable URLs.

6. Support Contacts