For independent patient advocates
An appeal-letter assembler that refuses to make things up
You know the argument. The grind is the assembly — quoting the denial exactly, citing the right rule and deadline, and making sure every fact in the letter is backed by a document and not a memory. This guards that step.
The one rule
It never writes a fact it can’t trace.
Every fact in the letter resolves to a confirmed client field or a verbatim quote from a source document — or it doesn’t go in. It goes on a “needs from you” list instead.
Cite-or-abstain
Every quote from a denial letter, EOB, or letter of medical necessity must resolve verbatim against the source you supplied. If it isn’t in the document, it isn’t in the letter.
Copy-or-abstain on patient facts
Name, DOB, member ID, insurer are copied exactly from your confirmed client fields. Anything unconfirmed or missing is flagged — never guessed.
Sealed sources
Each source is sealed with a SHA-256 hash, and the assembler re-verifies that seal before quoting from it — if the text doesn’t match the seal, the citation fails closed.
Right statute, right deadline
Maps the appeal track and quotes the governing rule and filing window — Medicare redetermination (42 CFR §405.942, 120 days), MA reconsideration (§422.582, 60 days), commercial/ERISA (29 CFR §2560.503-1(h), 180 days).
How it works
Paste the denial. See what holds — and what’s missing.
- Paste the denial letter. It becomes a sealed source. The text is matched on the Health Agent server to build the letter — it is not sent to any AI model.
- Quote the facts. Enter the claim number, date of service, and denial reason as the exact words from the letter. Anything not found verbatim fails closed to the gap list.
- Confirm the patient header. Name, DOB, member ID, insurer — copied exactly, blanks flagged.
- Get the governed preview. A grounded, cited draft plus an explicit list of everything it refused to assert — so you see the gaps before you file, not after a second denial.
Honest scope
What it is, what it isn’t.
It is
- An assembler that traces every fact to a document or a confirmed field
- A cite-or-abstain, fail-closed letter builder
- A speed & accuracy guard on the assembly step
- Tamper-evident on the source documents
It isn’t
- A tool that predicts whether you’ll win
- A medical-necessity author — that’s the physician’s letter
- A replacement for your judgment, signature, or license
- A guarantee of any specific outcome
The design-partner pilot
Run real client denials through it. Tell me where it helps and where it gets in the way.
I’m looking for a small number of independent advocates as design partners. Pilot pricing is design-partner pricing, named with you — nothing is committed here.
Where your client’s data goes — straight answer. The text-assembler step is deterministic: the text you paste is sealed and matched on the Health Agent server to build the letter, and it is not sent to any AI model. The platform also has a separate document-photo feature. By default that photo is read by OCR running locally on the Health Agent server, in the same container — the image is not sent to any third-party AI provider, and the uploaded file is encrypted at rest. The text the reader extracts from that file is encrypted at rest as well — not stored in the clear — and every time it is opened, that access is recorded to a tamper-evident audit ledger. Generated artifacts and abandoned or failed uploads are auto-purged on a retention schedule; a document you keep is retained until you delete it. (Sending a photo to a cloud AI provider for higher-accuracy reading is off by default; Bonis Systems will enable it only under a signed Business Associate Agreement.) Local OCR is text extraction — not de-identification and not a HIPAA Safe-Harbor determination. Before you run a single real client document, I’ll give you the exact data-flow in writing — what touches a cloud service and what doesn’t — so you can make your own compliance call. The pilot can be scoped to de-identified, text-only intake.
See it on a denial you know.
Open a free account — that’s your design-partner login — and run one denial through the governed assembler. You’ll see exactly what it backs and what it refuses to assert.