The tools public health workers rely on every day

Public health institute employees use a mix of standard office software, specialized disease tracking systems, and data analysis tools that most people outside the field have never heard of. The specific software depends on the job — an epidemiologist analyzing disease patterns uses different tools than a communications officer writing health alerts — but nearly all public health workers touch at least one government-mandated system during their day.

Understanding what these tools do helps explain why public health responses take the shape they do, why certain data gets collected the way it does, and what kinds of delays or bottlenecks can happen when systems don't talk to each other.

Key Takeaways

  • Disease reporting happens through state-mandated systems like the National Electronic Disease Surveillance System (NEDSS), not through a single national database.
  • Most public health offices use standard Microsoft Office software alongside specialized epidemiology and mapping tools like ArcGIS and Epi Info.
  • Electronic lab reporting systems connect hospitals and testing facilities directly to health departments, though the speed and completeness varies by state.
  • Data analysis and visualization tools like R, Python, and Tableau let epidemiologists spot outbreaks and track disease trends, but require staff training to use well.
  • Many public health offices still use older systems that don't integrate smoothly with newer ones, creating manual data entry work and delays.

Disease surveillance and reporting systems

The backbone of public health work is disease tracking. When a doctor diagnoses a reportable disease — measles, tuberculosis, foodborne illness — that information flows into a state surveillance system. Most states use NEDSS (National Electronic Disease Surveillance System), a web-based platform that collects case reports, tracks demographics, and flags outbreaks. NEDSS is not a single national database; each state runs its own version, and data flows to the Centers for Disease Control and Prevention (CDC) on a schedule, not in real time.

Some states have built their own systems on top of NEDSS or replaced it entirely. California uses CalREDIE (California Reportable Disease Information Exchange), and New York uses ECLRS (Electronic Clinical Laboratory Reporting System). These state systems often have different interfaces, different data fields, and different reporting timelines, which is why a disease case that takes two weeks to report in one state might take four weeks in another. Electronic lab reporting (ELR) systems automate some of this work by sending positive test results directly from hospitals and labs to the health department. When it works, a positive COVID-19 test appears in the surveillance system within hours. When it doesn't — because a lab uses an older system, or the connection drops, or the data format doesn't match — staff have to enter the result by hand.

Mapping and geographic analysis tools

ArcGIS, made by Esri, is the standard mapping software in public health. Epidemiologists use it to plot disease cases on a map, identify geographic clusters, and visualize which neighborhoods have the highest rates of a disease. ArcGIS can layer multiple data sources — case locations, population density, income levels, hospital locations — to help identify patterns that raw numbers alone might miss.

Many public health offices also use Google Earth and Google Maps for simpler geographic questions: where are the nearest clinics to a case, what's the travel time between locations, or how many people live in a particular area. These tools are free and require less training than ArcGIS, but they can't handle the statistical analysis that epidemiologists need for outbreak investigation. The choice between tools often comes down to budget and staff expertise rather than which tool is technically best.

Data analysis and statistics software

Once data is collected, epidemiologists analyze it to understand trends and test hypotheses. Epi Info, a free tool made by the CDC, is designed specifically for outbreak investigation. It lets epidemiologists create questionnaires, enter case data, and run statistical tests to identify what people with the disease have in common — what they ate, where they traveled, who they contacted.

R and Python are programming languages that many public health agencies use for more complex analysis. They're free and powerful, but they require staff who know how to code. Smaller or under-resourced health departments often can't afford to hire data scientists, so they rely on Epi Info or simpler tools like Excel and SPSS (a statistical software package that costs money but is easier to learn than R). Tableau and Power BI are data visualization tools that turn numbers into dashboards and charts. During the COVID-19 pandemic, many health departments used these tools to create public-facing dashboards showing case counts, hospitalizations, and vaccination rates. These tools can connect directly to surveillance databases and update automatically, or they can be fed data manually on a schedule.

Office and communication software

Public health workers spend significant time in Microsoft Office — Word for reports, Excel for data management and simple analysis, PowerPoint for presentations to elected officials and the public. Many health departments also use Outlook for email and calendar management, and SharePoint or OneDrive for file sharing and document collaboration.

