Medical device product development runs across five phases, and each one closes on concrete deliverables: user needs, design inputs, design outputs, verification and validation evidence, and a design package ready for manufacturing transfer.
What Is Medical Device Product Development?
Regulatory compliance is part of every phase, from the first site visit to the last production lot.
What Is the Difference Between Medical Device Design and Development?
Design covers what the device does and how a clinician or patient interacts with it: the intended use, the interface, the form factor, the workflow it has to fit into. Development covers how the device is actually built and proven: architecture, components, code, tolerances, testing, manufacturing readiness.
Medical device design and development is treated as a single regulated activity under ISO 13485 and FDA 21 CFR Part 820, which govern design controls from design inputs through design transfer. Splitting the two in practice is where traceability breaks down, because a design change made without a corresponding development record leaves a gap a regulator will find.
Which Standards and Regulations Apply?
In the US, the backbone is FDA’s Quality Management System Regulation (QMSR). Since February 2, 2026, 21 CFR Part 820 incorporates ISO 13485:2016 by reference, and compliance with it is a regulatory requirement for manufacturers selling in the US.
In plain terms, the same quality management system standard now applies on both sides of the border. MDSAP helps here too: FDA and Health Canada both take part in the program, and FDA can accept an MDSAP audit report in place of a routine inspection.
| Standard | What it covers |
|---|---|
| ISO 14971 | Risk management across the whole device lifecycle |
| IEC 62366-1 | Usability engineering |
| IEC 62304 | The software lifecycle |
| IEC 60601-1 | Basic safety and essential performance of medical electrical equipment |
| ISO 10993-1 | Biological evaluation of materials that contact the body |
The standards in the table appear on both FDA’s and Health Canada’s lists of recognized standards. Following them makes compliance far easier to demonstrate in your submission.
Caroline Lau
Quality Assurance Coordinator at CLEIO
What Are the 5 Key Phases of Medical Device Product Development?
At CLEIO, we run every medical device program through five phases we call IDEAL: Immerse, Define, Elaborate, Adapt and Launch. Together, the five phases cover the design process regulators expect, from user needs and design inputs to verification, validation and design transfer.
One thing to keep in mind before we go through them one by one: the process is iterative. Design, engineering, testing and risk management keep informing one another, so expect to revisit earlier decisions as you learn.
Immerse
Understand the problem and the market
Define
Elaborate
Adapt
Launch
1
Immerse: Understand the Clinical Need and Check Feasibility
Immerse is the first step: it’s where you figure out what problem you’re actually solving, for whom, and in what setting. That means user research, observing clinical workflows alongside healthcare professionals, market research on existing solutions and your first round of regulatory homework.
François Gélinas
Director of Design at CLEIO
2
Define: Turn Research Into Requirements and a Risk Analysis
Define translates what you learned into something engineers can build against and testers can verify: design inputs. Functional requirements, performance requirements, safety requirements, interface behavior, technical constraints and the intended use statement all land here.
And it’s where you answer the regulatory question: what class is your device, and which pathway will it take to market? That answer sets the regulatory requirements you’ll have to meet, and with them your development plan, your compliance documentation and your timeline. If you’re unsure, we break it down in our guide on how to identify the regulatory pathway for your medical device.
3
Elaborate: Develop the Concept Through Prototyping
Elaborate is where the concept becomes a real device. Industrial designers and mechanical, electronic and embedded engineers work in parallel, and medical device prototyping takes you from rough proofs of concept to fully functional prototypes. Proofs of concept are where technical feasibility gets confirmed or ruled out, cheaply.
4
Adapt: Verification and Validation
In Adapt, you test the device to show that it meets its safety and performance requirements. These tests produce most of the evidence regulators will review. Two activities matter a lot here. Verification asks whether you built the device according to its specifications. Validation asks whether you built the right device for its intended use and the people who rely on it.
Verification covers bench testing against each design input, electrical safety and performance testing under IEC 60601-1 for powered devices, and biocompatibility evaluation for materials that contact the body. If your device runs code, that software follows its own lifecycle under IEC 62304, and its verification records feed the same design history file as the hardware. We cover the requirements, safety classes and development steps in our guide to medical device software development.
Validation includes human factors validation testing, also called summative evaluation, built on IEC 62366-1 usability engineering. It’s run on the final design, and FDA’s human factors guidance calls for at least 15 participants from each distinct user population. So if your device is used by both healthcare professionals and patients at home, plan for two groups of at least 15.
5
Launch: Transfer to Manufacturing and Go to Market
Launch is the handoff from development to production. Design transfer makes sure your manufacturing processes reproduce the final, validated design, unit after unit, lot after lot. Before full-scale production begins, you’ll validate the manufacturing process, qualify your suppliers and double-check every label.
Case Study
Discover our case study on how we designed SoundBite's Medical Console
How Long Does Medical Device Product Development Take?
| Device class | Typical pathway | Evidence required | Development timeline |
|---|---|---|---|
| Class I | Most are exempt from premarket submission | General controls and labeling; design controls apply only to Class I devices with automated software and a short list of named device types | Shortest of the three, though quality system and supplier qualification work still apply |
| Class II | 510(k) | Substantial equivalence to a predicate, bench and usability testing | 12 to 24 months |
| Class III | PMA | Clinical data, full design history file | 3 to 5 years |
Where Do Timelines Usually Slip?
- The regulatory pathway gets confirmed too late
If you classify your device as Class II at kickoff and then have to reclassify it while you prepare the submission, you’ll need a new testing plan and a new documentation scope.
- Usability problems surface during summative evaluation
If you run your human factors work after you’ve locked the form factor, you have two options: accept a known use error, or reopen tooling.
- The design history file is assembled after the fact
David Dupuis
Director of the Project Management Office at CLEIO
Should You Build In-House or With a Development Partner?
Across the medical device industry, some manufacturers run product development entirely in-house. Others bring in a partner for part of it, or all of it. In practice, the choice comes down to a few questions about your team, your processes and your schedule.
When In-House Development Makes Sense
In-house development works best when you already operate a certified quality management system with the compliance expertise to maintain it, when your team covers human factors, design, engineering and quality without borrowing people from other programs, and when a steady pipeline of device projects keeps that expertise current.
When to Work With a Development Partner
How CLEIO Handles Medical Device Development
At CLEIO, human factors engineering, industrial design, mechanical and electronic engineering, software and quality work as one team, inside a single ISO 13485 certified quality management system, so design controls and compliance documentation are built into the work as it happens. Our medical device development services cover every phase.
Creating medical devices that are safe, usable and compliant is demanding from start to finish, and it follows a recognizable pattern. Programs that choose their regulatory pathway early, that study real clinical use before locking a form factor, and that build traceability as they go rather than afterwards, reach the market on schedules they can actually defend.
Get a free, 45-minute consultation with our industry-leading experts
Frequently Asked Questions About Medical Device Development
What are the 5 phases of medical device product development?
What is the difference between verification and validation?
How long does medical device product development take?
How does ISO 13485 support medical device product development?
What is the difference between a 510(k) and a PMA?
A 510(k) shows that your device is substantially equivalent to a legally marketed predicate device. It covers most Class II devices and leads to FDA clearance. A PMA requires valid scientific evidence of safety and effectiveness, generally from clinical trials, applies to Class III devices and leads to FDA approval. We compare both, along with De Novo, in our guide to the medical device regulatory pathway.