Skip to main page content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Access keys NCBI Homepage MyNCBI Homepage Main Content Main Navigation
. 2006:2006:166-70.

Healthcare software assurance

Jason G Cooper  1 , Keith A Pauley
Affiliations

Healthcare software assurance

Jason G Cooper et al. AMIA Annu Symp Proc. 2006.

Abstract

Software assurance is a rigorous, lifecycle phase-independent set of activities which ensure completeness, safety, and reliability of software processes and products. This is accomplished by guaranteeing conformance to all requirements, standards, procedures, and regulations. These assurance processes are even more important when coupled with healthcare software systems, embedded software in medical instrumentation, and other healthcare-oriented life-critical systems. The current Food and Drug Administration (FDA) regulatory requirements and guidance documentation do not address certain aspects of complete software assurance activities. In addition, the FDA's software oversight processes require enhancement to include increasingly complex healthcare systems such as Hospital Information Systems (HIS). The importance of complete software assurance is introduced, current regulatory requirements and guidance discussed, and the necessity for enhancements to the current processes shall be highlighted.

PubMed Disclaimer

Figures

Figure 1
Figure 1
Software Assurance Process
Figure 2
Figure 2
Criticality-Based Assurance Model
See this image and copyright information in PMC

References

    1. Charette RN. “Why Software Fails,”. IEEE Spectrum. 2005 September 5;
    1. Linberg KR. Proc. 6th Annu. IEEE Symp. On Computer-Based Medical Systems. Ann Arbor MI: 1993. Defining the role of software quality assurance in a medical device company; pp. 278–283.
    1. Leveson NG, Turner CS. “An investigation of the Therac-25 accidents,”. IEEE Computer. 1993 Jul;26:18–41.
    1. FDA Criteria for Device Classification. 2002. 21 CFR 820. Available: http://www.fda.gov/cdrh/devadvice/3132.html.
    1. Medical Devices; Current Good Manufacturing Practice (CGMP) Final Rule; Quality System Regulation. October 7. 1996. AEI-Brookings Joint Center for Regulatory Studies, RIN: 0910–AA09. - PubMed

MeSH terms

LinkOut - more resources