INTERNAL DRAFT — NOT FOR PUBLICATION. Copy marked ⚑ requires sign-off against the intended-purpose memo before going live. All other content is cleared for internal review only.
⚠ TGA Stage 1 — effective 21 March 2026 Australian hospitals

Medical device recall governance,
verified and audit-ready.

ROQAIAH helps Australian hospitals receive, action, and close medical device recall notices — with the evidence trail your quality team needs for TGA mandatory reporting.

Why now — 3 facts
21 Mar
TGA Stage 1 mandatory reporting in effect
Live
10
Calendar days to report death or serious injury events to TGA
Mandatory
1 Jul
UDI phase-in — Class III devices and Class 4 IVDs
2026
ROQ
Maturity levels 1–5 — from notice-driven to verified closure
Framework
Regulatory basis
Therapeutic Goods Act 1989 — mandatory recall reporting obligations
Privacy Act 1988 — APPs 1–13, minimum-PID design
ASD Essential Eight — ML1 alignment from launch
AU-hosted infrastructure — Azure Australia East, data sovereignty
TGA Stage 2 — monitoring from 2027

Australian hospitals receive recall notices. Proving they acted on them is the hard part.

When a medical device recall notice arrives, the work has just begun. Tracking affected devices across wards and sites, coordinating actions, collecting evidence, managing exceptions, and producing a defensible closure record — that is the recall execution gap.

01
Notices arrive, but action tracking is fragmented

Recall notices come from TGA, manufacturers, and distributors — often by email, sometimes by post. Most hospitals manage the response in spreadsheets, shared drives, or email threads. There is no single record of what was done, by whom, and when.

02
Inventory matching is manual and error-prone

Matching a recall notice against affected device stock across multiple wards, theatres, and stores is time-consuming work. Without a structured process, devices can be missed — and there is no audit trail to prove they weren't.

03
Closure cannot be proven without structured evidence

TGA mandatory reporting requires that hospitals demonstrate recall completion. An email chain is not a verified closure record. Exceptions — devices not recovered — need documented risk decisions. Most hospitals cannot produce this evidence quickly.

04
The 10-day mandatory reporting clock starts immediately

For events involving death or serious deterioration of a person's health related to a high-risk device, TGA Stage 1 requires a report within 10 calendar days of becoming aware. The clock does not wait for internal processes to catch up.

This is a CEO-level obligation

TGA mandatory reporting under Stage 1 places formal obligations on healthcare facilities. Quality leads, biomedical engineering teams, and hospital executives need a consistent, repeatable process — not a one-off response each time a notice arrives.

10-day TGA reporting timer

Automated countdown from event date, with escalation alert at day 7 to the quality lead. The most commercially critical single feature — built in from day one.

🔍

Device and inventory triage

Match recall notices to affected device stock at site level. Assign by department and ward. Quantity affected, quantity accounted for — tracked in the same record.

Verified closure sign-off

Named sign-off by an authorised role. Timestamp. Closure decision. Exception flag where devices were not recovered. A defensible record your team can produce on request.

📁

Evidence pack — RCES aligned

Upload and index supporting documentation against the Recall Closure Evidence Set (RCES) artefact classes. Store evidence where it belongs — attached to the case that needs it.

📊

KPI dashboard and audit export

Time-to-identify, time-to-action, verified closure rate, open exceptions, overdue actions. Export a full audit-ready PDF pack for board, TGA, or ACHS EQuIP review.

From TGA notice to verified closure — in one platform

A five-step workflow that gives your quality team a consistent, repeatable process for every recall event.

1
Notice received
TGA alert, manufacturer notice, or distributor communication captured as a structured case record
2
Device triage
Affected devices matched to site inventory. Wards and departments assigned. 10-day clock starts
3
Action & evidence
Actions assigned to owners. Evidence uploaded and indexed against RCES artefact classes
4
Exceptions logged
Devices not recovered documented with reason code, risk decision, and escalation path
5
Verified closure
Named authorised sign-off, timestamp, audit-pack exported. Case closed. Evidence retained

Start free. Scale when you are ready.

Three tiers designed to meet hospitals where they are — from a weekly intelligence digest to a full hosted recall operations platform.

Tier 0
Recall Watch
Free — no commitment
Weekly TGA recall intelligence delivered to your quality inbox. No software, no data, no obligation.
  • Weekly TGA device recall digest
  • Class I recall alerts — death / serious injury scope
  • Stage 1 mandatory reporting updates
  • ROQ maturity self-assessment guide
  • RCES evidence checklist (PDF)
  • Governance charter starter template
  • Monthly 20-minute advisory call
Subscribe — no cost
Tier 1.5 / Network
Recall Ready Network
Negotiated — multi-site groups
For hospital groups managing recall governance across multiple sites. Consolidated executive view, group-level reporting.
  • Everything in Recall Ready
  • Multi-site site hierarchy and dashboard
  • Group-level KPI rollup and audit pack
  • Executive reporting pack — quarterly
  • Dedicated implementation support
  • Priority support SLA
Enquire — group pricing

Publication-grade research. Not a vendor claim.

ROQAIAH is grounded in peer-reviewed research defining the recall execution gap and the governance framework for verified completion.

P1 — Recall governance paper

Closing the Recall Execution Gap — a governance framework for verified medical device recall completion

Under editorial review at Globalization & Health. Citable now. Defines the Recall Closure Evidence Set (RCES), ROQ maturity model (levels 1–5), and governance metrics (TTI, TTA, VCR, EB, RRD, EoC).

↗ doi.org/10.21203/rs.3.rs-9098866/v1
RCES — Recall Closure Evidence Set

A structured evidence standard for recall closure

The RCES defines 19 artefact classes that constitute auditable verified recall completion. ROQAIAH's evidence-pack module is built around RCES artefact classes — connecting your workflow directly to the evidence standard.

5
ROQ maturity levels
19
RCES artefact classes
6
Governance KPI metrics
L1–L3
Conformance levels
🔒

Privacy and data governance — built in from the start

All data is stored exclusively in Australian sovereign data centres (Azure Australia East). No standing vendor access — support is JIT, customer-approved, and fully logged. ROQAIAH is designed around device-event records, not patient records — minimising Privacy Act obligations from the ground up. APP privacy policy, data-residency commitment, and NDB incident response plan provided at contract stage.

Privacy Act 1988 (Cth) APPs 1–13 NDB scheme AU data sovereignty ASD Essential Eight ML1 Zero standing vendor access Azure Australia East Minimum-PID design

Start with Recall Watch — free, this week.

Subscribe to ROQAIAH Recall Watch and receive weekly TGA recall intelligence, a triage guide, and governance templates — with no software, no data, and no commitment.

Subscribe free → Request a Recall Ready demo