NewMissing Records Detection: flags every visit, provider, and date missing from the file. See how →
HomeSolutionsToxic Exposure Review
TOXIC TORT EXPOSURE RECORD REVIEW

General causation is a literature question. Specific causation is a records question.

Toxic tort exposure record review services assemble what specific causation is argued from: the documented exposure history, dose and duration indicators, the latency interval, the diagnostic record and every alternative cause the file contains, each cited to its page. The causation opinion belongs to the expert.

Click any row → the source page it cites
Exposure causation record digest · Case #IME-4812 documented
Adams, Timothy · plaintiff record
342 pp / 2 packets received logged
11 duplicate pages removed free
p.140 — wrong patient quarantined
Pages 342 Documents 27 Cited 100%

The manual is published. The Rule 702 judge applies 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 toxic exposure causation, both are already published.

The standard and the referee
The rulebook
  • Federal Rule of Evidence 702 as amended in December 2023, and the general-versus-specific causation split courts apply under it, under which an agent capable of causing a disease still has to be shown to have caused this plaintiff’s
  • The Reference Manual on Scientific Evidence, third edition, and its chapters on epidemiology and toxicology, which set what a court expects a causation opinion to address
  • The Restatement (Third) of Torts: Liability for Physical and Emotional Harm §28 on the plaintiff’s burden on factual cause, including the toxic-substances comment
  • The published record for the agent at issue, including the ATSDR toxicological profile and the relevant IARC monograph, against which dose, route and latency are read
The referee
  • The trial court at a Rule 702 hearing, and in an MDL the transferee judge deciding general causation for every case in the litigation at once
  • The defence toxicologist and epidemiologist, who read the same file for the alternative causes the report did not address
  • The settlement administrator applying the matrix, where the litigation resolves on tiers rather than trials
A specific causation opinion excluded for never addressing a documented alternative cause From 10¢ to as low as 5¢/page here, duplicates free
Exposure causation record digest · Case #IME-4812 cited 100%
Packet342 pp / 2 packets · 11 deduplicatedlogged
Exposure historyAgent, route, duration, source documentcited
Latency intervalFirst documented exposure to first diagnosiscomputed
Alternative causesSmoking, occupation, comorbidity, family historyflagged
Digest delivered · cited 100% · no causation opinion
How it works

3 steps between the record and the causation opinion.

01

Send the whole file

Medical records, occupational and employment history, product and residence history, industrial hygiene or monitoring data where it exists, and prior claims records, in any format.

02

Get the digest back, page-cited

The documented exposure history with each entry traced to its source, the latency interval computed from dated entries rather than asserted, and every alternative cause the record contains carried as its own flagged row.

03

The expert forms the opinion

General causation, specific causation, dose reconstruction and differential etiology are the expert’s work. The digest is the cited record the analysis rests on.

The boundary, in writing

A cited record, not a causation opinion.

We assemble and cite what the record documents. We do not opine on general or specific causation, reconstruct dose, perform a differential etiology, or assess whether an agent can cause a disease. Those are the expert’s, and Rule 702 is why they have to be.

Alternative causes are flagged rather than argued. A twenty-year smoking history in a primary care note is a fact in the record, and an expert who has not seen it before writing is the expert who gets excluded.

Audit trail · Case #IME-4812 exportable
08:12Packet received · 342 pp / 2 packetssystem
08:3111 pages deduplicatedsystem
08:44p.140 flagged — wrong patientsystem
08:54Exposure causation record digest complete · digest delivered · cited 100%system
09:20Exposure causation record digest reviewed · citations verifiedreviewer
09:26Exposure causation record digest exported · report structure assembled by the expertreviewer
Every access logged · file deleted 30 days after delivery
Why Medrecords AI

The rules the platform never breaks.

Medrecords AI EVERY LINE CITED
CASE #IME-4812 · ADAMS, T.342 pp
2/14 — ER visit, right knee p.4
4/18 — arthroscopic surgery p.61
p.140 — wrong patient quarantined
Medrecords AI
Read every page · cite every line

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.

Powered by the platform

7 capabilities behind every exposure causation record digest.

The exposure causation digest is one deliverable of the same platform that reads, sorts, and cites the whole record.

Medical Records OCR

Decades of records plus employment and product history are read in full, including handwritten occupational health files.

IN ACTION · 2,800 pp / 11 sources, read in full

Medical Chronology

Exposure entries, symptom onset and diagnosis assemble on one timeline, so latency is measured from dated pages rather than from the complaint.

IN ACTION · first exposure → diagnosis, one timeline

Verifiable AI Citations

Every alternative cause links to the entry that documents it, so the expert addresses it before the other side does.

IN ACTION · digest → cited 100%

Medical Summary Reports

It exports into the expert’s report structure, the plaintiff fact sheet, or a settlement matrix submission.

IN ACTION · digest → report structure

Medical Record Deduplication

Forty charts pulled from multiple practices and EHR migrations carry their share of duplicate visit notes. Each is matched and collapsed to one canonical record, so the prescribing pattern is read once per real encounter.

IN ACTION · 40 charts → duplicate visit notes collapsed to 1 record each

Missing Records Identification

A prescribing pattern read across 40 charts is only as sound as the file behind it. When a chart references a visit, refill, or referral that never made it into the production, the gap is flagged before the pattern goes to the board.

IN ACTION · prescribing pattern cross-checked → gaps flagged before submission

Cross-Exam Simulator (beta)

A board investigator or defense counsel builds a case from the chart abstraction. This beta tool maps the questioning a physician facing that hearing is likely to face on the gaps and pattern in their own record. A rehearsal tool, not legal advice.

IN ACTION · prescribing pattern → likely hearing questions mapped (beta)
FAQ

Toxic exposure review, answered.

No. Causation in a toxic tort is an expert opinion subject to Rule 702, argued in two stages. We assemble the cited factual record the specific causation stage is argued from: exposure, dose indicators, latency and alternative causes.

Product liability medical causation covers device and drug injury where the exposure is a discrete event. This covers chemical and environmental exposure, where dose, route, duration and latency are the contested facts and the general causation question is litigated separately.

Yes. The same digest structure populates a plaintiff fact sheet and a settlement matrix submission, and files are processed at whatever volume the litigation produces.

No. Medrecords AI does not retrieve records from providers or facilities. You bring the records you already have — review starts in minutes from upload. Retrieval vendors take days; you can keep yours and still cut the review to minutes.

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.