Difference between revisions of "IEC 62304"

From LIMSWiki
Jump to navigationJump to search
(Transcluded, per John)
 
(Added cats)
 
Line 1: Line 1:
{{wikipedia::IEC 62304}}
{{wikipedia::IEC 62304}}
==Notes==
==Notes==
This article is a direct transclusion of [https://en.wikipedia.org/wiki/AbioCor the Wikipedia article] and therefore may not meet the same editing standards as LIMSwiki.
This article is a direct transclusion of [https://en.wikipedia.org/wiki/AbioCor the Wikipedia article] and therefore may not meet the same editing standards as LIMSwiki.
Line 8: Line 9:
[[Category:Regulation of medical devices]]
[[Category:Regulation of medical devices]]
[[Category:Software standards]]
[[Category:Software standards]]
[[Category:Testing standards]]

Latest revision as of 20:09, 11 March 2016

IEC 62304medical device software – software life cycle processes[1] is an international standard published by the International Electrotechnical Commission (IEC). The standard specifies life cycle requirements for the development of medical software and software within medical devices. It has been adopted as national standards and therefore can be used as a benchmark to comply with regulatory requirements.

Implications of IEC 62304 for software

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]

Contents

Source:[3]

General requirements

Software development process

  • 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

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

  • Establish software maintenance plan
  • Problem and modification analysis
  • Modification implementation

Software risk management process

  • Analysis of software contributing to hazardous situations
  • Risk control measures
  • Verification of risk control measures
  • Risk management of software changes
  • Security and reliability through software quality

Software configuration management process

  • Configuration identification
  • Change control
  • Configuration status accounting

Software problem resolution process

  • 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

See also

References

  1. ^ International Electrotechnical Commission (2006). "Medical device software – Software life cycle processes" (PDF). INTERNATIONAL IEC STANDARD 62304 First edition 2006-05. International Electrotechnical Commission. Retrieved 2 June 2012.
  2. ^ Hall, Ken (June 1, 2010). "Developing Medical Device Software to IEC 62304". EMDT - European Medical Device Technology. Retrieved 2024-01-17.
  3. ^ "IEC 62304:2006(en) Medical device software — Software life cycle processes". ISO. 2006. Retrieved 15 June 2017.
  4. ^ "Developing Medical Device Software to IEC 62304 | MDDI Medical Device and Diagnostic Industry News Products and Suppliers". www.mddionline.com. June 2010. Retrieved 2024-01-17.


Notes

This article is a direct transclusion of the Wikipedia article and therefore may not meet the same editing standards as LIMSwiki.