Medical device product development is the process of taking a device from an identified clinical need to a product that is cleared or approved for market and monitored once patients use it. Every stage, from the first design inputs to post-market surveillance, has to leave a documented record that shows the device does what it was designed to do and stays safe in use.
Most published stage lists stop at the stage names: ideation, prototyping, testing, launch. They rarely say which regulation applies to each step or which record you will be asked to produce. Both follow the chain of evidence that connects the stages. You translate user needs into design inputs and develop outputs to meet those inputs. You verify each output against its input and validate the finished device against the user needs. You trace risk controls into requirements and tests along the same chain and reassess it after every change following a design review. When an auditor asks for your evidence, this chain is what they follow.
What Is Medical Device Product Development?
Medical device product development is a regulated lifecycle in which the engineering work and the evidence for that work are produced together. Under the FDA’s Quality Management System Regulation (QMSR), the core requirements come from ISO 13485:2016, which the QMSR incorporates by reference. ISO 13485 sets the quality management system requirements for companies that design and manufacture medical devices. Its design and development clause defines the steps you work through in this process.
The 2016 edition of ISO 13485 is still the current one. ISO last reviewed and confirmed the ISO 13485:2016 standard in 2025.
The lifecycle runs well past launch. Risk management under ISO 14971 applies from the first concept of a device until it is decommissioned and disposed of, so the development record stays open for as long as the device is on the market. A team that treats development as engineering only, and leaves the documentation for later, has to rebuild the evidence after the fact. An auditor usually finds the gaps at that point.
What Are the Stages of the Medical Device Development Process?
A medical device development program can be organized into seven practical stages. Each stage produces records that support the development file, while formal design reviews are conducted at suitable stages defined in the design and development plan. Use the table to find the ISO 13485 clause behind each stage and the evidence an auditor expects:
| Stage | ISO 13485 clause | Typical records/evidence | Review type |
|---|---|---|---|
| Clinical need and concept | Feeds 7.3.3 (inputs) | Intended use statement, user needs | Concept approval |
| Feasibility | 7.3.2 (planning) | Design and development plan, early risk analysis, regulatory strategy | Feasibility review |
| Design and development | 7.3.3–7.3.5 | Approved inputs, approved outputs, design review records | Design reviews, design freeze |
| Verification and validation | 7.3.6–7.3.7 | Verification plans and results, validation plans and results | Verification and validation complete |
| Design transfer | 7.3.8 | Transfer records, production specifications | Transfer review |
| Regulatory submission and launch | Draws on 7.3.10 (file) | Submission package, design and development file | Clearance, grant or approval |
| Post-market surveillance | 8.2.1–8.2.3, 8.5.2–8.5.3, 7.3.9 | Complaint records, corrective and preventive action (CAPA) records, change records | Change review |
The sections below take each stage in order, with what it produces and the decision that closes it.
Clinical Need and Concept
Development starts with an unmet clinical need and the intended use of the device: who uses it, on which patients and in what environment. Your team turns market research and clinical input into user needs written in the language of users and patients. Record the intended use early, because classification, risk analysis and validation all depend on it.
Feasibility
At feasibility, you test whether the concept is technically and financially workable. You also start the risk analysis and decide on a classification and regulatory strategy. The design and development plan begins here. Waiting until the design is mature to choose a pathway can mean finding out late that the device needs clinical data you did not plan for.
Design and Development
At this stage, you translate user needs into design inputs and develop design outputs, such as drawings, specifications and software, with formal design reviews at the points your plan defines. Outputs are approved before release, and the design and development plan defines where formal reviews are needed. Those reviews are conducted at suitable stages and documented.
Verification and Validation
Verification and validation answer two different questions. Design verification confirms that each design output meets its design input. Design validation confirms that the device meets user needs and its intended use. A device can pass every verification test and still fail validation if the inputs did not capture what users need.
Design Transfer and Manufacturing
Design transfer turns design outputs into manufacturing specifications that production can follow repeatably. The work covers design for manufacturability, pilot production and supplier controls. The manufacturer has to confirm that what manufacturing builds matches what the design phase specified.
Regulatory Submission and Launch
Assemble your submission package from the evidence collected so far: requirements, risk analysis, verification and validation results, and labeling. Use the outcome terms precisely. The FDA clears a device through a 510(k), approves a device through a premarket approval (PMA) application, and grants a De Novo classification request.
Post-Market Surveillance
After launch, you record and investigate complaints, report deaths, serious injuries and certain malfunctions to the FDA through Medical Device Reporting (MDR), report corrections and removals made to reduce a risk to health, and run corrective and preventive action (CAPA). Each of those can reopen the design, which is where the traceability in the last section of this guide matters.
How Does Medical Device Design and Development Work Under the QMSR?
Under the QMSR, you plan design and development, define inputs and outputs, conduct reviews, verification and validation, control transfer and changes, and maintain the design and development file (ISO 13485 Clause 7.3 and its subclauses).
Manufacturers of Class II and Class III devices, and of certain Class I devices, must comply with those subclauses (21 Code of Federal Regulations (CFR) 820.10(c)). The Class I devices covered include devices automated with computer software, plus five device types listed in the regulation. The Quality Management System Regulation took effect on 2 February 2026. The rule also incorporates clause 3 of ISO 9000:2015 and now requires risk management explicitly.
What Changed From the Old Quality System Regulation
The former Quality System Regulation (QSR) set out design controls at 21 CFR 820.30, and it defined separate record types, including the Design History File (DHF), Device Master Record (DMR) and Device History Record (DHR). In the current CFR, 820.30 falls within a Reserved range (§§ 820.20–820.30). “Design controls” was the QSR’s term. Teams that learned the work under that name will recognize the activities, which now carry the ISO 13485 names.
Compliance with ISO 13485 alone does not satisfy the QMSR. The FDA added limited requirements of its own, including record controls (820.35) and labeling and packaging controls (820.45).
Design and Development Planning
Your design and development plan has to document six things (ISO 13485 Clause 7.3.2):
- Stages: The design and development stages the project will pass through.
- Reviews: The reviews needed at each stage.
- Verification, validation and transfer: The activities that fit each stage.
- Responsibilities: Who holds responsibility and authority for design and development.
- Traceability methods: How design outputs will be traced to design inputs.
- Resources: The resources needed, including the competence of personnel.
The traceability item is easy to underrate. If your plan does not say how outputs will trace to inputs, you will not be able to prove at design review that they do.
Design Inputs and Outputs
Design inputs are the product requirements you derive from user needs. They have to include functional, performance, usability and safety requirements, applicable regulatory requirements and standards, and the outputs of risk management (ISO 13485 Clause 7.3.3). Your team reviews inputs for adequacy, approves them and keeps records. For the method of translating user needs into design inputs, write each input so that someone can verify it.
Design outputs must meet the inputs. They must also provide information for purchasing, production and service, contain or reference product acceptance criteria, and specify the characteristics essential for safe and proper use (ISO 13485 Clause 7.3.4). Outputs are approved before release.
Design Review, Verification and Validation
Design reviews take place at the stages your plan sets. Verification follows documented plans, and the 2016 edition added explicit requirements for verification records and for interface considerations.
Validation includes the evidence that users can operate the device safely. Human factors validation testing is one portion of design validation. The testing covers all critical tasks, uses participants who represent the intended users, and tests a user interface that represents the final design.
The usability engineering process behind it follows IEC 62366-1. The FDA finalized its guidance on the content of human factors information in marketing submissions on 29 May 2026.
For device software, IEC 62304 is an FDA-recognized voluntary consensus standard that provides a commonly used framework for software lifecycle processes. Validation also includes clinical evaluations or performance evaluations carried out under applicable regulatory requirements (ISO 13485 Clause 7.3.7).
Design Transfer and Design Changes
Design transfer requires documented procedures for moving design outputs into manufacturing (ISO 13485 Clause 7.3.8). Changes are where the evidence chain most often breaks.
Before you implement a design change, you have to identify it, review it, verify and validate it as appropriate, and approve it (ISO 13485 Clause 7.3.9). The review has to assess the change’s effect on constituent parts, on product in process or already delivered, and on the inputs and outputs of risk management and product realization. In practice, an approved change can require reassessment of the related design review, verification evidence and risk management records.
The Design and Development File
The design and development file contains or references all the records needed to show compliance with the design and development requirements, including the plan and procedures (ISO 13485 Clause 7.3.10). Many teams still call it the DHF, but the QMSR does not use that term.
The DMR and DHR map to ISO 13485 records as well, though not one to one, which matters if you are migrating legacy procedures. For the full comparison, see DHF, DMR and DHR under QMSR. To keep the file ready for audit, link its records as you create them instead of compiling them before an audit.
How Does Risk Management Shape Medical Device Design?
Risk management runs alongside design from concept to post-market. Design inputs have to include the outputs of risk management, so the two processes cannot run separately.
ISO 14971:2019 is the current edition, last reviewed and confirmed in 2025. The standard requires you to set objective criteria for risk acceptability but does not specify acceptable risk levels.
From Hazard to Risk Control to Requirement
You start by identifying hazards and hazardous situations, estimating each risk and evaluating it against the acceptability criteria in your risk management plan. ISO 14971 requires a risk analysis but does not mandate a specific technique. Design failure mode and effects analysis (DFMEA) and fault tree analysis are common choices, not requirements. An FMEA works from failures, so on its own it can miss risks that arise during normal use.
When a risk is not acceptable:
- Choose risk controls in priority order: inherently safe design first, then protective measures in the device or manufacturing process, then information for safety.
- Verify that each control is implemented and record the results in the risk management file. Implementation verification can be part of design verification.
- Verify that each control is effective and record the results in the risk management file. Effectiveness verification can be part of design validation, including testing with users.
After the risk controls are implemented and individual residual risks are evaluated, you evaluate the overall residual risk against the acceptability criteria defined in the risk management plan. If the overall residual risk is not acceptable, a benefit-risk analysis may be needed to determine whether the benefits of the intended use outweigh that risk. A risk management review takes place before commercial distribution.
Tracing One Infusion Pump Hazard Through the Records
The following example shows how a single hazard links to each record. Take an insulin infusion pump:
- Hazard, hazardous situation and harm: Insulin’s glucose-lowering action is the hazard. A software or delivery-control failure allows a bolus above the configured maximum, exposing the patient to excessive insulin. The resulting harm can be hypoglycemia.
- Risk control: Your team picks a protective measure: the software rejects any bolus above a configured maximum.
- Design input: That control becomes a design input, “The pump shall reject a bolus request that exceeds the configured maximum,” which is traced to the hazard.
- Verification: A verification test enters a bolus above the limit and confirms that the pump rejects it. This proves the control is implemented.
- Effectiveness: System-level verification or validation confirms the maximum-bolus control prevents delivery above the configured limit. If the rejection message is safety-related, human factors validation confirms users respond appropriately.
- Residual risk: The residual risk record cites both results.
If someone later changes the configured maximum, the design input, the test and the residual risk record all need to be reassessed.
How Does Device Classification Change the Development Process?
Device classification strongly influences the regulatory pathway and premarket evidence required, while the depth of development activities also depends on the device’s complexity, intended use and risk.
Under the FDA’s device classification system, roughly 1,700 generic device types are grouped into 16 medical specialty panels. Each type is assigned to Class I (general controls), Class II (general and special controls) or Class III (general controls and premarket approval). To find your device type, match it to a classification regulation in 21 CFR Parts 862–892 and look up its three-letter product code in the FDA’s Product Classification database.
510(k), De Novo or PMA
Class usually determines the pathway. Most Class I devices are exempt from premarket notification, most Class II devices need a 510(k), and most Class III devices need a PMA. A 510(k) shows that a device is substantially equivalent to a legally marketed predicate, and its performance data can include non-clinical bench testing as well as clinical data where it is needed.
A PMA rests on valid scientific evidence that the device is safe and effective, and that evidence usually includes clinical data. De Novo is a separate pathway for novel low-to-moderate-risk devices that have no predicate. Once the FDA grants a De Novo request, the device can serve as a predicate for later 510(k)s.
The 510(k) vs PMA comparison covers how to choose. Outcomes for each pathway are listed on the FDA’s Device Approvals and Clearances page.
What a Higher Class Adds Before and After Submission
A first Class II device on a 510(k) and a Class III device on a PMA differ most in the work that comes before submission. A significant-risk clinical study needs an approved investigational device exemption (IDE) and institutional review board (IRB) approval before it starts.
The FDA may refer a PMA to an advisory committee for public review. FDA reviews the manufacturing information in a PMA and may conduct quality-system inspections before approval. After approval, changes that affect safety or effectiveness generally require a PMA supplement or another FDA-permitted submission or notification, depending on the type of change. Significant design changes can therefore carry regulatory obligations in addition to engineering work. Teams that also sell in the EU face a separate conformity route under the EU Medical Device Regulation or, for IVDs, the In Vitro Diagnostic Regulation.
How Do You Keep Medical Device Requirements Traceable From User Needs to Post-Market?
You keep requirements traceable by linking each item to the next as you create it, in both directions, so that any record can be followed upstream to its source and downstream to its evidence. Bidirectional traceability lets you answer two audit questions: has every requirement been verified, and does every test trace back to a requirement?
The Chain an Auditor Follows
The design side of the chain runs from user needs to design inputs, then to outputs, verification and validation. The risk side runs alongside it through requirements, risks, tests, and verification evidence. The risk management file has to trace each identified hazard to its risk analysis, its risk evaluation, the implementation and verification of its risk controls, and the evaluation of residual risk.
An auditor can start anywhere on either chain. A missing link at any point means you have a requirement you cannot show was verified, or a control you cannot show was implemented.
What a Late Requirement Change Has to Show
When you change a requirement late in development, you have to identify every design output, risk control, test and labeling item it affects. In the pump example, raising the configured bolus maximum changes the design input. The verification test that confirmed the old limit is now out of date, and you must reassess the residual risk evaluation. If the limit appears in the instructions for use, you must revise the labeling too.
If you maintain links in a spreadsheet by hand, you must identify those affected items yourself. If you overlook them, you leave the outdated test marked as passed and verification incomplete until an auditor or FDA reviewer identifies the gap. Before you approve a change, list every downstream item linked to the changed requirement and record a decision for each one.
Why Current Traceability Makes Audit Evidence Quick
Traceability kept current during development is what makes audit evidence quick to produce, because the links already exist when someone asks for them. Convergent Dental moved off a document-based requirements process while preparing a De Novo Classification Request. After the move to Jama Connect®, Convergent Dental’s audit preparation decreased from three weeks to one day.
Feeding Post-Market Data Back Into the Design
Complaints, MDR reports and CAPA investigations often lead to design changes, and each design change reopens the chain under ISO 13485 Clause 7.3.9. A corrective action can itself be a risk control, or it can create new hazards through software, material, supplier or specification changes. When you open a CAPA, link it to the requirements and risk records it affects, so the risk management file is updated in the same change.
If you are evaluating tools for this work, check two things. First, confirm that a change to an upstream item flags every linked downstream item for review. Second, confirm that the tool can work alongside the systems your engineers already use instead of replacing them.
How Jama Connect Supports Medical Device Product Development
Jama Connect® is the product context platform that unifies requirements, risk, and test management and connects them through Live Traceability™ across the development lifecycle, helping teams build complex, regulated products with less rework and provable compliance. When an upstream requirement changes, suspect links flag every downstream test and risk item linked to it for assessment. A suspect flag marks an impact to review. It does not mean the downstream item is wrong.
Review Center supports design reviews with approval decisions and electronic signatures. Baselines are point-in-time references of a project or a set of items. You still have to control them through your review process.
Build a Traceable Medical Device Product Development Process Today
The order that saves the most rework is to classify at feasibility, open the risk file at concept, and link each need to its tests as you write them, because every one of those started late has to be rebuilt from memory before an audit.
Jama Connect supports that chain from the first user need. Trace one need to its verification evidence in a free 30-day trial.
Frequently Asked Questions About Medical Device Product Development
How long does medical device development take?
Development time depends mostly on class and pathway. A Class III PMA device usually takes longer because it generally requires more extensive evidence and review, which may include clinical studies conducted under an IDE, advisory committee review and preapproval inspection. The FDA usually makes a 510(k) substantial equivalence decision within 90 days, but that time covers the review only. The design, testing and documentation before submission usually take far longer.
What is the difference between design verification and design validation?
Design verification asks whether you built the device right against its inputs, and design validation asks whether you built the right device for its users. You must validate on representative product, which includes initial production units, batches or their equivalents. You must record why you chose the product you used. You must also complete validation before you release the device to customers.
When should you start a risk management file?
Start the risk management file at concept, before the design inputs are frozen, because risk management outputs are a required design input. The file does not need to be a single document. Records can be kept in any format, provided the file references them. Your risk management plan sets the acceptability criteria, and you record any later change to the plan in the file.
Can you use agile development under the QMSR?
Yes, provided the iterations run inside your design and development plan, design reviews and change control. AAMI TIR45:2023 gives guidance on agile practices for medical device software. One documented approach is to put user needs and system requirements under change control before sprints begin and to have the software development plan identify which iteration reviews count as formal design reviews.



