|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Coping with Defective Software in Medical Devices
April 2006 (vol. 39 no. 4)
pp. 40-45
| ASCII Text | x | ||
| Steven R. Rakitin, "Coping with Defective Software in Medical Devices," Computer, vol. 39, no. 4, pp. 40-45, April, 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/MC.2006.123, author = {Steven R. Rakitin}, title = {Coping with Defective Software in Medical Devices}, journal ={Computer}, volume = {39}, number = {4}, issn = {0018-9162}, year = {2006}, pages = {40-45}, doi = {http://doi.ieeecomputersociety.org/10.1109/MC.2006.123}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - Computer TI - Coping with Defective Software in Medical Devices IS - 4 SN - 0018-9162 SP40 EP45 EPD - 40-45 A1 - Steven R. Rakitin, PY - 2006 KW - Clinical software engineering KW - Medical software KW - Healthcare technology VL - 39 JA - Computer ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MC.2006.123
Embedding defective software in medical devices increases safety risks. Given that all software is inherently defective, how can medical device manufacturers identify and manage risk? An effective, tailored risk management process can make the task less daunting.
Index Terms:
Clinical software engineering, Medical software, Healthcare technology
Citation:
Steven R. Rakitin, "Coping with Defective Software in Medical Devices," Computer, vol. 39, no. 4, pp. 40-45, April 2006, doi:10.1109/MC.2006.123
Usage of this product signifies your acceptance of the Terms of Use.