Certification first, compensation second — both turn on the same file.
VCF and WTC Health Program record review reads one file against two published standards: the presence and exposure documentation behind eligibility, the certified-condition list in 42 CFR Part 88, and the minimum latency interval a cancer must clear before it can be certified. We organize and cite; the government certifies and decides.
Two published standards. Two separate graders.
We do not build for a case type until we can name the standard that defines a correct output and the person who grades the file against it. Here both are published in the Code of Federal Regulations, and the file passes two desks, not one.
Certification comes first and compensation follows, so a gap that stalls the first stage stalls the second as well.
Two decades of care, arriving in pieces.
A single claim file runs from about 400 to 3,000 pages, with roughly 1,700 in the middle of that range. It rarely arrives as one production. The Clinical Center of Excellence chart comes from one source, outside treating records from several more, and the presence and employment documentation from somewhere else again.
What makes it hard is the shape of the paper, not the length. Twenty years of visits produce degraded scans, faxed copies of faxes, handwritten intake and clinic notes, and the same discharge summary re-produced in three separate packets. The condition that matters may be named once, in the middle of a chart that is mostly about something else.
About 900 new claims a month in 2025, up from roughly 700 a month in 2024 — near 10,800 a year, and rising.
$16.8B to more than 71,000 claimants since 2011, with about $2B awarded in 2025 alone.
Four steps, and you keep the decisions.
Send one real file
The productions as you already hold them, in whatever formats they arrived in. In the demo case, 342 pages across 2 packets, with a wrong-patient page quarantined before the read starts.
We return the read, page-cited
Every documented condition with its diagnosis date, the presence and exposure documentation, and the gaps we could not find on any page. Each line links back to the page it came from.
We scope the build together
You tell us where the read missed your working practice, and we shape the output around the packet your team actually assembles. If the case type is not buildable, we say so instead of shipping something thin.
You run it on your files
Your team submits the certification and the claim. We never certify a condition, decide eligibility, or estimate an award. Those calls sit with the WTC Health Program, the Special Master, and the claimant's counsel.
The rules the platform never breaks.
HIPAA, under a signed BAA
Every file is handled under our Business Associate Agreement, from the first byte.
Never trains a model
Your records are never used to train any AI model — ours or anyone else's.
Every line cited
If we can't cite it, we don't say it. Every sentence links to its source page.
Deleted after delivery
Files are deleted 30 days after delivery, with a full audit log of every access.
Four capabilities behind every record check.
This read is one deliverable of the same platform that reads, sorts, and cites the whole record.
Medical Chronology
Twenty years of visits become one timeline, ordered by date and synced to every source page, so the documented exposure dates and the documented diagnosis date sit on the same line.
Missing Records Identification
Names the gaps out loud: the production that stops short of the diagnosis, the referral with no follow-up chart, the condition mentioned with no dated record behind it.
Negative Findings Detection
Surfaces the explicit negatives a long chart buries: the normal study, the denied symptom, the condition a clinician ruled out and never mentioned again.
Verifiable AI Citations
If we can't cite it, we don't say it. Every line in the read links to the page range it was pulled from, which is what makes a submission checkable by someone else.
Send one file. We'll tell you what we can read.
No obligation. If the case type is buildable we'll scope it; if it isn't, we'll say so.