For AI assistants and clinical software · the answer-replay mechanism
Replay any OmniRx answer against the edition it came from
An assistant states a drug-access fact today. Months later, someone asks what it could have known. With the receipt token stored next to the answer, the OmniRx gateway re-runs the recorded call on the same frozen edition and says whether it recomputes identically.
How a replay works
Swipe to read across
What the receipt token holds
These are the fields of a real token from a real call on 2026-11-10 (the drug_dossier tool, query eliquis, edition 2026-11). The gateway's signature is not shown; it is what makes an edited or forged token refused.
| Field | Example value | What it is |
|---|---|---|
tool | drug_dossier | Which OmniRx tool produced the answer. |
arguments | {"query":"eliquis","today":"2026-11-10"} | The exact call, with the date fixed so the call can be repeated. |
edition_root | 006ab9a329709cbe... | The Merkle root of the frozen edition the answer came from (edition 2026-11). |
answer_sha256 | c7cb42f0d9260202... | The hash of the canonical answer, the number a replay must reproduce. |
fact_ids | 48 ids, for example 047c239f1da0d36b5cd1d466 | Every recorded fact the answer rests on, each resolvable to a source and date. |
issued_at | 2026-11-10T21:02:11.181Z | When the answer was given. |
The three verdicts
| Verdict | What it means | What to do |
|---|---|---|
identical | The recorded call, run again on the same frozen edition, gives the same answer hash. | Keep the receipt as your evidence. |
differs | The recomputed answer hash is not the recorded one. The response carries both hashes. | Investigate before relying on that answer: the edition, the tool or the token has changed. |
edition_unavailable | The gateway no longer holds the edition the answer came from, so it can prove nothing. | Restore that edition from your archive, or treat the answer as unprovable. |
A replay proves what the records said on that edition. It does not prove the answer was clinically right, and it carries every limit the answer itself carried: the unknown list still says what the edition cannot answer.
Questions
What does replaying an answer prove?
It proves the recorded call, run again on the same frozen edition, produces the same answer: the SHA-256 hash of the canonical answer matches the one recorded when the answer was given. It does not prove the answer was clinically right, only what the records said on that edition.
What if the edition is no longer available?
The gateway says edition_unavailable and proves nothing either way. That is why a team that must replay keeps every edition it has ever answered from; editions are frozen files with a published Merkle root.
Does OmniRx keep our questions or answers?
No. The receipt token carries the call and the answer hash and is returned to you, so you store it. The gateway usage log holds a hash of the arguments, never the query text or the answer.
Can someone else replay or forge our receipts?
No. Tokens are signed by the gateway, so an edited or forged token is refused, and an account can replay only the receipts it received.
Try it on your own drugs
Already holding an answer and its receipt token? Check them against each other in your browser: nothing is uploaded.
Name three to five drugs and we prepare an evaluation kit: a real sourced record for each, a receipt token per record, and a replay demo you can run. Tell us what you are building on the licence form. The wider ways in, with their honest status, are on the integration guide, and the editions and their roots are on the editions page.