Anatomy of a Review-Ready PMS Evidence Pack for Infusion Pump Reviews
A PMS evidence pack template is the portable, audit-ready output of one product-level review. This walkthrough shows what goes into an infusion pump evidence pack — signal summary, product relevance, complaint trend snapshot, labeling and IFU excerpts, training references, prior decision log entries, reviewer notes, and final rationale — and how a Product Review Workspace produces it. RA/QA owns the final decision.
What a review-ready evidence pack is
A review-ready evidence pack is the structured output of one product-level review — the same output a Product Review Workspace produces when an RA/QA team finishes organising a question. It contains the signal summary, the product relevance notes, the evidence considered, the decision log language, and the next-review recommendation. It is review support; the qualified team approves the content and owns the conclusion.
A PMS evidence pack template benefits from having product-level reviews captured in this portable format.
Why an infusion pump team would use one
For infusion pump reviews, the evidence pack is what makes the review record portable. It is the artifact you hand to:
- the qualified RA/QA reviewer who needs to confirm or revise a conclusion
- the next reviewer who picks up the question six months later
- the audit reader who asks what was considered and why
- the board or executive who needs a one-page summary of the review
It is not a CAPA record and it is not a QMS document. It is the review-support artifact that connects the signals to the decision.
What sections it contains
- Signal summary — the signals that prompted the review and how they relate.
- Product relevance notes — which product or product variant each signal touches.
- Complaint trend snapshot — the relevant complaint history excerpt.
- Labeling / IFU excerpts — relevant labeling and quick-start sections.
- Training material references — relevant onboarding and competency notes.
- Prior decision log entries — what was decided in related earlier reviews.
- Reviewer notes — the qualified reviewer's assessment.
- Final rationale or next-review recommendation — the conclusion the qualified team reached.
Example table of contents
| Section | Pages | Source |
|---|---|---|
| Signal summary | 1 | Workspace |
| Product relevance | 1 | Workspace + QMS |
| Complaint trend snapshot | 1 | QMS / CAPA log |
| Labeling / IFU excerpts | 1 | IFU |
| Training references | (linked) | LMS |
| Prior decision log | (linked) | Workspace |
| Reviewer notes | 1 | Reviewer |
| Final rationale | 1 | Reviewer |
A typical sample pack is 4 pages of content with linked references; a full review pack expands to 8–12 pages depending on the depth of the complaint history and prior decisions.
How evidence is linked to review questions
Each evidence reference is linked to the review question it answers. An IFU excerpt is linked to a labeling-clarity question. A complaint trend snapshot is linked to a complaint-trend question. A prior decision log entry is linked to the rationale-continuity question. This linkage is what lets a future audit or follow-up review trace what was considered and why.
The Product Review Workspace produces these links; the qualified team approves them.
How decision rationale is captured
The decision log entry in the evidence pack records:
- Signals reviewed and how they relate
- Evidence considered
- Product relevance assessment
- Conclusion (action, no action, monitoring)
- Reviewer name and date
Example decision log language for a simulated infusion pump case:
Reviewed: 2026-04-15. Reviewer: RA/QA manager, MedCo Devices. Review question: do scattered programming-confusion signals on Pump Model A warrant labeling-clarity follow-up? Signals reviewed: internal complaints CC-2026-0312 and CC-2026-0388 referencing rate-programming confusion on Pump Model A; field training feedback from Q1 2026 noting similar setup questions at two sites. Evidence considered: complaint history (last 12 months); IFU sections 4.2 and 4.3; the prior labeling review dated 2025-11; ISO 14971 risk file entries H-12 and H-15; IEC 62366 usability engineering notes; public MAUDE-style signal search returned no related public adverse event for the simulated review window. Conclusion (qualified team): review complete; monitor complaint trend for the next two review windows; revisit if a related complaint shows a severity change or a new public signal references the same use scenario. Final RA/QA and QMS decisions remain with the qualified team.
Illustrative example. MedCo Devices and Pump Model A are fictional. The wording is illustrative — every team's voice is different, and the qualified reviewer's exact phrasing belongs to that team.
What it looks like for an RA/QA reader
For an RA/QA reader, the pack opens with a one-page summary of the review question and conclusion. The next pages support that conclusion with the signals, evidence, and decision rationale. The last page captures the next-review recommendation — what to revisit, when, and under what conditions.
Want the sample pack for your device class?
A short sample pack shows what the workspace output looks like for a simulated infusion pump case.
Possible next steps for an RA/QA team
If your team is considering moving review records out of spreadsheets:
- Start with one product family and one review question
- Use the sample pack as a template for the first review record
- Capture the decision log language even for “review complete; no action” outcomes
- Compare against the sample pack format after the first three reviews
Get the sample evidence pack
See the workspace output for an infusion pump review.
Email me the sample evidence pack
Or schedule a walkthrough applied to your device class: Request a Product Review Workspace Demo
Review support only. RA/QA owns the final decision. Not framed as legal counsel, not a regulatory or legal opinion, not a CAPA record. Final RA/QA, regulatory, and QMS decisions remain with the qualified team.
FAQ
Is the evidence pack a CAPA record?
No. It is review support for the qualified team. CAPA records remain in the QMS.
Can the pack be exported to a regulator?
It can be used as supporting context for an internal review or external discussion, but it is not a regulatory filing. The qualified team decides what to file and where.
How is it different from a complaint investigation?
A complaint investigation focuses on one complaint and one product. The evidence pack captures one review question that may span multiple signals, products, or labeling references — including the question's reasoning and the conditions that would reopen it.
Apply this to your device
Pick the lightest-weight first step that works for your week. We’ll reply with available Mountain Time slots within one business day. No deck, no long pitch.
Review support only. We do not provide regulatory or legal determinations. Final RA/QA, regulatory, and QMS decisions remain with your qualified team.
Related Articles
The RA/QA Gap Is Not Evidence Collection. It Is Decision Reuse.
Why similar-device signals need to become structured review points, not just archived narratives or attachments. A four-layer model RA/QA teams can use to turn external signals and internal product events into inspection-ready decisions, with an infusion pump example.
May 18, 2026
PMS ExplainedA QMS Is Required. But Is It Learning?
When a complaint, supplier change, or peer-device recall lands on a reviewer's desk, do all the prior reviews on the same failure mechanism, the same component, and the same risk area come back into the reviewer's pane automatically? Or does the reviewer have to remember to look, hunt across folders, and rebuild the rationale by hand? This article looks at the QMS gap between storing a record and retrieving it on the next event.
May 15, 2026
PMS ExplainedWhy Medical Device RA/QA Teams Need a Product-Specific Compliance Digital Twin
QMS records process completion; a product-specific compliance digital twin records whether compliance work is producing better product-level outcomes. This explainer covers what the digital twin is, how the Product Review Workspace exposes it, and why RA/QA leaders need it now — alongside the QMS, not instead of it.
May 15, 2026