Public proof-of-existence registry
Did this record change after it was signed?
A record is fingerprinted on your device: a 64-character SHA-256 hash that breaks if a single character changes. Only the fingerprint joins a public registry, with a timestamp. The document never leaves your device.
When an AI model makes a clinical recommendation, who is accountable? HashCare answers with evidence instead of assurance: the review standard, the ledger, the errata.
Sealed fingerprint…
01 · In 15 seconds
HashCare in 15 seconds
- Did the note change after signing? Signed, then disputed by a family or a payer. Who can prove it?
- Change one character. It breaks. A 64-character SHA-256 fingerprint, made in your browser.
- Stamped into Bitcoin, daily. Anyone can recompute the root. No account, no permission.
- Anchor a document. Keep the file. Hashed on your device. Only the fingerprint joins the registry.
- HashCare. Evidence instead of assurance. hashcare.com
02 · Two records, one question
Edit either record. Watch the fingerprint break.
Edit either record below. Watch the fingerprint break in real time. This is exactly how a family, a payer, or an OIG auditor would verify a disputed care note. Everything runs in your browser; nothing is uploaded.
In production, the signed hash is anchored in the public HashCare registry and countersigned into Bitcoin daily via OpenTimestamps. Any party — family, MCO, OIG — can run this comparison against the anchored fingerprint without asking anyone for permission.
03 · The accountability chain
AI drafts it. A physician signs it. The fingerprint is public.
AI generates
LMN, prior auth, clinical note, care plan
Physician reviews
A named, specialty-matched physician signs — or declines
Hash created
SHA-256, timestamp-anchored, tamper-evident
Anchored & countersigned
Public registry; root countersigned into Bitcoin daily
Anyone verifies
Family, payer, or OIG — paste the hash, see who signed
Today’s actual registry root
reading /roots/latest.json…
Not an illustration. This is the live root of the public registry, read from /roots/latest.json as this page loaded — the SHA-256 of every fingerprint anchored to date, sorted and joined. Recompute it yourself →
04 · How it works
Four steps. Not one of them asks you to trust us.
This is the whole mechanism. It is deliberately small, because a proof you cannot check yourself is just a claim with extra steps.
Fingerprint it locally
Any file or text is SHA-256 hashed in your own browser using the Web Crypto API. The content is never uploaded and never reaches us — only the 64-character fingerprint does. Nothing can be reconstructed from it.
Anchor the fingerprint
The hash and a timestamp go into a public registry. No account, no key. An optional public label is reviewed before it appears; leave it blank and the anchor stays private while remaining verifiable by anyone holding the original.
Countersign the day
Daily, the registry publishes a root — the SHA-256 over every anchored fingerprint, sorted and newline-joined — and stamps it into the Bitcoin blockchain via the open OpenTimestamps standard. The proof outlives the operator.
Anyone re-derives it
Four commands, published in full. Download the fingerprint list, recompute the root, and check the timestamp against a specific Bitcoin block. You do not need an account, a node, or our cooperation — and if we ever rewrote history, this is the step that would catch us.
05 · What gets anchored
What is running, and what is only designed.
A site about provenance does not get to be vague about its own. Below, every capability is labelled by whether it is actually anchoring records today. The counter is read live from the registry — it says what it says.
This is a small number, and we publish it rather than imply a larger one. The registry opened in July 2026 and everything in it is still ours. What changed on 2026-09-04 is that it stopped being a static list: the physician review loop now writes a receipt for every determination it issues, and those receipts land here automatically. They are synthetic pilot cases — no BAA is executed anywhere in this estate, so no real patient record has been near it — but the path from a signed determination to a publicly checkable fingerprint now runs end to end without anyone deciding to publish it. Verify the count against the raw list → · Read the errata →
Running today Live
Proof of Existence, No Account Live today
Anyone can anchor any document right now — a manuscript, a dataset, a signed agreement, a photograph, a contract you do not want to show anyone. It is hashed in your browser, so we never see the content. No account and no permission. This is the part of HashCare that works today for a stranger who does not trust us at all.
Anchor a document →The Review Standard Live today
The Five Tests of a Real Review — licensed and matched, independent, engaged and measured, receipted, durable — published openly for anyone to use or fork. The canonical text is itself anchored in this registry, so the standard cannot be quietly edited after the fact. Version 1.0, integrity-protected by its own content hash.
Read the standard →Daily Bitcoin Countersign Live today
Daily, a scheduled job stamps the registry root into Bitcoin via OpenTimestamps and commits the proof publicly. It runs on one machine, so a day it is off or offline gets no root (six days since it began on 2026-07-14, the latest 2026-10-08); every date it ran is listed, and an anchor from a missed day is in the next published root. Nothing here depends on this company continuing to exist: if HashCare disappears tomorrow, every proof issued before then remains checkable by anyone, forever, using open tools we do not control.
See the recipe →Physician Attestations Live — synthetic pilot
Every determination the ClinicalSwipe review loop issues is anchored here, labelled by verdict. A signature commits to the signed letter and the documents the reviewer relied on; a revision or a decline commits to the verdict and the written rationale, under the reviewer’s NPI. A signature proves who signed; the revisions and honest declines prove someone actually looked — and since 2026-09-05 both answers are on the public record. No BAA is in place, so every one of these is a synthetic case; no real patient has been near it. The rules those cases are decided under are anchored too: the fingerprint of ClinicalSwipe’s determination protocol, version 2026-09-11.1, as published at clinicalswipe.com/protocol, has been in this registry since 2026-09-17 (check it). Its exact canonical text is published too, at clinicalswipe.com/protocol/2026-09-11.1.txt, so you do not have to take our word for what it says: recompute it yourself with curl -s https://clinicalswipe.com/protocol/2026-09-11.1.txt | shasum -a 256 and the result is the anchored fingerprint.
Designed, not yet running In design
Care Records and LMN Issuance Designed — not yet running
The design: caregiver shift notes, care goal updates, and Letters of Medical Necessity hashed at issuance and again at sign-off, so the two-hash chain shows the document was not altered in between — family-owned and checkable by any authorised party without asking a platform’s permission. Half of it is live: the sign-off hash, through ClinicalSwipe. The issuance hash and the caregiver records are not anchored yet, so the chain is not complete and should not be described as if it were.
co-op.care →Routing Decisions Designed — not yet running
The design: when an AI recommends a provider, a pathway, or a purchase, it is routing care. Anchoring the routing event — what was recommended, on what basis, by which model version — is what would make conflict-of-interest review possible at all. A platform cannot audit its own routing; a receipt can. This one matters most and exists least.
SurgeonValue →06 · What changes in 2027
Outcomes are about to be published against your name.
A fingerprint has always been a nice property. It is about to become a practical one, for a specific and dated reason.
The moment this matters — July 2026. Four things are now true at once. TEFCA crossed one billion health records exchanged, with information-blocking referred to the DOJ — the pipes are built and enforced. CMS’s WISeR model made licensed-clinician review of AI decisions a payment requirement. ChatGPT for Clinicians made AI drafting free for every licensed clinician in America. And CMS proposed the first Medicare payment category for clinical AI — status indicator O1, paid per use — while admitting in the same rule that per-click billing “raises concerns regarding program integrity.” Free drafting, mandated review, enforced pipes, per-use payment — and still no proof of what was done, by whom, under whose license.
CMS’s ACCESS Model — Advancing Chronic Care with Effective, Scalable Solutions — began 5 July 2026 and runs ten years. It pays on outcomes rather than activities, and CMS states it will publish participants’ risk-adjusted outcomes in a public directory so patients and referring clinicians can compare. Separately, the mandatory episode models score a named clinician or institution across a period.
Put those together and something changes about what a clinical record is for. Until now the record mostly had to satisfy a payer once. From here it also has to stand behind a number published next to your name, that a patient and a referring clinician will read, and that you may one day need to dispute.
Which raises a question that has an uncomfortable answer for most of the market. A great many capable companies will collect those outcomes for you, reconcile the episode, and write results back into your system. That is real work and worth paying for. But the record it produces lives in their schema, under a contract. That is fine right up until the relationship ends, the vendor is acquired, or the number is challenged.
A record you did not sign is not yours, and an attestation you cannot verify without the vendor is not portable.
That is the entire argument for this layer, and it is a narrow one. A SHA-256 fingerprint does not care who is still in business. It says one thing — this is the document that was signed, at that moment, unchanged — and anyone can check it without asking us, or them, for permission.
Said plainly, because this page does not get to be vague about itself: the argument above is why the surgeon-side and physician-review rails are worth wiring. It is not a claim that they are wired. The audit layer above says exactly what is anchoring records today, and the counter is read live from the registry. Believe that, not this.
The full derivation — the routing layer, the payment models, and the four forces that converge on one artifact — is at solvinghealth.com/model. Sources are CMS and ARPA-H primary pages, read 10 September 2026.
The AI drafts it. Who signs it?
07 · SolvingHealth ecosystem
The products this is built for.
HashCare is the receipt layer for the SolvingHealth products below. Each one has a real accountability problem this is meant to close — and each is described here by the problem, not by an integration that is not finished. The counter above is the honest measure of how far that has got.
In the stack: chanio.com keeps your context on your own Mac, harnesshealth.ai runs the work under physician-set rules, and HashCare is the proof.
ClinicalSwipe
The physician review loop: an AI drafts, a named and specialty-matched physician signs or declines. Live and running, and since 2026-09-05 every determination it issues — signed, revised or declined — is anchored in this registry, labelled by verdict. Synthetic pilot until a BAA is in place.
clinicalswipe.com →ComfortCard
A QR-accessible emergency profile for a caregiver or paramedic to read at the door. Where a stranger has to trust a record on sight, a fingerprint is the natural fit.
comfortcard.org →co-op.care
Worker-owned care with family-owned records. The families, not the platform, should be able to prove what a shift note said — which is the whole argument for a receipt they can check without us.
co-op.care →SurgeonValue
Surgeon-side encounter and billing work, where a claim signed under a physician’s own NPI is the thing that has to hold up later. The strongest case for anchoring at ingestion, and the next one to build.
surgeonvalue.com →The Physician Network
The licensed reviewers whose signatures anchor here. NPI-verified, specialty-matched, paid per review — join the network that signs what AI drafts.
altru.care/physicians →HarnessHealth
The physician-governed harness for engineering teams, exposed as narrow MCP tools rather than open-ended access. Synthetic and test data only — no BAA is in place, so no protected health information goes through it.
harnesshealth.ai/developers →08 · Show the chain
“Verified by HashCare” — a badge any site can carry.
If your product anchors its records to HashCare, say so. Paste the snippet below anywhere HTML renders — no JavaScript, no dependencies, one link back to the audit layer.
<a href="https://hashcare.com" target="_blank" rel="noopener"
style="display:inline-flex;align-items:center;gap:7px;padding:7px 13px;
background:#131f38;border:1px solid rgba(13,115,119,0.5);
border-radius:8px;font-family:Arial,Helvetica,sans-serif;
font-size:12px;font-weight:700;color:#14a4a9;text-decoration:none;">
<svg width="13" height="13" viewBox="0 0 22 22" fill="none" aria-hidden="true">
<path d="M11 2L3 6v6c0 4.8 3.2 9.3 8 10.4C16.8 21.3 19 16.8 19 12V6l-8-4z"
stroke="currentColor" stroke-width="1.75" stroke-linejoin="round"/>
<path d="M7.5 11.3l2.4 2.4 4.6-4.8" stroke="currentColor" stroke-width="1.75"
stroke-linecap="round" stroke-linejoin="round"/>
</svg>
Verified by HashCare
</a>
Works now, no account
Anchor something you might have to prove later.
A manuscript before you send it. A dataset before you publish. A signed agreement, a photograph, a clinical protocol, a disclosure you may one day need to date. It is hashed in your browser, so the document never leaves your device and we never see it — and the timestamp holds even if this company does not.
Anchor a documentNot a clinical signature, not a copyright registration, not legal advice. It proves a document with that exact fingerprint existed at that time — nothing more, and nothing less.
Building something that needs receipts for physician review? The rail is being built in the open. Leave an address and you will hear when it is real — not before.
No spam, no drip sequence, no cohort urgency.