Synthetic sample. Synthetic demonstration. The cleared product family, signal themes, and review points shown on this page are illustrative — they are not drawn from any real client engagement. A real Post-Clearance Review Point Pack uses your actual cleared product family and source-cites every row.
Post-Clearance Review Point Sample
After clearance, the work changes. The question is no longer “how do we submit?” but “how do we turn this product family into a reusable baseline for PMS, complaints, CAPA screening, risk review, labeling / usability, supplier / service review, product change review, and Canada-entry planning?” This page is a redacted demonstration of how that workspace looks once a Product ID is anchored to a cleared product family.
TrueMedDevice provides source-backed evidence organization and research support. We do not provide regulatory, legal, or compliance advice. We do not determine device classification, submission pathway, substantial equivalence, licence eligibility, safety, effectiveness, or compliance. Final decisions remain with qualified RA/QA professionals, consultants, or the manufacturer.
1. Starting point
ExampleCo’s connected infusion-pump accessory family is on the market and has been used in hospitals and clinics for more than two years. The team can answer day-to-day product questions, but the post-market evidence surface is scattered across complaints, CAPAs, risk files, supplier records, and engineering change requests. A qualified RA/QA reviewer cannot easily ask “what does the external public record say about this exact family right now?” without manual sweeps.
2. Product ID evidence baseline
The Product ID for the cleared family carries the same six-layer structure as a pre-market Product ID — only the contents shift to reflect a post-clearance posture.
| Field | Illustrative value |
|---|---|
| Product family (illustrative) | ExampleCo Connected Infusion-Pump Accessory family (synthetic) |
| Manufacturer | ExampleCo, Inc. (synthetic; not a real entity) |
| Jurisdiction lock | United States / FDA |
| Status | Cleared 510(k); on market for >24 months |
| Use environment | Hospital / clinic; some long-term-care and home-infusion deployments |
| Key functions in scope | Dose delivery support, alarm signalling, software-based parameter limits, service / repair release controls |
| Similar device family (Layer 4 comparators) | Predicate-adjacent infusion pump families and accessory product codes — verified against the openFDA product code on file |
| Known public signal categories | Recalls, MAUDE events, Warning Letters, FDA Safety Communications |
| Demo as-of date | 2026-05-21 |
3. Public safety signal themes
The pack groups public-record findings into themes the qualified reviewer can map onto QMS, PMS, complaints, CAPA, and supplier workflows.
Alarm issues
Missed, delayed, or false alarms during occlusion, air-in-line, infusion-complete, or low-battery conditions. Anchored to public recall / MAUDE rows in real packs.
Battery / power
Reduced run-time, charge failures, and inadvertent shutdowns. Often correlated with battery supplier changes or stored-inventory aging.
Software / version control
Drug library updates, parameter limit changes, and patch-release sequencing. Surface area for change-control questions.
Labeling / usability / IFU
Set-up sequence errors, labeling that conflicts with current software behavior, and IFU steps no longer matching the most recent release.
Service / supplier issues
Repair-depot release without complete testing, supplier component substitutions, and process-control gaps observed in public recalls.
Adverse event reporting
Trends in MAUDE event types and narrative themes — under-reporting risk explicitly flagged in any real pack.
Recalls
Predicate-family and direct-product recalls in the last five years, with public root-cause text quoted verbatim and source-linked.
4. Review Point Library
Each row converts an external public signal theme into a candidate review point that the qualified RA/QA reviewer can adopt, modify, or set aside.
| QMS / PMS area | Candidate review question |
|---|---|
| Complaint intake fields | Does the current complaint form capture model, software version, lot, and the specific failure mode themes surfaced in public signals (alarm, battery, software, labeling, service)? |
| CAPA screening questions | For each newly opened complaint that matches a public signal theme, does the CAPA screen ask whether a similar issue is already in the public record for the product family? |
| Risk file hooks | Does the risk management file include hazard / hazardous-situation / harm chains that correspond to each public signal theme? When was each chain last re-evaluated against current public evidence? |
| PMS monitoring categories | Does the PMS plan list each public signal theme as a monitored category, with an external-source check cadence and a defined trigger for escalation? |
| Change-control questions | For each proposed product change, does the change-control record reference the relevant public signals and the qualified RA/QA reviewer’s analysis of whether the change addresses, introduces, or is unaffected by them? |
| Labeling / usability review points | When labeling, IFU, or human-factors validation is updated, does the review reference the labeling- and usability-related public signals identified for the product family? |
| Supplier / service follow-up | Are repair-depot release controls, supplier qualification records, and component-substitution traceability aligned with the service / supplier themes surfaced in public records? |
5. Example: a product-change question
“If we change an alarm threshold, what evidence should appear before the RA/QA decision?”
What the reviewer brings to the workspace
- Proposed change: lower the upstream-occlusion alarm threshold by one pressure unit.
- Originating record: engineering rationale memo, draft change-control entry.
- What the qualified RA/QA reviewer needs to see before the decision.
| Source surfaced by the workspace | What appears for the qualified reviewer |
|---|---|
| Complaints (last 24 months) | All complaint records mentioning “occlusion,” “no alarm,” “false alarm,” or related text — pre-filtered for the affected product family. |
| CAPA / risk hooks | Open CAPAs touching alarm behaviour, plus the relevant risk file rows for occlusion hazardous-situation chains. |
| External public signals (Layer 2 / Layer 4) | Recall and MAUDE rows naming occlusion-alarm behaviour, with source URLs — both for the product family and for predicate / peer comparators. |
| Prior review points | Past review points where alarm threshold logic was discussed, with the date, the qualified reviewer, and the supporting evidence at that time. |
The workspace surfaces evidence; the qualified RA/QA reviewer makes the decision about whether the change is acceptable, whether CAPA is required, and whether the change triggers a new submission. TrueMedDevice does not make any of those determinations.
6. What the buyer gets
- Product ID evidence baseline anchored to the cleared product family.
- Public safety signal sweep across recalls, MAUDE, warning letters, and FDA Safety Communications — categorised by theme.
- Review Point Library — candidate review points for complaints, CAPA screening, risk file hooks, PMS categories, change-control, labeling/usability, and supplier/service review.
- Worked example of a product-change question, showing how the workspace surfaces complaints, CAPA/risk hooks, external signals, and prior review points before the qualified RA/QA decision.
- Source ledger — every external signal row carries a verifiable URL.
- Monthly Product ID workspace option — signal refresh and source-backed Q&A as new public signals appear, anchored to the same Product ID file.
Decision support, not decision replacement. TrueMedDevice provides source-backed evidence organization and research support. We do not provide regulatory, legal, or compliance advice. We do not determine device classification, submission pathway, substantial equivalence, licence eligibility, safety, effectiveness, or compliance. Final decisions remain with qualified RA/QA professionals, consultants, or the manufacturer.