Type 1 NPI

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

One Type 1 NPI follows the individual

The National Plan and Provider Enumeration System assigns NPIs. Its current application help distinguishes Type 1 individuals from Type 2 organizations. The Type 1 number belongs to the individual, rather than to an employer, group, clinic, job, or payer.

The current CMS NPI application, CMS-10114, says an individual may obtain only one NPI regardless of taxonomies, professional licenses, or business locations. A behavior analyst who works for two practices does not obtain a different Type 1 NPI for each employer. Each practice still needs its own evidence that the individual is permitted and configured for its payer route.

The identifier is reusable across legitimate roles. Its presence in a directory or claim field says which individual the number identifies. It does not say that every service, location, provider type, supervision arrangement, or billing relationship is allowed.

Sole proprietor and corporation are different structures

CMS treats an individual operating as a sole proprietor as Type 1. A sole proprietor cannot obtain a Type 2 NPI for that sole proprietorship. By contrast, an incorporated individual can have a personal Type 1 NPI and a Type 2 NPI for the corporation.

Tax classification, entity law, payer enrollment, ownership restrictions, contracts, and claim routing still need separate analysis. The NPI application category does not choose a legal structure or authorize professional practice.

The number persists while its record changes

The current CMS NPI fact sheet explains that an individual receives one Type 1 NPI. The CMS NPI page says the NPI remains the same after changes such as name or address. Do not apply for a new number merely because a clinician changes employers, moves, adds a license, or practices at another site.

Current 45 CFR 162.410 requires a covered health care provider that has an NPI to report changes in required data elements to the NPI Enumerator within 30 days. Build an owner, evidence source, due date, submission record, and verification step for those changes.

An NPPES update does not automatically update Medicare or another payer. Send required changes through every applicable enrollment, credentialing, roster, directory, contract, and licensing route. Record the separate acceptance and effective date returned by each system.

The number contains no provider qualifications

Current 45 CFR 162.406 defines the NPI as a 10-position numeric identifier whose last position is a check digit and whose other positions contain no embedded intelligence. The identifier does not encode profession, specialty, state, license, employer, service site, or payer status.

Taxonomy codes in NPPES describe classifications associated with the record. They do not grant a license, expand scope, establish competence, or make a payer recognize the individual for an ABA service. Verify current taxonomy reporting against the actual role, then separately verify the authority and payer evidence that matter for the proposed work.

The CMS fact sheet also states that an NPI does not ensure licensure or credentialing, enroll a provider in a health plan, or guarantee payment. Keep those gates visible whenever staff copy an NPI from NPPES.

Map the person to each payer configuration

For every payer-product-group-location-service combination, maintain a dated relationship between the individual and the required claim roles. The record should include:

• legal name and Type 1 NPI verified against NPPES
• license, certification, scope, competence, and supervision evidence applicable to the work
• payer provider type, individual enrollment or credentialing state, and effective dates
• group affiliation, reassignment, roster, contract, and site evidence when applicable
• billing, rendering, supervising, ordering, or referring role allowed by the route
• source, owner, refresh trigger, unresolved discrepancy, and release decision

One individual may be accepted with one payer, pending with another, and ineligible for a third provider type. Use configuration-level states rather than a practice-wide “credentialed” checkbox.

Before a claim is released, match the actual service record to the correct person, role, NPI, billing provider, location, authorization, code, units, and service date. A valid Type 1 NPI cannot repair missing enrollment, an expired license, a roster gap, or a service performed by someone else.

A fictional Type 1 NPI audit

A fictional ABA practice locks 14 individual-provider configurations that reached review for one payer product. All 14 have a Type 1 NPI. Twelve match the individual's current legal name, primary taxonomy, and practice information in NPPES, so NPPES-record completeness is 12 of 14, or 85.7%.

Nine configurations also have current license or role evidence, payer acceptance, group affiliation, site, and effective dates. Configuration release readiness is 9 of 14, or 64.3%. The five holds remain visible: two NPPES discrepancies, one payer application pending, one missing group link, and one site not yet accepted.

Among the nine released configurations, eight have a first claim reach payer intake acceptance after the defined response window. Intake yield is 8 of 9, or 88.9%. That result does not establish adjudication, payment, or clinical quality.

Measure identity and relationship quality

Useful measures include NPPES-complete individual records divided by records due; payer configurations with every required relationship and effective date divided by configurations reviewed; unresolved identity discrepancies by age; first-transmission NPI or provider-role rejects divided by mature first transmissions; and repeat errors divided by claims exposed to the same configuration version.

Report pending applications, roster holds, payer rejects, adjudicated denials, and payments separately. Segment by individual, payer, product, group, site, service, and error source.