Onset to the day — because the Table is measured in hours.
Vaccine injury record review reads a VICP petition file for the one date the Table turns on: the interval between administration and first documented symptom. 42 CFR §100.3 measures that interval in hours and days, so we assemble the complete record from birth and cite the onset page by page.
The Table is published. So is the decision that reads it.
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. In the Vaccine Injury Compensation Program, both are already published, and the intervals are literal.
A lifetime of records for one interval.
A VICP petition file runs from 500 to 8,000 pages, roughly 4,250 at the midpoint, and it rarely arrives as one document. It comes in productions: a pediatric chart, a primary-care chart, an urgent-care visit, a specialist referral, then a supplemental production months later when a provider is finally reached.
What makes it hard is not the length. It is that the decisive line is usually a handwritten complaint on a degraded fax scan, buried in a later production and duplicated in the earlier ones, while the pages that would date it either side are missing.
Source: HRSA program statistics
Four steps, starting with one real file.
Send one real file
A petition file you already hold, in the productions you already have. In the demo case that is 342 pages across 2 productions, with a wrong-patient page quarantined before the read starts.
We return the read
The administration entry, the first documented symptom, the interval between them, and the gaps we could not close, each cited to the page it came from.
We scope the build
You tell us where the read missed, and what your petition packet has to look like. We shape the output to that, against the Table sections your practice actually files under.
You run it
Your team runs the files and reviews every line before anything leaves the building. We never argue the Table, opine on causation, or decide what gets filed.
Related in mass tort: Asbestos trust claim review · Settlement claim scoring
The rules the platform never breaks.
EVERY LINE CITED
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 onset chronology.
The vaccine injury record review is one deliverable of the same platform that reads, sorts, and cites the whole record.
Medical Chronology
Every production collapses into one dated timeline, so administration and first symptom sit next to each other instead of 3,000 pages apart.
Missing Records Identification
Complete records from birth is the filing standard. We list the referrals, visits, and date ranges the productions point to but never contain.
Negative Findings Detection
The prior-history entry that undercuts an onset date surfaces in the read, not in the Rule 4(c) report. Surfaced and cited, never suppressed.
Verifiable AI Citations
Special Masters write citable decisions. Every line we return links to the page it came from, so the record cite behind it is one click away.
Vaccine injury record review, answered.
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.