A modern, accessible way to report a vaccine adverse event
One smart form, two audiences. The same configurable question set adapts its language, depth, and follow-up questions to whoever is reporting — a member of the public on a phone, or a clinician at the point of care.
-
I'm reporting for myself or a family member
Plain-language questions, one step at a time. No medical vocabulary needed — describe what happened in your own words.
Start a public report → -
I'm a healthcare professional
Clinical terminology and additional structured fields: dose series, route, VIS date, concomitant medications, and lab data.
Start a provider report →
For CDC program staff: both versions above render from a single configuration file. See the low-code configuration console — add a question, edit wording or branching rules, and watch the live form change, no developer involved. Every save is snapshotted with one-click rollback.
Technical Approach & Risk Register → How this prototype maps to the production architecture in CDC-managed Azure, measured performance evidence, the Section 508 approach, and the top technical risks with mitigations.
What this prototype demonstrates
Each capability below maps to a performance requirement in the PWS.
- Branching "smart" report form Follow-up questions appear only when relevant — medical-care details after "yes," per-symptom onset and severity after each symptom checked, pregnancy only when age and sex make it applicable.
- Plain-language public version vs. clinical provider version Every question carries dual wording in configuration; the wizard renders the right variant per audience, and providers see additional structured fields.
- Low-code configurability for CDC personnel Sections, questions, wording, requirements, and branching rules live in one JSON configuration, editable through the admin console without a code deployment.
- Question authoring and rule building in the console Program staff can add entirely new questions — any field type, answer options, required flag, and a branching rule — and attach branching rules to existing questions, with a live preview of both audience versions.
- Configuration version history with one-click rollback Every save creates a named snapshot with an automatic summary of what changed; any earlier version can be restored instantly, standing in for a production approval workflow with a full audit trail.
- Plain-language assists for public reporters Symptom choices are worded in everyday terms with recognizable descriptions (clinical terminology appears only in provider mode), helper text supports the harder questions, and an "in your own words" escape hatch means nobody is blocked by vocabulary.
- VAERS-compatible structured data capture Submissions render as structured JSON in an HL7 FHIR AdverseEvent-flavored shape, with a sample mapping to VAERS 2.0 form items.
- Mobile-friendly, fast, and Section 508-minded Static, framework-free pages with zero external requests load well under the 3-second requirement; semantic HTML, keyboard operability, visible focus, and live-region announcements throughout.
- Documented technical approach and risk management The Technical Approach & Risk Register maps this prototype to the production architecture in CDC-managed Azure and states the top technical risks with concrete mitigations.