Powering immunization workflows across 50+ schools, with infrastructure mapped for 150 statewide
Scope
Technology stack
○ Introduction
Setting the scene
Wellbility State School is a statewide school immunization operations platform designed to streamline consent collection, clinical workflow coordination, reporting, and workforce training management for New Hampshire school-based vaccination programs.
The software serves a large and distributed public health environment, supporting 50+ schools (currently mapped for 150 schools) across districts with role-based access, high-volume operational workflows, and compliance-oriented data handling.
This project also reflects our identity as a health tech specialist software agency: we focus on solving healthcare delivery and healthcare operations problems where clinical accuracy, data quality, interoperability, and compliance are non-negotiable.
○ The Core Idea
One system to coordinate school vaccination programs end-to-end
Rather than managing data through disconnected tools, emails, spreadsheets, PDFs, and ad hoc exports, the platform brings all stakeholders into one workflow: from consent intake to administration reporting, while supporting statewide governance and local execution.
○ The Problem
What we were up against
Before a unified platform, school immunization operations suffered from a recurring set of challenges. From a healthcare perspective, these are not just administrative inefficiencies. They directly affect timeliness of care delivery, confidence in vaccination records, and the ability of public health teams to make reliable decisions.
Fragmented data and workflows
Consent forms live in paper files or disconnected PDFs. School and district teams run separate processes with little standardization. Status tracking is manual and delayed.
Clinical and administrative burden
Staff spend significant time collecting, sorting, and validating forms. Data required for vaccine administration is spread across multiple systems. Errors increase when teams re-enter data into downstream reporting tools.
Reporting complexity at scale
Standardized reporting across many schools is hard without a shared data model. Lot number and eligibility tracking are difficult to enforce consistently across districts.
Training readiness gaps
Vaccination programs rely on a workforce that must complete mandatory training and upload required documents. Without integrated tracking, staff readiness becomes a bottleneck.
Public health integration requirements
State-level immunization workflows require strict data format and quality controls. Integration with NHIIS-compatible HL7 and batch exports introduces technical and operational complexity.
Healthcare-specific risk profile
Vaccination programs involve protected and clinically relevant data. Errors in collection or transfer can create care and compliance risk. Healthcare workflows require traceability: who updated what, when, and under which context.
○ Our Solution
A modular, role-based platform with an operations-first architecture
The platform was designed to support both program operations (consent, vaccination status, reporting, export) and workforce enablement (training enrollment, prerequisites, profile documentation). It closes the gap between software workflows and healthcare workflows, turning fragmented administration into a dependable operating model.
01
Operations-first design
Built around the full vaccination program lifecycle: consent intake, administration, status tracking, and compliance reporting.
02
Role-aware architecture
Admin, RPHN, Vaccinator, and School Nurse roles drive data visibility, action permissions, and navigation scope.
03
Integration-ready backbone
NHIIS-oriented HL7/SOAP flow, batch text export, and Moodle LMS integration for training and workforce readiness.
○ Business Context
Single-state focus with statewide scale
This implementation is specifically aligned to New Hampshire's operational context: NHIIS-oriented integration patterns, NH-specific school mapping, and district/school structures that match real delivery models.
State-level leaders
Public health program leaders overseeing vaccination outcomes across New Hampshire.
District supervisors
Mid-level coordinators managing school clusters and district-scoped operations.
RPHN & vaccinator teams
Clinical staff administering vaccines and documenting outcomes at the school level.
School nurse / check-in staff
On-site personnel managing student intake and consent verification.
Parents & guardians
Consent submission, notifications, and status visibility for their children.
○ Product Capabilities
What we built
- Authentication & role-based access: Token-based login with Admin, RPHN, Vaccinator, and School Nurse roles driving data visibility and action permissions.
- Consent form lifecycle: Create, update, status progression (Signed → Completed → Not_Vaccinated), duplicate prevention, image capture, and parent notification workflows.
- School & district management: Master-data governance with year-aware retrieval, district-scoped filtering, and RPHN visibility controls.
- User & workforce administration: Role assignment, clinical type management, profile/document uploads (licenses, oaths, attestations, BLS), and readiness tracking.
- Training & Moodle integration: LMS provisioning, course enrollment sync, prerequisite gating (oath, attestation, license), and grade/status tracking.
- Lot number management: CRUD operations, active lot filtering, and lot-linked reporting for traceability.
- Reporting & export: Filtered reports by RPHN/district/school/status/lot, grouped views, CSV export, and PDF generation.
- NHIIS integration: HL7/SOAP submission flow, batch text file generation, segment construction (MSH/PID/NK1/RXA/RXR/OBX), ACK/ERR parsing, and submission logging.
○ Consent Form Lifecycle
The operational backbone of the platform
Consent forms are the core domain object. Their lifecycle drives the entire vaccination program workflow, from parent submission through clinical administration to compliance reporting.
○ Challenges
Execution constraints we had to solve
Integration complexity: NHIIS/HL7
Health data exchange requires strict structure and semantics. Message validation and ACK/ERR interpretation are non-trivial. We addressed this with structured HL7 message assembly, ACK/ERR parsing with persistence in submission logs, and defensive handling around submission and parse flows.
Integration complexity: Moodle LMS
Workforce identities must stay synchronized across systems, and enrollments can drift without proactive sync. We implemented on-login Moodle provisioning, periodic course sync routines, and authenticated launch URL generation.
Scaling to 150 mapped schools
High data volume and concurrent operations across distributed entities required pagination, school/district scoped query patterns, and frontend data table tooling for practical high-volume management.
Role and governance complexity
Different users need different permissions and visibility footprints. Errors in scoping create compliance risk. We built role-scoped backend queries, guarded routes, and distinct school vs district association logic by role.
Data quality and duplicate prevention
Duplicate or malformed records create downstream reporting and clinical risk. We implemented duplicate checks on consent intake, data normalization patterns, and controlled status transitions with explicit update paths.
○ What We Have Achieved
Measurable operational outcomes
The platform delivers meaningful improvements across every dimension of school immunization operations, from consent handling speed to reporting confidence and workforce readiness.
○ Why This Matters
What it takes to deliver software for a U.S. state program
Delivering software for a U.S. state-level operational program demands reliability under real-world public service conditions, interoperability with state health data exchange expectations, strong operational guardrails for data quality and access control, and the ability to serve many institutions under one governance model.
Reliability at public-service scale
Real-world conditions with distributed teams, high-volume data, and non-negotiable uptime requirements.
State health data interoperability
NHIIS-compatible HL7 and batch export integration meeting strict format and quality controls.
Operational guardrails
Data quality enforcement, traceability, and access control across all participating schools and roles.
Multi-institution governance
One platform supporting 150 schools, multiple districts, and diverse role types under unified oversight.
○ Strategic Takeaways
What this project reinforced
01
Build around workflows, not just forms
The platform succeeds because it supports the full operational cycle, not individual data entry screens.
02
Treat integrations as products
HL7 and LMS integrations need observability, retries, and governance, not just connectivity.
03
Role design is core architecture
In statewide operations, authorization is part of business logic, not just a security layer.
04
Scale begins with data shape
Consistent school/district/user modeling enables practical expansion across the full state network.
05
Operational UX matters as much as backend correctness
Teams need fast list views, filters, exports, and guided flows to stay productive at high volume.
○ Future Opportunities
What this unlocks
Multi-state configuration
Extending the platform beyond New Hampshire with state-specific configuration models.
Additional interoperability standards
Broader integration support for emerging health data exchange requirements.
Analytics dashboards & KPI trends
Expanded operational analytics for program leadership decision-making.
Integration health monitoring
Advanced observability for NHIIS submission success rates and system reliability.
○ Conclusion
Mission-driven health operations software at state scale
Wellbility State School is a meaningful example of mission-driven health operations software: it connects school-based clinical workflows, statewide program oversight, and training readiness in one practical system.
By supporting large school networks, role-based operations, and integration-heavy requirements, it enables faster, safer, and more coordinated vaccination program execution at state scale.
It also demonstrates the value of healthcare-specialist engineering: domain knowledge in health data flows, clinical operations, and public health reporting is what makes this kind of statewide implementation successful.
Related case studies
Explore similar outcomes
Digital Health / Care Communication
Patient Talker
Patient Talker is a HIPAA-compliant mobile platform that captures consultations, generates AI-powered medical summaries, and securely connects patients with caregivers around one accurate source of truth.
Read case studyHealthcare Operations / HealthTech
Previa
We built Previa to streamline one of healthcare’s most frustrating administrative workflows: prior authorization. The platform brings patient records, insurance data, clinical codes, AI-generated justification letters, and payer integrations into one connected web experience, helping healthcare teams submit cleaner requests faster and track every authorization in real time.
Read case studyHealthcare Operations / HealthTech
Medibill
We built Medibill to help medical professionals manage the financial and administrative side of their practice from a single mobile platform. The app combines billing policies, electronic claims submission, financial analytics, document management, progress tracking, and pre-procedure patient engagement into one connected experience, giving doctors and practice teams better visibility, faster workflows, and less operational friction.
Read case study