Therac-25 Lawsuit for Victims Against the AECL

Slides:



Advertisements
Similar presentations
The Basics of Patient Safety How You Can Improve the Safety of Patient Care.
Advertisements

IT Roles and Responsibilities: How Good is Good Enough? IS 485, Professor Matt Thatcher.
“An Investigation of the Therac-25 Accidents” by Nancy G. Leveson and Clark S. Turner Catherine Schell CSC 508 October 13, 2004.
The Therac-25: A Software Fatal Failure
A Gift of Fire, 2edChapter 4: Can We Trust the Computer?1 PowerPoint ® Slides to Accompany A Gift of Fire : Social, Legal, and Ethical Issues for Computers.
Vocabulary First Aid: Immediate and temporary care given to the victim of an accident or sudden illness until professional medical help arrives. Barriers.
Social Implications of a Computerized Society Computer Errors Instructor: Oliver Schulte Simon Fraser University.
An Investigation of the Therac-25 Accidents Nancy G. Leveson Clark S. Turner IEEE, 1993 Presented by Jack Kustanowitz April 26, 2005 University of Maryland.
Can We Trust the Computer? Case Study: The Therac-25 Based on Article in IEEE-Computer, July 1993.
+ THE THERAC-25 - A SOFTWARE FATAL FAILURE Kpea, Aagbara Saturday SYSM 6309 Spring ’12 UT-Dallas.
Week 5 - Wednesday.  What did we talk about last time?  Attacks on hash functions.
Protecting patients- now and in the future Linda Matthew Senior Pharmacist National Patient Safety Agency.
Slides prepared by Cyndi Chie and Sarah Frye. Fourth edition revisions by Sharon Gray. A Gift of Fire Fourth edition Sara Baase Chapter 8: Errors, Failures,
Reliability and Safety Lessons Learned. Ways to Prevent Problems Good computer systems Good computer systems Good training Good training Accountability.
Motivation Why study Software Engineering ?. What is Engineering ? 2 Engineering (Webster) – The application of scientific and mathematical principles.
IT Safety and Reliability Professor Matt Thatcher.
A Gift of Fire Third edition Sara Baase
A Gift of Fire Third edition Sara Baase
Errors, Failures and Risks CS4020 Overview Failures and Errors in Computer Systems Case Study: The Therac-25 Increasing Reliability and Safety Dependence,
COMS W3156: Software Engineering, Fall 2001 Lecture #2: The Open Class Janak J Parekh
SWE Introduction to Software Engineering
Jacky: “Safety-Critical Computing …” ► Therac-25 illustrated that comp controlled equipment could be less safe. ► Why use computers at all, if satisfactory.
Cancer Clinical Trials: The Basics. 2 What Are Cancer Clinical Trials? Research studies involving people Try to answer scientific questions and find better.
Toward A Reasonable Programmer Standard Responsibility and Negligence in Software Design.
Software Failures Ron Gilmore, CMC Edmonton April 2006.
Lecture 7, part 2: Software Reliability
Dr Andy Brooks1 Lecture 4 Therac-25, computer controlled radiation therapy machine, that killed people. FOR0383 Software Quality Assurance.
DJ Wattam, Han Junyi, C Mongin1 COMP60611 Directed Reading 1: Therac-25 Background – Therac-25 was a new design dual mode machine developed from previous.
Death by Software The Therac-25 Radio-Therapy Device Brian MacKay ESE Requirements Engineering – Fall 2013.
Therac-25 : Summary Malfunction Complacency Race condition (turntable / energy mismatch) Data overflow (turntable not positioned) time‘85‘86‘88 ‘87 Micro-switch.
1955 when Codman who is also known as father of Patient safety looked at the outcome of patient care 1984 Anaesthesia patient safety foundation established.
Therac-25 Final Presentation
Therac 25 Nancy Leveson: Medical Devices: The Therac-25 (updated version of IEEE Computer article)
ITGS Software Reliability. ITGS All IT systems are a combination of: –Hardware –Software –People –Data Problems with any of these parts, or a combination.
Course: Software Engineering © Alessandra RussoUnit 1 - Introduction, slide Number 1 Unit 1: Introduction Course: C525 Software Engineering Lecturer: Alessandra.
Chapter 8: Errors, Failures, and Risk
1 Can We Trust the Computer? What Can Go Wrong? Case Study: The Therac-25 Increasing Reliability and Safety Perspectives on Failures, Dependence, Risk,
Slides prepared by Cyndi Chie and Sarah Frye1 A Gift of Fire Third edition Sara Baase Chapter 8: Errors, Failures, and Risks.
Security and Reliability THERAC CASE STUDY TEXTBOOK: BRINKMAN’S ETHICS IN A COMPUTING CULTURE READING: CHAPTER 5, PAGES
Therac-25 Case Family vs. Programmer. People Suffered From Different Type of Bad Programming Database accuracy problems. Many people could not vote in.
Dimitrios Christias Robert Lyon Andreas Petrou Dimitrios Christias Robert Lyon Andreas Petrou.
© 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. System design techniques Quality assurance. 1.
A Systems Perspective on Building Security Into Applications Dr. William J. Hery Polytechnic University
Computing is Socio-Technical or: Why Stakeholder Listing is Inadequate for Thoughtful Ethical Analysis Chuck Huff St. Olaf College For NSF Computer Ethics.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 1.
Therac-25 CS4001 Kristin Marsicano. Therac-25 Overview  What was the Therac-25?  How did it relate to previous models? In what ways was it similar/different?
Around one million people in the UK \on insulin injections to control levels of glucose Statistics show there have been 3,931 serious incidents involving.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Finish Ethics Next Week Research Topics in HCI CS 321 Human-Computer Interaction.
Directed Reading 1 Girish Ramesh – Andres Martin-Lopez – Bamdad Dashtban –
Randy Modowski Adam Reimel Max Varner COSC 380 May 23, 2011 Accountability.
Chapter 8: Errors, Failures, and Risk Zach Archer Daniel O’Hara Eric Strittmatter.
CHAPTER 9: PROFESSIONAL ETHICS AND RESPONSIBILITIES BY: MATT JENNINGS SHANE CRAKER KYLER RHOADES.
Introduction to Assurance
EE 585 : FAULT TOLERANT COMPUTING SYSTEMS B.RAM MOHAN
COMP60611 Directed Reading 1: Therac-25
Therac-25 Accidents What was Therac-25? Who developed it?
A Gift of Fire Third edition Sara Baase
PowerPoint® Slides to Accompany
Reliability and Safety
Creating Electrical Circuits
Therac-25.
System design techniques
Reliability and Safety
Week 13: Errors, Failures, and Risks
Software Engineering for Safety: a Roadmap
Reliability and Safety
8 Medication Errors and Prevention.
Computer in Safety-Critical Systems
A Gift of Fire Third edition Sara Baase
Presentation transcript:

