Notice intake & triage
Capture TGA reference, device class, event type, date received, and reporting obligation flag. Auto-generate the 10-day mandatory reporting countdown from event date.
The platform boundary is narrow on purpose: recall operations, action management, evidence packs, closure verification, exception handling, and management visibility. Nothing outside this scope.
Each module addresses a discrete part of the recall lifecycle. Together they form a continuous, evidence-backed workflow from notice receipt to verified closure.
Capture TGA reference, device class, event type, date received, and reporting obligation flag. Auto-generate the 10-day mandatory reporting countdown from event date.
Match the notice to affected device stock at site level. Assign by ward and department. Record affected quantities, UDI capture, and lot number verification.
Assign responsible owners, set due dates, track action types and sub-tasks. Auto-escalate overdue actions to quality lead at configurable thresholds.
Upload and index supporting documentation against the 19 Recall Closure Evidence Set artefact classes. Store evidence where it belongs — attached to the case that needs it.
Document devices not recovered with reason code, risk decision rationale, and escalation path. Exceptions are required for closure defensibility — the module makes them impossible to skip.
Time-to-identify, time-to-action, verified closure rate, open exceptions, and overdue actions. Export a full audit-ready PDF for board, TGA, or ACHS EQuIP review.
The recommended operating model is a single-tenant hosted service with a minimum-PID design, controlled support access, and a customer-visible activity model. All in Australian data centres.
A clear four-phase sequence from public shell to full hosted service, pilot readiness, and network expansion.
Phase 1 — Now
Website, brand assets, service pages, privacy posture note, and launchable contact route. TGA Stage 1 urgency signal live on homepage.
Phase 2 — Weeks 5–8
Synthetic notice-to-closure demo, KPI dashboard mockup, evidence-pack example, and first Recall Watch bulletins delivered to early subscribers.
Phase 3 — Months 2–5
Tenancy model, roles, intake, tracker, evidence module, dashboard, audit trail, and verified closure sign-off. First customer tenant deployed.
Phase 4 — Months 5–10
UDI module, multi-site group dashboard, TGA notice auto-import, ACHS EQuIP evidence alignment, and procurement support pack.
Workflow, evidence, closure, and oversight take priority over visual theatre. Every feature must earn its place by reducing recall risk or improving auditability.
Vendor access is zero-standing, JIT, and customer-approved. Support is visible, time-bound, and logged. No hidden background access at any tier.
The platform does not diagnose, screen, predict, or treat. Every external sentence is checked against the intended-purpose memo before publication.
A 20-minute walkthrough using synthetic data from a comparable hospital type. Remote, no commitment, focused on your current workflow.