International standard for medical software
IEC 62304 –medical device software –software life cycle processes[1] is aninternational standard published by theInternational Electrotechnical Commission (IEC). The standard specifies life cycle requirements for the development ofmedical software and software within medical devices. It has been adopted as national standards and therefore can be used as abenchmark tocomply with regulatory requirements.
Implications of IEC 62304 for software
[edit]The IEC 62304 standard calls out certain cautions on using software, particularly SOUP (software of unknown pedigree or provenance). The standard spells out a risk-based decision model on when the use of SOUP is acceptable, and defines testing requirements for SOUP to support a rationale on why such software should be used.[2]
Source:[3]
General requirements
[edit]Software development process
[edit]- Software development planning
- Software requirements analysis
- Software architectural design
- Software detailed design
- Software unit implementation and verification
- Software integration and integration testing
- Software system testing
- Software release
Effect of safety classification on required development process documentation
[edit]| Software documentation[4] | Class A | Class B | Class C |
|---|
| Software development planning | X | X | X |
| Software requirements analysis | X | X | X |
| Software architectural design | | X | X |
| Software detailed design | | | X |
| Software unit implementation | X | X | X |
| Software unit verification | | X | X |
| Software integration and integration testing | | X | X |
| Software system testing | X | X | X |
| Software release | X | X | X |
|
| X - required |
Software maintenance process
[edit]- Establish software maintenance plan
- Problem and modification analysis
- Modification implementation
Software risk management process
[edit]- Analysis of software contributing to hazardous situations
- Risk control measures
- Verification of risk control measures
- Risk management of software changes
- Security and reliability throughsoftware quality
Software configuration management process
[edit]- Configuration identification
- Change control
- Configuration status accounting
Software problem resolution process
[edit]- Prepare problem reports
- Investigate the problem
- Advise relevant parties
- Use change control process
- Maintain records
- Analyse problems for trends
- Verify software problem resolution
- Test documentation contents