Therac-25 Lawsuit for Victims Against the AECL Zeke Dunlap Quinncy Thomas Sterling Sanders

Therac-25 Victims The Therac-25 software is directly to blame for the injures to six victims between 1985 and 1987. The Atomic Energy of Canada Ltd. (AECL) carries the burden of blame for the massive overdoses of radiation that the Therac-25 gave to patients being treated by the software. Three deaths were caused by this unimaginable lapse in judgment by the AECL.

Whose to blame? The AECL did not take the appropriate measures to insure that the Therac-25 would provide the utmost safety precautions for the patients who were being treated with the software. Insufficient testing, numerous bugs, bad safety design, and poor programming techniques were all contributors to the incidents that injured patients who trusted the Therac-25.

Design Flaws in the Therac-25 The software developers were too cheap! The Therac-20 has independent protective circuits for monitoring electron-beam scanning, plus mechanical interlocks for policing the machine and ensuring safe operation. Too avoid extra expenses, AECL decided not to duplicate all the existing hardware safety mechanisms and interlocks. . Error messages were not informing to the operators of the software. There were no definitions found in the manual that came with the Therac-25. The Therac-25 basically had reused software. This was discovered when bugs found within the previous model of the Therac-20 was also found in the Therac-25..

Bug in the Therac-25 A major bug in the Therac-25 was an overflow error, which could have been prevented if careful design techniques would have been implemented. The overflow error checked off that the system was ready to begin radiation, when the system was actually giving harmful doses of radiation to the patients.

AECL’s Tenacity The AECL repeatedly stated that there was no possibility of an overdose of radiation that could be caused by the software. After the 2nd incident, the AECL told the FDA that the source of the problem could not be located, but the AECL publicly stated that the safety of the Therac-25 had been improved by 5 times after they implemented some safety features in reaction to the incident. A Canadian agency urged the AECL to implement more safety features, but the AECL insisted that the software was now safe.

Overconfidence Some hospitals using the Therac-25 implemented their own safety mechanisms. Those hospitals never had a single overdose of radiation on any patients. Other hospitals felt secure when the AECL told them it would be a waste of money to implement safety mechanisms because the software was safe.

Conclusion The AECL’s irresponsibility should not be overlooked. The victims of the Therac-25 should not be left without some retribution. The AECL’s lack of emphasis on the safety of the software is extremely tragic in such a safety critical software system.