Knowledge Base

Most clinicians keep one Type 1 for years; companies collect Type 2s as they split or merge. Spotting false “duplicates,” sole-prop wrinkles, and when to stop guessing.

Same credentialing packet, different boxes: how NPI, EIN/TIN, state license numbers, and payer-specific IDs each get used, and why pasting the wrong one breaks edits.

Running a practice under your own name can still mean both a personal Type 1 and an organization Type 2 under CMS rules: when that happens and where the official guidance lives.

Person vs legal entity in NPPES: Type 1 for the individual, Type 2 for the organization, and the usual ways both land on a single claim.

NUCC Health Care Provider Taxonomy on the NPPES row: what those codes are (and are not), primary vs secondary, claim edits, and where to verify with CMS and official files.

The ten-digit ID that shows up on claims and forms: who gets one, Type 1 vs Type 2 in one pass, and what an NPI still doesn’t prove about licenses or enrollment.

Direct and related endpoint fields on organization rows: enough context to read the screen without earning a second job as a standards attorney.

Search by ten digits or by name against public NPPES fields, then know when to repeat the same lookup on CMS so you’ve got a dated screenshot your policy accepts.

Which provider fields CMS publishes in the extract, what any mirror site can show, and the gap between “public row” and “everything in the chart.”

Legal names, married names, credentials, DBAs, and clinic brands: why what you type rarely matches the registry string character for character.

Two addresses on one NPI: where patients might walk in vs where mail lands, why both can be valid, and why neither is a GPS of “who’s on call tonight.”

We’re one of many mirrors of public NPPES columns. Here’s what that implies for freshness, proof, and the moment your compliance officer asks for cms.hhs.gov on the screen.

Zero rows? Walk format, typos, check-digit mistakes, deactivated NPIs, and “did the file refresh yet?” before you assume the number never existed.

The registry says deactivated. What now? Roles on the claim, timing, and why your payer manual still beats a blog post when edits fly back.

Deactivated isn’t always a typo: what status means in NPPES, why history still shows up in search, and how that differs from fat-fingering the number.

Pre-flight checks billers still run (NPI, taxonomy, address sanity) and where loop-specific edits live so you’re not arguing from memory in a denial thread.

NPPES for the public snapshot; boards, OIG, and payer portals for everything else. A workflow-shaped view of what to pull and what still needs primary source proof.

Insurance forms, HSA paperwork, or your own files: ways to match a doctor or clinic to a ten-digit NPI without treating the registry like Yelp.

Enumeration first, Medicare enrollment second: why owning an NPI doesn’t automatically mean you’re paid-up with every MAC, and where those threads split.

The NPI on the claim is one column in a stack that still includes supplier enrollment, taxonomy, and payer-specific hoops, especially in DME.

Incorporated groups: the Type 2 that signs contracts and the Type 1s who render care, plus the copy/paste mistake that ships every year anyway.

Agency Type 2, bedside Type 1s, and the usual mess when addresses and episode billing don’t line up with what families see on a map.

Chains, independents, and the pharmacists behind the counter: how organization Type 2 and individual Type 1 rows usually line up in NPPES.

Rotations, billing under supervision, and when a trainee really needs their own NPI. Your program’s written rule beats whatever you half-remember from orientation.

Monthly full-file semantics: when engineers nuke-and-load a warehouse, when auditors want “what CMS shipped on date X,” and why you still eyeball weird rows on the website.

Keys, rate limits, CORS, and where the parameter table lives: our JSON surface for apps that still need the government registry when compliance says so.

Terabytes of public columns still deserve access control: retention, vendor enrichments vs CMS-sourced fields, and not shipping “insights” nobody can reproduce.

Lighter than the monthly dump: weekly change feeds, deactivation lists, gap detection when someone was on PTO, and who owns the pager when a file is late.

Wrong legal name, locked NPPES login, or you need it in writing from the source: CMS channels vs anything a third-party lookup can do (spoiler: we can’t fix the row).

Moves, legal name changes, taxonomy shifts, acquisitions: log into NPPES before small drift becomes a week of denials nobody budgets for.