The MDR of 5 April 2017 requires every manufacturer's quality management system to include "a strategy for regulatory compliance, including compliance with conformity assessment procedures and procedures for management of modifications" (Article 10(9)). Article 15 created the person responsible for regulatory compliance (PRRC). In the US, the Quality Management System Regulation (21 CFR Part 820, incorporating ISO 13485:2016 by reference) took effect on 2 February 2026 (FDA).
Regulatory affairs (RA) is a set of legal obligations that runs from the first intended purpose statement to the last software update. This article covers each RA task across the lifecycle with its EU and US legal basis, and the PRRC role.
The lifecycle at a glance
| Lifecycle stage | EU anchor | US anchor | Source |
|---|---|---|---|
| Qualification | MDR Art. 2(1); MDCG 2019-11 | Device definition | MDR; FDA |
| Classification | MDR Art. 51, Annex VIII | Class I, II or III | MDR; FDA |
| Regulatory strategy | MDR Art. 10(9) | 510(k), De Novo, PMA; IDE (21 CFR 812) | MDR; FDA |
| Technical documentation and QMS | MDR Art. 10(4), 10(9), Annexes II and III | 21 CFR Part 820 (QMSR) | MDR; FDA |
| Conformity assessment and premarket | MDR Art. 52; declaration of conformity (Art. 10(6)) | Premarket submission | MDR; FDA |
| Registration | MDR Art. 29 and 31 | 21 CFR 807 | MDR; FDA |
| Post-market surveillance and vigilance | MDR Art. 83 to 87 | 21 CFR 803 | MDR; FDA |
| Change control | MDR Art. 10(9); Annex VII Section 4.9 | Software change guidance | MDR; FDA |
Sources: MDR; FDA Overview of Device Regulation.
In our view, RA starts with the intended purpose. Qualification, class, route and evidence all follow from it.
Qualification and classification
Under MDR Article 2(1), software can be a medical device in its own right. MDCG 2019-11 Rev.1 explains how to qualify and classify software. In the US, FDA's Classify Your Medical Device page starts with whether the product meets the device definition.
Under the MDR, the class follows from the rules in Annex VIII (Article 51), including Rule 11 for software, explained in MDCG 2019-11 and MDCG 2021-24 Rev.1. FDA uses Class I, II and III, with regulatory control increasing from Class I to Class III.
Strategy, documentation and conformity assessment
Article 10(9) makes the regulatory strategy part of the quality management system. In the US, the main routes are 510(k), De Novo and PMA, with an investigational device exemption under 21 CFR 812 for clinical studies. FDA feedback can be requested through the Q-Submission Program before a submission. Our article on regulatory strategy for the EU and US covers the planning.
The manufacturer draws up and keeps the technical documentation up to date (Article 10(4); Annexes II and III). The applicable conformity assessment procedure, including any notified body involvement, follows from Article 52. The manufacturer then draws up the EU declaration of conformity (Article 10(6)). Our article on SaMD technical documentation covers its structure for software.
In the US, the QMSR sets the quality system requirements, and the premarket route depends on the device type.
In our view, RA output is a set of controlled records: the strategy, technical documentation, registrations, PMS and change assessments. It is not a department.
Registration
| Obligation | Rule | Source |
|---|---|---|
| Device registration in EUDAMED | MDR Art. 29 | MDR |
| Actor registration (manufacturers, authorised representatives, importers) | MDR Art. 31 | MDR |
| Update of actor data, including PRRC details | Within one week of a change | MDR Art. 31(4); MDCG 2019-7 |
| US establishment registration and listing | 21 CFR 807; annually between 1 October and 31 December | FDA Overview of Device Regulation |
Sources: MDR; MDCG 2019-7 Rev.1; FDA.
Post-market surveillance, vigilance and change control
Under the MDR, Articles 83 to 86 set out post-market surveillance, and Article 87 covers reporting of serious incidents and field safety corrective actions. MDCG 2023-3 Rev.2 explains the vigilance terms. Our article on post-market surveillance covers the EU and US requirements.
In the US, according to FDA's mandatory reporting page, manufacturers report under 21 CFR 803 within 30 calendar days, and 5-day reports within 5 work days.
Change control starts from the "management of modifications" in Article 10(9). Where a notified body is involved, the manufacturer must inform it of planned changes before they are implemented (Annex VII Section 4.9, as cited in MDCG 2019-7). For US 510(k) devices, FDA's October 2017 guidance Deciding When to Submit a 510(k) for a Software Change helps decide whether a new submission is needed.
The PRRC
MDCG 2019-7 Rev.1 (December 2023) explains Article 15.
Qualification (Article 15(1)):
(a) a diploma, certificate or other formal qualification in law, medicine, pharmacy, engineering or another relevant scientific discipline, plus at least one year of professional experience in regulatory affairs or quality management systems for medical devices; or
(b) four years of professional experience in regulatory affairs or quality management systems for medical devices.
Availability: micro and small enterprises do not need the PRRC within their organisation, but must have one "permanently and continuously at their disposal" (Article 15(2)). The role can therefore be subcontracted.
Duties (Article 15(3)): the PRRC is responsible for ensuring at least that:
(a) device conformity is checked under the quality management system before release;
(b) the technical documentation and EU declaration of conformity are drawn up and kept up to date;
(c) post-market surveillance obligations are met;
(d) reporting obligations are fulfilled;
(e) for investigational devices, the statement in Annex XV Chapter II Section 4.1 is issued.
The PRRC must suffer no disadvantage within the organisation for carrying out these duties (Article 15(5)). An authorised representative must also have a PRRC permanently and continuously at its disposal (Article 15(6)); according to MDCG 2019-7, this cannot be the same person as the non-EU manufacturer's PRRC. Our article on the role of the PRRC covers the role in more detail.
In our view, the PRRC checks that the RA system works, but the legal responsibility stays with the manufacturer.
A hypothetical example
Hypothetical example: a Dutch start-up develops symptom-triage software.
Intended purpose: it documents the intended purpose and checks qualification against MDCG 2019-11.
Class: it applies Rule 11 and records the rationale.
Strategy: it sets its regulatory strategy under Article 10(9).
Documentation: it builds the technical documentation under Annexes II and III.
PRRC: as a small enterprise, it appoints an external PRRC under Article 15(2).
Registration: it registers as a manufacturer and registers its device (Articles 31 and 29).
After launch: it runs post-market surveillance and vigilance, and assesses each release under its change procedure.
Conclusion
Regulatory affairs covers qualification, classification, strategy, documentation, conformity assessment, registration, post-market surveillance and change control, each with its own legal basis in the EU and US. The PRRC checks that these obligations are met.
In our view, start with the intended purpose, keep every RA decision as a controlled record, and give the PRRC the access needed to check them.
If you need help setting up regulatory affairs for your device, our regulatory strategy team can help, or contact MedQAIR.
Frequently asked questions
What does regulatory affairs do in a SaMD company?
It qualifies and classifies the software, sets the regulatory strategy, maintains the technical documentation, handles registrations, post-market surveillance and vigilance, and assesses changes.
Is the PRRC the same as the regulatory affairs manager?
Not necessarily. The PRRC is a legal role under Article 15 with specific qualifications and duties. An RA manager can hold it if they meet the requirements.
Can a small company outsource the PRRC?
Yes. Micro and small enterprises may have the PRRC permanently and continuously at their disposal instead of within the organisation (Article 15(2)).
Does every software update need a new submission?
No. Each change is assessed under the change procedure. Where a notified body is involved, it must be informed of planned changes; in the US, FDA's software change guidance helps decide for 510(k) devices.
Classification or strategy first?
Classification. The strategy depends on the class, and the class depends on the intended purpose.