GB PMSR/PSUR Dual-Report Architecture: How to Structure Post-Market Surveillance Reports for Devices Sold in Both EU and Great Britain
Step-by-step guide to building a dual PMSR/PSUR reporting architecture that satisfies both EU MDR/IVDR and Great Britain SI 2024/1368 requirements — data-period alignment, GB-specific content, MHRA standardized format, FSCA linkage, trend reporting, record retention, and responsible-owner mapping.
This article covers one operational challenge: how to structure your Periodic Safety Update Reports (PSURs) and Post-Market Surveillance Reports (PMSRs) so that a single reporting process satisfies both EU MDR/IVDR requirements and Great Britain's new PMS requirements under SI 2024/1368 (effective 16 June 2025). It provides a side-by-side comparison of both regimes, a unified report template, data-period alignment strategy, GB-specific content sections, and the practical workflow for dual submission.
The UK's Medical Devices (Post-market Surveillance Requirements) (Amendment) (Great Britain) Regulations 2024 (SI 2024 No. 1368) came into force on 16 June 2025. It inserts a new Part 4A into the UK Medical Devices Regulations 2002, establishing PMS obligations for all devices placed on the market or put into service in Great Britain — including CE-marked devices certified under EU MDR/IVDR.
Key Differences: EU MDR vs GB SI 2024/1368
Dimension
EU MDR/IVDR (Articles 84–86, Annex III)
GB SI 2024/1368 (Part 4A)
Practical Implication
Geographic scope
EU/EEA market
Great Britain (England, Scotland, Wales)
Northern Ireland follows EU rules; GB requires separate compliance
PMSR update frequency — Class I / Class A-B IVD
"Updated when necessary"
Every 3 years
GB imposes a fixed cadence for low-risk devices
PSUR update frequency — Class IIa
Every 2 years
Every 2 years
Aligned
PSUR update frequency — Class IIb, III, AIMD / Class C-D IVD
Every year
Every year
Aligned
Record retention
Lifetime of device + period defined in PMS plan
15 years (implantable) or 10 years (other) from end of PMS period
GB retention period is explicit; EU is plan-defined
Incident definition
Defined in MDR Art. 2(64)
Expanded definition including malfunction, deterioration, incorrect use, inadequate labeling
GB is broader
Expected side-effect exclusion
Excludes expected and documented side-effects
No such exclusion
GB requires reporting of expected side-effects if they reach incident threshold
Trend reporting
Statistically significant increase in frequency/severity
Significant adverse impact on risk analysis
GB threshold focuses on risk-analysis impact rather than statistical significance
PSUR bundling
Per device or device category
Per category/group only if same CER/PER and devices are similar
GB bundling criteria are more restrictive
Patient/public engagement
Not explicitly required
PMS plan must consider user experience through patient and public engagement
GB adds qualitative data source
MHRA reporting portal
EUDAMED (EU)
MORE (Manufacturer's On-Line Reporting Environment)
Separate submission channels
PSUR submission to AB
Available to NB upon request
Must be submitted directly to Approved Body
GB is proactive, not reactive
Standardized format
No mandated template
MHRA published standardized PSUR and PMSR templates (June/September 2025)
GB requires specific format
Dual-Report Architecture: Three Options
Option Comparison
Option
Description
Pros
Cons
Recommended When
A: Unified PSUR with GB Annex
Single PSUR document structured to satisfy both EU MDR and GB requirements, with a GB-specific annex
Single maintenance effort; consistent data; AB/NB review in one document
Must carefully address all GB-specific requirements; annex may be lengthy
Device sold in both EU and GB with same risk class; manufacturer has unified PMS system
B: Separate PSURs from shared data
EU PSUR and GB PSUR are separate documents drawing from the same PMS database
Clean separation; each optimized for its audience
Double the document production effort; risk of data inconsistencies
Regulatory strategy requires distinct documents; different NB and AB
C: EU PSUR + GB PMSR (where device is lower risk in one market)
EU requires PSUR; GB only requires PMSR (or vice versa)
Reduced burden for lower-risk market
Must still verify GB content meets all SI 2024/1368 requirements
Device has different classification in EU vs. GB
Recommendation
For most manufacturers, Option A (Unified PSUR with GB Annex) is the most efficient. BSI, the largest UK Approved Body, has confirmed that clients should upload a single PSUR that meets both regulations to the BSI Client Portal, using a cover page to identify which regulations, devices, and data periods are covered.
Add: GB classification if different from EU; UKCA mark status; UK Responsible Person details
RA
Volume of Sales / Exposure Data
EU/EEA sales data, estimated user population
Add: GB sales data broken down by GB and NI; worldwide data for comparison per regulation 44ZM
Commercial / QA
Serious Incidents
Per EU vigilance requirements
Add: GB serious incidents using IMDRF AET codes; investigation conclusion codes per MHRA format; MORE portal reference numbers
Vigilance / QA
Expected Side Effects
Excluded from EU PSUR
Required in GB section: report serious incidents related to side effects using IMDRF AET Annex F codes; investigation conclusion codes per MHRA template
Vigilance / Medical
Trend Reporting
Statistically significant increases
Add: GB trends assessed against risk analysis impact; pre-determined thresholds; MHRA notification status
Vigilance / RA
FSCA Summary
EU FSCAs with dates and scope
Add: GB-specific FSCAs with MORE portal reference numbers; FSN final dates; regions impacted; linkage to prior PSURs
Vigilance / RA
PMCF / Clinical Data
PMCF findings, literature review, CER updates
Add: GB-specific clinical data if available; patient/public engagement findings per regulation 44ZF(3)(v)
Clinical / RA
Risk Management Update
Updated risk-benefit assessment per ISO 14971
Add: GB-specific residual risk assessment; impact on UK risk analysis
Risk Mgmt
Corrective and Preventive Actions
CAPA summary
Add: GB-specific CAPAs; MHRA notification records
QA
Technical Documentation Updates
Changes to IFU, labeling, design
Add: UKCA labeling changes; UK RP notification records
RA
Conclusions
Overall benefit-risk conclusion
Add: Separate GB benefit-risk conclusion; statement on continued GB market placement
Medical / RA
GB Annex (if applicable)
N/A
Detailed GB data tables per MHRA standardized format; GB/NI sales breakdown; patient engagement findings; MHRA-specific IMDRF coding
RA
Data-Period Alignment Strategy
Challenge
EU PSURs are updated on a rolling basis from the date the device is placed on the EU market. GB PSURs are due within 1 year (Class IIb/III) or 2 years (Class IIa) of the device being placed on the GB market after 16 June 2025 — or within the same period from 16 June 2025 for devices already on the market.
Alignment Decision Tree
Q1: Was the device first placed on the EU market
before 16 June 2025?
├── YES → Q2
└── NO (launched after 16 June 2025) → Q3
Q2: Was the device already registered with MHRA
and sold in GB before 16 June 2025?
├── YES → GB PSUR data period starts 16 June 2025
│ (saving provision in SI 2024/1368)
│ Align EU data period to include this date
│ if possible
└── NO → GB PSUR data period starts from GB placement date
Q3: Launch dates in EU and GB are close together?
├── YES → Use a single data period covering both markets
└── NO → Overlapping data periods; extract GB data
from shared PMS database for GB-specific sections
Data-Period Alignment Table
Scenario
EU Data Period
GB Data Period
Strategy
Device on EU market 2022, on GB market 2022
Per MDR schedule (e.g., annual)
Starts 16 June 2025; first GB PSUR due by 16 June 2026 (Class IIb/III) or 16 June 2027 (Class IIa)
Time the next EU PSUR to cover the GB period; include GB data as a subset
Device launched in both markets simultaneously in 2026
From launch date
From launch date
Single data period; one unified PSUR
Device on EU market only, GB launch planned 2027
From EU launch
From GB launch (2027)
EU PSUR covers EU data; first GB PSUR triggered at GB launch
FSCA Identified
│
├── EU Notification
│ ├── Notify NB via EUDAMED (if applicable)
│ ├── Submit FSN to national competent authorities
│ └── Document in EU PSUR
│
├── GB Notification
│ ├── Submit FSN to MHRA via MORE portal
│ ├── Use MHRA FSN template
│ ├── Report to UK Responsible Person
│ └── Document in GB PSUR section
│
└── Cross-Reference
├── Link FSCA reference numbers (EU + GB)
├── Confirm scope alignment (same devices affected?)
└── Ensure corrective action timeline meets
both EU and GB requirements
FSCA Summary Table for Dual PSUR
FSCA Reference (EU)
FSCA Reference (GB/MORE)
Device(s) Affected
Date Reported (EU)
Date Reported (GB)
Reason
Regions
Status
Linked to Prior PSUR?
FSCA-2025-001
MIR-GB-2025-0045
Model X, UDI-DI 12345
2025-03-15
2025-03-16
Needle guard failure
EU + GB
Closed
No
FSCA-2025-002
MIR-GB-2025-0067
Model Y, UDI-DI 67890
2025-07-01
2025-07-02
Labeling error
EU + GB
Open
Yes (PSUR 2024)
Practical Workflow: Building the Dual PSUR
Step-by-Step Process
Step
Activity
Owner
Timeline
Output
1
Confirm data period covers both EU and GB requirements
RA
T-60 days
Agreed data period
2
Extract EU PMS data from PMS database
QA / Vigilance
T-50 days
EU data package
3
Extract GB PMS data (GB/NI sales, GB incidents via MORE, GB FSCAs)
QA / Vigilance
T-50 days
GB data package
4
Code GB incidents using IMDRF AET Annex D and F
Vigilance
T-45 days
Coded GB incident tables
5
Document patient/public engagement findings (GB)
Clinical / RA
T-40 days
GB engagement summary
6
Compile unified PSUR using shared template
RA
T-30 days
Draft PSUR
7
Internal review (medical, QA, legal)
Cross-functional
T-20 days
Reviewed PSUR
8
Upload to NB portal (EU) and AB portal (GB)
RA
T-10 days
Submitted PSUR
9
Submit to MHRA upon request (GB)
RA
As requested
MHRA submission
10
File in PMS archive with dual-regulation index
QA
T-0
Archived PSUR
Common Failure Modes and How to Remediate
Failure Mode
Root Cause
How to Remediate
GB sales data not available
GB sales not tracked separately from EU
Implement GB-specific sales tracking in ERP/logistics system; require UK RP to provide market data
GB incidents not coded with IMDRF AET
Vigilance team used EU coding only
Train vigilance staff on IMDRF AET; add MHRA coding requirements to vigilance SOP
Patient/public engagement missing from GB section
No GB-specific user feedback collected
Add GB patient feedback collection to PMS plan; include in complaint analysis SOP
PSUR cover page does not identify both regulations
Template only referenced EU MDR
Update PSUR template to include regulation 44ZM reference and AB certificate numbers
FSCA dates misaligned between EU and GB
EU and GB notifications submitted at different times
Align FSCA notification timelines; submit to MHRA within same 24-hour window as EU
Record retention period too short
Company used EU plan-defined period which was shorter than GB 10/15 year requirement
Set global retention policy to minimum 15 years for implantables, 10 years for others
Trend reporting threshold mismatch
EU statistical threshold applied to GB data
Define separate GB trend threshold based on "significant adverse impact on risk analysis" language
PSUR bundling not permitted under GB rules
EU PSUR bundled by device family; GB requires same CER/PER