Skip to content
FonteumPublic-records evidence

← All sources Care quality graph

CMS POS

CMS Provider of Services (POS) File

U.S. Centers for Medicare and Medicaid Services · Tier-1 · research-only (never on individual profiles)

Registered source

The Provider of Services (POS) file is the canonical CMS list of Medicare/Medicaid-certified providers. CCN (PRVDR_NUM) is the primary key. Fonteum uses the 'Quality Improvement and Evaluation System' (QIES) distribution as the deterministic identity backbone for cross-source joins (Care Compare star ratings, PBJ staffing, Health Deficiencies, OIG LEIE sanctions, ownership chains). The QIES 'Hospital and other' distribution covers hospitals, hospital swing beds, hospices, PRTFs, and psychiatric hospitals; SNFs / HHAs / ASCs / Dialysis are not in this distribution and are sourced from the per-cluster Care Compare snapshots that already live in the Fonteum pipeline.

What Fonteum uses it for

How this source shows up on Fonteum.

CCN identity backbone for supported joins where each participating dataset supplies a compatible CCN. Surface usage: brand-hub Care Compare modules + audit-pack export.

What this source does NOT mean

POS QIES does not contain NPIs (the modernized iQIES dataset does). The CCN-NPI crosswalk is performed by the Fonteum join engine via NPPES Type 2 fuzzy match. POS records the certification status at snapshot time; it is not real-time and does not capture intra-quarter changes.

What this dataset answers

Research and data questions this source supports.

  • Resolve a CMS Certification Number (CCN) to facility name, type, address, and participation dates — the identity backbone for any cross-source join across Care Compare, PBJ, Deficiencies, and LEIE.
  • Build a facility-level join engine that uses CCN as the primary key to link nursing-home star ratings, staffing data, health deficiencies, and ownership chains.
  • Enumerate all active Medicare-certified facilities by state and type to support a regional healthcare capacity analysis.
  • Validate that a facility's CCN is still active (termination_date is null) before joining it to real-time quality data.
  • Support M&A diligence on skilled nursing facilities with POS participation dates, certified bed counts, and chain affiliation.

Dataset size: 68,211 certified facilities (Q1 2026 snapshot)

Fields used

Per-field display contract.

Fields listed below show their configured `display_allowed` flag from the §94 provenance schema. Fields marked write-locked are captured for audit and are not rendered on profile pages.

Renders on profile

12 fields
ccnCMS Certification Number (PRVDR_NUM)
facility_nameFacility name (FAC_NAME)
street_addressStreet address (ST_ADR)
cityCity (CITY_NAME)
stateState (STATE_CD, USPS)
zip_codeZIP code (ZIP_CD, TEXT)
phone_numberPhone number (PHNE_NUM)
facility_typeFacility type (derived from PRVDR_CTGRY_CD)
provider_category_codeProvider category code (PRVDR_CTGRY_CD)
certification_dateCertification date (CRTFCTN_DT)
termination_dateTermination/expiration date (TRMNTN_EXPRTN_DT, null = active)
original_participation_dateOriginal Medicare participation date (ORGNL_PRTCPTN_DT)

Write-locked — captured to provenance, not displayed

5 fields
certified_bed_countCertified bed count (CRTFD_BED_CNT)
total_bed_countTotal bed count (BED_CNT)
fips_state_codeFIPS state code
fips_county_codeFIPS county code
cbsa_codeCBSA code
Limitations

What we can’t infer from this source.

  • QIES 'Hospital and other' distribution scope is narrower than full POS — covers hospitals (PRVDR_CTGRY_CD=01), hospital swing beds (06), hospices (12), PRTFs (19), and psychiatric hospitals (21). SNFs / HHAs / ASCs / Dialysis live in iQIES + Care Compare per-cluster snapshots.
  • NPI is absent from QIES — bridge to NPPES Type 2 happens at the join-engine layer (`src/lib/pos/ccn-resolver.ts`), not at ingest.
  • Quarterly cadence — intra-quarter certification changes are not in the snapshot until the next quarterly publish.
  • Termination dates not always backfilled for legacy closures pre-1990s; null = active at snapshot time, NOT 'currently operating today'.
  • CCN format varies by facility type; always preserve as TEXT with leading zeros.
