Type 2 NPI

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Type 2 identifies an organization or eligible subpart

The National Plan and Provider Enumeration System assigns NPIs. Its application help places organizations in Type 2. Examples include corporations, partnerships, governmental units, and other organizational health care providers.

The current CMS NPI application, CMS-10114, also allows an organization to obtain NPIs for eligible subparts. It describes a subpart as a component of an organization that furnishes health care and may represent a different location or type of health care. A location difference alone does not automatically settle the decision.

Current 45 CFR 162.410 requires a covered organization to obtain an NPI for a subpart that would itself be a covered health care provider if it were a separate legal entity. It permits NPIs for other qualifying subparts. Entity structure, applicable law, regulatory instructions, and operations therefore inform the analysis.

Type 2 is distinct from ownership and tax identifiers

A solely owned corporation is an organization and uses Type 2 for the corporate provider identity. Its clinician-owner may also hold a personal Type 1 NPI. CMS treats a sole proprietor differently: the individual uses one Type 1 NPI, and the sole proprietorship does not receive a Type 2 NPI.

Keep these records separate:

The NPI does not replace formation documents, foreign qualification, professional or facility authority, ownership disclosures, tax setup, insurance, or payer enrollment.

Subpart decisions need a written rationale

Avoid two shortcuts: assigning one Type 2 NPI to everything without analysis, or creating an NPI for every site because a directory has a location field. Instead, inventory legal entities, components, service types, locations, tax relationships, licenses, enrollment routes, billing arrangements, records, and operational control.

For each proposed organization or subpart identity, record:

• legal entity and component name
• reason the component is or is not treated as an NPI subpart
• applicable law, regulator, CMS instruction, and payer source
• legal business name, EIN or TIN, taxonomy, address, and contact evidence
• authorized official, approval date, effective period, and reassessment trigger
• enrollment, contract, roster, directory, claim, remittance, and banking mappings

The CMS form instructs an organization that assigns separate NPIs to subparts to remove from the parent record taxonomy codes that belong only to those subparts. This helps keep the enumeration record coherent. It does not establish that every payer will enroll or contract with the same structure.

The identifier remains stable while data changes

Current 45 CFR 162.406 defines an NPI as a 10-position numeric identifier with a check digit and no embedded intelligence. The number itself does not reveal entity type, ownership, specialty, state, tax ID, site, or payer relationship.

The CMS NPI page explains that an NPI remains the same after changes such as name or address. Section 162.410 requires covered providers to report changes in required NPPES data within 30 days. CMS-10114 assigns the Type 2 certification to an authorized official for the organization.

Set a controlled update path for legal-name, address, taxonomy, contact, authorized-official, and subpart changes. NPPES acceptance is one completion event. Submit separate changes to applicable licensing bodies, Medicare, Medicaid, commercial payers, clearinghouses, directories, banks, and vendors, then retain each response and effective date.

Enumeration does not create payer approval

The current CMS NPI fact sheet states that an NPI does not ensure licensure or credentialing, enroll a provider in a health plan, or guarantee payment. A Type 2 number can exist while the organization remains unlicensed for a proposed service, unenrolled with a payer, outside a network, absent from a roster, or misconfigured for claims.

Map the organization identity separately for each payer, product, service, site, claim format, and date. Confirm the billing-provider role, tax identity, pay-to arrangement, individual rendering-provider relationships, enrollment, contract, roster, authorization, and electronic trading route.

Claim acceptance confirms only the state represented by that acknowledgment. Clean-claim status, coverage, medical necessity, adjudication, remittance, and payment remain later questions.

A fictional Type 2 NPI review

A fictional ABA organization has one corporation, three service sites, and two Type 2 NPIs based on a documented parent-and-subpart analysis. Staff lock ten payer configurations that reached review. Eight map the correct Type 2 NPI to the legal business name, tax identity, payer enrollment, contract or allowed nonparticipating route, site, roster, and claim role. Configuration readiness is 8 of 10, or 80%.

Two configurations remain held. One payer has not accepted the subpart-site relationship. Another configuration still points to the parent NPI after the payer instructed the practice to use the subpart. Both remain in the denominator.

Of the eight released first transmissions, seven reach payer intake acceptance after the route's response window. Intake yield is 7 of 8, or 87.5%. The figures do not prove coverage, payment, or that two NPIs are the right design for another organization.

Measure structure and configuration quality

Useful measures include Type 2 records with a current entity or subpart rationale divided by records due; payer configurations with complete identity and effective-date evidence divided by configurations reviewed; unresolved organization mismatches by age; first-transmission billing-provider or NPI rejects divided by mature first transmissions; and repeat errors divided by claims exposed to the same configuration version.

Report enumeration changes, payer applications, roster holds, claim rejects, adjudicated denials, and payments as separate cohorts. Segment by legal entity, subpart, NPI, payer, product, service, site, and source version.