We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.
To save content items to your account,
please confirm that you agree to abide by our usage policies.
If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account.
Find out more about saving content to .
To save content items to your Kindle, first ensure no-reply@cambridge.org
is added to your Approved Personal Document E-mail List under your Personal Document Settings
on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part
of your Kindle email address below.
Find out more about saving to your Kindle.
Note you can select to save to either the @free.kindle.com or @kindle.com variations.
‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi.
‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.
Providing a concise and accessible overview of the design, implementation and management of medical software, this textbook will equip students with a solid understanding of critical considerations for both standalone medical software (software as a medical device/SaMD) and software that is integrated into hardware devices. It includes: practical discussion of key regulatory documents and industry standards, and how these translate into concrete considerations for medical software design; detailed coverage of the medical software lifecycle process ; accessible introduction to quality and risk management systems in the context of medical software; succinct coverage of essential topics in data science, machine learning, statistics, cybersecurity, software engineering and healthcare bring readers up-to-speed; six cautionary real-world case studies illustrate the dangers of improper or careless software processes. Accompanied by online resources for instructors, this is the ideal introduction for undergraduate students in biomedical engineering, electrical engineering and computer science, junior software engineers, and digital health entrepreneurs.
This chapter discusses the processes of identifying the needs of our users, which is the first step in the software life cycle. We begin with an overview of the structure of creating new projects. Next, we apply the “Brown Cow” model (Section 11.1) as a guide for how to go about understanding the user’s current situation and future needs.
In this short chapter, we discuss the final three steps in the software life cycle: (1) deployment (Section 16.1), (2) maintenance (Section 16.2), and (3) decommissioning (Section 16.3). These are complex topics in their own right.
This chapter provides an overview of quality management systems (QMS). There is an increasing emphasis of regulators on the “organization” as opposed to the “product,” which places an even greater emphasis on the use of a QMS. We first introduce what a QMS is (Section 4.1) and provide some regulatory background, including a discussion of the recent FDA precertification program.
This chapter presents an introduction to risk management, a core regulatory requirement for all medical software. We begin with an overview of the regulatory background (Section 5.1) and then review both the international standard ISO 14971:2019 and a recent guidance document from the IMDRF. Next, we describe the process of risk analysis (Section 5.2), including issues related to the use of artificial intelligence/machine learning (AI/ML) techniques.
This chapter provides some basic background on selected topics in software engineering. This should be useful for those readers whose background is primarily in basic science and engineering, who may have not been previously exposed to this type of material. This chapter is meant to complement the introduction to mathematical topics presented in Chapter 8.
This chapter describes the software design document. This is the first step in the software life cycle where we leave the abstract plane and begin to think more concretely about the product. The structure of this chapter is as follows. First, we discuss (Section 13.1) that we are at the point of creating a bridge from the system requirements to the actual code.
This chapter presents the “business” view of medical software. It takes a company to bring an idea to market and, ultimately, clinical use. We begin with a brief description of issues related to entrepreneurship (Section 6.1): Should somebody who has a promising idea consider starting a company on their own?
This chapter presents an example medical software life cycle process. We first introduce the topic (Section 10.1), and introduce our example project – the image-guided neuro-navigation system – that we will use to illustrate the process over the next few chapters.
Much of the work involved in the development of medical software (and in particular the process of software validation) depends critically on an understanding of topics such as probability theory, statistics, and increasingly machine learning. The goal of this chapter is to provide students with some theoretical grounding in this general area.
This chapter describes the process of creating a system requirements document which is one of the most important steps in the software life cycle. First, we orient ourselves as to our position in this life cycle (Section 12.1). Next, we present a brief review of key regulatory issues (Section 12.2), and following this we describe a template for creating this document (Section 12.3).
This chapter begins by defining what medical software is and what makes it unique, and describing the regulatory process that governs it (Section 1.1), including a brief introduction to industry standards. Following this, we discuss the constraints (both business and technical) placed on the software process by the medical environment (Section 1.2).
This chapter describes the regulatory process for medical software, with a particular emphasis on the documents issued by the United States Food and Drug Administration (FDA). We first describe the FDA itself (Section 2.1), including a brief history of how the current process has evolved over the past century.