AI summary
A PTAN is a Provider Transaction Access Number used by a Medicare Administrative Contractor for enrollment and authentication. CMS Manual Pub. 100-09, issued 2009-03-04, documents one-to-many NPI/PTAN relationships. CMS's Medicare Fee-For-Service Public Provider Enrollment extract, released 2026-06-30, omits PTANs, so this page does not offer a PTAN lookup.
Each receipt below describes its exact retained artifact or live source. Dates and digests never cross artifact boundaries.
Evidence publisher: Centers for Medicare & Medicaid Services (CMS). Source date: 2009-03-04.
No captured bytes are represented; use the live publisher link to re-check this source.
Evidence publisher: Centers for Medicare & Medicaid Services (CMS). Source date: 2026-06-30.
No captured bytes are represented; use the live publisher link to re-check this source.
Scope and material limitation
This page defines the Medicare contractor identifier from CMS material. It does not expose private enrollment correspondence or infer a PTAN from public data.
Dated source facts
Source-snapshot manifest receipt
This receipt attests the source snapshot manifest, not any individual fact.
The answer-series chain record is unsigned. It does not authenticate a person, organization, eligibility state, or individual fact.
3ecd0bef7fe723cbe004b5bd229a8ce3fb9b460a135d72f970ed33f42fe95fdcaab83a3930620560b1b76469144808828e860474b656826bb8f9874d92a105b35ef1c6edf6c362e06d95298ced596bf149ecce9bff766f78b14a05c6e727cd010unsignedPrimary-source chain
Limitation: The manual defines PTAN use in Medicare contractor authentication and permits one-to-many NPI/PTAN relationships. No public PTAN corpus is supplied.
Limitation: The quarterly public extract is not real-time, omits PTANs and protected fields, and does not independently decide present billing eligibility or application acceptance.
Re-derive this answer from the named source and dated scope; no Fonteum account is required.
Methodology and limitations
Frequently asked questions
What’s on file, by the numbers
Platform snapshot · 2026-08-30
Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.
Source authority is record-specific
Use the issuer named on the record.
Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.
Reproducible by design
Inspect the evidence each published figure actually supplies.
Source and date
Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.
Available derivation
Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.
Daily observations
Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.
Named medical review
Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.