WorkflowPatient Safety

Expectedness & Causality Medical Review Copilot

Expectedness assessment against the right edition of the RSI, with the clause quoted and the causality evidence laid out

Every serious event judged against the label in force that day, with the clause quoted.

See one case, screen by screen ↓
demo6.4sfor five agents to pick the edition, search it, quote the clause, lay out causality and set the clock
demo7termsMedDRA terms searched for one reported event, each marked found, lesser severity or not found
target14minmedian medical review per serious case, down from 26
target100%of expedited reports filed on time, judged on the right edition
The problem

Why expectedness calls are slow, and easy to get wrong

A serious case lands with its clock already running from Day 0. Before the safety physician can judge it, someone has to work out which reference applies: the investigator’s brochure edition in force on the onset date for a trial, the USPI for a US 15-day Alert decision, the SmPC for the EU — with the CCDS beside them, and a new edition approved but not yet in effect.

Then the term has to be found, and it is rarely there word for word. “Alanine aminotransferase increased” in the RSI does not make drug-induced liver injury expected; a listed reaction that was life-threatening this time may not be. The causality picture — dosing dates, dechallenge, other medicines, viral serology — sits across the narrative and the lab tables. Done by hand, every case is a search, and every search is a chance to judge the case on the wrong edition.

target26minmedian medical review per serious case by hand
typical7 or 15daysfrom Day 0 to an expedited SUSAR report — 7 if fatal or life-threatening
demo18%of serious cases reviewed in 30 days were unexpected — 74 of 412
Where a serious case’s days go before it is signedestimated
By hand7 days
With the solution2.2 days
  • Finding the edition in force and its section1 → 0.1 d
  • Searching for the term and its MedDRA neighbours1 → 0.1 d
  • Pulling the causality evidence together2 → 0.5 d
  • Follow-up questions to the investigator2 → 1 d
  • Signature and second review1 → 0.5 d

Estimated split for one serious case on a 15-day clock, by hand and with the solution.

How it works

How a serious case moves

Six specialist agents pick the right reference, search it, read the clause and lay out the causality evidence; a safety physician decides and signs.

What comes in
Case inCoded serious case · with every label and brochure edition
Agents at work
Reference pickeredition in force
Then
MedDRA neighbour searchrelated terms, severity
Causality evidencetimeline, for and against
Then
Listedness readerquotes the clause
Follow-up query writerasks for missing facts
Then
Reportability clockdue date per authority
A person decides
Safety physiciandecides and signs; fatal cases signed twice
What comes out
Signed medical assessment
Report queued on its clock
Every verdict cited
One case, step by step

One serious case, from received to signed

