Highlights
Industries: Academic Research, Environmental Monitoring · Use case: Air and wastewater pathogen surveillance · Product: LabKey SDMS
- 126 air sampling sites in operation, from Madison to Zambia, Brazil, Taiwan and Nepal
- Pipeline results written directly into LabKey SDMS, with no manual transfer step
- Public dashboards covering almost 100 viruses across 12+ cities
- Role-based access, so each partner sees only its own data
Contents: Background | Journey | Challenges | Why LabKey | Results | Conclusion
Background
The David H. O’Connor Lab at the University of Wisconsin-Madison, part of the Global Infectious Disease Laboratories, has a long history of research in virus genomics and primate immunogenomics. Since the COVID-19 pandemic, the lab shifted first into genomic surveillance of viruses and then into broad environmental pathogen monitoring. Today the Lungfish environmental monitoring project samples air and wastewater, with 126 air sampling sites as close as the Madison community and as distant as Zambia, Brazil, Taiwan and Nepal.
The Journey
The David H. O’Connor lab at UW-Madison and LabKey have worked together since 2009, across a long list of projects such as primate research. LabKey provided the platform for the lab’s Zika portals, where data was shared publicly in real time, and later for its SARS-CoV-2 Open Research Portal. Services and ongoing support have been part of the relationship throughout.
The lab’s respiratory virus monitoring began during the pandemic, and today it is part of Lungfish, an open research collaborative that states its mission as “… we turn signals from air and water into shared knowledge that supports earlier awareness of emerging threats and better preparedness.”
Academic, industry, public health and community partners, including the University of Wisconsin-Madison and the University of Missouri, work together to monitor pathogens in air and wastewater. The lab built the program on LabKey SDMS from the start, using one system that today holds the metadata, sample data and bioinformatic results for a program that keeps growing.
Lungfish is the latest project in a long-term partnership, and the lab’s use of LabKey has grown with each one.
Challenges
Many inputs, one record: Data reaches Lungfish from partner-site volunteers using data collection apps, from lab staff updating site and sample metadata, and from bioinformatics pipelines. All of it has to land in one trustworthy place.
Pipeline output at sequencing scale: Deep, untargeted metagenomic sequencing of wastewater and air samples requires large compute on a high-performance computing (HPC) cluster or in the cloud. Results from those pipelines have to reach the tracking system without a person carrying them over.
Partner-specific access: Partner sites, including schools and clinics, should see their own data and nobody else’s, ideally through a dashboard built for their site.
Varied data sharing rules: Sites sit in different states and countries, each with its own sharing requirements. The team treats respect for those rules as its first priority.
Public-facing data with a short turnaround: Stakeholders such as school nurses need current results presented clearly, and the lab wants to cut the time between sample and answer.
Why LabKey
After partnering with LabKey for many years, the team knew exactly how to set up SDMS to meet the needs of this project:
Direct pipeline-to-system data flow: The LabKey Python and JavaScript software development kits (SDKs) removed the manual step between compute and tracking. Pipelines on the HPC cluster or in the cloud write results straight into the system, and no one has to mediate transfers. When Python needs data back, a SQL query returns it, ready to load into a data frame for further transformation and visualization.
A backend that dashboards can read: Scheduled extract, transform, load (ETL) jobs prepare the data inside LabKey, so public dashboards receive it ready to present. The dashboards use the JavaScript SDK to pull what they need at the moment they need it, then apply final transformations before generating a heat map or other display.
“Ultimately LabKey’s role here is as a web backend to supply data that is then ready for presentation on public dashboards.”– Nick Minor, O’Connor Labs at University of Wisconsin-Madison
Room to extend: For outputs that go beyond the built-in transformation tools, the team renders HTML dashboards and reports with third-party compute and inserts them back into LabKey.
Role-based access control for partners: Because those dashboards and reports live in LabKey, permissions control who sees what. Each partner reaches only its own data, along with a custom dashboard for its site.
One system for metadata, results and views: Site and sample metadata, ingested pipeline results and cached transformations live in the same place. Data collection apps built for partner sites insert directly into LabKey lists, and lab staff keep metadata current with bulk and individual row inserts. That gives the team a consistent operating model for building each new dashboard.
Automation that supports faster turnaround: Automation tools in LabKey SDMS are a direct help in reducing turnaround time and improving data presentation.
Results
A weekly workflow that largely runs on its own: Much of the web of pipelines, uploads and transformations runs without manual steps. Sequencing data returns from the partner sequencing core by the time the team starts their work week, and the team’s Monday work is reviewing results in LabKey: what showed up where, and whether anything calls for a conversation with public health.
Steady growth in sample volume: This operating model has played a big role in the team’s ability to keep scaling the number of samples it handles month by month. The team continues to expand to more air sampling and wastewater sites on the same SDMS foundation.
Public dashboards drawn from the same data: A prototype city wastewater dashboard shows levels of almost 100 viruses across 12 cities. A separate dashboard for Dane County, Wisconsin schools draws on the lab’s in-house 20-pathogen respiratory PCR panel, which returns results faster than metagenomic sequencing. Each week the team also generates a custom PDF report card for each school, which families access through the LabKey SDMS setup.
Fast answers to questions the data was not built for: When the 2026 cyclospora outbreak began in North America, the team realized its untargeted data could answer questions about a parasite that is not a typical target. They mined the existing data for a longitudinal view across the past two summers, to judge whether this summer was remarkable. A preprint on that work is under review.
Conclusion
For the O’Connor lab, LabKey SDMS is the operational foundation for a surveillance program that has grown from a local effort into 126 sites across several countries. The team has more in progress: automated site onboarding with welcome kits for new partners, shorter turnaround, and workflows that combine computational and laboratory steps for rapid response to emerging pathogens. A person still checks with partners and public health departments whenever something concerning appears, so that each partner can decide whether to share results.
“If you’re already using LabKey, these tools are already at your fingertips, and I’d encourage you to take a look.”– Nick Minor, O’Connor Labs at University of Wisconsin-Madison
Hear it firsthand from UW-Madison’s Lungfish presentation at the 2026 SDMS User Conference.