Source metadata

Authority, license, publisher cadence.

Authority

U.S. Centers for Medicare and Medicaid Services

Tier

Tier-1 · research-only (never on individual profiles)

Publisher / configured cadence

Declared or configured cadence: Quarterly (Q1 / Q2 / Q3 / Q4). Not evidence of the latest loaded source date.

License

U.S. government public-domain works (17 U.S.C. § 105). Attribution required: 'Source: CMS Provider of Services (QIES) · {publish-date} · Snapshot {YYYY-MM-DD}'. License ↗

Attribution requirement

Source: CMS Provider of Services (QIES) · {publish-date} · Last checked {YYYY-MM-DD}

ToS & usage notes

What the source allows.

U.S. government public-domain works. CMS publishes the POS file at data.cms.gov with explicit redistribution rights. Attribution must include the dataset id (QIES `8ba0f9b4-9493-4aa0-9f82-44ea9468d1b5`) and the snapshot date.

Sample provenance

What a single field looks like in the graph.

This worked example shows the provenance shape used when a surfaced field has populated source, last-checked, display-rule, and confidence metadata. Individual fields may omit unavailable values.

Field

Hospital certification (write-locked example)

Sample value

SOUTHEAST HEALTH MEDICAL CENTER · CCN 010001 · DOTHAN AL · 420 beds

Provenance line

Source: CMS Provider of Services (QIES) · 2026-01-01 · Snapshot 2026-05-07 · Display rule: write-locked — sample only, profile rendering depends on hero / module surface

How to access

Official API, bulk download, and Fonteum endpoints.

Frequently asked

Common questions about CMS POS.

What is the CMS Provider of Services (POS) file?
The Provider of Services (POS) file is the master facility registry for all Medicare-certified providers published by CMS via the iQIES (Internet Quality Improvement and Evaluation System) portal. It assigns a CMS Certification Number (CCN) to every nursing home, hospital, home health agency, hospice, dialysis facility, and ambulatory surgical center participating in Medicare. The CCN is the primary key used to join all Care Compare datasets.
Where can I download the CMS POS file?
CMS publishes the POS file as a quarterly CSV download at data.cms.gov/provider-data under the 'Provider of Services' dataset. The full file includes all active and terminated facilities. It is U.S. government public-domain data with no redistribution restriction beyond attribution.
What is a CMS Certification Number (CCN) and how does it relate to an NPI?
A CMS Certification Number (CCN) — formerly called a Medicare Provider Number — is the facility-level identifier assigned to Medicare-certified providers by CMS. An NPI is the provider-level identifier assigned to individuals and organizations under HIPAA. A single facility typically has one CCN and may have one or more NPIs. The iQIES POS file does not include NPI; a separate join to NPPES Type 2 records is required to link CCN to NPI.
How often does the CMS POS file update?
CMS publishes the iQIES POS CSV quarterly (Q1–Q4). That publisher schedule is not proof that Fonteum loaded the newest quarter; inspect the displayed source or serving-table date before relying on freshness. Intra-quarter certification changes and closures may be absent until a later file is loaded.
What facility types are covered in the CMS POS file?
The loaded POS file represents many Medicare-certified facility categories, including skilled nursing facilities, hospitals, home health agencies, hospices, dialysis facilities, ambulatory surgical centers, rural health clinics, and federally qualified health centers. Each row's provider_type value follows the CMS POS data dictionary; inspect the loaded file before inferring complete category coverage.
See also
  • /sources → The generated source-catalog subset — documented datasets Fonteum cites.
  • /data-provenance → The provider graph — pipeline diagram, source-family clusters, field-level provenance examples, display rules.
  • /methodology → Documented sourcing, publisher cadence, observed freshness, and corrections policy.
  • /editorial-policy → Independence, sourcing, conflicts, corrections, retractions.

What’s on file, by the numbers

Platform snapshot · 2026-08-11

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
73fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

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.

Browse source records and their stated limitations →

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.

Read the full provenance and attestation methodology →

Request access