Dental industry data

Dental industry data, from the original sources.

Where does dental industry data come from? Nine government sources: the federal NPI registry, state dental boards, Medicaid fee schedules, the OIG exclusion list, Medicare Part B claims, the NPDB, HPSA shortage designations, Census demographics, and federal grants. ProviderSignal aggregates all nine into one provider intelligence platform. Every record traces to an authoritative origin. No data brokers. No user-submitted data. No guesswork.

The landscape

Nine sources, one platform.

Dental industry data splits into layers: who exists (the NPI registry), who can practice (state licensure), what care pays (Medicaid fee schedules and Medicare claims), who is barred from federal programs (OIG exclusions), where supply falls short (HPSA designations and Census demographics), and the malpractice climate around it all (NPDB). Each layer below links to its authoritative origin, with our extraction methodology and refresh cadence.

NPI / NPPES Registry

Centers for Medicare & Medicaid Services (CMS)·download.cms.gov/nppes/NPI_Files.html
CoverageAll 50 statesRefreshWeeklyRecords277,853 dental

The National Plan and Provider Enumeration System is the federal registry of every healthcare provider in the United States. Each provider receives a unique 10-digit NPI number that serves as the universal cross-reference key across all other data sources. ProviderSignal extracts dental-specific records using taxonomy codes (122300000X and subtypes) and loads the full provider profile: name, address, specialty, entity type, sole proprietor status, parent organization, authorized official, secondary specialties, enumeration date, and state license numbers embedded in the 50 Other Provider Identifier fields.

Methodology
Bulk CSV download (~9.3GB extracted). State license numbers are parsed from Other Provider Identifier slots into JSONB for direct matching against state board records. Weekly diffs detect deactivations, reactivations, and address changes.

State Dental Board Enrichment

42 state boards + DC·www.tsbde.texas.gov/
Coverage42 states + DCRefreshDaily to weeklyRecords147,339 enriched

State dental board data provides the enrichment layer that transforms a basic NPI directory entry into an actionable provider intelligence record. 42 states + DC are live, including all top markets (CA, TX, FL, NY, IL, OH, PA, NJ, MA, GA, NC, MI, WA). ProviderSignal matches board records to NPI entries using a six-tier strategy: exact license number match (from NPI Other Provider Identifier fields), name + ZIP fallback, fuzzy name + city with nickname expansion, relaxed multi-provider address match, name-only with confirmation signals, and a former last name retry for name-change cases.

Methodology
Key fields extracted: license number, status (active / expired / revoked / suspended), expiration date, birth year, graduation year, dental school, county, disciplinary action flag, anesthesia and sedation permits with dates, practice description, practice types, and remedial plan status. Daily or weekly diff engine compares snapshots to generate license_events and trigger_events for the alerts feed and rep trigger digest.

State Medicaid Fee Schedules

State Medicaid programs (all 50 states + DC)·www.tmhp.com/
CoverageAll 50 states + DC + GPCIRefreshQuarterlyRecords50 states + DC + 110 GPCI

State Medicaid fee schedules provide the actual reimbursement rates dental providers receive for procedures billed to Medicaid. Unlike Medicare, which pays $0 for dental (Medicare does not cover dental services), Medicaid programs set state-specific fee-for-service rates for CDT procedure codes. ProviderSignal loads Medicaid dental fee schedules for all 50 states plus DC, with adult and pediatric rate splits and multi-locality breakdowns where states publish them, plus the CMS Geographic Practice Cost Index (GPCI) data for all 110 localities nationwide.

Methodology
Rates stored with facility and non-facility distinctions. Adult and pediatric splits where applicable (FL, AR, LA, CT, NJ, KY). GPCI components (work, practice expense, malpractice) loaded for rate adjustment calculations. Quarterly diff detects rate changes above a 5% / $5 threshold and writes events to the Market Signals feed.

OIG LEIE Federal Exclusions

HHS Office of Inspector General·oig.hhs.gov/exclusions/
CoverageNationwideRefreshMonthlyRecords~180 dental exclusions

The List of Excluded Individuals and Entities names providers barred from participation in federally funded healthcare programs (Medicare and Medicaid) for program fraud, patient abuse, or license-board actions. An excluded provider cannot bill federal programs, which changes the calculus for anyone selling to, acquiring, or partnering with the practice. ProviderSignal matches the exclusion list against dental NPIs monthly and flags exclusions across search, scoring, exports, and the map.

Methodology
Monthly bulk CSV load matched on NPI. The is_federally_excluded flag gates UI surfaces, applies a scoring penalty, and annotates exports, so an excluded provider never silently surfaces in a call list or target shortlist. Roughly 180 dental providers currently carry an active federal exclusion.

CMS Medicare Part B Claims

Centers for Medicare & Medicaid Services (CMS)·data.cms.gov/
CoverageNationwideRefreshAnnualRecords51,287 / 11 yrs

