Great Britain’s PMS Requirements Are in Force: What Manufacturers Should Do Now
Great Britain’s strengthened post-market surveillance requirements are now in force. Learn how medical device and IVD manufacturers should connect PMS plans, complaints, vigilance, trend analysis, and reports.
By Melita Ball

Great Britain's strengthened post-market surveillance requirements are now in force. For medical device and IVD manufacturers placing devices on the GB market, PMS is no longer something to refresh only before an audit, certificate review, or regulator question.
It must operate continuously.
The MHRA's updated framework places greater emphasis on active monitoring, structured PMS systems, vigilance, trend analysis, and timely action when safety or performance signals appear. For manufacturers, the practical challenge is not just knowing the requirement. It is connecting the people, data, records, and decisions that make PMS work.
The short answer
Post-market surveillance is becoming a real-time operating system for product safety, performance, and lifecycle control.
If PMS data lives in disconnected complaint logs, service records, spreadsheets, customer support notes, distributor emails, and periodic reports, the manufacturer may not see risk early enough or explain decisions clearly enough.
Why GB PMS matters now
The new PMS requirements apply to medical devices placed on the market or put into service in Great Britain from June 16, 2025 onward. They are part of a broader reform direction intended to strengthen patient safety, improve traceability, and enable faster response to emerging issues.
Even manufacturers with mature EU MDR or IVDR PMS processes should not assume GB readiness is automatic. GB has its own regulatory framework, its own reporting expectations, and its own market access responsibilities. Companies selling into multiple jurisdictions need a way to maintain market-specific obligations without creating separate, conflicting PMS systems.
Where manufacturers feel the pressure
PMS plans must be usable, not theoretical
A PMS plan should describe how the manufacturer collects, evaluates, and acts on post-market information. Too often, PMS plans are generic documents written to satisfy a documentation expectation.
A useful plan should answer practical questions:
- What data sources are monitored?
- Who reviews each source?
- How often are trends evaluated?
- What thresholds trigger escalation?
- How are vigilance decisions made?
- How are risks updated?
- How are CAPA and field actions considered?
- How are PMS outputs documented and approved?
If the plan does not match daily operations, it will fail when the company needs it most.
Complaint handling and PMS are too often separated
Complaints are one of the most important inputs into PMS, but they are not the only input. Service data, repairs, customer feedback, adverse incidents, returns, literature, registry data, clinical follow-up, production nonconformities, distributor feedback, and user training issues may all contribute to the post-market picture.
Manufacturers need a system that connects complaint handling to broader PMS analysis. Otherwise, the company may resolve individual complaints while missing the trend.
Trend signals need decision rules
Trend analysis is difficult when the organization has no defined signal thresholds. How many similar complaints are enough to trigger escalation? What level of severity requires immediate review? When does a service pattern become a quality investigation? When does a usability issue require labeling review?
The answer depends on the device, risk profile, population, use environment, and prior evidence. The key is to define the decision rules before the signal appears.
PMS must feed risk management
Post-market data should update the manufacturer's understanding of risk. If a new failure mode appears, an expected failure occurs more often than anticipated, or a known hazard has a different severity pattern, the risk file may need review.
This is where many systems break down. PMS reports are created, but risk files remain unchanged. CAPAs are opened, but product risk and labeling are not reassessed. Field feedback is discussed, but design inputs for future changes are not updated.
A strong PMS process closes the loop.
Reports should be outputs of controlled evidence
PMS reports should not be manual writing projects assembled from scattered files. They should be outputs of a controlled monitoring process.
That means source data, review decisions, trend analyses, risk updates, CAPA links, vigilance assessments, and conclusions should be traceable. When a report states that no corrective action was required, the company should be able to show how that conclusion was reached.
A practical GB PMS readiness check
Manufacturers can start with a focused review of one device family placed on the GB market.
Ask:
- Is there a current PMS plan for the device?
- Does the plan identify all relevant post-market data sources?
- Are review responsibilities and frequencies defined?
- Are complaint, incident, service, distributor, literature, and user feedback inputs connected?
- Are trend thresholds and escalation rules documented?
- Are vigilance reporting decisions recorded with rationale?
- Are CAPA, risk management, labeling, and design change processes linked to PMS outputs?
- Can the team produce the evidence behind the PMS report without manual reconstruction?
If the answer depends on one person's memory, that is a system risk.
What good looks like in practice
A mature PMS system works like a feedback network. Data comes in from complaints, customers, service, distributors, literature, clinical sources, vigilance systems, and production. The system routes signals to the right owners. Quality evaluates recurrence and severity. Regulatory evaluates reportability and market obligations. Risk management is updated when new information changes the risk profile. CAPA is opened when systemic correction is needed. Design and labeling changes are assessed when product improvement is required. Leadership sees meaningful trends through management review.
That operating model makes PMS more than a report. It becomes a disciplined way to keep the device controlled after launch.
Key takeaways
- Great Britain's strengthened PMS requirements are now in force for applicable devices placed on the GB market or put into service from June 16, 2025 onward.
- Manufacturers should review whether PMS plans reflect real operations.
- Complaint handling, vigilance, service data, trend analysis, CAPA, risk management, and lifecycle change should be connected.
- PMS reports should be traceable outputs of controlled evidence, not last-minute manual summaries.
- A modern compliance platform helps global manufacturers manage market-specific PMS obligations without fragmenting the quality system.
How IntelaSolve helps
IntelaSolve supports post-market surveillance, vigilance, complaints, CAPA, risk management, regulatory reporting, quality events, and lifecycle change in one compliance infrastructure platform. For manufacturers selling in Great Britain, the EU, the United States, Canada, and other global markets, IntelaSolve helps keep post-market evidence connected, current, and ready for regulatory review.
Request early access to IntelaSolve or complete the Compliance Readiness Analysis to evaluate whether your PMS system is ready for market-specific obligations across the full regulatory lifecycle.
