Grading, attribution and drug interaction checks in one pass, with an adverse event report PDF at the end

What shipped in week 12

Week 12 (the week of 16 March 2026) joined the analyses a coordinator runs on an encounter into one pass. When CTCAE grading finishes, multi-drug attribution and drug interaction analysis now start on their own, every step streams its progress as it runs, and the adverse event report PDF gained a new template: an AE log built for monitoring visits, with the reports each event points to and a signature block for the investigator.

It is for the coordinators and investigators who grade, attribute and report adverse events on combination regimens.

The multi-drug attribution pipeline: one grading run, three analyses

The CTCAE grading workflow is now the parent of two child analyses. When grading completes, its output (the graded events, de-duplicated, with standardized drug names and the timing extracted from the note) is converted into typed input for:

• Multi-drug attribution, which scores each adverse event against every drug in the regimen using the WHO-UMC and Kramer causality algorithms, with the reasoning shown.
• Drug interaction analysis, which checks the regimen for interactions between its drugs and for pharmacokinetic compatibility.

The three results sit side by side in one tabbed view, each with its own progress indicator and a completion badge. A guard ensures the two child analyses run exactly once per grading run, however often the page re-renders, so no encounter collects duplicate results.

For a typical combination regimen such as FOLFOX or carboplatin and paclitaxel, the path from clinical note to graded, attributed events now runs without anyone starting the next step by hand. Every result is still a suggestion the investigator accepts or overrides: AI suggests, clinicians decide. For how scoring works per suspect drug, see per-suspect attribution with the working shown; for the concept itself, what multi-drug attribution is.

Real-time workflow streaming: watch each grading step as it runs

Grading has five steps, and each now reports its own progress instead of the screen waiting for the whole run:

Step	What it does
Term extraction	Pulls adverse event terms from the clinical note
Drug standardization	Resolves the drugs named in the note to standard names
Batch CTCAE lookup	Finds the candidate CTCAE criteria for every extracted term at once
Clinical judgment	Weighs the evidence against the criteria and proposes a grade
Output assembly	Builds the graded events the rest of the pipeline reads

Completed steps collapse, the running step shows its output as it arrives, and pending steps show that they are waiting. On a long note, a coordinator can read the extracted terms and standardized drug names while clinical judgment is still working.

The stream is stored with the encounter, so reopening it shows the same progress rather than starting over. Each note is also fingerprinted by its exact text, so an edited note gets a fresh analysis instead of the result for the earlier wording.

Since then (April 2026): streaming moved into the workflow engine itself.

What the adverse event report PDF contains

The adverse event report PDF has a new AE log template, laid out as a participant-level record for monitoring visits:

• One row per adverse event: the CTCAE term, the verbatim text from the note, the grade, onset and resolution, whether the event is serious, relatedness, whether it was expected, the action taken (such as the drug held or discontinued), the date each report went to the sponsor, IRB and FDA, and a column for the investigator.
• A CTCAE grade quick reference, so a reader can check a grade against its definition on the page.
• A reporting matrix showing which kinds of event typically go to which report: FDA MedWatch, the IRB unanticipated problem report, the sponsor serious adverse event report and the AE log itself, with the regulatory references (21 CFR 312 and ICH E6).
• Signature lines for the investigator.

The encounter summary report also marks each event with a regulatory flag, from "AE log only" to all four reports, and stays pending until a clinician attests to it. An unsigned summary starts no reporting clock. The week after, report generation for FDA MedWatch, IRB and sponsor serious adverse event reports followed; what Burna AI does today lists the current reports.

Smaller fixes that shipped the same week

• CTCAE term search renders its results correctly again, after the app and the lookup it calls were brought back into agreement on the shape of a result.
• Sign-in codes stay valid for 15 minutes instead of 10.
• Patient MRN. The patient creation form requires an MRN, it saves with the record, and patient search matches on it.
• Reports view. Clearer headings and layout on the reports tab.
• Sign-in origins. The list of web and app addresses allowed to sign in now lives in one shared configuration read by both API services, instead of three separate copies.

Since then (July 2026): the provider web app these features shipped in was retired; the platform is app.burna.ai.

To see grading, attribution and the AE report PDF on your own encounters, book a 15-minute conversation.