The complete index — every link verified live

Everything HashCare, on one page.

The proof layer for clinical AI: free anchoring, verifiable receipts, a published review standard, and a registry countersigned into Bitcoin every day. This page is the whole map — pages, proofs, endpoints, stories, and the primary sources underneath them.

The product surfaces

The documents & proof files

The API — auth-free, works today

The stories — each one paragraph, each load-bearing

1 · The AI drafts it. Who signs it?

Four things are now true at once: TEFCA moved a billion records with DOJ-enforced pipes; 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 paying for clinical AI per use. Free drafting, mandated review, enforced pipes, per-use payment — and still no proof of what was done, by whom, under whose license. That question is the entire product.

2 · China published the definition. The US hadn't.

When China opened the world's first AI-native hospital in March 2026, it published the consensus definition of an AI hospital the same day. In the US, Joint Commission, URAC, and NCQA certify organizations, and WISeR requires review per determination — but nobody had defined what counts as a real human review of a single AI decision. The Five Tests fill that gap: licensed and matched, independent, engaged (measured), receipted, durable. Published free, versioned, and hash-anchored in the registry it prescribes — so priority is provable forever.

3 · Medicare will pay for AI per click — and can't prove a click happened.

The CY2027 outpatient rule creates the first Medicare payment category for clinical AI: 36 codes, up to $950.50 per analysis, paid to the facility. In the same section, CMS admits per-click billing "raises concerns regarding program integrity." A four-field receipt — content hash, algorithm version, anchored timestamp, reviewer NPI — closes the gap for effectively nothing, and it's generatable today. The docket that decides the category's rules is open until August 31, 2026.

4 · Proofs that outlive the operator.

Every day, the whole registry is rolled into one root hash and stamped into Bitcoin via OpenTimestamps. Anyone can recompute the root from the public hash list and check the timestamp against the Bitcoin blockchain — no trust in HashCare required. If HashCare vanished tomorrow, every receipt would still verify. A proof that dies with its vendor was never a proof.

5 · The rubber stamp is the failure mode — measured, and named.

The NOHARM benchmark (Stanford/Harvard, 57 authors) found AI-assisted physicians scored lower than AI alone as practiced — presence isn't engagement. Bob Wachter, chair of medicine at UCSF: "You can't train someone to pay attention on the 40th time if it's been right 39 times in a row." That's why Test 3 requires a measured disagreement rate, not an assumed one — and why this site claims accountability, never accuracy.

6 · The Review Rail — the standard, staffed.

For WISeR vendors and coverage-decision AI: state-matched, NPI-verified physician review delivered as an API, a receipt per determination, double-review calibration statistics, and a fixed-price two-week pilot on 50 real determinations. Scored against the published Five Tests, test by test. The network is ClinicalSwipe; the receipts are HashCare; the pipe is the harness.

7 · Proof is free. Judgment is priced.

Anchoring costs nothing and always will — proof of existence is infrastructure, not a toll. What's priced is judgment: licensed physicians reviewing clinical AI output, with receipts attached. The rail stays free so the receipts become universal; the signature is the product.

Primary sources (what everything above cites)

The network

What's deliberately not here: user content (never uploaded — only fingerprints exist), pricing theater (anchoring is free, forever), and claims that human review improves accuracy (the evidence is mixed; this whole stack claims accountability and verifiability, which are provable). Every link on this page returned HTTP 200 on the day it shipped; the registry root above re-proves itself daily.