Provider-level utilization and payment data from the Medicare Part B program. While most dental services are not covered by Medicare, oral surgeons and medical-benefit dental procedures (for example jaw fracture repair, tumor excision) generate Medicare claims. These records serve as a volume proxy: providers who appear in Medicare Part B data are actively treating complex cases and generating insurance-billable procedures.

Methodology
Auto-download pipeline builds URLs for 2013-2023 datasets from data.cms.gov. Records include NPI, HCPCS / CPT code, place of service, beneficiary count, service count, average submitted charge, average Medicare payment, and average allowed amount. 51,287 rows across 3,975 unique dental NPIs spanning 11 years, $366M lifetime Medicare tracked.

NPDB (National Practitioner Data Bank)

U.S. Department of Health and Human Services·www.npdb.hrsa.gov/
CoverageNationwideRefreshQuarterlyRecords~2,800 state-year aggregates

The National Practitioner Data Bank collects reports on medical malpractice payments and adverse actions taken against healthcare practitioners. The NPDB Public Use Data File is anonymized by federal law and contains no NPI numbers, names, or individually identifiable information. ProviderSignal processes the raw file into aggregate statistics: malpractice payment counts and amounts by state and year, adverse action trends, and basis-of-action breakdowns.

Methodology
Individual provider-level discipline data comes from state dental boards (disciplinary action flags), not NPDB. The aggregate NPDB data provides regional risk context. State-level trends display on provider profiles as contextual malpractice climate indicators. A 3-year rolling average detects anomalous years (>20% spike) and writes events to the Market Signals feed.

HRSA HPSA Designations

Health Resources & Services Administration·data.hrsa.gov/
CoverageNationwideRefreshQuarterlyRecords~13,000 designation records

Dental Health Professional Shortage Area (HPSA) designations identify geographic areas, populations, or facilities with a shortage of dental providers. HPSA designations carry significant implications: providers practicing in HPSAs may qualify for National Health Service Corps loan repayment, Medicare bonus payments, and J-1 visa waivers. For DSO expansion planning, HPSAs represent underserved markets with built-in federal incentives.

Methodology
Downloaded from data.hrsa.gov CSV export. Each designation includes the HPSA name, score (higher = more severe shortage), designation type (geographic, population, facility), status, and county / ZIP mapping. HPSA overlays appear on the interactive map and factor into whitespace analysis.

Census ACS Demographics

CoverageZCTA nationwideRefreshAnnualRecords~33,800 ZCTAs

The American Community Survey 5-Year Estimates provide ZIP Code Tabulation Area (ZCTA) level demographics essential for market analysis. ProviderSignal loads population counts, median household income, median age, and age distribution breakdowns nationwide. This data powers the whitespace analysis engine, demographic map overlays, and the per-capita ratios on the public data pages.

Methodology
Fetched via Census Bureau API using ACS 5-Year Detailed Tables. Population and income data combined with provider density calculations to produce provider-per-capita ratios at the ZIP level. ZIPs with high population and low provider counts surface as underserved market opportunities.

Grants.gov + SAM.gov

Federal grant and contract databases·www.grants.gov/
CoverageNationwideRefreshQuarterlyRecords~2,500 opportunities tracked

Grants.gov aggregates federal grant opportunities across all agencies. ProviderSignal searches for dental and oral health-related opportunities and surfaces active funding for community health centers, dental education programs, workforce development, and underserved population outreach. SAM.gov provides federal contract opportunities including dental service contracts for VA facilities, military bases, and federal prisons.

Methodology
Grants.gov REST API v1 (search2 endpoint) filtered for dental / oral health keywords. SAM.gov Opportunities API v2 filtered for dental NAICS codes and keywords. Both stored in the grant_opportunities table with title, agency, funding amount, application deadline, and direct link to the opportunity page.
State coverage

What's live, what's enriched, what's coming.

Every state gets the federal baseline layer (NPI, Medicare, Census, HPSA). License enrichment from state boards comes online state-by-state.

StateNPI baselineLicense enrichmentMedicaid feesRefresh
Top markets (CA, TX, FL, NY, PA, IL, NJ, NC)Full enrichment + MedicaidDaily to weekly
Mid-size markets (MI, WA, MA, WI, AZ, TN, MO, OR, IN)Full enrichmentWeekly
Newer rollouts (CO, OK, AR, LA, KY, IA, ID, ME, RI, WY, KS, CT, ND, HI, DC, DE, SD, AL, AK, NM, NV, VT, NH)Full enrichmentWeekly
Frozen snapshots (OH, MN, WV)License data frozen · portal blockedSee note
Roadmap (GA, MD, UT, MS, MT, NE, SC, VA)Medicaid only · License build queuedPending

Frozen snapshots. OH, MN, and WV license data is fully loaded but static: all three state portals moved behind aggressive bot-defense walls in mid-2026. The NPI baseline and Medicaid fee schedules for these states keep refreshing on cadence; license fields reflect the last successful sweep. They return to weekly refresh if the portals reopen or records-request exports land.

