State health departments
Agencies that run the statewide registries and receive feeds from every provider in the state.
- Immunization registry services
- Electronic lab and case report intake
- Data sharing with local departments
Government and Research / Public Health
Public health software for health departments and NGOs
Reports arrive from hundreds of providers in different message formats, case investigators work from spreadsheets, and grant reports are rebuilt by hand each quarter. Agnotic Technologies builds public health software for state and local health departments and health NGOs that receives provider feeds, runs case follow-up and keeps program records ready for funders.
Feeds
Immunization, lab and case reports
Cases
Investigation and follow-up
Grants
Program records kept for funders
Trusted by global innovators
Industry Overview
What is public health software?
Public health software is the set of systems a health department or health NGO uses to receive immunization, laboratory, syndromic and electronic case reports from providers, investigate cases and follow up contacts, run programs and outreach, and report to funders. Agnotic Technologies builds these systems for government and NGO health programs around the standards providers already send.
Who it is for
Who do we build public health systems for?
Each organization receives, acts on and reports data differently. We start from your programs and your funders.
Local and county health departments
Teams that investigate cases, follow up contacts and run clinics and outreach.
- Case investigation queues
- Contact follow-up and outreach
- Clinic and program records
Health NGOs and community organizations
Grant-funded programs that serve people directly and report to funders and agencies.
- Participant and service records
- Grant metrics and reports
- Referrals to and from agencies
Industry Challenges
Where do public health data systems fall behind?
The gaps we look for first, because each one delays a case or a report.
The same person appears under three records because immunization, lab and case feeds each create their own.
Lab messages fail validation and sit in an error queue that nobody watches, so the sender never hears about it.
Electronic case reports arrive but are not linked to the matching lab result or the open investigation.
Investigators copy data from the surveillance system into spreadsheets to work their caseload.
Grant metrics are rebuilt by hand each quarter from exports that do not match each other.
Disclosures and data sharing with partners are not logged, so the agency cannot show who received what.
Surveillance flow
How does surveillance data reach CDC and flag an outbreak?
In electronic disease surveillance, a case reaches CDC once the agency confirms it against the surveillance case definition, maps it to the condition's NNDSS message mapping guide and sends an HL7 v2 case notification. Agnotic Technologies builds that path plus aberration alerts that compare counts with what is expected and send them to an epidemiologist.
| Step | What the agency system does | Who checks it |
|---|---|---|
| 1. Classify the case | Applies the surveillance case definition for the condition and records the case as confirmed, probable or suspect, with the evidence behind it | The investigator or epidemiologist who owns the condition |
| 2. Map to the message mapping guide | Maps case fields to the generic and condition-specific data elements in the NNDSS message mapping guide for that condition, and flags required fields still empty | The informatics team, before the condition goes live |
| 3. Send the case notification | Builds the HL7 v2 case notification from the mapped fields and sends it on the agency's schedule, including updates when the case changes | The system, with each message and its version logged |
| 4. Track the acknowledgment | Records CDC's response, queues rejected messages with the reason and resends after correction | An informatics analyst who works the error queue |
| 5. Compare counts with expected | Counts cases by condition, area and week and compares them with an expected range built from past periods | The system, using the method your epidemiologists approve |
| 6. Review the alert | Sends counts above the expected range to an epidemiologist with the case list behind them; nothing is published or shared automatically | An epidemiologist, who decides whether an outbreak investigation starts |
Our Approach
How should an agency approach a public health build?
Three decisions we make with your epidemiology, informatics and program leads.
Keep one person index across every feed
Immunization, lab, syndromic and case reports all match to one person record, with the match rules and their results visible to staff.
Validate at the door and tell the sender
Messages are checked on arrival, and failures go back to the sending provider with a reason instead of waiting in a queue.
Link every case to its source reports
An investigation opens from the report that triggered it and keeps every later report attached, so the case history is complete.
Capabilities
What do we build into public health software?
Modules for health departments and NGOs, alone or as one platform.
Message intake and validation
HL7 v2 and FHIR intake with validation, acknowledgements and feedback to senders.
Person matching
One person record across feeds, with review queues for uncertain matches.
Immunization registry services
Dose records, deduplication and query responses with history and forecast.
Lab and syndromic processing
Reportable result rules and syndromic feeds passed to surveillance analytics.
Electronic case report intake
eICR and reportability response handling, linked to the person and the case.
Case investigation
Queues, forms and tasks for investigators, opened from the triggering report.
Contact follow-up and outreach
Contact lists, follow-up schedules and messages in the languages your community uses.
Program and grant reporting
Program metrics from source records, with exports for each funder.
How It Works
How does a report become a closed case?
The path we build for one report, from the provider's message to the closed investigation.
Receive
The message arrives from a provider, lab or health information exchange.
01
1
Validate and acknowledge
Structure and coding are checked, and the sender gets an acknowledgement or a reason for rejection.
02
2
Match the person
The report is matched to an existing person record or creates a new one for review.
03
3
Apply condition rules
Reportable condition rules decide whether the report opens or updates a case.
04
4
Investigate
The case goes to an investigator's queue with the source reports attached.
05
5
Follow up contacts
Contacts are listed, reached and tracked through their follow-up period.
06
6
Close and report
The case closes with its outcome, and counts flow to surveillance and program reports.
07
7
Engineering Stack
Systems and standards behind public health software
Chosen to fit the feeds you receive and the systems you already run. We build in your cloud account or data center.
Standards
HL7 v2.5.1 messagesHL7 FHIR R4 and the eCR implementation guideHL7 CDA for eICR and reportability responseLOINC and SNOMED CT coding
Data
Person index with match rulesCase and investigation modelProgram and grant recordsDisclosure log
Integration
Health information exchangesPublic health laboratory systemsVital recordsGIS for case mapping
Security
Role-based access by programAudit loggingEncryption in transit and at restSSO with your identity provider
Feed table
Which provider feeds does the agency system receive?
Each public health data stream, the standard providers send it in, the ONC criterion their certified health IT meets and what the agency system must do on receipt.
| Data stream | Standard and message | Provider-side ONC criterion | What the agency system must do |
|---|---|---|---|
| Immunization | HL7 v2.5.1 immunization messages under the Immunization Messaging guide, Release 1.5 | 45 CFR 170.315(f)(1) | Accept dose messages, deduplicate, and answer queries with history and forecast |
| Syndromic surveillance | HL7 v2.5.1 under the PHIN Messaging Guide for Syndromic Surveillance | 45 CFR 170.315(f)(2) | Ingest visit feeds and pass them to surveillance analytics |
| Electronic lab reporting | HL7 v2.5.1 under the Electronic Laboratory Reporting to Public Health guide | 45 CFR 170.315(f)(3) | Validate coding, match the person and open or update a case when reportable |
| Electronic case reporting | eICR in HL7 FHIR eCR or HL7 CDA, with the reportability response | 45 CFR 170.315(f)(5) | Receive the eICR and response, link them to the person and case, and route by jurisdiction |
Measured Impact
What should a health department be able to see?
Views we build with your epidemiology and program teams.
Feed health
Messages by sender
Messages received, rejected and corrected for each provider.
Timeliness
Report to investigation
Time from report arrival to the first investigator action.
Caseload
Open investigations
Cases by condition, investigator and stage.
Program
Grant measures
Program measures from source records, ready for each funder.
Use Cases
Where do agencies and NGOs start?
First releases we scope, each small enough to ship and check.
01
Lab report intake and feedback
Validation and sender feedback for electronic lab reports.
02
Case investigation workspace
Investigator queues opened from incoming reports.
03
Immunization registry upgrade
Dose deduplication and query responses on current standards.
04
eCR linkage
Electronic case reports linked to persons, labs and cases.
05
NGO program records
Participant, service and referral records with funder reports.
06
Outreach campaigns
Reminder and follow-up messages for clinics and programs.
Integrations
Which systems does public health software connect to?
The systems a public health platform reads from or writes to, agreed during scoping.
Incoming reports
Provider EHRs and health information exchanges
Lab results
Public health laboratory system
Registry
Immunization information system
Epidemiology
Surveillance analytics
Births and deaths
Vital records
Funder reporting
Grants management
Outreach
Messaging providers
Compliance-First Development Services Backed by Global Standards
We build secure, scalable products designed for privacy, interoperability, and regulatory readiness from day one across every sector we serve.
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, and strict access controls.
Fast Healthcare Interoperability Resources
Enabling standardized health data exchange through standards-based API mappings.
Health Level Seven International
Supporting enterprise-grade interoperability for clinical messaging and record workflows.
Our Edge
Why Global Leaders Choose Us
We combine deep technical expertise with industry-specific knowledge to deliver solutions that aren't just functional, but transformational.
Enterprise-Grade Security
We implement rigorous security protocols and compliance standards (HIPAA, GDPR, SOC2) across all industrial solutions to protect sensitive data.
High-Performance Scaling
Our architectures are built to handle massive data loads and user bases, keeping performance steady whether you're serving ten or ten million.
Accelerated Time-to-Market
Using our suite of internal tools and proven frameworks, we cut setup work so your first release reaches users sooner.
Embedded AI Integration
Beyond simple wrappers, we build deep-learning integrations and predictive analytics directly into the core of your industry-specific workflows.
Engagement Model
How does a public health software engagement work?
Agencies usually begin with one feed or one program. We size that release with your informatics lead and commit to its scope.
01
Scoping call
We review your feeds, programs, current systems and funder reporting.
02
Feed and program mapping
Your informatics and program staff fill the feed table and the program measures with us.
03
Fixed-scope first release
One feed or one program end to end, with validation, matching and audit logs in place.
04
Onboard senders
Providers are tested and moved to production one group at a time, with feedback on rejected messages.
05
Scale and support
More feeds, programs and reports under change control.
Facts and sources
Which standards and rules shape public health software?
Short facts we design the feeds, disclosures and records around, each linked to its primary source.
ONC certification criterion 170.315(f)(1) requires certified health IT to create immunization information in HL7 2.5.1 under the Implementation Guide for Immunization Messaging Release 1.5, and to request and display a patient's evaluated immunization history and forecast from a registry.
Source: 45 CFR 170.315(f)(1) and 170.205(e)(4) (eCFR)For standards-based electronic case reporting, certified health IT must match encounters to the Reportable Conditions Trigger Code value set, create an eICR in the HL7 FHIR eCR or HL7 CDA format, and receive and process the reportability response.
Source: 45 CFR 170.315(f)(5)(ii) (eCFR)The HL7 FHIR Electronic Case Reporting implementation guide (US Realm, v2.1.2) defines transactions and profiles for the electronic initial case report (eICR), the reportability response (RR) and electronic reporting and surveillance distribution (eRSD).
Source: HL7 FHIR eCR Implementation Guide v2.1.2A covered entity may disclose protected health information to a public health authority authorized by law to collect it for preventing or controlling disease, including disease reporting, public health surveillance, investigations and interventions.
Source: 45 CFR 164.512(b)(1)(i) (eCFR)Recipients and subrecipients of federal awards must retain all award records, including financial records, supporting documentation and statistical records, for three years from the date they submit the final financial report.
Source: 2 CFR 200.334 (eCFR)
Voice of success
We don't just build products; we forge lasting partnerships. See how we've helped industry leaders transform their vision into technical reality.
“I can clearly see how Agnotic has a unique way of handling end-to-end development. They are always active on quick chat and provide support quickly.”
Aaron Phelan
Founder, Benchmark
“Agnotic combines deep technical expertise with strong domain knowledge. They understand the business context, anticipate challenges, and make collaboration smooth and effective.”
John Pasmore
Founder, Latimer
“Agnotic is the best technical team we evaluated. Their engineering excellence made our work dramatically easier and allowed us to stay focused on what matters most for maternal care outcomes. They took full ownership of the technical execution, and we are always happy to continue working together.”
Kim Smith
Founder, My Lauren
Related pages
Related government and health data services
This page covers public health reporting and programs. These pages cover the citizen and health data work around it.
Unified citizen services gateway
Resident portals, identity and payments for government services.
Population health software
Risk stratification and care gaps for providers and payers.
FHIR integration services
FHIR APIs and implementation guide work for health data exchange.
Government and research software
All the government and research software we build.
Electronic case reporting (eCR) integration
The EHR side of eCR: trigger code matching, eICR generation and the reportability response.
More in Gov & Research
More Gov & Research Solutions
Explore other production-grade engineering platforms we deliver across gov & research.
Frequently Asked Questions
Yes. Most immunization, lab and syndromic feeds still arrive as HL7 v2.5.1, while electronic case reports can come as HL7 CDA or FHIR. We build intake for each format into one person and case model.
It depends on the agency's structure, so your counsel decides. HIPAA lets providers disclose protected health information to a public health authority authorized by law to collect it, and we build disclosure logging and role-based access either way.
Every feed matches to one person index. Clear matches link automatically, uncertain ones go to a review queue, and every merge is logged so it can be undone.
Yes, with separate access. NGOs can record participants, services and referrals and send agreed data to the agency, while seeing only their own records.
The number of feeds and senders, the programs in scope, person matching complexity, data migration from older systems and the funder reports needed. We estimate once the feed table is filled, since each feed carries its own validation and onboarding work.
Sender onboarding usually takes longer than the build itself. We date the first feed or program release after the feed table is complete and the first senders are lined up.
Yes. CDC provides HL7 message mapping guides and CSV implementation guides for every public health reporting jurisdiction to implement NNDSS case notifications. We map each condition to its guide, send the notifications, track the responses and keep every message version, while your epidemiologists decide which cases are notified.
Industries