Guided workflow
Each step maps to the live AU-COMM-1 product story without exposing internal operator tooling.
Signal intake
A new safety signal enters the hospital workflow. The user sees what triggered the case and whether it is a watch signal, a case, or a reportable incident.
Route decision
The platform records why the case goes to ASDER, IRIS, a centralised route, or no healthcare-facility report at this stage.
Affected-asset list
Hospital inventory is reconciled so the site can confirm which units are affected, pending, or clear.
Evidence and proof
Operational evidence and submission proof are collected without turning the platform into a patient-record system.
Closure review
The case is closed only when affected units, actions, proof, and exceptions are all accounted for.
Audit pack
The hospital exports a concise, board-ready, audit-ready summary instead of reconstructing the case later.
What the demo shows
Operational proof of need
Why serial-scoped recalls, incomplete closure evidence, and sponsor/hospital workflow fragmentation create a real gap for hospitals.
Not architecture depth
The demo avoids internal normalization, gap-register, and adapter mechanics. Those stay in the testing platform and operator layer.
Commercial wedge
Recall-readiness and auditability first. That stays aligned with the AU commercialization lane.