Product Review Workspace for Medical Device RA/QA Teams

When something happens with a medical device product, RA/QA teams often have to answer a practical question before they can decide what to do next:

What exactly should we review, what evidence do we need, which QMS path may apply, and how do we document the rationale?

That question can appear in many situations.

A complaint comes in. A repair trend starts to appear. A supplier issue needs review. A software signal raises a question. A field event needs triage. A change request needs impact assessment. A standard, SOP, or guidance document is updated.

In each case, the RA/QA team is not just reading a regulation in the abstract. The team has to apply it to a specific product, a specific workflow, a specific record, and a specific decision.

That is why TrueMedDevice is building a Product Review Workspace for medical device RA/QA teams — a product-centered review file that organizes evidence, public signals, comparable incidents, standards and SOP references, product-specific review points, candidate workflow paths, rationale prompts, supplier evidence asks, and Evidence Record Drafts around the affected product.

What is a Product Review Workspace?

A Product Review Workspace is a product-centered review file for a medical device product or product family.

It brings together the information RA/QA teams need when a product event triggers a review question.

Instead of scattering the review across emails, spreadsheets, public databases, SOP documents, standards, previous records, and ad hoc notes, the workspace organizes the review around the affected product.

It can help bring together:

• product events and review triggers
• public signals and comparable incidents
• applicable standards, SOPs, and guidance
• product-specific review points
• candidate QMS workflow paths
• rationale prompts
• supplier evidence asks
• Evidence Record Drafts

The purpose is simple:

Help RA/QA teams see the evidence, review the options, decide what to do next, and leave a better-documented record.

The final decision still remains with the qualified RA/QA team.

Why this matters for RA/QA teams

There is a lot of useful regulatory and quality content available today.

You can find posts, articles, and guidance explaining ISO 13485, ISO 14971, FDA QSR requirements, complaint handling, CAPA, PMS, supplier controls, software changes, usability, and risk management.

That content is helpful.

But RA/QA work usually becomes difficult at the next step:

How do we apply this general guidance to our specific device?

For example, a general explanation of ISO 14971 can describe risk management principles. But when a complaint or field signal occurs, the team still has to ask:

• Does this signal affect our product risk file?
• Is this similar to an issue seen in comparable devices?
• Does this require supplier follow-up?
• Is this only a complaint investigation, or does it also need CAPA screening?
• Does this affect labeling, usability, software, design controls, or post-market surveillance?
• What evidence should be collected before deciding?
• What rationale should be documented?

A general article cannot answer those questions for a specific infusion pump, IV set, software-enabled device, sterile product, reusable device, or supplier-dependent component.

A Product Review Workspace is designed to close that gap.

It turns general standards, SOPs, guidance, and public signals into product-specific review points.

What the workspace helps organize

The Product Review Workspace is not just a document repository. It is a structured review environment around a product.

1. Evidence and public signals

The workspace can organize public signals, comparable incidents, recalls, safety communications, enforcement history, adverse event patterns, and other source-backed information relevant to the product or product family.

The goal is to help the RA/QA team see the broader picture before deciding what to do next.

2. Standards and SOP mapping

A major value of the workspace is mapping general requirements to the product’s actual review workflow.

Instead of saying, “Here is ISO 13485,” or “Here is ISO 14971,” the workspace helps ask:

What does this requirement mean for this product, this event, and this QMS decision?

That may include mapping standards, regulations, guidance, and internal SOPs to specific review questions, decision points, and documentation needs.

3. Device-specific review points

Different products need different review logic.

An infusion pump does not raise the same review questions as a sterile single-use device. A software-enabled device does not raise the same questions as a purely mechanical product. A supplier-controlled component may require a different review path than an internal manufacturing issue.

The workspace helps convert broad RA/QA concepts into practical, product-specific review points.

4. Candidate workflow paths

The workspace can help organize possible next steps, such as:

• complaint investigation
• supplier follow-up
• risk file review
• change-control screening
• CAPA screen
• PMS input
• management review input
• regulatory-reporting consideration

These are not automatic decisions. They are candidate paths for qualified RA/QA review.

5. Evidence Record Draft

The output is an Evidence Record Draft.

This is a source-backed draft that captures what was reviewed, what evidence was considered, which review points were raised, what rationale may be needed, and what still requires RA/QA judgment.

The draft is not the final QMS decision.

It is a structured starting point for the team to edit, override, approve, and file according to its own QMS process.

When would RA/QA use it?

The Product Review Workspace is designed for product-event review moments. Typical triggers include:

Complaint or repair trend

A complaint pattern or repair / service trend appears, and the team needs to decide whether the issue requires further investigation, risk review, supplier evidence, CAPA screening, or PMS input.

Supplier issue or supplier change

A supplier issue, material change, component change, or supplier communication raises a question about impact, evidence, and QMS workflow.

Software signal or software change

A software anomaly, update, cybersecurity signal, or field feedback raises a review question that needs structured evidence and workflow consideration.

Field event or safety signal

