JetPatient · Trust & Methods Home · Accreditation · Verify us · What we can't do yet
The promise ledger

What we can do,
and what we can't yet.

Marketing pages describe the finished product. This one describes the real one. If a capability is listed as not built, we have removed every claim that depended on it — and the product literally refuses to render those claims until it is true.

Capabilities

Four states, and we are strict about the difference.

Credential verification against a published framework built
Every clinic is assessed per site and per specialty against 247 researched credentials across 17 markets. See it →
An append-only record of what we verified and when built
Hash-chained, publicly recomputable, with published head hashes. See it →
Correcting our own claims in public built
This is release one. The habit is the point. The public page was archived in r57; the log is kept.
Naming the clinician who performs your procedure partial
The rule is canonical (CD-003) and the application now captures a rendering-clinician roster with an attestation. The post-operative confirmation loop is not built, so we cannot yet prove concordance.
Re-verifying credentials on a published cadence not built
Renewal monitoring (T-90 / T-30 / T-0) is specified and unbuilt. We previously claimed 90-day re-verification. We removed that claim rather than keep it.
Automatic checks against public registers not built
157 of 247 credentials have a public register we could query. None is automated yet; every verification today is manual.
Publishing how many of our clinics hold each credential tier not built
Requires re-verifying every clinic already listed. Until then we publish no network-wide credential counts.
Country-level JCI counts refused
JCI's directory returned HTTP 403 to every automated request. We cannot source a number to its own register, so we publish none — and we removed the four we had.
Outcome data linked to credential tier not built
The most valuable thing we could eventually show, and the furthest away. It needs volume we do not have.

Claims the product refuses to render

These are held in fixtures/claims.json with a confidence of unverified. Our rendering layer will not display them, and our build guard fails if any surface tries. The failure mode is silence, not a confident wrong number.

accreditation.jci.counts
JetPatient does not publish country-level JCI facility counts.
JCI's own directory returned HTTP 403 to every automated request during the 14 Aug 2026 research, so no count can be sourced to its primary register. Third-party counts also mix facility types — the UAE has 200+ accredited organisations but roughly 70-90 hospitals.
clinician.concordance.rate
Clinician concordance — the share of procedures performed by the clinician named on the patient's quote.
Requires the CD-003 loop end to end: named at quote, verified as an individual, confirmed in the Passport record post-operatively. Do not publish a figure until real procedures have passed through it.
verification.cadence
Credential re-verification cadence.
Renewal monitoring (T-90 / T-30 / T-0) is specified but unbuilt. The build previously claimed 90-day re-verification. Do not restate any cadence until the job runs.
network.credential_tier_counts
Number of clinics in the JetPatient network holding each credential tier.
Requires re-verification of the existing clinic profiles against fixtures/credentials.json. This is the number that replaces country-level JCI counts.