Official-source guide · checked July 16, 2026

Find the pending Medicare provider enrollment list—and read it correctly.

CMS publishes two public pending-initial enrollment datasets. Here is the shortest reliable path to the current files, the safe way to compare editions, and the limitation that matters most: pending is not approved.

The short answer

Open both CMS datasets, not the quarterly approved-provider file.

If a bookmarked dataset page moves, use the CMS Medicare Provider-Supplier Enrollment catalog or search the machine-readable CMS data.json catalog for the two exact titles.

Current source receipt

What the live CMS catalog reported when this guide was checked.

Catalog modifiedJuly 14, 2026
Current file dateJuly 13, 2026
Physician rows8,173
Non-physician rows6,393

Those dated links are evidence for this check, not permanent “latest” URLs. Resolve the current distribution from CMS before each run.

Reproducible workflow

Four steps turn the public files into a defensible change signal.

  1. 01
    Resolve both dataset families

    Read the live CMS catalog and select distributions for the exact physician and non-physician titles. Do not scrape a search-result page or hard-code one dated UUID forever.

  2. 02
    Keep the newest two versions

    For each family, order the CSV distributions by their publication or file date. Preserve URL, date, row count, and a file hash in the run receipt.

  3. 03
    Diff the normalized NPI sets

    Trim whitespace, validate 10-digit NPIs, deduplicate, then keep current NPIs that were absent from the immediately prior physician and non-physician files.

  4. 04
    Enrich from NPPES and verify

    The CMS CSVs currently expose only NPI, last name, and first name. Use a current NPPES record for taxonomy and public practice details, and treat every field as a research lead that still needs verification.

What a row means

The useful event is appearance in a pending file—not approval.

You can say

This NPI appeared in a CMS initial-enrollment application file that was pending contractor processing on the dated snapshot.

You cannot say

This provider is approved, enrolled, credentialed, licensed, accepting patients, operating at the NPPES address, or interested in a vendor.

CMS explains the application workflow in its Medicare Provider Enrollment guidance. The older but still linked pending-file methodology and data dictionary define the file scope and fields.

Inspect a worked result

A free sample shows the enrichment and receipt before any purchase.

The July 13 validation compared the July 13 and July 9 physician and non-physician files. It found 1,763 newly present NPIs, completed 1,763 of 1,763 NPPES lookups, and retained 211 records matching the disclosed behavioral-health taxonomy set across 42 jurisdictions.

The sample demonstrates one narrow behavioral-health use case. It is not a complete list of every pending Medicare application and does not change the status limitations above.

Primary sources

Use the official surface as the authority.

ActableSite is not CMS and does not determine enrollment status. Source links and dated counts were checked July 16, 2026; CMS can replace files and revise its catalog.

Pending Medicare enrollment list questions

Is the pending Medicare provider enrollment list an approval list?

No. CMS describes these as initial applications pending contractor processing. A listed NPI is not proof of Medicare approval, billing privileges, licensure, credentialing, availability, or buying intent.

Why are there two CMS files?

CMS publishes separate Pending Initial Logging and Tracking datasets for physicians and non-physicians. A complete national comparison needs both.

Does the CMS file include a practice address or specialty?

The current CSVs contain NPI, last name, and first name. Address, taxonomy, credential, and status context require a separate current NPPES lookup and still need verification.

How do I identify newly pending applications?

Resolve the two newest versions of both CMS datasets, normalize the NPI field, and keep NPIs in the current files that were absent from the immediately prior files.