TT Teck evaluator walkthrough

Explore the prototype by capability

A focused demonstration of guided reporting, provider-specific logic, CDC-facing configuration, measurable usability, and an integration-ready data boundary.

Choose a demo pathView evaluation metrics

Public reporter

Plain-language guided reporting with autosave, validation, clinical context, document recommendations, review, and structured output.

Or start from a blank report →

Healthcare provider

Demonstrates the vaccine-administration-error pathway where no adverse event occurred, suppressing unnecessary event fields.

Or start from a blank report →

CDC admin

Edit landing guidance and FAQ content without changing source code, then inspect local structured submissions.

Open CDC admin demo
What this proves

Designed around the evaluation story

≤ 10 minTypical submission target instrumented
AutosaveDraft recovery reduces lost work
AccessibleFocus states and linked error summaries
ConfigurableCDC content changes without redeploy
Prototype evaluation alignment

Mapped directly to the six RFQ prototype areas

1
Problem & objectives

Reduces burden for public and provider reporters while improving completeness, usability, and data quality.

2
Sound & feasible approach

Working server-rendered workflow, persistent drafts, validation, structured output, and a separable integration adapter.

3
Innovation & originality

Reporter-aware branching, rules-based supplemental-document guidance, autosave/recovery, and measurement built into the experience.

4
Risks & mitigation

Unknown CDC backend contracts are isolated behind an adapter; undisclosed business rules remain configurable rather than hard-coded assumptions.

5
Performance alignment

Instrumentation explicitly tracks the ≤3-second page-load, ≤10-minute typical submission, and abandonment-improvement objectives.

6
Scale & extensibility

Form workflow, program content, analytics, and backend mapping are separated so requirements can evolve without rebuilding the entire application.