Pre-go-live pilot — no BAA is executed, no production case has been reviewed, and every case so far runs on synthetic data. What is live, in numbers →
Infrastructure for healthcare AI

Open pipes.
Signed answers.

The technology layer under every site in the network.

Every healthcare AI company needs the same plumbing and the same missing piece. The plumbing — FHIR, HIPAA tooling, identity, PROMs — is open source under Apache 2.0. The missing piece is a licensed physician who will put their name on what your model produced. That is the part that cannot be automated, and the part we are built around.

Open code
Apache 2.0
Public data API
No key, no signup
The signature
A physician signs or declines
Creating the health system that works for you — instead of you working for it.
solvinghealth.com/api/v1Calling
curl 'https://solvinghealth.com/api/v1/clearances/search?q=knee&limit=3'
Calling the live API…
  1. One real request to the keyless public data API. Nothing is stored.
Public federal data only. No patient information.Try six datasets →
Keyless developer runtime

Make a real call. No key, no signup.

Pick a public dataset. The request below runs live against the same keyless API every site in the network uses, and every answer names the exact source it came from. Public federal data only — no patient information goes in or comes out.

Available federal pipes
curl https://solvinghealth.com/api/v1/…
Ready
  1. Pick a dataset to run it.
Raw JSON
Public federal data only. No patient information goes in or comes out.Every endpoint, the SDKs and the OpenAPI spec →
How an answer gets signed

AI does the work. A named physician signs it.

  1. 01 · InConsented dataRecords, PROMs, what the person tells you. Never used for training.
  2. 02 · ModelAny modelYours, ours, or whatever your team already uses. The output is an unsigned draft.
  3. 03 · GateA draft until a physician signs itA named, specialty-matched physician signs or declines. Nothing clinically meaningful passes unsigned.
  4. 04 · OutA receipt anyone can checkNPI-bound, timestamped, hash-anchored on hashcare. An auditor checks it without trusting anyone in the chain.

Every site in the network runs on this layer. See every site →  ·  Watch one synthetic patient get attested at every step →

The signed moment

Change one character. Watch the proof fail.

A sample determination record, not a real attestation: no case, patient or physician behind it. Its fingerprint was taken when it was “signed”. Edit anything and your browser recomputes the SHA-256 on the spot.

Fingerprint at signing
computing…
Fingerprint of the record now
computing…
Matches — this record is exactly what was signed.

That fingerprint, never the record and never patient data, is what goes on the public ledger. How verification works →

The governing principle

Interpretation got cheap. Accountability did not.

When the cost of producing a clinical judgement collapses, the industry built on that cost collapses with it. What survives is a licensed human who owns the decision, and proof anyone can check. SolvingHealth keeps the cheap part open and puts a physician's name on the part that has to be owned.

Watch one synthetic patient get attested at every step →

Partnership inquiries

Talk to us.

Health systems, payers, device companies and AI developers who want physician-governed AI infrastructure they do not have to build themselves.

We respond within one business day.

Received. We reply within one business day.