Quick Answer: Daniel Jernigan, a longtime public health leader and new contributing scholar at the Johns Hopkins Bloomberg School of Public Health, was elected to the National Academy of Medicine in November 2026. He's best known for helping build the electronic lab reporting standard that still sends laboratory results to public health agencies. His current work focuses on helping health departments handle the flood of data produced by pathogen-agnostic genomic sequencing.
When the National Academy of Medicine announces new members, the list usually reads like a résumé of institutional power. Jernigan's story is different. The honour recognizes a career spent on something most people never see: the plumbing that tells public health agencies what's circulating in their communities. As The Johns Hopkins News-Letter reported, seven Hopkins faculty members received the honour this year, and Jernigan is among them. His election is worth a closer look, because the problems he's solving are the ones that decide how fast your local health department can respond to an outbreak.
Who Daniel Jernigan Is and Why the Academy Noticed
Jernigan recently joined the Bloomberg School's Center for Health Security and the Center for Outbreak Response Innovation as a contributing scholar. Before that, he spent more than a decade in roles at the Centers for Disease Control and Prevention and the Washington State Department of Health. Those roles included directorships and large data modernization projects. He also served as an incident manager during the 2014 Ebola response.
The National Academy of Medicine cited his work on data management for disease monitoring as a major achievement. That's a useful signal for anyone trying to understand the field. Outbreak response depends less on dramatic science than on whether a lab result reaches the right person before the window for action closes. Jernigan's career has been about shrinking that window.
From Fax Machines to Automated Reporting
To see why his early work matters, start with the problem he inherited. In 1995, penicillin-resistant Streptococcus pneumoniae, which public health staff called DRSP, emerged as an antimicrobial-resistant pathogen. That prompted a decision to start national surveillance. The tools available were grim. As Jernigan recalled, surveillance depended on paper forms that were filled out and faxed in, a process he described as "just awful and slow and burdensome."
His team took a different approach. Instead of asking clinicians to report by hand, they connected laboratory information management systems directly to public health reporting. At the time, that was a novel idea. They worked with Health Level Seven (HL7), an international standards development organization, to define how the data would be structured. They then built a working implementation with what is now Quest Diagnostics, so reportable laboratory findings could flow automatically. The system was tested during the 1996 Summer Olympics in Atlanta, where officials needed real-time visibility into disease activity.
Here's the part most histories skip. That standard is still in use. Electronic laboratory reporting is what lets agencies track reportable diseases like salmonella and generate the case counts that drive a response. The same approach was later applied to processing death data more efficiently. A reform that began as a fix for paper bottlenecks became basic infrastructure.
Why Automation Beats Manual Reporting Every Time
The common assumption is that the main barrier to better surveillance is getting more people to report. Jernigan's experience points somewhere else. The bottleneck is usually the handoff between systems. When a lab result has to be transcribed, faxed, or re-keyed, delay and error creep in at every step. When the lab system speaks the same standard as the public health system, the report is generated as a byproduct of the testing itself.
That's the counter-intuitive lesson: the most effective surveillance improvement often isn't a new test or a new analytic model. It's removing a human step from the middle of the workflow. Standards like HL7 make that possible because they define the shared language that lets two systems exchange data without someone translating in between.
There's a real caveat, though. Automation only works when labs, vendors, and health departments agree on the standard and keep their implementations current. A reporting feed that silently breaks can look fine on a dashboard while missing cases for weeks. Any surveillance system needs routine checks that confirm the data still arrives complete.
Pathogen-Agnostic Sequencing and the Data Problem
Jernigan's current focus at Hopkins builds on this foundation. Traditional diagnostics are targeted. As he explained, if you want to know whether a specimen contains salmonella, you run a test designed to find salmonella DNA. The answer is yes or no for the organism you chose to look for.
Pathogen-agnostic genomic sequencing changes that logic. You prepare the specimen and ask a broader question: what's in this? The sequencing output reports the genetic material present, without requiring you to know beforehand what you're looking for. That matters for emerging threats. Jernigan pointed to its potential for screening everything from new Ebola variants to monkeypox, and for surveillance systems that need to catch surprises.
Here's where the trade-off shows up. Targeted tests produce a small, interpretable answer. Agnostic sequencing produces an enormous amount of data, most of it irrelevant to any given decision. Jernigan describes the result as "like a fire hose being directed at them." The advance in detection creates a new bottleneck: interpretation.
| Surveillance approach | What it produces | Main constraint |
|---|---|---|
| Paper forms, faxed reports (1990s practice) | Delayed, manually transcribed case reports | Speed and transcription errors |
| Electronic lab reporting via HL7 standards | Automated reports for reportable diseases | Standards alignment and feed reliability |
| Targeted molecular testing | Yes/no results for specific pathogens | Only detects what you already suspect |
| Pathogen-agnostic genomic sequencing | Broad readout of all detectable genetic material | Volume and interpretation of results |
Meta Bridge and the Translation Gap
This is where Jernigan's work at Hopkins becomes practical. The project he describes as Meta Bridge aims to connect highly technical sequencing outputs to the decisions public health staff actually make. As he put it, the goal is "bridging the highly technical to the actions that public health can do with that information."
That framing matters. A state epidemiologist doesn't need to read raw sequence reads. They need to know whether a signal is new, whether it's clinically relevant, and what action it justifies. The gap is translation, not detection. Closing it requires people who understand both the laboratory and the response side, which is exactly the combination Jernigan has built his career around.
Most guides on genomic surveillance focus on the sequencing technology. That's the easier half. Here's what most people stop short of asking: who does the interpretation when the data arrives faster than the staff can review it? Without a clear answer, more sensitive detection can make outbreak response slower, not faster.
Trust, Evidence, and the Limits of Institutional Advice
Jernigan's acceptance remarks went beyond technical work. He described a shift in how much trust people place in established institutions, including the CDC, and argued for decisions grounded in evidence. He pointed to the University of Minnesota's CIDRAP, which he said is now doing evidence evaluation for vaccine recommendations, a role he implied had previously sat with the CDC.
He also made specific claims about capacity. He cited a 30% drop in CDC staff and what he called "crazy budget changes," which he argued are making it hard for the Department of Health and Human Services to respond as needed. He said he has written about the concern in multiple opinion pieces and believes the country is in worse shape to handle a major outbreak than it was before the COVID-19 pandemic.
These are Jernigan's own assessments, and they deserve to be read as such. Staffing figures and budget decisions are contested, and different analysts weigh them differently. Evidence-review arrangements can also be complementary rather than substitutes for federal guidance. The useful takeaway isn't a verdict on any one agency. It's that surveillance capacity depends on staff, funding, data standards, and the trust that lets officials act on what they find.
Why does this matter to you? Because the systems Jernigan describes are the ones that decide whether a local health department hears about a cluster of infections in days or in weeks. Those are the systems worth watching, even when they never make headlines.
Frequently Asked Questions
Who is Daniel Jernigan?
Daniel B. Jernigan is a public health leader who recently joined the Johns Hopkins Bloomberg School of Public Health as a contributing scholar. He previously held directorial roles at the CDC and the Washington State Department of Health and served as an incident manager in the 2014 Ebola response. He was elected to the National Academy of Medicine in 2026.
What is the National Academy of Medicine?
The National Academy of Medicine is a U.S.-based organization that brings together experts to advise on health and medical issues. Membership is elected each year and is considered a major professional honour. Its advice informs policy on health topics, both nationally and internationally.
How does electronic lab reporting reach public health agencies?
Electronic lab reporting connects a laboratory's information system directly to public health reporting systems. Standards such as HL7 define how results are structured, so reportable findings can be sent automatically rather than faxed or transcribed. This speeds up case detection and reduces errors.
How can health departments handle the data from genomic sequencing?
Health departments need a process that translates raw sequencing output into specific public health actions. That means defining which signals matter, who reviews them, and what response each one triggers. Jernigan's Meta Bridge project is one approach to bridging technical results and operational decisions.
Closing Thoughts
Daniel Jernigan's election recognizes a career built on making public health data move faster and mean more. The most useful lesson is that detection is only half the job; the other half is turning results into decisions before the window closes. If you work with surveillance data, try auditing one reporting feed this week: check how long a result takes to reach your team, and where a person has to retype it. Share this with someone who manages a lab or health data system and is wrestling with the same bottleneck.