The EU Medical Device Regulation (MDR 2017/745) is one of the most comprehensive regulatory frameworks for medical products worldwide. For emerging MedTech companies, navigating EU MDR compliance can feel complex, documentation-heavy, and difficult to structure.
During the webinar From R&D to Market: IP and Regulatory Strategy Across the Product Life Cycle, Anne-Sophie Grell explained that MDR is best understood as a development framework rather than a submission exercise.
When regulatory requirements are integrated into product development from the start, they strengthen product quality, regulatory readiness, and market access. When they are addressed late in the development process, they often lead to costly remediation, delays, and additional regulatory complexity.
So what does MDR compliance actually require for an emerging MedTech company?
1. Start with Product Qualification and Get It Right
The first critical step is determining whether your product qualifies as a medical device under EU MDR.
Product qualification determines:
- The applicable conformity assessment pathway
- The level of clinical evidence required
- The involvement of a Notified Body
- The complexity of the technical documentation
Anne-Sophie highlighted that qualification is not always straightforward. Many products sit at the boundary between regulatory categories, for example between:
- Medical devices and medicinal products
- Medical devices and cosmetic products
In these cases, the intended use of the product becomes the determining factor.
💡 Clearly define intended use early to determine product qualification at the beginning of development. This helps avoid costly regulatory changes, redesign efforts, or documentation adjustments later in the product lifecycle.
2. Build Your Quality Management System from the Start
Another key message from the webinar was the importance of implementing a Quality Management System (QMS) early in development.
Under MDR, manufacturers must establish a quality management system that goes beyond simple certification against ISO 13485. While ISO 13485 remains a central standard, MDR requires broader integration of regulatory, quality, and lifecycle management processes.
However, a QMS should not be viewed merely as a regulatory requirement. It is the operational backbone of product development.
A well-implemented QMS defines:
- How development activities are documented
- How risk management is performed
- How manufacturing processes are controlled
- How post-market obligations are managed
Anne-Sophie emphasised that the QMS must function as a real operational system rather than a static set of documents. It should support how teams work across management, human resources, engineering, regulatory affairs, and quality functions.
💡 Invest in cross-functional training. Engineers, scientists, and quality professionals must understand the regulatory framework in which they are developing products. This ensures that the entire development team understands the requirements that will ultimately shape the product.
3. Follow the Design and Development Process Formally
A significant portion of MDR technical documentation relates to the design and development process.
During the webinar, Anne-Sophie illustrated this using a simple example: a coffee cup. The example demonstrated the logic behind design control.
The process follows a structured sequence:
- User needs define the intended functionality of the product.
- These needs translate into design inputs.
- Design inputs lead to design outputs, which describe how the product is built.
- Outputs are verified against the inputs.
- The final product is validated against the original user needs.
This structured development process must be clearly documented. Notified Bodies need to see evidence that development followed defined procedures and that design decisions were verified and validated systematically.
Manufacturers must also identify and apply the relevant standards for their device. Typical examples include:
- ISO 14971 for risk management
- ISO 13485 for quality management systems
- IEC 62304 for software lifecycle processes, where applicable
💡 Apply these standards from the start. They help demonstrate compliance with MDR requirements and provide a structured framework for development activities.
4. Understand the Evolving MDR Regulatory Landscape
Anne-Sophie also discussed the evolving regulatory environment surrounding MDR.
In December 2025, the European Commission proposed amendments aimed at addressing industry concerns regarding regulatory complexity and capacity constraints among Notified Bodies.
These proposed changes include:
- Simplifying certain administrative requirements
- Addressing specific classification challenges
- Introducing more flexibility in areas such as audits
However, the core objectives of MDR remain unchanged. Patient safety, robust clinical evidence, and high product quality remain the foundation of the regulation.
💡 Stay informed on regulatory updates, but don't delay compliance efforts waiting for simplifications. The fundamental regulatory expectations remain high for emerging MedTech companies.
5. CE Marking Is the Beginning, Not the End
One of Anne-Sophie's central messages during the webinar was that CE marking marks the start of the product lifecycle rather than the end of the regulatory journey.
Post-market obligations under MDR are extensive and ongoing. These include:
- Post-Market Surveillance (PMS)
- Periodic Safety Update Reports (PSUR)
- Post-Market Clinical Follow-Up (PMCF)
- Maintaining UDI registration
- Incident and vigilance reporting
The UDI module of EUDAMED is already mandatory, meaning traceability of medical devices is now a live requirement rather than a future one.
💡 Account for post-market responsibilities in your operational planning and budgets during early product development. CE marking is a milestone, not the finish line.
The Bigger Picture: MDR as a Development Framework
MDR compliance for emerging MedTech companies can seem demanding. However, as Anne-Sophie emphasised during the webinar, it becomes significantly more manageable when it is treated as a development framework rather than a submission checklist.
Companies that succeed under MDR are those that:
- Integrate regulatory thinking early
- Build a real and operational quality management system
- Define product qualification and intended use clearly
- Structure development according to formal design control principles
- Plan for the full product lifecycle, including post-market activities
In other words, regulatory strategy should not begin shortly before CE marking. It should shape how the product is designed, developed, documented, and maintained from the very beginning.
Speak to Our Regulatory Experts
QbD Group supports MedTech companies in navigating the full MDR compliance journey — from early development strategy and technical documentation to CE marking and post-market obligations.
Speak to our regulatory experts →
Or watch the full webinar on demand →
This article is based on the QbD × Gevers × Biovia webinar: From R&D to market: IP and regulatory strategy across the product life cycle, held on 26 February 2026. Speakers: Anne-Sophie Grell (QbD Group) and Stijn Lagaert (Gevers).
关于作者
PhD Physics, MSc Medical Physics · Manager Regulatory Affairs – Medical Devices
Anne-Sophie is a Regulatory Affairs leader with over two decades of experience in medical physics, diagnostic imaging, and medical device regulation. She supports clients navigating EU MDR, FDA, and international regulatory frameworks.
Navigate Regulatory Complexity with Confidence
Navigate complex regulatory landscapes with expert guidance across pharmaceuticals, medical devices, and IVD.
Read more
