The decision-reuse moment
Picture the RA/QA lead after a peer-device recall and a customer complaint land in the same week. The team can collect sources, but the harder question is how the review decision becomes reusable when the next similar event arrives.
Decision reuse means each review leaves behind a source-backed record of what was checked, what was different, what stayed open, who owned the decision, and when the reasoning should reappear.
Four-layer RA/QA framework
| Layer | What to capture |
|---|---|
| External signal mapping | FDA databases, TPLC, MAUDE, recalls, early alerts, product-code clues, source limits, and access dates. |
| Event triage | Complaint, CAPA, risk, PMS, supplier, service, label, IFU, support, customer, and prior review record links. |
| Action decision support | Same/different facts, affected-scope questions, owner map, candidate next actions, and decisions held for qualified review. |
| Inspection-ready reuse | Source ledger, rationale, owner, boundary, review status, evidence gap, and reuse tag for future similar events. |
What good looks like
A useful decision-reuse record is short, source-linked, and easy to re-open. It should show why the prior review did or did not apply to the next event.
It should also make uncertainty visible. If the signal source is incomplete, the product match is uncertain, or the owner decision is pending, that status belongs in the reusable record.
Source ledger
What it can tell you
FDA public database families that can support external signal mapping and product-code research.
What it cannot decide
Whether one public record changes a device-specific regulatory, risk, customer, or product decision.
What it can tell you
FDA source-integration context and limitations for total product life cycle data.
What it cannot decide
Whether a public signal set is complete or decisive for one product.
What it can tell you
Public medical-device report search context for adverse-event and product-problem signal collection.
What it cannot decide
Whether a report applies to one product, confirms causation, or changes a company action.
What it can tell you
FDA public reporting context that can frame reportability review questions.
What it cannot decide
Whether one event creates a reporting action or what timing applies to one company.
What it can tell you
Public recall and early-alert context for external signal mapping.
What it cannot decide
Whether one product, supplier, lot, software version, or customer event is affected.
What it can tell you
FDA public QMSR context for quality-system and inspection transition questions.
What it cannot decide
Whether one reusable decision record, QMS record, or review framework is adequate.
Frequently asked questions
Does this framework decide what action the company should take?
No. It prepares source-backed review points and reusable decision records. Reportability, recall, CAPA, risk, supplier, customer, clinical, legal, and leadership decisions remain with qualified reviewers.
What should be reused from a prior review?
Reuse source links, search terms, product-code context, same/different facts, internal record links, owner decisions, open questions, boundaries, and evidence-gap notes.
Need reusable RA/QA review points?
Send one public signal and one internal event. We can scope a source-backed decision-reuse packet for qualified review.
Reader feedback
Useful pages should feed the next topic choices. Leave a signal or a short comment.