A field event or external signal needs triage against the product’s intended use, known risks, comparable incidents, and possible reporting or escalation paths.

Change question

A product, process, labeling, software, supplier, or manufacturing change needs review before the team decides what QMS record should be opened or updated.

Standard, SOP, or guidance update

A new or revised standard, guidance document, regulation, or internal SOP may affect how the product should be reviewed. The workspace helps compare what changed, what may matter to the product, and whether the product-specific review workflow should be updated.

The key advantage: not generic guidance

This is the most important difference.

A Product Review Workspace is not just another general regulatory article, checklist, or template.

It is mapped to the product.

That means the review points, workflow options, standards mapping, and evidence structure can be adapted to the device, product family, intended use, risk profile, supplier dependencies, software profile, and QMS process.

It also means the workspace can improve over time.

When a new public signal appears, the workspace can help assess whether it is relevant to the product. When a standard or guidance document is updated, the workspace can help identify what changed and how that change may affect the product-specific review points. When a team completes a review, the review logic can become part of the product’s accumulated review knowledge.

The result is a reusable, improving review workflow around the product.

The team does not need to start from a blank page every time.

What RA/QA gets from the workspace

A Product Review Workspace can help RA/QA teams move from scattered information to a clearer review process. The team gets:

• a product-specific review page
• organized public signals and comparable incidents
• mapped standards, SOPs, and guidance considerations
• device-specific review points
• candidate QMS workflow paths
• rationale prompts
• supplier evidence questions
• an Evidence Record Draft
• a reusable workflow that can improve over time

This can support better documentation, clearer decision-making, and a more traceable review record.

What this is not

TrueMedDevice’s Product Review Workspace is designed to support qualified RA/QA teams.

• It does not replace the QMS.
• It does not make legal or regulatory determinations.
• It does not certify compliance.
• It does not decide whether a product is safe, marketable, reportable, or compliant.
• It does not replace the judgment of qualified RA/QA professionals.

Instead, it helps organize the review before the team opens, updates, or closes a formal QMS record.

Why start with one product family?

The best way to use a Product Review Workspace is to start narrow.

Instead of trying to build a broad compliance system across every product and every process, the workspace can begin with one product family and one review use case.

For example:

• one infusion pump product family
• one IV administration set product family
• one complaint trend review
• one supplier issue workflow
• one software signal workflow
• one change-control screening workflow
• one guidance update review

Starting narrow makes the review concrete.

It allows the workspace to be built around real product information, real review points, real QMS paths, and real RA/QA decisions.

That is where the value becomes visible.

Summary

TrueMedDevice’s Product Review Workspace for medical device RA/QA teams helps turn product events, public signals, standards, SOPs, guidance, and comparable incidents into product-specific review points.

It is designed for the moment when RA/QA needs to decide:

• what to review
• what evidence matters
• which workflow path may apply
• what rationale should be documented
• what record draft should be prepared

It is not generic guidance. It is not a QMS replacement. It is not an automated regulatory determination.

It is a product-specific review workspace that helps RA/QA teams make clearer, better-documented, source-backed decisions before opening, updating, or closing a QMS record.

Start with one product family

Review support only. Not legal advice, not a regulatory determination, and not a QMS replacement. Final decision remains with your qualified RA/QA team.

FAQ

Is a Product Review Workspace a QMS replacement?

No. The Product Review Workspace is review support before the team opens, updates, or closes a formal QMS record. It does not replace the QMS, does not make regulatory determinations, and does not decide reportability, CAPA need, or marketability. The final decision remains with the qualified RA/QA team.

How is this different from generic ISO 13485 or ISO 14971 guidance?

General guidance describes principles. A Product Review Workspace maps those principles to a specific device, product family, intended use, supplier profile, software profile, and review event — turning general standards, SOPs, and guidance into product-specific review points and candidate workflow paths.

What is a Product Event Review?

A Product Event Review is one structured review triggered by a product event — a complaint, repair / service signal, supplier issue, software anomaly, field event, change question, or similar trigger. Each Product Event Review files under a Product ID so reviews stay tied to the same device, identifiers, and evidence history over time.

What is an Evidence Record Draft?

An Evidence Record Draft is a dated, source-backed draft that captures what was reviewed, what evidence was considered, which review points were raised, what rationale was documented, and what still requires RA/QA judgment. RA/QA edits, overrides, approves, and files the draft according to the team’s QMS process. The draft is a structured starting point, not a final QMS decision.

Which review situations does the workspace support today?

The current MVP focuses on complaint investigation support, repair / service trend review, supplier issue or supplier-change review, software anomaly or software-change review, field event / safety signal review, change-control screening, CAPA screen support, PMS / management-review input, and regulatory-reporting consideration support. The workspace organizes the evidence and surfaces candidate workflow paths — it does not make the determination.

How do we start?

Start narrow. Pick one product family and one event type, then build the Product Review Workspace around that. The narrower the starting scope, the faster the review logic becomes concrete and the easier it is to see the value before broadening to more products and more workflows.