Healthcare talent graph
The healthcare
talent graph.
7,372,909 clinicians registered in America. 3,319,741 employer edges, 1,859,947 dated departures, and the states each one is licensed in. All of it queryable over one API. Count the market before you buy the records.
The count is not answering right now. Leave your email and we will send it for that role.
The graph
The list is the easy part.
The edges are not.
- Clinicians
- 0
- Employer groups
- 0
- Affiliations
- 0
- Departures observed
- 0
Market read by role and state
Supply, pay, demand, and how the role actually gets filled.
Click any state to view the market strategy for that role and state.
- Occupational therapists
- New YorkCaliforniaTexasPennsylvaniaIllinoisNew JerseyNorth CarolinaOhioMassachusettsWisconsinMinnesotaVirginiaWashingtonGeorgiaColoradoIndianaMissouriTennesseeArizonaOregon
- Physical therapists
- CaliforniaNew YorkTexasPennsylvaniaIllinoisNew JerseyNorth CarolinaOhioWashingtonMassachusettsVirginiaGeorgiaColoradoWisconsinMinnesotaArizonaTennesseeIndianaMissouriOregon
- Physicians
- CaliforniaNew YorkTexasPennsylvaniaIllinoisOhioMassachusettsNorth CarolinaNew JerseyGeorgiaVirginiaWashingtonMinnesotaMissouriArizonaColoradoWisconsinTennesseeIndianaOregon
- Speech-language pathologists
- New YorkTexasCaliforniaIllinoisOhioNorth CarolinaPennsylvaniaMissouriVirginiaNew JerseyGeorgiaArizonaColoradoWashingtonMassachusettsWisconsinTennesseeMinnesotaIndianaOregon
- Nurse practitioners
- TexasCaliforniaNew YorkOhioPennsylvaniaIllinoisGeorgiaTennesseeNorth CarolinaMassachusettsVirginiaNew JerseyArizonaIndianaWashingtonWisconsinColoradoOregon
- Physical therapy assistants
- TexasCaliforniaPennsylvaniaOhioIllinoisNew YorkWisconsinNorth CarolinaVirginiaIndianaTennesseeWashingtonMissouriColoradoMassachusettsGeorgiaNew JerseyArizona
- Physician assistants
- CaliforniaTexas
- Registered nurses
- CaliforniaTexas
Movement
Who left. And which practice is short because of it.
Fourteen snapshots of the employer graph since 2022. When a clinician leaves one practice and surfaces at another, we hold both dates.
A departure with no known arrival is still a vacancy.
The API
Joined, and queryable.
Eight endpoints over the graph. A search costs one credit, a collected record two, a mover three. A search that matches nothing costs nothing, so you can size a market for less than the price of one record. The same key works over REST or MCP, so your agent can query the graph directly.
How many match, and who. Filter by specialty, city, state and radius. OIG-excluded clinicians (the LEIE list) are removed before results are returned. One credit, free when it matches nothing.
POST /v1/clinicians/search
{ "specialty": "Physical Therapist",
"city": "Fresno", "state": "CA",
"radius_miles": 25 }
→ { "total_count": 812, "results": [ … ] }The full record for one NPI: identity, licence, employment, movement.
Full records for the clinicians you picked, in one call.
POST /v1/clinicians/bulk_collect
{ "npis": ["1003158056", "1013600055"],
"fields": ["identity", "license",
"employment", "signals"] }
→ 2 full recordsClinicians who changed employer, filterable by specialty, state and observation window. Each row carries both employers and both dates.
POST /v1/movements/search
{ "specialty": "Physical Therapist",
"state": "CA",
"since": "2026-01-01" }
→ movers, newest firstEveryone who left one employer group, with the window it happened in.
Employer groups ranked by departures inside one window.
Every employer we have observed for one NPI, in order.
The fourteen snapshot dates since 2022. Every move resolves to the window between two of them.
Managed sourcing
You give us the role.
We give you the meeting.
Not building on the API? We source, contact and book against the same graph. And if your recruiters want their own hands on the engine, that door is the platform.
812
Physical Therapists within 25 miles of Fresno
- Sanctioned
- Excluded before the list reaches you
- Contact
- Resolved by us per clinician, outside the graph API
Buyers
One set of data.
Three buyers.
Size a requisition before you take it. See which practices are already short.
- Count the market for a role and radius before you sign the contract.
- Departures with no known arrival, so you call the practice that just lost someone.
Local supply against your roster, by specialty and licence state.
- Every clinician within a radius of each site, by specialty.
- The states each clinician is licensed in, so you know who is in scope for each site. Current standing stays with the boards.
Every licensed clinician, with the licence states that decide who sees whom.
- Per clinician: NPI, specialty, practice address, licence states.
- OIG-excluded providers filtered out before they reach a listing.
One asset. Four doors.
Every page on this site is a different door onto the same graph. Pick the one that matches how you work.
The fourth door feeds the asset: every clinician who joins upgrades a public registry row into a consented, contactable profile. That loop is what nobody else can copy.
Questions about the data
Where does this clinician data come from?
The NPPES national provider registry, matched to employment and movement records so a search reflects where someone works today rather than a static profile. Every field traces to a source row.
Are excluded providers filtered out automatically?
Yes. OIG-excluded clinicians (the LEIE list) are removed before results are returned, on this page's search and the API alike.
Is searching free?
Search costs one credit, and it's free when a query matches nothing. Filter by specialty, city, state and radius before you spend one.
Can I see who recently changed employer?
Yes. The movements endpoints return clinicians who changed employer inside a chosen window, with both employers and both dates on each row, plus who left a given employer with no known arrival yet.
Do I need to integrate the API to use this?
No. This page runs the same search directly in the browser. The API is for teams who want the same data wired into their own tools.
Put the graph behind your product.
Create an account, take a key, and query the graph over the API or MCP. Or tell us what you are building and we run your requirement against the graph with you.