A 52-year-old man in study VLT-302 is hospitalised with drug-induced liver injury on Veltrimab. The SAE form arrives on Oct 3. Here is what happens next, screen by screen, in the working solution.

  1. 01Morning

    Every open serious case, placed on the day its report is due

    Dr. Maya Chen · Safety physician

    Maya opens the solution to 8 serious cases open, 5 on an expedited clock and 7 waiting for her. The clock runway sets each case on its due date — clinical trials on the SUSAR clock, marketed products on the 15-day Alert and EU 15-day reports. The liver injury on Veltrimab, MR-26-1184, sits at Oct 18 with agents ready.

    References in force today: “Veltrimab · IB Edition 10 takes effect Nov 1. Events with onset before Nov 1 stay on Edition 9.”

  2. 02Opened

    The case opens, and the review starts

    The agents

    MR-26-1184: subject 114-0087 at Site 114, Chicago, Day 0 Oct 3, investigator’s causality “related”. The SAE report sits on the right with its passages highlighted. Five agents run in view: the reference picker, the MedDRA neighbour search, the listedness reader, the causality evidence agent and the reportability clock.

    Reference picker: “Onset Sep 22 → IB Edition 9 in force · IB Edition 10 starts Nov 1 — not used”

  3. 036.4 seconds later

    Unexpected — with the clause it rests on

    Listedness reader

    The proposed verdict for drug-induced liver injury is Unexpected, high confidence. Onset was 22 Sep 2026, so Edition 9 applies. Edition 9 §7.4 lists alanine aminotransferase increased and transaminases increased — raised enzymes, not liver injury. The raised ALT reported in the same case is proposed as listed.

    “Edition 9 lists only raised liver enzymes; liver injury is greater in severity, which makes it unexpected. Edition 10 lists it but is not in force on the onset date.”

  4. 04Next

    The right edition, and every term searched

    Reference picker · MedDRA neighbour search

    The edition timeline shows the onset on Sep 22 inside Edition 9’s window (Mar 1 – Oct 31). Edition 10 was approved on Sep 30 but applies only from Nov 1. The search covers seven MedDRA terms under Hepatocellular damage and hepatitis NEC: two are found, both at lesser severity; five, including hepatotoxicity and hepatitis, are not found.

    “The version in force at the moment of occurrence decides.”

  5. 05Next

    Exposure and event on one timeline

    Causality evidence

    Two doses of Veltrimab 150 mg on Aug 12 and Sep 9, acetaminophen from Sep 15 to 20, onset on Sep 22, in hospital from Sep 23 to 29, the drug stopped on Sep 24 — and ALT plotted against its upper limit of 41, from 24 at baseline to 412 and back down to 96 by Oct 2.

  6. 06Her call

    The evidence for and against, then her assessment

    Dr. Maya Chen · Safety physician

    Four facts support a causal role: onset 41 days after the first dose, a positive dechallenge, viral hepatitis A to E negative with a normal ultrasound, and raised enzymes already in Edition 9. One is against: acetaminophen 2 g/day for 6 days, ending 2 days before onset. Hy’s Law is not met. The agents suggest reasonable possibility, RUCAM 7 · probable; Maya records Yes, and the comment for the case is drafted from the evidence.

    The causality agent never records causality for the physician, and the investigator’s “related” is never downgraded for expedited reporting.

  7. 07If a fact is missing

    The questions to the investigator, drafted

    Follow-up query writer

    “Ask investigator” opens three numbered questions to the principal investigator at Site 114: liver tests in the 6 months before the first dose, any herbal or over-the-counter products besides acetaminophen, and the next ALT, AST and bilirubin results. The reply is requested by Oct 10, inside the clock.

    Nothing is sent until the physician approves it.

  8. 08Signed

    One signature, with its meaning

    Dr. Maya Chen · Safety physician

    The summary lists each event as proposed, the causality and the reportability: IND safety report, due Oct 18. Maya signs as Dr. Maya Chen · Safety physician with her password, and the meaning is recorded with the signature.

    “Meaning: I have reviewed the listedness and causality of this case and approve this medical assessment.”

  9. 0911 days before due

    Every report queued on its clock

    Reportability clock

    The reportability is now final, from the signed assessment: an IND safety report under 21 CFR 312.32 to FDA and a SUSAR report to EudraVigilance, both on the 15-day clock and due Oct 18, a SUSAR notice to investigators and ethics committees with the report — all three queued — and a DSUR line listing for the annual safety report.

    “Seriousness: Hospitalisation · Listedness: Unexpected · Causality: reasonable possibility”

  10. 10Every month

    Review time, verdicts and where the labels disagree

    The safety team

    412 serious cases reviewed in the last 30 days, 37 of 37 expedited reports on time, a median of 14 minutes per case against 26 before agents. Every verdict the physician changed is listed with the reason and its second signature — interstitial lung disease, for one, moved to unexpected because the outcome was fatal and the label lists only non-fatal pneumonitis.

Who it’s for

Built for everyone who carries a serious case.

The same case, seen by the four people who handle it — what their week looked like, and what it looks like now.

MC
Dr. Maya ChenSafety physician
Reviewer · signs
Before
Opens each serious case by hunting for the right IB edition and searching it term by term.
Now
Starts from a proposed verdict with the clause quoted and the causality evidence laid out, and spends the time on the judgement.
OH
Dr. Omar HaddadSenior safety physician
Second reviewer
Before
Co-signs fatal and changed calls from a narrative, and has to rebuild the reasoning himself.
Now
Gets the fatal or life-threatening unexpected cases and every changed verdict with the evidence and the first signature already on them.
LO
Lena OrtizSafety labeling lead
Reference owner
Before
Tracks by hand which label lags the CCDS, and which open cases that touches.
Now
Approves each new edition and its effective date before the agents use it, and sees which open cases each one touches.
SP
Sam PatelCase processing lead
Submissions
Before
Chases physicians for signed assessments as the 7- and 15-day dates close in.
Now
Sees every signed assessment and every report queued with its authority, clock and due date.
Built on the engine

6 agents. Each with one job, and hard limits.

Six specialist agents pick the right reference, search it, read the clause and lay out the causality evidence; a safety physician decides and signs.

Reference picker

Chooses the reference documents that apply to each event: the IB edition in force on the onset date for trials; USPI, CCDS, SmPC and local label by market for marketed products.

  • Never uses an edition outside its in-force window
  • Cites the onset date it used
MedDRA neighbour search

