System Safety in Healthcare: Lessons Learned From Designing for Safety

Dev Raheja

doi:10.56094/jss.v56i3.10

Authors

Dev Raheja

DOI:

https://doi.org/10.56094/jss.v56i3.10

Keywords:

design for safety, lessons learned

Abstract

Designing for safety is a process. When the right process is followed, results can be great, such as eliminating most of the warranty costs. The opposite is also true in the absence of the right process. There is a saying: “If we don’t know where we are going, that’s where we will go.”

Author Biography

Dev Raheja

Mr. Dev Raheja has been a System Safety and System Reliability Engineering consultant for over 25 years. His range of consulting encompasses transportation systems, electric power systems, high tech industry, aerospace, defense systems, medical systems, and consumer products. He has conducted training in several countries including Sweden, Australia, Japan, UK, Turkey, Germany, Poland, Singapore, Brazil, South Africa, and Canada. He has done training and consulting work with NASA, U.S. Army, GM, Boeing, Eaton, Nissan Aerospace, Litton, General Dynamics, ITT, BAE Systems, Lockheed-Martin, Harley-Davidson, and United Technologies.

Prior to consulting, Mr. Raheja worked at General Electric, Cooper Industries, and at Booz-Allen & Hamilton. He is the author of several books including Assurance Technologies Principles and Practices (Second Edition, Wiley 2006), and Design for Reliability (Wiley, 2012). A Fellow of the System Safety Society, he has a received Scientific Achievement Award and the Educator-of the-Year Award from the society.

Mr. Raheja serves on the Patient and Families Advisory Council at Johns Hopkins Hospital as a patient safety advocate. He is Associate Editor for Healthcare Safety for The Journal of System Safety and an Associate Professor at University of Maryland where he teaches the “Design For Reliability” course which includes design for safety and trustworthiness.

References

Raheja, D. G. and M. Allocco. Assurance Technologies Principles and Practices: A Product,Process, and System Safety Perspective, 2nd ed., Wiley, Hoboken, NJ, 2006, Appendix. https://doi.org/10.1002/047000942X DOI: https://doi.org/10.1002/047000942X

Farrow, D. R. presented at the Fifth International Workshop on Risk Analysis and Performance Measurement in Aviation, sponsored by FAA and NASA, Baltimore, August 19-21, 2003.

Mann, C. C. "Why software is so bad," Technol. Rev., July-August 2002. https://www.technologyreview.com/s/401594/why-software-is-so-bad/