PrototypeSynthetic data only. This is a demonstration built for a CDC RFQ response. It is not a CDC system and is not connected to VAERS. Do not enter real personal or health information.
Vaccine Adverse Event Reporting — Prototype

Demonstration build — Miranium AI LLC response to CDC RFQ 75D301-26-Q-00146

A guided, plain-language way to report what happened after a vaccination.

This demonstration shows a redesigned reporting experience: one form that adapts to who is filling it in, asks only the questions that apply, explains itself as you go, and collects supporting documents in the same flow.

Where would you like to go?

What is different about this form

It asks only the questions that apply to you
Field visibility is driven by a declarative rules layer, not hard-coded branches. A provider reporting a vaccine administration error with no adverse event never sees a single adverse-event question.
It speaks your language, not ours
The same underlying data element is labelled in plain English for the public and in clinical terminology for providers. One data model, two vocabularies.
It helps you find the right documents
Upload happens inside the form, and a suggestion engine reads your answers to propose which records would help a reviewer most.
Programme staff can change the wording themselves
Labels, help text, tooltips and questions-and-answers are editable in an admin screen with no code change and no deployment.

Demonstration only

Nothing entered here is transmitted to CDC or to VAERS. Use made-up names and details. To file a real report, use the official VAERS site.

For evaluators

The report form carries a scenario loader that fills in a complete synthetic report for each of the three user flows, including the vaccine-error flow that suppresses every adverse-event field.

See the acceptance criteria and where each one is demonstrated