Expands each preferred term to its synonyms and the other terms in the same high-level term, searches the applicable documents and marks each hit as the same, lesser or greater severity.

  • Search depth set in Settings
  • Reports every term searched, found or not
Listedness reader

Reads the hits in context and proposes listed, unexpected or “your judgement” for each event and document, quoting the clause it rests on.

  • Every verdict quotes a clause
  • Proposes only — the physician decides
  • A fatal or life-threatening reaction is listed only when the RSI says so
Causality evidence

Builds the exposure and event timeline and lists the evidence for and against a causal role — onset, dechallenge, rechallenge, other causes, known effects — with a WHO-UMC or RUCAM suggestion.

  • Never records causality for the physician
  • The investigator’s “related” is never downgraded
Follow-up query writer

Drafts the question to the investigator or reporter when evidence is missing — baseline labs, other medicines, rechallenge, autopsy.

  • Asks only for what changes the assessment
  • The physician approves before sending
Reportability clock

Works out what each authority needs and by when — SUSAR 7 or 15 days, US 15-day Alert, EU 15-day, periodic — from the signed verdicts and causality, and queues the report once the physician signs.

  • Final only after the electronic signature
Safety physician

Decides and signs. The agents propose; a named person decides.

Ask in plain words

Ask about any case, edition or rule

The physician can ask in plain words about any open case, reference document or review rule — or tell it what to change. Every answer points to the passage behind it.

Why is the liver injury on MR-26-1184 unexpected?

Because the onset was 22 Sep 2026, and the RSI in force on that date decides — IB Edition 9. Raised enzymes are listed, but liver injury is greater in severity, which makes it unexpected. Edition 10 lists it — but only from Nov 1. With the investigator’s “related”, it is a 15-day SUSAR due Oct 18.

Which open cases change when IB Edition 10 takes effect?

None of today’s open cases change — each is judged on the edition in force at onset, and every onset is before Nov 1. What changes is new events from Nov 1: drug-induced liver injury and life-threatening anaphylaxis become listed. MR-26-1184 and MR-26-1190 keep Edition 9.

Where do Corventa’s labels disagree?

One serious term: toxic epidermal necrolysis. CCDS v14 and the SmPC list it; the USPI of 06/2025 lists erythema multiforme only. Because a US 15-day Alert report is judged on the current labeling, MR-26-1179 is unexpected for the US and due Oct 16 — until the USPI update filed on Sep 2 is approved.

Flag every case where the USPI lags the CCDS

Done. New rule: flag a case when its event is in the CCDS but not yet in the USPI. Running it on the open cases finds one — MR-26-1179, toxic epidermal necrolysis on Corventa. The flag shows on the case and Lena Ortiz gets a weekly list. The rule is live in Settings and recorded in the audit trail.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

HomeWhat needs the safety physician today: cases waiting, unexpected cases on a running clock, the next report due, and the references in force.
Cases in medical reviewEvery serious case with the reference used, listedness, causality, stage and clock — filterable by stage and product.
Agents at workFive agents run in view on the case, each with what it found, beside the SAE report.
The proposed verdictUnexpected, with the reasoning, the citations and the edition timeline — the IB clause highlighted on the right.
Edition and MedDRA searchWhich edition applies on the onset date, the verdict in each document, and every MedDRA term searched.
Causality timelineDosing, other medicines, onset, dechallenge and the ALT curve on one timeline.
Evidence and assessmentEvidence for and against, the investigator’s view, the agents’ suggestion and the physician’s own call.
Follow-up queryNumbered questions to the investigator, drafted for the physician to approve and send.
Electronic signatureThe physician signs the medical assessment with name, password and the meaning of the signature.
ReportabilityWhere the case goes — FDA, EudraVigilance, investigators and ethics committees, the DSUR — with clocks and due dates.
Reference safety documentsEvery IB, CCDS, USPI and SmPC edition per product, with the dates it is in force.
The review dashboardCases reviewed, minutes per case, unexpected share, reports on time, where the labels disagree and the verdicts the physician changed.
Review rulesWhich edition applies, the fatal and life-threatening rule, MedDRA search depth, causality convention and second signatures.
Governance

Built for medical review: quoted, signed, on the record.

Every verdict quotes its clauseEach listed or unexpected call names the edition and quotes the clause it rests on; click it to see the passage highlighted in the IB, CCDS, USPI or SmPC.
The edition in force decidesThe reference in force on the onset date applies — never a newer approved edition that is not yet in effect. A new edition is approved by the reference owner before the agents use it.
Agents propose, a physician decidesVerdicts and causality are proposals. Only a safety physician decides and signs, and the agents never record causality for them.
Signed with meaning, name and timeThe medical assessment is approved with an electronic signature — the physician’s name, password and the meaning of the signature, recorded together.
A second physician where it mattersA fatal or life-threatening event assessed as unexpected, or a proposed verdict the physician changes, needs a second safety physician’s signature before the report is queued.
Every step on the recordThe case activity is immutable and shows people and agents alike — which edition was chosen, what was proposed, what was recorded and who signed. Rule changes are versioned in the audit trail.
Configuration

