Playbook: Medicare Plan Finder
Welcome to DocMe360’s Provider Data Implementation Playbook, our guide to planning, building, and launching provider data solutions that work in the reWelcome to DocMe360’s Medicare Plan Finder (MPF) Playbook, your guide to helping Medicare Advantage plans prepare for and operationalize MPF requirements.
MPF is more than a compliance initiative. It sits at the intersection of provider directory APIs, provider data accuracy, and evolving CMS transparency requirements. As these initiatives increasingly depend on the same underlying provider data, health plans need sustainable operating models built on trusted data, strong governance, and repeatable processes.
This playbook outlines the strategies, controls, and operational practices needed to achieve MPF readiness while building a stronger foundation for long-term compliance and performance.
The plays
01
Position MPF as an operational capability
Treat MPF as a business-critical function, not a regulatory deadline.
Provider directory data now influences member acquisition, network visibility, compliance performance, and public trust. Plans need durable operating models that support ongoing accuracy and transparency.
How we do it:
- Establish MPF as an executive function impacting member acquisition, broker confidence, network integrity, and compliance risk
- Define ownership across business and technical teams
- Align success metrics to network accuracy and operational performance
02
Assess readiness and prioritize gaps
Understand the current state before promising the solution.
Most plans already have pieces of the required infrastructure in place, but not in a form that CMS can reliably consume. The key is identifying operational, data, and technical gaps that create the greatest readiness risk.
How we do it:
- Assess provider data architecture and workflows
- Review API and file publishing capabilities
- Evaluate governance, monitoring, and support models
- Prioritize remediation based on compliance and operational risk, such as missing provider-plan relationships, incomplete NPIs, poor data freshness, gated APIs, broken endpoints, weak reconciliation, or unclear ownership
03
Select the right publication strategy
Choose an approach the organization can sustain.
CMS allows plans to publish provider directory information through machine-readable files or publicly accessible FHIR-based APIs. The right path depends on organizational maturity, timelines, and long-term interoperability goals.
How we do it:
- Evaluate existing interoperability capabilities
- Recommend API, file-based, or hybrid approaches based on current state and organizational objectives
- Balance compliance timelines with long-term scalability
04
Build (or rebuild) a provider data foundation
Accurate provider-plan relationships depend on a governed provider data foundation.
Before organizations can publish reliable MPF data, they must understand where provider information originates, establish authoritative data sources, and define ownership across credentialing, contracting, provider directory, and interoperability platforms.
How we do it:
- Inventory provider data across credentialing, contracting, network, claims, directory, and interoperability systems.
- Identify authoritative sources for provider demographics, locations, specialties, affiliations, and participation.
- Establish governance and stewardship for provider data ownership and maintenance.
- Build a trusted provider data foundation for MPF, Provider Directory APIs, and future CMS requirements.
05
Design for desired data elemets
Compliance starts with complete and structured data.
Successful MPF execution depends on publishing a minimum set of provider directory data elements in a CMS-acceptable structure. Missing or malformed data will create validation failures, inaccurate plan representation, or both.
How we do it:
- Validate data attributes – required identifiers, demographic elements, location data, specialty, language, plan linkage, and contract year
- Standardize transformation and publication rules
- Implement upstream quality controls
Learned in practice: read our Sideline “Where plans most commonly fail validation” to learn how we build validation-ready data models.
06
Embed compliance into the delivery process
Compliance planning cannot be an afterthought.
Plans must maintain required MPF information in the Health Plan Management System (HPMS) and complete executive attestations regarding data accuracy and completeness.
How we do it:
- Identify HPMS owners and approvers
- Incorporate HPMS entry, maintenance, and attestation into the integrated project plan
- Prepare attestation documentation and evidence packages early
07
Engineer for reliability and accessibility
Publicly available data must remain available.
CMS expects consistent access to provider directory information. Reliability, performance, and accessibility are critical components of readiness.
How we do it:
- Validate public accessibility requirements
- Test uptime, performance, and conformance
- Monitor publication infrastructure continuously to maintain reliable daily CMS access
08
Operationalize data reconciliation
Trust requires ongoing verification.
Provider data must remain aligned across source systems and public directories. MPF increases the visibility of data mismatches, making routine reconciliation a requirement.
How we do it:
- Implement reconciliation processes across published content, source systems, web directory, and downstream reporting outputs
- Monitor data quality and exception trends
- Establish remediation workflows and accountability
Learned in practice: read our Sideline “Directory accuracy risks CMS consistently finds” and “How DocMe360 assesses MPF readiness” for expert tips on preparing for (and passing!) CMS audits.
09
Execute through cross-functional governance
MPF success requires coordinated ownership.
Provider data operations, credentialing, contracting, IT, interoperability, compliance, and member-facing directory teams all play a role in readiness.
How we do it:
- Create a cross-functional governance structure with business, technical, compliance, and operational owners
- Define decision-making processes to address risks and blockers quickly
- Maintain integrated project and risk management plans
10
Establish the steady-state operating model
Go-live is just the beginning.
MPF is not a launch-and-leave initiative. Plans need repeatable processes for maintaining accuracy, managing changes, responding to findings, and supporting future regulatory requirements.
How we do it:
- Define production support responsibilities
- Develop standard operating procedures (SOP) and escalation paths
- Establish ongoing governance and performance monitoring
11
Prepare for accuracy reviews and validation
Directory accuracy is now a critical compliance expectation.
CMS continues to evaluate provider directory quality through validation activities (i.e., direct calls to provider offices) and accuracy reviews. Plans should proactively identify and correct issues before they impact compliance or member experience.
How we do it:
- Conduct routine quality audits
- Perform targeted provider verification activities (i.e., secret-shopper spot checks or vendor-supported accuracy audits)
- Monitor high-risk accuracy indicators
- Drive continuous improvement through root-cause analysis
Find more in our “Sideline” and “Overtime” pages that outline MPF readiness essentials and common mishaps to avoid in real-world MPF implementations.
Final Note: MPF is transforming provider directory management from a back-office compliance function into a visible, member-facing capability. Plans that succeed will combine strong provider data operations, disciplined governance, reliable publication processes, and continuous quality improvement.
DocMe360 helps clients bridge provider data, interoperability, workflow design, compliance readiness, and operational excellence to create sustainable MPF programs that are built for the future.
Overtime
Data elements required for MPF readiness
Plans should ensure the following information is complete, current, and accurately maintained:
Provider information
- NPI
- Provider of facility name
- Provider type or facility type
- Specialty
- Languages
- Service location address
- Phone number
- Last updated date
Plan participation information
- Contract number
- Plan ID
- Segment ID
- Contract year
- Provider-plan relationship
Publication requirements
- Publicly accessible API or machine-readable file
- Appropriate FHIR resource relationships
- CMS-accessible publication endpoints
Learned in practice: In complex implementations, the first several weeks after go-live often revealed operational scenarios that were not fully exercised during testing. Dedicated stabilization support, rapid triage, and strong business participation significantly reduce disruption and improve operational confidence.
Things to avoid
Some mistakes are common, expansive, and very avoidable.
Treating MPF as only a technology project
MPF requires operational, governance, and provider data transformation, not just technical publication.
Delaying HPMS and attestation activities
Compliance milestones should be managed alongside implementation milestones
Ignoring provider-plan relationship quality
Accurate participation data is fundamental to MPF success and, ultimately, maintaining trust among beneficiaries.
Operating without monitoring
Organizations need visibility into availability, quality, and publication performance.
We’re proud of how we work, but we are always improving. This playbook is a living document, just like the products we build. Let’s keep building, learning, and delivering great things together.
Sideline
Where plans most commonly fail validation
CMS validates provider directory submissions using a three-tier framework that can impact visibility in Medicare Plan Finder.
Tier 1: Fatal Errors
Issues that prevent CMS from ingesting provider directory data and may result in suppression from MPF.
Common examples include:
- Inaccessible public URLs
- Invalid HTTPS certificates
- Invalid JSON structure
- Missing contract identifiers
- File retrieval failures
Tier 2: Record-Level Errors
Issues that cause individual providers or facilities to be excluded from MPF.
Common examples include:
- Missing or invalid NPIs
- Missing or invalid addresses
- Missing provider-plan relationships
- Invalid contract, plan, or segment identifiers
Tier 3: Informational Warnings
Issues that do not prevent publication but indicate data quality concerns.
Common examples include:
- Missing specialties
- Missing languages
- Missing accepting-new-patients status
- Missing phone numbers
- Incomplete location data
- Stale provider records
Key validation focus areas: NPI validity and completeness; provider-plan association accuracy; contract, plan, and segment ID integrity; address and geocoding accuracy; specialty completeness; accepting-new-patients status; phone number validity; data freshness; FHIR resource and reference integrity
Directory accuracy risks CMS consistently finds
CMS directory reviews and validation activities consistently focus on
provider information that directly impacts member access and network transparency.
These indicators should be monitored through routine reconciliation, provider outreach, quality scorecards, and secret-shopper-style audits.
Common Accuracy Risks
- Incorrect provider addresses
- Invalid or disconnected phone numbers
- Missing or inaccurate specialties
- Missing accepting-new-patients status
- Provider type mismatches
- NPI discrepancies
- Stale provider records
- Incorrect plan participation information
Secret Shopper Validation Focus
CMS reviewers commonly verify:
- Provider presence at listed locations
- Participation in the advertised MA plan
- Accepting-new-patients status
- Specialty accuracy
- Address accuracy
- Phone number accuracy
- Provider and practice name accuracy
How DocMe360 assesses MPF readiness
DocMe360 evaluates MPF readiness across six operational domains to identify gaps and prioritize remediation efforts.
0.1 Data & Relationship Quality
- Provider demographics and identifiers
- Provider-plan relationships
- Specialty and participation data
- Data completeness and freshness
0.2 Publishing & Technical Readiness
- API or machine-readable file capabilities
- Publication architecture and performance
- FHIR conformance and validation
- Endpoint accessibility and monitoring
0.3 Production Operations & Monitoring
- Provider demographics and identifiers
- Provider-plan relationships
- Specialty and participation data
- Data completeness and freshness
0.4 Governance & Operating Model
- Ownership and accountability
- Data stewardship processes
- Escalation and decision-making structures
- Ongoing quality management
0.5 Compliance & HPMS Readiness
- HPMS access and ownership
- URL management processes
- Attestation preparation
- Evidence and audit support
0.6 Testing & Validation
- CMS-style validation testing
- Directory parity reviews
- End-to-end crawl testing
- Defect management and remediation