IEC 62304:2015 Medical Device Software Lifecycle Processes
The IEC standard for medical device software life cycle processes, built from the complete Edition 1.1 text (2006 with Amendment 1:2015): 99 requirement leaves across development, maintenance, risk management, configuration management and problem resolution, each marked with the software safety classes A, B and C it applies to.
IEC 62304:2015 Medical Device Software Lifecycle Processes is a compliance framework from International (IEC); harmonised as EN 62304 under the EU MDR; FDA recognised consensus standard; adopted as ANSI/AAMI/IEC 62304 and nationally with 6 domains and 99 controls that map to 194 other frameworks. The largest domains are Clause 5: software development process – IEC 62304:2015 Medical Device Software Lifecycle Processes (54 controls), Clause 7: software risk management process – IEC 62304:2015 Medical Device Software Lifecycle Processes (13 controls), Clause 4: general requirements (quality system, risk management, safety classification, legacy software) – IEC 62304:2015 Medical Device Software Lifecycle Processes (8 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (6)
Clause 4: general requirements (quality system, risk management, safety classification, legacy software) – IEC 62304:2015 Medical Device Software Lifecycle Processes
Clause 5: software development process – IEC 62304:2015 Medical Device Software Lifecycle Processes
Clause 6: software maintenance process – IEC 62304:2015 Medical Device Software Lifecycle Processes
| Code | Title |
|---|---|
| iec-62304-2015-medical-device-software-lifecycle-processes::6.1 | 6.1 Establish software maintenance plan |
| iec-62304-2015-medical-device-software-lifecycle-processes::6.2.1 | 6.2.1 Document and evaluate feedback |
| iec-62304-2015-medical-device-software-lifecycle-processes::6.2.2 | 6.2.2 Use software problem resolution process |
| iec-62304-2015-medical-device-software-lifecycle-processes::6.2.3 | 6.2.3 Analyse change requests |
| iec-62304-2015-medical-device-software-lifecycle-processes::6.2.4 | 6.2.4 Change request approval |
| iec-62304-2015-medical-device-software-lifecycle-processes::6.2.5 | 6.2.5 Communicate to users and regulators |
| iec-62304-2015-medical-device-software-lifecycle-processes::6.3.1 | 6.3.1 Use established process to implement modification |
| iec-62304-2015-medical-device-software-lifecycle-processes::6.3.2 | 6.3.2 Re-release modified software system |
Clause 7: software risk management process – IEC 62304:2015 Medical Device Software Lifecycle Processes
| Code | Title |
|---|---|
| iec-62304-2015-medical-device-software-lifecycle-processes::7.1.1 | 7.1.1 Identify software items that could contribute to a hazardous situation |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.1.2 | 7.1.2 Identify potential causes of contribution to a hazardous situation |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.1.3 | 7.1.3 Evaluate published SOUP anomaly lists |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.1.4 | 7.1.4 Document potential causes |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.1.5 | 7.1.5 Document sequences of events |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.2.1 | 7.2.1 Define risk control measures |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.2.2 | 7.2.2 Risk control measures implemented in software |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.3.1 | 7.3.1 Verify risk control measures |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.3.2 | 7.3.2 Document any new sequences of events |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.3.3 | 7.3.3 Document traceability |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.4.1 | 7.4.1 Analyse changes to medical device software with respect to safety |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.4.2 | 7.4.2 Analyse impact of software changes on existing risk control measures |
| iec-62304-2015-medical-device-software-lifecycle-processes::7.4.3 | 7.4.3 Perform risk management activities based on analyses |
Clause 8: software configuration management process – IEC 62304:2015 Medical Device Software Lifecycle Processes
Clause 9: software problem resolution process – IEC 62304:2015 Medical Device Software Lifecycle Processes
| Code | Title |
|---|---|
| iec-62304-2015-medical-device-software-lifecycle-processes::9.1 | 9.1 Prepare problem reports |
| iec-62304-2015-medical-device-software-lifecycle-processes::9.2 | 9.2 Investigate the problem |
| iec-62304-2015-medical-device-software-lifecycle-processes::9.3 | 9.3 Advise relevant parties |
| iec-62304-2015-medical-device-software-lifecycle-processes::9.4 | 9.4 Use change control process |
| iec-62304-2015-medical-device-software-lifecycle-processes::9.5 | 9.5 Maintain records |
| iec-62304-2015-medical-device-software-lifecycle-processes::9.6 | 9.6 Analyse problems for trends |
| iec-62304-2015-medical-device-software-lifecycle-processes::9.7 | 9.7 Verify software problem resolution |
| iec-62304-2015-medical-device-software-lifecycle-processes::9.8 | 9.8 Test documentation contents |
Your Compliance Coverage
If you comply with IEC 62304:2015 Medical Device Software Lifecycle Processes, you already cover:
EN 50716:2023 - Railway Applications - Requirements for Software Development
31%
41 controls mapped
Compare →GAMP 5 - Good Automated Manufacturing Practice
10%
13 controls mapped
Compare →ICH Q10 - Pharmaceutical Quality System
7%
9 controls mapped
Compare →+ 191 more: NIST SP 800-82 Revision 3: Guide to Industrial Control Systems (ICS) Security (6%), MTCS (Singapore) (6%)
See all 194 mapped frameworks ↓Maps to 194 other frameworks
Coverage is not the same as your position
This page shows what IEC 62304:2015 Medical Device Software Lifecycle Processes overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is IEC 62304:2015 Medical Device Software Lifecycle Processes and who does it apply to?
IEC 62304:2015 Medical Device Software Lifecycle Processes is a compliance framework from International (IEC); harmonised as EN 62304 under the EU MDR; FDA recognised consensus standard; adopted as ANSI/AAMI/IEC 62304 and nationally with 6 domains and 99 controls. The IEC standard for medical device software life cycle processes, built from the complete Edition 1.1 text (2006 with Amendment 1:2015): 99 requirement leaves across development, maintenance, risk management, configuration management and problem resolution, each marked with the software safety classes A, B and C it applies to. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does IEC 62304:2015 Medical Device Software Lifecycle Processes actually require?
IEC 62304:2015 Medical Device Software Lifecycle Processes has 99 controls organised across 6 domains. The largest domains are Clause 5: software development process – IEC 62304:2015 Medical Device Software Lifecycle Processes (54 controls), Clause 7: software risk management process – IEC 62304:2015 Medical Device Software Lifecycle Processes (13 controls), Clause 4: general requirements (quality system, risk management, safety classification, legacy software) – IEC 62304:2015 Medical Device Software Lifecycle Processes (8 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of IEC 62304:2015 Medical Device Software Lifecycle Processes do I already cover?
IEC 62304:2015 Medical Device Software Lifecycle Processes maps to 194 other compliance frameworks. The top mapping partners are EN 50716:2023 - Railway Applications - Requirements for Software Development (31% coverage), GAMP 5 - Good Automated Manufacturing Practice (10% coverage), ICH Q10 - Pharmaceutical Quality System (7% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement IEC 62304:2015 Medical Device Software Lifecycle Processes?
Start your IEC 62304:2015 Medical Device Software Lifecycle Processes compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about IEC 62304:2015 Medical Device Software Lifecycle Processes requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 99 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,120 frameworks.
Get Started Free →Free forever, no credit card required