Primary-source verification, with the paperwork attached
Credentialing does not just need the right answer. It needs an auditable record of where that answer came from and when — one that still holds up in a survey two years later.
Start free → 100 verificationsThe evidence, not just the status
Every verification produces a tamper-evident certificate: canonical JSON with a SHA-256 hash and an HMAC signature, retained for seven years and retrievable as JSON or PDF. It records the provider details submitted, the sources consulted, the result read at that timestamp, and the signing key used. That is an audit-quality record of a federated lookup, which is what a surveyor actually asks to see.
# Every verification returns an identifier and a signed hash { "verification_id": "vrf_a1b2c3d4e5", "certificate_hash": "sha256_9f8e7d6c5b4a...", "sources_checked": ["NPPES", "OIG", "IL Division of Professional Regulation (primary source)"], "checked_at": "2026-09-07T10:30:00Z" } # Retrieve the full certificate later, as JSON or PDF GET /v1/certificates/vrf_a1b2c3d4e5
To be precise about what a certificate is: it attests what the sources said at the time we read them. It is not an independent legal attestation that a provider is properly licensed, and we would rather state that plainly than let the distinction surface during an audit.
Sources your accreditors already accept
The Illinois IDFPR lookup is recognised by the Joint Commission and NCQA as an approved primary source, and eLicense Ohio states the same for its online status. Where a state's data is a mirror of the board's own published file, the certificate records that file's as-of date, so the age of the evidence is explicit rather than assumed.
Retiring the scraper fleet
Most credentialing platforms end up maintaining per-board integrations, and they break quietly rather than loudly. A board redesigns its portal; a bulk file silently stops updating; a state exposes a status field whose meaning is not what it appears.
Two examples from states we run in production. Ohio's headline status is coarse — Active, Inactive, Closed — while the real detail sits in a sub-status such as Lapsed or Suspended, so a naive integration reports a lapsed credential as active. Pennsylvania returns every licence a person has ever held, frequently listing an expired graduate training permit ahead of the active MD, so a first-match integration reports a practising physician as expired. Those are the details that turn into a bad credentialing decision, and they are the work you stop maintaining.
Re-credentialing cycles
Re-verification is periodic by nature, and bulk verification accepts up to 100 providers per call for cycle work. Between cycles, monitoring posts a signed webhook when a status changes, so a suspension mid-cycle does not wait for the next review date. Each re-verification produces its own certificate, which is what builds the longitudinal file a surveyor expects.
Common questions
Is this accepted as primary-source verification?
The Illinois IDFPR lookup is recognised by the Joint Commission and NCQA as an approved primary source, and eLicense Ohio states the same for its online status. Data comes from the state boards themselves, and each certificate records which sources were consulted and when.
What exactly is in the certificate?
Canonical JSON with a SHA-256 hash and an HMAC signature: the provider details submitted, the sources consulted, the result read at that timestamp, and the signing key id. Retrievable as JSON or PDF, independently verifiable, retained for seven years.
Can we re-verify a whole panel at once?
Yes. Bulk verification accepts up to 100 providers per call, which suits re-credentialing cycles. Between cycles, monitoring posts a signed webhook when a provider's status changes.
How do you avoid false OIG exclusions on common names?
Around 90% of exclusion records carry no NPI, so name-only matching over-flags. A matching npi or dob confirms an exclusion and a different one rules that record out as a different person. Sending dob is the most effective way to clear a common-name collision.
Put verification evidence in your credentialing file
Start with 100 free verifications. No credit card. Read the docs or the source reference.
Create your account →