SurgeonValue
CMS-0057-F: Every Medicare Advantage payer must now publish your directory data as a public, unauthenticated API — updated within 30 days of any change.
CMS-0057-F · Plan-Net 1.2.0 · Effective 2026

Your payer directory entry is now public data

CMS now requires every Medicare Advantage payer to publish a complete, machine-readable provider directory — no login, no API key. Updated within 30 days of any change. What's in that directory affects your ASM performance scoring, patient routing, and prior auth outcomes.

Run the 5-point auditRegister interest in monitoring
No authentication required by any MA payerUpdated within 30 days of any changeBulk export via FHIR $export endpoint
What the rule mandates
CMS-0057-F Provider Directory requirements
Plan-Net 1.2.0 conformance
Updated NUCC taxonomy + bulk export support
30-day update window
Additions, terminations, and attribute changes
Zero authentication
No OAuth, no API key, no app registration
FHIR bulk export
$export endpoint, NDJSON, _since parameter
Per-location network flags
New patient acceptance by location + plan
Why It Matters Now

Three ways your directory entry affects your income

The directory isn't just about patients finding you. With ASM launching January 2027, the data in that file is directly connected to how CMS benchmarks your episode costs.

01
ASM specialty code mismatch
Plan-Net 1.2.0 updated the NUCC taxonomy value sets. If your specialty code in the payer directory doesn't match what CMS uses for ASM peer grouping, your episode costs get benchmarked against the wrong surgeons. You can't appeal a score that was calculated on bad data.
ASM risk
02
Patient routing and referral leakage
Health systems, insurance portals, and referral networks consume these directories programmatically. If your "accepting new patients" flag is wrong at any location, automated routing sends cases elsewhere — silently, at scale, every day.
Revenue leak
03
Termination lag creates billing exposure
Payers have a 30-day window to update terminations. If you leave a network and patients continue to book in-network expecting coverage, you're exposed to surprise balance billing complaints — even if the payer was late on the update.
Compliance risk
The Intelligence Angle

The same mandate that creates risk also creates intelligence

The $export endpoint CMS mandated includes a _since parameter — a timestamp-based delta query that shows every provider record changed since a given date. Polling those endpoints is the planned design; it is not running today.

Monitoring for these changes is a design, not a running service. Today you can audit your own entry against the five checks below.

Tell us you want this →
↻
Daily delta scans (design)
Planned: poll payers' _since endpoints. Not running today.
◎
Specialty code verification
Confirm your NUCC taxonomy code matches your ASM enrollment record
◇
Network status alerts (design)
Planned. No alerts are sent today.
◈
Location accuracy check
Verify active practice locations match your Medicare enrollment
≡
ASM peer group alignment
Confirm your directory entry puts you in the right benchmarking cohort
Self-Audit

The 5-point directory audit

These are the five most common directory errors that affect surgeon income. Answer honestly — most surgeons can't say yes to all five.

Have you verified your NUCC taxonomy code in every MA payer directory in the last 6 months?
ASM scoring error
Is your "accepting new patients" status accurate at each of your practice locations?
Revenue miss
Are all active practice locations listed, and do the addresses match your billing address on file with CMS?
Prior auth friction
Have you confirmed you haven't been silently terminated from any MA network in the past 90 days?
Surprise balance billing exposure
Does your organization affiliation in the directory match your current employment arrangement?
Credentialing mismatch
Plan-Net 1.2.0

The specific changes that affect surgeon data

The migration from Plan-Net 1.1.0 to 1.2.0 was due January 1, 2026. These are the changes with direct downstream effects on provider data accuracy.

New patient acceptance — per location, per network
Previously a single flag per provider. Now each PractitionerRole can carry multiple new patient indicators — one per location, one per plan. Payers that haven't migrated may be showing an aggregate that doesn't reflect your actual availability.
Routing errors
NUCC taxonomy value set updates
Multiple specialty value sets were updated to reflect changes in the NUCC taxonomy. Specialty codes valid under 1.1.0 may fail conformance validation now. If your specialty code is stale, your peer group in ASM benchmarking is wrong.
ASM scoring error
Bulk export ($export) formally added
Plan-Net 1.2.0 explicitly defines how to retrieve inactive and terminated provider records in bulk, including querying for records changed within a specific time window using _since. This is how monitoring is planned to work; it is not running today.
Intelligence opportunity
'OTHER' category removed from HealthcareService
Services mapped to OTHER in payer source systems now produce invalid FHIR resources unless payers updated their transformation logic. If your service type is misclassified, your practice may not appear in the right category searches.
Discoverability
Register interest

Want directory monitoring? Tell us.

Tell us you want this; it is planned, not running. Nothing is scanned and no alerts are sent today. Leave your email and we will write if it ships.

See ASM exposure instead →