Skip to content
FonteumPublic-records evidence
Fonteum Data GlossaryProvider

Type 2 NPI: Definition and Healthcare Context

Full name: Organizational National Provider Identifier

A Type 2 NPI is a National Provider Identifier assigned to organizations — health care entities that provide health care services or supplies and have a workforce that submits claims under the organization's name. Hospitals, group practices, clinics, laboratories, and home health agencies are examples. A single organization may have multiple Type 2 NPIs for distinct subparts that file separately with Medicare. Type 2 NPIs are managed through NPPES and included in public bulk data downloads.

Source file
Not reported
Published
Not reported
Retrieved
Not reported
Snapshot
Not retained for this reference page
Data as of
Not reported
Last updated: 2026-07-11Reviewed by: Dr. Jennifer Montecillo, MDGullas College of Medicine, 2019. Non-practicing medical reviewer.

How it’s used

  • CMS NPPES NPI Registry: Type 2 records use entity_type_code 2 and can include organization names, authorized officials, and submitted practice locations.
  • CMS Provider of Services (POS) File: facility records use CCNs as primary identifiers; an NPI join is available only where the source supplies one.
  • CMS Care Compare: most facility quality datasets are keyed by CCN, not organizational NPI; the ASC file is a documented NPI-bearing exception.

Frequently asked questions

What is a Type 2 NPI?
A Type 2 NPI is assigned to organizations — hospitals, group practices, home health agencies, and other health care entities that bill under the organization's name.
Can an organization have multiple Type 2 NPIs?
Yes. An organization may obtain separate Type 2 NPIs for subparts — such as hospital departments that file cost reports or claims independently.
Do all hospitals have an NPI?
Yes. All HIPAA-covered hospitals and other health care organizations must have a Type 2 NPI for use in electronic administrative transactions.

What’s on file, by the numbers

Platform snapshot · 2026-08-30

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
16fresh 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