| Scope boundary | Does the product have a medical intended purpose, act as an accessory, or otherwise fall within Regulation (EU) 2017/745? | Is the product a consumer product placed or made available on the market, with risks that are not already covered by MDR, so a GPSR review is needed? | Do not use GPSR as a shortcut around MDR. Qualify the product under MDR first, then document what remains outside the medical-device file. |
|---|
|
| Covered actors | MDR analysis starts with intended purpose, medical claims, software outputs, IFU statements, accessory use, and user population. | GPSR analysis starts with the product's consumer safety characteristics, its presentation, and whether the product is safe for consumers in normal and foreseeable use. | Preserve claim evidence with the scope decision because a marketing or IFU change can change the regulatory route. |
|---|
|
| Trigger | Annex XVI can bring listed non-medical products into MDR-style controls when common specifications apply. | GPSR is triggered when a consumer product is outside sector-specific rules or when a covered product has risks that are not addressed by those rules. | Beauty, wellness, body-modification, skin-treatment, and similar products need a documented Annex XVI screen before the GPSR side is considered complete. |
|---|
|
| Core obligations | MDR evidence should include qualification rationale, classification rule, technical documentation, clinical evaluation, PMS or PMCF where relevant, vigilance procedures, UDI data, and EUDAMED records. | GPSR evidence should include internal risk analysis, technical documentation, traceability, contact details, instructions and safety information, and recall or accident-response records. | Use a shared evidence index only if each record is tagged to the regime and claim it actually supports. |
|---|
|
| Evidence record | MDR devices need PMS and vigilance routing, including serious-incident and field safety corrective action assessment. | GPSR issues should route to the Safety Business Gateway, consumer warnings, recall notices, and market-surveillance notifications. | Incident intake should ask whether the product is an MDR device, an Annex XVI product, a dual-purpose product, or outside the MDR file. |
|---|
|
| Timing and deadlines | If a medical purpose, accessory relationship, classification rule, Annex XVI category, or MDR PMS/vigilance trigger is present, keep the issue in the MDR workstream. | If none of those MDR anchors applies, treat the matter as a separate general product-safety question and verify current GPSR duties from a GPSR source before acting. | The useful output is a short scope record: product facts, claims reviewed, MDR conclusion, Annex XVI conclusion, open GPSR-source gap, owner, and next review trigger. |
|---|
|
| Enforcement | MDR enforcement focuses on conformity assessment, vigilance, post-market surveillance, and market surveillance for devices in MDR scope. | GPSR enforcement focuses on dangerous consumer products, market surveillance, Safety Gate notifications, and recall handling. | Do not use GPSR as a shortcut around MDR. Qualify the product under MDR first, then document what remains outside the medical-device file. |
|---|
|
| Overlap and reuse | MDR and GPSR can overlap on a product's non-medical risks, but MDR remains the first check when the intended purpose is medical or the product is an accessory or Annex XVI product. | GPSR handles the safety gaps that remain after sector-specific legislation has been checked, including products that are outside MDR scope. | Do not use GPSR as a shortcut around MDR. Qualify the product under MDR first, then document what remains outside the medical-device file. |
|---|
|
| Practical decision rule | Does the product have a medical intended purpose, act as an accessory, or otherwise fall within Regulation (EU) 2017/745? | If not, does the product fall within the consumer-product safety regime and need a GPSR source check for the remaining risks? | Do not use GPSR as a shortcut around MDR. Qualify the product under MDR first, then document what remains outside the medical-device file. |
|---|
|