For internal communication, some agencies use Slack or Microsoft Teams, especially for rapid coordination during outbreaks. Email remains the official record for most health departments, though, because it's easier to archive and retrieve for legal and regulatory purposes. Public health communications staff use Canva or Adobe Creative Suite to design health alerts, social media graphics, and educational materials. Larger agencies might have dedicated graphic designers; smaller ones often rely on templates and free tools.

Contact tracing and case management platforms

During disease outbreaks, staff need to track who has been exposed to a case and follow up to see if they develop symptoms. Salesforce is a customer relationship management (CRM) tool that many health departments adapted for contact tracing during COVID-19. It lets staff log calls, track follow-up dates, and see the status of each contact at a glance.

Some states built their own contact tracing systems or used specialized platforms like Tele-Epidemiology or Salesforce Health Cloud. Others used simpler tools like Google Forms and Google Sheets to collect information and track contacts manually. The variation in tools meant that contact tracing speed and completeness looked very different from state to state during the pandemic. A health department with an integrated system could reach contacts within hours; one using paper and phone calls might take days.

Laboratory information systems

Public health labs use Laboratory Information Management Systems (LIMS) to track samples, manage test results, and ensure quality control. These are specialized systems, often custom-built or heavily modified for each lab's workflow. Common platforms include Sunquest, LabWare, and Cerner LIS. These systems connect to the electronic lab reporting systems that send results to surveillance databases, though the connection is often manual or batch-based rather than real-time.

The quality of lab data depends heavily on how well the LIMS is set up and maintained. A lab that hasn't updated its system in years might still be exporting results as PDF files that someone has to manually type into the surveillance system. A newer lab might have automated the entire process, but only if someone invested the time and money to build the integration.

Challenges when systems don't work together

The biggest operational problem in public health is that these tools don't integrate smoothly. A case report might start in a hospital's electronic health record (EHR), move to an electronic lab reporting system, land in a state surveillance database, and then need to be manually entered into a contact tracing platform. Each handoff is a chance for data to be lost, delayed, or entered incorrectly.

Older health departments might still use systems from the 1990s that can only export data as a PDF or a printed report. Newer departments might have built integrations between their surveillance system and their mapping tool, but those integrations break when either system updates. Staff often spend more time moving data between systems than analyzing it. Funding for public health IT is limited and fragmented. Federal grants might pay for a new surveillance system but not for training staff to use it, or for the IT support needed to keep it running. This is why some public health offices have cutting-edge tools sitting unused while staff continue to work in Excel.

Frequently Asked Questions

Can the public see what software public health departments use?

Some of it, yes. Health departments publish dashboards and maps built with Tableau or ArcGIS, and those are public-facing. The underlying surveillance databases and case management systems are not public — they contain personal health information and are protected by privacy laws. You can request aggregate data (total cases by age group, for example) through public records requests, but you can't see individual case records.

Why did contact tracing during COVID-19 seem so slow in some places?

Many health departments had to build contact tracing systems from scratch in a matter of weeks. Some used tools they already had (like Salesforce), some used free tools (like Google Forms), and some hired contractors to build custom systems. The tools themselves weren't the only bottleneck — staffing, training, and unclear protocols also caused delays — but a health department using paper and phone calls will always be slower than one using an integrated digital system.

Do all states use the same disease surveillance system?

No. All states use NEDSS or a NEDSS-compatible system, but many have customized it heavily or built their own system on top of it. This means a case report that takes two weeks to reach the CDC in one state might take four weeks in another, and the data fields collected might differ slightly. The CDC works to standardize this, but state autonomy and limited funding mean variation persists.

What happens if a public health worker doesn't know how to use the software?

Training is inconsistent. Some agencies have dedicated IT staff who train new employees; others expect people to figure it out on their own or learn from colleagues. During the COVID-19 pandemic, many health departments hired temporary staff with no public health background and minimal training on surveillance systems, which contributed to data quality problems and reporting delays.