May 4, 2026
BioWatch Brief: Rapid Pathogen Risk Assessment via Staged LLM Triage
David Nai, Kevin Fickert, Jessica Anderson
Biosecurity analysts face a growing asymmetry: outbreak reporting volume has expanded substantially while the number of trained personnel able to synthesise that information in real time has not. BioWatch Brief compresses the analyst intake stage from hours to minutes via a three-stage LLM pipeline (structured extraction, retrieval against a curated corpus of historical outbreaks and biosecurity policy frameworks, and grounded analysis), producing a structured risk card from arbitrary input reports. The architecture deliberately separates fact extraction from retrieval and synthesis, constraining LLM outputs at each stage and surfacing uncertainty rather than masking it. Built on gpt-4.1-mini with a curated 21-entry open corpus (16 historical outbreaks, 5 policy/framework documents) normalised across pathogen, location, transmission, response history, lessons learned, and source URLs. React frontend, FastAPI backend, single /analyze_report endpoint. Built at the Apart AIxBio Hackathon, April 2026 (University of Pennsylvania).
The problem framing in your introduction is strong, the asymmetry between outbreak reports and analyst capacity is a real chokepoint. The architectural argument in your discussion, that structural fidelity has to be enforced rather than prompted for, is a good contribution worth exploring and developing further. I could see a lot of value in a tool like this existing.
The idea is sound, but the current implementation does have limitations. To your credit you identify and flag many of them in the limitations section. The RAG search is tied to key words, and the current corpus is small, so it limits the usefulness but does work for a demonstration for a hackathon. However, the full results are not provided anywhere and only one example is given.
Tying one of the categories to geography could be limiting as well. While some viral and bacterial families which can cause a PHEIC are geographically limited, others are not, influenza immediately springs to mind. Geographic anchoring also somewhat limits the effectiveness for bioweapons or engineered pandemics which could cause GCBRs and could, by design, be first unleashed anywhere. One could consider keeping the fields but weighing them differently in the scoring in some manner.
The scenario library described in the reports is author and crafted to match exactly what the tool needs, was used during development, and had no held-out set. Section 4 then reflects expected behavior on constructed examples, rather than evidence the system works on inputs it hasn't seen or might be messier. The line that uncertainty flags "correlated with the cases where ground-truth assessment was itself ambiguous to the human authors" is somewhat confusing, and essentially the authors agreeing with themselves.
The planning notes /doc on GitHub suggested running 10–15 archived ProMED alerts with documented outcomes as an eval. That would have been great and would have given you real evidence for the report. Even a smaller number, like five archived alerts with retrospective WHO classifications, would substantially strengthen this section and serve as stronger proof BioWatch Brief is behaving and functioning as intended.
The linked codebase is somewhat hard to follow compared to the submitted final write up. It looks like there are two distinct pipelines in it? Pipeline.py and main.py?
The first has the FastAPI backend using OpenAI's gpt-4.1-mini and seemss to match the staged pipeline described in your Methods section. It also has the keyword-scored retrieval over the fixed corpus and the grounded synthesis. The two LLM round trips. It is also named "main." I judged only on this one, as it seems to be the submission.
The second is using the Anthropic SDK and Claude Opus 4.5 with tool use and the output is quite different, but has no RAG/keyword based corpus retrieval. I am not scoring on this pipeline, as the paper seems to indicate the first, but the outputs here seem richer and more informative. So just a flag it could be good to build towards this more in-depth and informative outputs in the submitted, RAG + corpus grounded tool.
You also have code for a live signal assessment in the first / main pipeline but that does not seem to be implemented in any way with a way to get live signal, though the planning document has some ideas in it. Not judging on that, just flagging this is a good area to expand and work on if you continue with this tool.
A minor quibble but the write-up likely used some resources that are not cited. The mention of BlueDot and Metabiota sent me googling as I was curious if said BlueDot was related to BlueDot impact at all, and the first result in this paper https://pmc.ncbi.nlm.nih.gov/articles/PMC7378493/. Feel like this should have been cited in the report, which then makes me wonder if there are other missing citations. I am not saying there are, just it raises the spectre of it. You do also disclose the use of of LLMs for brainstorming, but the planning MD appears to be generated by Claude / Claude Code and I am sure it was after a lot of back and forth with user(s) but it is more a design spec than just a brainstorming doc. Which I think is fine, that's the way things work now, but maybe could have been disclosed differently. This is such a new area it is hard to say, so not scoring against this at all, just mentioning it.
Cite this work
@misc {
title={
(HckPrj) BioWatch Brief: Rapid Pathogen Risk Assessment via Staged LLM Triage
},
author={
David Nai, Kevin Fickert, Jessica Anderson
},
date={
5/4/26
},
organization={Apart Research},
note={Research submission to the research sprint hosted by Apart.},
howpublished={https://apartresearch.com}
}