Your SOP’s rules, not ours

Which document applies, how deep the search goes, the causality convention and who signs second are all settings.

SettingDefaultChoose from
Use the reference in force on the event onset dateOnIB editions by onset date; labels by the date the case was received
Fatal or life-threatening reactions are unexpected unless the RSI says soOnListed terms without “life-threatening” go to the physician for judgement
Search MedDRA neighboursSame high-level termPreferred term only · Same high-level term · Same high-level group term
Judge US cases on the current USPIOnThe CCDS is shown beside it but never decides a 15-day Alert report
Causality conventionReasonable possibility · yes or noReasonable possibility · yes or no · WHO-UMC categories
Suggest a RUCAM score for liver eventsOnShown beside the WHO-UMC suggestion
Second signature when fatal or life-threatening and unexpectedDr. Omar HaddadDr. Omar Haddad · Dr. Priya Raman
Approves a new edition before agents use itLena OrtizLena Ortiz · Dana Okafor
Connections

Works with the systems you already run

Your safety databasecases, MedDRA coding and E2B(R3) submissions
Labeling repositoryCCDS, USPI, SmPC and IB editions with effective dates
MedDRAterms and hierarchy, version 29.1
Case follow-up mailboxquestions to investigators and reporters
Your PV SOPscausality convention and second-signature rules
Reporting rulesIND safety reports, SUSARs, 15-day Alert and EU 15-day
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
14min
median medical review per serious case, down from 26
By hand26 min
With agents14 min
target
100%
of expedited reports filed on time, judged on the right edition
37 of 37 in the last 30 days
target
96%
of agent verdicts kept by the physician, each one cited
4 in 100 changed by the physician

“demo” = seen in the working solution, on its sample cases · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published rules (21 CFR 312.32 and 314.80, ICH E2A — 7- and 15-day expedited reporting). People, companies and products named on this page are fictional — characters and sample data in the working solution.

Questions

What safety physicians ask us.

What is an expectedness assessment?

It is the decision whether a serious adverse reaction is listed in the applicable reference safety information — the IB’s RSI for a trial, the label for a marketed product — at the same severity and specificity. Together with seriousness and causality, it decides whether a case is reported on an expedited clock. The solution proposes the verdict with the clause quoted; the safety physician decides.

How does it know which edition of the IB or label applies?

The reference picker reads the onset date of each event and chooses the investigator’s brochure edition in force on that date — never a newer approved edition that is not yet in effect. For marketed products it uses the USPI for US 15-day Alert decisions and the SmPC for the EU, and always shows the CCDS beside them.

Does it find terms that are not reported word for word?

Yes. The MedDRA neighbour search looks for the reported preferred term, its synonyms and the other terms in the same high-level term, and marks each hit as the same, lesser or greater severity. A lesser-severity listing such as “transaminases increased” does not make liver injury listed. The search depth is a setting.

How does it handle causality?

The causality evidence agent builds the exposure and event timeline and lists what supports and what argues against a causal role — time to onset, dechallenge, rechallenge, other causes, known effects — with a WHO-UMC or RUCAM suggestion. It never records causality for the physician, and the investigator’s “related” is never downgraded for expedited reporting.

Do physicians stay in control?

Yes. The agents only propose. A safety physician agrees with or changes each verdict, records causality and signs the assessment with an electronic signature. Fatal or life-threatening unexpected events and changed verdicts need a second physician’s signature before the report is queued.

Can we use our own causality convention?

Yes. Causality can be recorded as reasonable possibility yes or no, or as WHO-UMC categories, and a RUCAM score can be suggested for liver events. The second-signature approvers and who approves a new reference edition are settings too.

Which systems does it connect to?

Your safety database for cases, MedDRA coding and E2B(R3) submissions, your labeling repository for CCDS, USPI, SmPC and IB editions with their effective dates, MedDRA, and the case follow-up mailbox for questions to investigators and reporters.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements — your medical review SOP, reference documents and a sample of past serious cases — and it goes live once every quality gate has passed. We will walk you through it on your own cases first.

See it on
your serious cases.

We’ll run Expectedness Review on a sample of your own serious cases and reference documents.