Skip to content

From One Safety Reporting Cycle to the Next

At World Patient Safety Congress Americas 2026, AlphaLife Sciences explored how teams can draft, review, and update periodic safety reports across cycles.

World Patient Safety Congress Americas 2026, October 13–15, Boston

Every reporting period brings new evidence and a familiar task for pharmacovigilance teams. Which parts of the previous safety report can carry forward, and which need a fresh assessment? That question framed our work at World Patient Safety Congress Americas, held October 13–15 in Boston. At Booth 221 and in the October 15 Next Gen Tech & Data session, AlphaLife Sciences focused on how AI could support the preparation and review of periodic safety reports. Explore our congress program.

Match the drafting method to the evidence

Cieayrra Boozer, our Product Specialist Lead, presented an AuroraPrime RMA workflow for the Periodic Benefit-Risk Evaluation Report (PBRER) and Development Safety Update Report (DSUR). Both reports bring together sections that call for different kinds of evidence. A narrative section can draw on approved reports and writing guidance. A summary tabulation needs confirmed data. Assessing signals and interpreting the benefit-risk profile require the safety team’s judgment.

Consider a report section that describes cases received during the reporting period. The author can identify the approved tabulation and verify the product scope and data cutoff before drafting the narrative. A reviewer can then check that the wording reflects the same scope as the table. If a medical interpretation is still pending, that question can remain visible for the safety team to resolve during review.

The workflow used section-specific sources and showed how an author can inspect the evidence behind generated text. It also covered how reviewer comments can guide proposed revisions in Microsoft Word, where authors can compare changes before deciding which edits to accept.

Make the reason for a revision visible

A reviewer’s request to clarify a sentence may be straightforward, while a comment that questions the underlying evidence requires a different response. If one reviewer asks for a stronger statement and another questions whether the cases support it, the author can bring both comments back to the relevant material. The safety team can agree on the interpretation, and the writer can check that the proposed edit reflects that decision before accepting it in Word.

The tracked edit gives the next reviewer a concrete change to assess. Recording why the sentence changed also helps the team distinguish an editorial correction from a revised scientific assessment when it returns to the report later.

Give the next report a reliable starting point

The next reporting cycle can begin with the previous approved report. Authors can set the new reporting period, compare revised passages with the prior version, and check which language still reflects the evidence. If the DSUR and PBRER share content, authors can assess what carries over and where the two reports need different treatment.

One way to test the handoff is to take a single approved section into the next cycle. Identify what depends on the new reporting period, which sources replace the previous ones, and which background statements remain accurate. Then have a reviewer confirm the updates against the new material and record any items that still need medical review. That exercise gives the team a practical way to assess how much of the prior work it can reuse with confidence.

Thank you to the pharmacovigilance community for joining us in Boston. Explore AuroraPrime RMA for safety reporting.

Close