Hawaii note. HI was fully enriched 2026-04-27 (license, status, expiration, disciplinary history). The state portal moved behind a per-request paywall in May 2026, so the roster now refreshes annually via the official DCCA list-builder export. Status and license dates update each cycle; addresses stay anchored to the 2026 snapshot.

Provider data management

How nine sources become one clean record.

Raw government data does not join itself. A state board file identifies a dentist by license number and name; the NPI registry identifies the same person by a 10-digit federal ID with a differently formatted address. ProviderSignal resolves them with a six-tier matching strategy, starting from exact license-number matches embedded in the NPI record and falling back through name-plus-ZIP, fuzzy name with nickname expansion, and address-cluster confirmation before any record is joined. Everything then passes through one normalization layer: street suffixes standardized, phone formats unified, and 130+ raw state license-status strings collapsed into seven canonical buckets, so a search filter means the same thing in every state.

Freshness is guarded, not assumed. Every refresh is diffed against the prior snapshot to generate license and trigger events, a staleness monitor flags any source that misses its cadence, and weekly reconciliation audits compare derived metrics against baselines so a silent upstream change cannot quietly reshape published numbers. When a record looks wrong, it can be traced back to its raw source fields in a few clicks.

How we work

Our data principles.

01

Source of truth, not source of rumor

Every data point traces back to a named government agency, licensed commercial dataset, or internally-computed signal with documented methodology. We don't scrape review sites. We don't buy third-party 'intent data.' If we can't attribute it, we don't surface it.

02

Refresh cadence over volume

A stale record is worse than no record. License-status changes propagate within 24 hours of detection (state boards refresh weekly, Texas and Florida daily). Medicare claims annually (that's as fast as CMS releases them). Census on the ACS 5-year rolling average. Our value isn't having more data than anyone, it's having fresher data than anyone.

03

Aggregate privacy, individual accuracy

NPDB malpractice data is federally anonymized, so we surface it only at state-year aggregate level. Individual-level discipline comes exclusively from state dental boards, where records are public by law. We never combine anonymous aggregates with individual records to re-identify practitioners.

04

Open methodology

The scoring algorithms, retirement risk calculation, and DSO detection logic are fully documented in-product. Every score shows its factor breakdown on hover. Every flag shows why it fired. Analysts can audit any record back to raw source fields in three clicks.

Common questions

Where does dental industry data come from?

The authoritative dental industry data in the US is government-published. Nine sources cover the landscape: the federal NPI registry (every provider), state dental board licensure files (status, expirations, discipline), state Medicaid fee schedules (reimbursement rates), the OIG exclusion list (providers barred from federal programs), CMS Medicare Part B claims (utilization), the NPDB public use file (malpractice climate), HRSA HPSA designations (shortage areas), Census ACS demographics, and federal grant and contract databases. ProviderSignal aggregates all nine into one platform, keyed on NPI.

Is there a free database of dentists?

Yes. The federal NPPES registry is free and lists every US dentist with an NPI number, and it is the backbone of this platform. What it lacks is everything that makes a record actionable: license status and expiration dates, disciplinary history, DSO affiliation, practice grouping, and change detection. ProviderSignal also publishes free public data surfaces built from the combined sources: Medicaid rates by state, DSO affiliation by state, and dentist counts by state.

How often does dental provider data update?

Each source updates on its own cadence: the NPI registry weekly, state dental boards weekly (Texas and Florida daily), the OIG exclusion list monthly, Medicaid fee schedules quarterly, HPSA designations and federal grants quarterly, and Medicare Part B claims and Census demographics annually. ProviderSignal's pipelines run on those cadences and diff every refresh, so a license status change in a covered state surfaces as an alert within about 24 hours of the state publishing it.

What is the NPI registry?

The National Provider Identifier registry (NPPES) is the federal enumeration system run by CMS. Every US healthcare provider who bills insurance holds a unique 10-digit NPI. Because the NPI appears in every other healthcare dataset, it serves as the universal join key: state licenses, Medicare claims, and exclusion lists all connect to a provider through it.

How does ProviderSignal manage dental provider data quality?

Three layers. Matching: state board records join to NPI entries through a six-tier strategy, from exact license-number match down to fuzzy name-and-city with confirmation signals. Normalization: addresses, cities, phones, and 130+ raw license-status strings collapse to canonical forms so records compare cleanly across states. Guardrails: weekly automated audits reconcile the pipeline's output against baselines and flag drift before it reaches the product, and every record can be audited back to its raw source fields.

Can developers or AI agents access this data?

Yes. A REST API (documented at /api-docs) serves search, license events, scoring, and reimbursement endpoints. AI agents can use the MCP server at mcp.providersignal.com, discover the platform via /llms.txt, or pay per call through the x402 and card-based agent payment rails documented at /docs/agent-payments.

Every change in your territory is already in the data. See it first.

7-day free trial. Your territory triggers ranked in under 60 seconds.

Start 7-day free trial
Cancel in 2 clicksAll 50 states · 42 + DC enrichedRefreshed weekly