Xenophon Papademetris is Professor of Radiology and Biomedical Imaging, and Biomedical Engineering at Yale University whose research focuses on biomedical image analysis and software development. He has over twenty years of experience in medical software design.

Klappentext

"The goal of this book is to provide in one brief and accessible volume a survey of the critical material involved in the design, implementation, and management of medical software for both standalone software ("software as a medical device - SaMD") and software that is part of a physical medical device. One will find more detailed treatments of many of the topics covered in this book in specialized books that focus on some of the topics we cover (e.g. software engineering, systems engineering, probability theory, machine learning). Depth was not our goal; this book is explicitly designed to provide a broad survey. Our hope is to familiarize the reader with the span of topics he or she may need in entering this field and to provide pointers to more specialized publications as this becomes necessary. For example, most computer scientists have very limited exposure to statistical decision theory, and we think that even the cursory coverage in this book will at least enable them to understand "what they do not know" and seek help as opposed to being ignorant of this entire field and attempting to reinvent the wheel in an amateurish manner! An emerging challenge in medical software is the increasing use of big data and artificial intelligence/machine learning (AI/ML) techniques. This places an even greater stress on proper software design and management. Given that these are "black box" methods, in which the human understanding of what actually is going on is limited, a proper software quality process will be even more critical in creating reliable software tools. We introduce this topic in Section 1.3. In that section we also provide pointers to the other sections of the book in which we discuss issues related to the use of AI/ML methods. This is an introductory book. One can and should follow the material here with further study, using both original regulatory materials, industry standards,1 and more advanced books.2 Our goal can be summarized by the phrase "to convert unknown unknowns to known unknowns." Our goal is to make our reader aware of important material he or she is not as familiar with as one should be, and to pursue further study to acquire such knowledge. This is not a programming book. Our goal is to describe the enabling activities that support programmers in producing high-quality software in the context of medical applications. We are less concerned by questions such as 'How should we code?' Our focus, rather, is on answering higher-level questions such as 'How do we decide what we need to code?' and 'How should the process be organized?' There is a wealth of material available that describes the actual coding process, and, therefore, we chose not to duplicate this type of description here"--

Zusammenfassung
An overview of medical software design, implementation and management. Covers technical, commercial and regulatory issues and includes cautionary real-world case studies. For undergraduates in biomedical engineering, electrical engineering, computer science, junior software engineers in the medical device industry, and digital health entrepreneurs.

Inhalt

Preface; Part 1. Regulatory, Business and Management Background: 1. Introduction to medical software; 2. The FDA and software; 3. Operating within a healthcare system; 4. Quality management systems; 5. Risk management; 6. Taking an idea to market: understanding the product journey; 7. Medical software applications and growth drivers; Part II. Scientific and Technical Background: 8. Mathematical background; 9. Topics in software engineering; Part III. An Example Medical Software Life Cycle Process: 10. The overall process; 11. Identifying user needs; 12. The system requirements specification; 13. The software design document; 14. Software construction and testing and verification; 15. Software validation; 16. Deployment, maintenance and decommissioning; Part IV. Case Studies: 17. Therac-25: software that killed; 18. Mars Climate Orbiter: lost without a trace; 19. Healthcare.gov: the failed launch of a critical webpage; 20. The 2020 Iowa Caucus app: an unreliable app that caused national embarrassment; 21. The Boeing 737-MAX disasters: using software to fix hardware problems; 22. The averted Y2K crisis: successful crisis and risk management; References; Index.