Immunization registry software that gets the dose into the state system once, correctly
An immunization information system, or IIS, is a confidential population based database recording vaccine doses administered in a geographic area. Nearly all 50 states operate one, and CDC publishes functional standards defining what they must do. Neurobird captures each dose once, submits it to the state IIS, detects duplicate patient records before they distort coverage, and reconciles VFC inventory against doses actually administered.
Watch the fields extract from the document.
Neurobird Immunization Registry in short
- Capture the dose once and submit it to the state immunization information system
- Detect duplicate patient records and merge candidates before they distort coverage
- Reconcile VFC inventory against doses administered rather than against memory
- v4.1 CDC publishes IIS functional standards defining what a registry must support, including data exchange and deduplication. CDC IIS functional standards
- 50 Nearly every US state operates an immunization information system, each with its own submission requirements. CDC
- Pricing runs 150 to 620 US dollars per month across 3 tiers. Early access is free.
What clinics and public health programmes actually deal with
Why it stays broken
The chart and the registry are separate systems joined by an interface that works maybe 940 times in 1,000. Mostly is the problem: the failures are silent, so nobody discovers the gap until a coverage report or a school entry check does it for them.
A clinic administering 4,000 doses a year can carry several hundred unmatched or duplicated records.
Providers ordering immunizations must submit immunization information to NYSIIS or the CIR within 14 days of administration of the immunization.
Neurobird Immunization Registry Document Automation Platform
Treat the submission as the job rather than an afterthought, and make the failures loud instead of silent.
- 1Capture the dose once and submit it to the state immunization information system
- 2Detect duplicate patient records and merge candidates before they distort coverage
- 3Reconcile VFC inventory against doses administered rather than against memory
- 4Surface series gaps so a recall list is generated from the data, not built by hand
What changes with Neurobird Immunization Registry?
The same work, read left to right: how it runs today, and how it runs once the record is in one place.
| Today | With Neurobird Immunization Registry |
|---|---|
| Doses get entered twice, once in the chart and once in the state registry, because the interface never quite worked | Capture the dose once and submit it to the state immunization information system |
| Duplicate patient records in the registry mean a child appears under immunised when they are not | Detect duplicate patient records and merge candidates before they distort coverage |
| VFC inventory reconciliation is a manual count against a system that does not match the fridge | Reconcile VFC inventory against doses administered rather than against memory |
Who is this for?
Same registry, three different obligations.
You report but do not control the interface
You need to know when a submission failed, without reading acknowledgement logs you were never trained on.
Coverage is measured across sites
Duplicates and gaps distort your numbers. You need deduplication before the coverage report, not after it.
You run VFC accountability
Inventory must reconcile to doses administered. You need that as a continuous check, not an annual scramble.
How does Neurobird Immunization Registry work?
Capture the dose once
Vaccine, lot, site, route and eligibility recorded at administration, in the form the IIS expects.
Submit and confirm
The record goes to the state IIS and the acknowledgement is tracked, so a rejected message is visible rather than lost.
Reconcile and recall
VFC inventory reconciles against doses administered, and series gaps generate a recall list from the data.
How immunization information systems actually work
Useful if you report to a state IIS or run VFC. Each source links out.
CDC publishes IIS functional standards defining what a registry must support, including data exchange and deduplication.
CDC IIS functional standardsNearly every US state operates an immunization information system, each with its own submission requirements.
CDCYear the Vaccines for Children programme began supplying no cost vaccine for eligible children, creating the inventory accounting duty.
CDC Vaccines for ChildrenDoses a modest clinic may administer annually, each requiring a registry record and inventory decrement.
Washington State IISImmunization registry software questions, answered
Key terms
- What is an immunization registry?
- An immunization information system, or IIS, is a confidential population based database that records vaccine doses administered within a geographic area. Nearly all US states operate one, and providers are generally expected or required to report doses to it.
- What is VFC inventory reconciliation?
- Vaccines for Children is a federal programme supplying vaccine at no cost for eligible children. Providers must account for that inventory: doses received, administered, wasted and on hand, reconciled against the doses recorded.
Why do duplicate records matter?
Because a duplicate splits a child's history across 2 records, so neither shows a complete series. Coverage looks lower than it is, recall lists target the wrong families, and a school entry check can fail on a fully immunised child.
Does this replace the state IIS?
No. It feeds it. The IIS is the system of record for the jurisdiction. This makes sure what you administered arrives there once, correctly, and tells you when it did not.
Why we are building this
Immunization data is one of the few areas where the public infrastructure genuinely exists. Every state runs a registry, CDC publishes functional standards, and the data matters for real public health decisions.
The weak link is the last mile: getting the dose from the clinic into the registry once, correctly, and knowing when that failed. Today it is often double entry and silent rejections.
We would rather build this with the people doing the entry than guess. Tell us how doses reach your registry, and where we have got it wrong.
Where the requirement comes from
CDC standards and state registry references.
- CDC IIS functional standards v4.1 What an immunization information system must support, including data quality and exchange.
- CDC, about immunization information systems Overview of IIS purpose, coverage and how providers interact with them.
- CDC Vaccines for Children programme Programme rules including provider inventory accountability duties.
- Washington State Immunization Information System An example state registry, showing submission expectations at jurisdiction level.
How much does Neurobird Immunization Registry cost?
Priced per clinic site because registry reporting is a site level duty. Users are unlimited.
- Dose capture
- IIS submission
- Acknowledgement tracking
- VFC inventory count
- Email support
- Everything in Single site
- Duplicate detection and merge
- Series gap recall lists
- Coverage reporting
- Named contact
- Everything in Multi site
- Jurisdiction level roll up
- Bulk historical import
- Role based PHI controls
- Onboarding and security review
Get free early access
If you report doses to a state registry, tell us where the submission actually breaks today.
Straight answer on where this is: In development. Early access gets the working preview, influence on what ships first, and early access pricing. It does not get you a login today, and it does not touch PHI before a security review.
Prefer email? Write to office@neurobird.com and a person will reply. No autoresponder.