Healthcare
The healthcare endpoints cover three resolved entities — the healthcare professional (HCP), the healthcare organization (HCO), and the drug — plus a shared clinical taxonomy. Each entity has its own section below; this overview covers what they share.
| Entity | Keyed by | Guide |
|---|---|---|
| HCP | aggkHcpId | A clinician or researcher. HCP · data dictionary |
| HCO | aggkHcoId | A hospital, practice, or institution. HCO · data dictionary |
| Drug | productNdc | A drug product, keyed by its 11-digit NDC. Drugs · data dictionary |
The shape of a workflow#
Every healthcare workflow follows the same two steps: match to resolve your input to an AggKnowledge ID, then get the entity or one of its sub-resources by that ID. Each entity guide has an Identifiers page (how to reference it and which handle to store) and a Matching page (how to resolve your input to a candidate).
How HCPs and HCOs link to the rest of the graph#
Healthcare entities aren’t an island. When an HCP is also present in the person graph, aggkPersonId links the record to a full Person — so you can join clinical activity to work history and contact data. Likewise aggkCompanyId links an HCO to a Company when the organization has been resolved to the firmographic graph.
Credits & tiers#
HCP, HCO, and drug endpoints are Tier 3; browsing the taxonomy is Tier 4 (tiers are rate-limit buckets, not pricing — see Credits, Tiers & Environments). Billing has one wrinkle worth knowing:
aggkHcpId — its record, diagnoses, procedures, and prescriptions — consumes a single credit for that HCP within the period, so re-fetching a professional you’ve already pulled this period is effectively free.