IEC 82304IEC 82304-1 — Health Software Product Safety
The international safety standard for health software products, covering standalone applications, mobile medical apps, and software as a medical device (SaMD).

On this page · 10 sections
- 1Overview of IEC 82304-1: Health Software Product Safety
- 2Defining the Scope: What is 'Health Software'?
- 3The Standard Trinity: IEC 82304, IEC 62304, and ISO 14971
- 4Product-Level Requirements and Validation
- 5QMS Integration: ISO 13485 and IEC 82304-1
- 6Security as a Safety Pillar
- 7Accompanying Documentation and the IFU
- 8Post-Market Activities and Maintenance
- 9Regulatory Context: FDA, EU MDR, and IMDRF
- 10Implementation Best Practices for Software Teams
How does IEC 82304 apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01Overview of IEC 82304-1: Health Software Product Safety
IEC 82304-1:2016, titled 'Health software — Part 1: General requirements for product safety', is the cornerstone standard for software products that operate on general computing platforms without being embedded in specific hardware. While its older sibling, [[iec-62304]], focuses on the software development *lifecycle* (the process of writing code), IEC 82304-1 focuses on the software *product* as a whole—its safety, fitness for use, and long-term maintenance 1.
The standard was developed in response to the explosion of 'Software as a Medical Device' (SaMD) and consumer health apps. Unlike traditional medical devices, where the software is just a component of a physical machine (like a CT scanner), standalone health software presents unique risks. These risks often stem not from hardware failure, but from poor usability, data corruption, or clinical misinformation. IEC 82304-1 provides the regulatory framework to manage these risks throughout the entire product lifespan, from initial design to final decommissioning.
By bridging the gap between clinical intent and technical execution, the standard ensures that a health app is not just a piece of code, but a validated health intervention. It forces manufacturers to treat software with the same rigour as a physical medical instrument, requiring documented evidence of safety and performance at every step. This product-centric approach is vital because, in many modern healthcare systems, the software *is* the treatment.
02Defining the Scope: What is 'Health Software'?
The scope of IEC 82304-1 is defined by the absence of dedicated hardware. It applies to 'health software products designed to operate on general computing platforms and intended to be placed on the market without dedicated hardware' 1. This distinction is critical for regulatory classification.
Common Examples Covered
- Mobile Medical Apps: Smartphone apps that assist in managing chronic conditions, such as diabetes trackers or cardiac monitoring tools.
- Clinical Decision Support (CDS): Algorithms that process patient data to suggest diagnoses or treatments to doctors. This includes software that flags potential drug-drug interactions.
- AI and Machine Learning Models: Standalone diagnostic tools, such as software that analyses X-ray images for signs of pneumonia or skin lesions for melanoma.
- Web-based Healthcare Portals: Platforms that handle clinical workflows, patient scheduling, and health data management where data integrity is paramount.
- General Health Apps: Wellness applications that may not be regulated as medical devices in all regions but still benefit from a safety-first development approach to avoid consumer harm.
What is Excluded?
The standard does *not* apply to software that is an integral part of a specific medical device hardware. For example, the software controlling a radiation therapy machine, a heart-lung bypass unit, or an implanted pacemaker is covered by the IEC 60601 series and IEC 62304 directly, rather than IEC 82304-1. The distinction is essentially: if you can install the software on a consumer laptop, tablet, or phone, it likely falls under IEC 82304-1 1.
03The Standard Trinity: IEC 82304, IEC 62304, and ISO 14971
For a manufacturer to be compliant with IEC 82304-1, they must also implement two other critical standards. The relationship is hierarchical and functional, creating a robust framework for software safety:
- IEC 82304-1 (The Product Wrapper): Governs the product requirements, validation, and post-market activities. It defines the 'what' and 'why' of the product safety.
- IEC 62304 (The Process Core): Governs the software development process, including coding standards, unit testing, and configuration management. It defines the 'how' of building the code 2.
- ISO 14971 (The Risk Foundation): Provides the framework for risk management, which is required by both software standards to identify and mitigate hazards 2.
In practice, IEC 82304-1 'calls' IEC 62304. It says: 'To develop the software part of this product, you must use the processes defined in 62304.' However, 82304-1 adds the layers that 62304 misses, such as **product validation** (does it work for the user in the real world?) and **accompanying documentation** (instructions for use and technical descriptions). Without 82304-1, a standalone software might be perfectly coded according to 62304 but could still be dangerous because its intended use was never validated with actual clinicians.
04Product-Level Requirements and Validation
IEC 82304-1 places heavy emphasis on the 'Health Software Product use requirements'. These are the needs the software must meet to be considered safe and effective in its intended environment. They are more than just functional specs; they include usability, security, and clinical efficacy.
The Validation Process vs. Verification
While verification (under 62304) proves the software was built right (i.e., it meets its technical specs), **validation** (under 82304-1) proves the right software was built (i.e., it meets the user's needs). The validation process must be planned and documented, including:
- Validation Planning: Defining how the product will be tested against its use requirements before development begins.
- Clinical Evaluation: Proving the clinical validity of the software's outputs, ensuring that the health benefits outweigh the risks 3.
- Usability Testing: Ensuring that the intended users (e.g., patients or clinicians) can use the software without making dangerous errors, typically following the [[iec-62366-1]] standard for usability engineering.
- Validation Report: A definitive document summarising the evidence that the product is safe for release and signed off by the responsible parties 1.
This validation phase is often the most challenging for SaMD manufacturers because it requires real-world testing or clinical data, which is much more complex than automated unit tests or continuous integration (CI) pipelines.
05QMS Integration: ISO 13485 and IEC 82304-1
While IEC 82304-1 is a product safety standard, it assumes the presence of a Quality Management System (QMS). For medical devices, this is typically [[iso-13485]]. The QMS provides the organisational structure—document control, training records, and management responsibility—that supports the technical activities of the standard.
Key touchpoints between the QMS and 82304-1 include:
- Design Control: The entire process of defining, developing, and validating the software product is part of the QMS's design control procedures.
- Supplier Management: If the software uses third-party libraries (SOUP - Software of Unknown Pedigree), the QMS must govern how those suppliers are evaluated and monitored.
- Corrective and Preventive Actions (CAPA): Any safety issues found during validation or after market release must trigger the QMS's [[capa]] process to ensure the root cause is addressed.
For startups, implementing 82304-1 without a QMS is like trying to build a skyscraper on sand. The standard provides the blueprint for the building, but the QMS provides the foundation and the project management required to complete it safely.
06Security as a Safety Pillar
One of the most modern aspects of IEC 82304-1 is its explicit link between security and safety. In health software, a security breach is not just a data privacy issue; it is a patient safety issue. If an attacker can alter a patient's lab results, intercept a critical alert, or disable a monitoring tool, the software becomes potentially lethal.
The standard requires manufacturers to include security requirements as part of the system design. This includes:
- Authentication and Authorisation: Ensuring only permitted users can access health data and perform clinical actions.
- Data Integrity: Protecting data from unauthorised changes during storage or transmission using encryption and hashing.
- Resilience: Ensuring the software remains operational or fails safely during a cyberattack or network outage.
- Post-market Patching: A clear, rapid process for identifying and fixing vulnerabilities discovered after the product is on the market.
07Accompanying Documentation and the IFU
A health software product is incomplete without its 'accompanying documents'. IEC 82304-1 Section 7 specifies that the product must be delivered with all information necessary for safe installation, configuration, and use 1.
The Instructions for Use (IFU) must be clear, accessible, and written for the intended user (who might be a layperson patient or a specialist surgeon). It must include:
- The Intended Purpose: A precise statement of what the software does and what it does not do (contraindications).
- Target Population: Who the software is for (e.g., 'adults with Type 2 diabetes who are not on insulin pumps').
- Operating Environment: The required hardware (e.g., screen resolution), OS versions, and minimum network bandwidth.
- Warnings and Cautions: Any risks that the user needs to be aware of, such as 'do not use this app to adjust medication without consulting a physician'.
Failing to provide adequate instructions or omitting critical safety warnings is a primary cause of regulatory rejection and product liability issues. The documentation is as much a part of the 'safety' of the product as the code itself. In the digital age, this documentation is often delivered via the app itself or a cloud portal, but it must remain version-controlled and accessible.
08Post-Market Activities and Maintenance
Health software is never truly 'finished'. Because the platforms it runs on (iOS, Android, Windows) are constantly changing, the software requires continuous maintenance. IEC 82304-1 Section 8 governs the post-market phase, ensuring the manufacturer remains responsible for the product's safety throughout its operational life 1.
Key post-market requirements include:
- Vulnerability Monitoring: Actively checking for new security flaws in third-party libraries (SOUP) or the underlying operating system.
- Feedback and Complaint Handling: A formal process for receiving, investigating, and documenting user reports of errors or safety issues.
- Field Safety Notices: A method for notifying users and regulators if a safety-critical bug is discovered and requires a 'recall' (which in software usually means an urgent patch).
- Decommissioning and Data Disposal: A plan for how to retire the software safely, ensuring patient data is either archived according to law or securely destroyed 1.
The transition from 'development' to 'maintenance' under 82304-1 is seamless because it relies on the maintenance processes already established in IEC 62304. However, it adds the clinical feedback loop that ensures the manufacturer stays informed of how the product performs in the hands of real users, not just in a controlled test environment.
09Regulatory Context: FDA, EU MDR, and IMDRF
IEC 82304-1 is a 'voluntary' standard, but in the highly regulated world of medical software, voluntary standards are the primary way to prove compliance with mandatory laws.
United States (FDA)
The FDA has formally recognised IEC 82304-1 (Recognition Number 13-97) 1. For manufacturers of SaMD, declaring conformity to this standard is the most efficient way to satisfy the requirements for 'Content of Premarket Submissions for Device Software Functions' 5. It demonstrates that the manufacturer has considered the product-level safety and usability concerns that simple unit testing misses.
European Union (MDR/IVDR)
The EU Medical Device Regulation (MDR) has strict requirements for software (Annex I, GSPR 17). While the MDR doesn't name specific standards, IEC 82304-1 is the 'state of the art' approach for standalone software. Notified Bodies expect to see a technical file that follows the 82304-1 structure for any SaMD or high-risk health app submission, particularly regarding the validation of clinical benefits.
International Convergence (IMDRF)
The International Medical Device Regulators Forum (IMDRF) has established a common framework for SaMD classification and clinical evaluation. IEC 82304-1 was built to align with this framework, meaning that a product compliant with the standard is much easier to launch in multiple global markets (e.g., Canada, Australia, Japan) simultaneously, as the core safety evidence remains the same 3.
10Implementation Best Practices for Software Teams
Successfully implementing IEC 82304-1 requires a shift in mindset from 'shipping code' to 'releasing a product'. For modern software teams, this means integrating regulatory requirements into their existing workflows rather than treating them as a final hurdle.
- Automated Traceability: Use tools that automatically link code commits to requirements and test results. This reduces the manual burden of creating a traceability matrix.
- Continuous Validation: While validation is often seen as a final step, teams can perform 'mini-validations' or usability checks during development to catch safety issues early.
- Security by Design: Integrate security scanning (SAST/DAST) into the CI/CD pipeline to satisfy the 82304-1 security requirements automatically.
- Living Documentation: Maintain the IFU and technical descriptions as 'code' (e.g., Markdown in the repository) to ensure they stay in sync with the software version.
By treating IEC 82304-1 compliance as a quality driver rather than a bureaucratic checkbox, software companies can build safer, more reliable health products that are ready for the global market.
Frequently asked questions
Q.Does IEC 82304-1 apply to internal hospital software?+
Technically, the standard applies to software 'placed on the market'. If a hospital develops software for its own internal use, it may not be legally required to follow 82304-1 by a regulator, but doing so is considered the industry best practice for ensuring patient safety and reducing organisational liability.
Q.Can I be compliant with IEC 82304-1 without following IEC 62304?+
No. IEC 82304-1 explicitly references IEC 62304 for the software lifecycle processes (Section 5). You cannot claim full compliance with the product safety standard without also having a compliant software development process that includes requirements analysis, architectural design, and rigorous testing.
Q.How does 82304-1 handle 'Agile' development methodologies?+
The standard is 'process agnostic', meaning it doesn't forbid Agile, Scrum, or Kanban. However, it requires that the *outputs* of the process—such as validation plans, risk assessments, and instructions for use—are formalised and version-controlled. Agile teams must ensure that their sprints include the time needed to generate this regulatory evidence.
Q.What is the difference between a 'Health App' and a 'Medical App' in this standard?+
The standard uses the broad term 'Health Software' to cover everything from lifestyle wellness apps to high-risk diagnostic tools. Whether an app is legally a 'medical device' depends on the regulator (e.g., FDA), but IEC 82304-1 provides the safety framework regardless of the legal classification, with the rigour of validation scaling with the risk.
Q.Who is legally responsible for 82304-1 compliance?+
The 'Manufacturer'—the legal entity whose name is on the label and who places the product on the market—is responsible. While external developers or contractors may perform the work, the manufacturer must provide the oversight and ensure the product meets all safety requirements before release.
Primary sources
Further reading
- IEC 62304: Software Life CycleThe core standard for medical software development processes, required by IEC 82304-1.
- ISO 14971: Risk ManagementThe global framework for managing risks in medical devices and health software.
- Software as a Medical Device (SaMD)Understanding the regulatory classification of standalone health software.
- IEC 62366-1: Usability EngineeringApplying user-centric design to ensure medical software safety and effectiveness.
Want to see how IEC 82304 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
