Digitizing your SaMD Testing

00:00

0.5
1
1.25
1.5
1.75
2

This is a podcast episode titled, Digitizing your SaMD Testing. The summary for this episode is: What is software as a medical device (SaMD)? How does one test SaMD? What testing is required? What are the risks related to your SaMD and its testing?  In this episode of the Global Medical Device Podcast, Etienne Nichols talks to Rahul Kallampunathil, Vice President of Arbour Group’s Digital Compliance practice, about digitizing your SaMD testing.Rahul builds teams that help companies proactively manage compliance risks toward a true digital enterprise. He is an innovative thinker with more than 18 years of experience in risk management, compliance, and internal controls focused on information technology and data. <h3>Some of the highlights of this episode include:</h3><ul><li>Rahul defines SaMD as software used to perform a medical purpose without being part of a hardware medical device. SaMD is capable of running on any general purpose platform, such as your Android or iOS mobile phone.</li><li>SaMD is different from software in a medical device (SiMD). SaMD is independent from hardware; SiMD is embedded in a physical medical device.</li><li>Also, there’s differences between SaMD and medical device data systems (MDDS). MDDS only transfers, stores, or displays medical device data, but it does not have an algorithm or business rule to help make medical decisions.</li><li>IEC 62304 impacts SaMD organizations and how they approach the risk of their solution. All SaMDs are not equal, and it’s important to understand the level of risk in every SaMD.</li><li>Companies should prepare for SaMD testing with a clinical evaluation to demonstrate a valid clinical association between SaMD’s output and targeted clinical condition.</li><li>Before thinking about designing and developing a product, a quality management system (QMS) should be established. Software companies need to adopt and modify their QMS to serve their product and its users, while fulfilling FDA requirements.</li><li>Rahul discusses the pros and cons of manual versus automated/electronic  documentation and testing, including risk management for patient safety.</li><li>Best practices for SaMD testing are using agile and devops methodologies. Potential pitfalls are not testing continuously, even after the product is on the market. </li></ul><h3>Memorable quotes from Rahul Kallampunathil:</h3>“Software as a medical device - it is software that is intended to be used for a medical purpose, and it performs that purpose without being part of a hardware medical device.”“There is no physical device, in this case, that you can touch and feel. It’s purely software.”“The nature of software - it’s something that you cannot touch or see. It’s all code. From a testing perspective, especially, there’s a lot of things that you need to pay attention to.” “The quality management system or quality management process, that has to be established even before you think about the product, even before you design the product.”<h3>Links:</h3><a href="https://www.linkedin.com/in/rahukall" rel="noopener noreferrer" target="_blank">Rahul Kallampunathil on LinkedIn</a><a href="https://www.linkedin.com/in/etiennenichols/" rel="noopener noreferrer" target="_blank">Etienne Nichols on LinkedIn</a><a href="https://www.arbourgroup.com/?utm_source=google&utm_medium=cpc&utm_campaign=&utm_term=arbour%20group%20llc&gclid=CjwKCAjwgr6TBhAGEiwA3aVuIeDRT-dWXWRK8KI8v6f_w4Txyww2Ok_kIXj4ynxmzwxSGCfVzOWCYhoCG5UQAvD_BwE" rel="noopener noreferrer" target="_blank">Arbour Group LLC</a><a href="https://www.fda.gov/medical-devices/digital-health-center-excellence/software-medical-device-samd" rel="noopener noreferrer" target="_blank">FDA - SaMD</a><a href="https://www.fda.gov/medical-devices/general-hospital-devices-and-supplies/medical-device-data-systems" rel="noopener noreferrer" target="_blank">FDA - Medical Device Data Systems (MDDS)</a><a href="https://www.fda.gov/medical-devices/digital-health-center-excellence/cybersecurity" rel="noopener noreferrer" target="_blank">FDA - Cybersecurity</a><a href="https://www.iso.org/standard/38421.html" rel="noopener noreferrer" target="_blank">IEC 62304</a><a href="https://www.imdrf.org/" rel="noopener noreferrer" target="_blank">International Medical Device Regulators Forum (IMDRF)</a><a href="https://www.youtube.com/channel/UCYfQsPqHW8H8mZ4xpM4gn1Q" rel="noopener noreferrer" target="_blank">Greenlight Guru YouTube Channel</a><a href="/medical-device-community" rel="noopener noreferrer" target="_blank">Greenlight Guru Community</a><a href="https://www.greenlight.guru/academy" rel="noopener noreferrer" target="_blank">Greenlight Guru Academy</a><a href="https://www.greenlight.guru/medical-device-community" rel="noopener noreferrer" target="_blank">MedTech Nation</a><a href="https://www.greenlight.guru/" rel="noopener noreferrer" target="_blank">Greenlight Guru</a>

DESCRIPTION

What is software as a medical device (SaMD)? How does one test SaMD? What testing is required? What are the risks related to your SaMD and its testing?

In this episode of the Global Medical Device Podcast, Etienne Nichols talks to Rahul Kallampunathil, Vice President of Arbour Group’s Digital Compliance practice, about digitizing your SaMD testing.

Rahul builds teams that help companies proactively manage compliance risks toward a true digital enterprise. He is an innovative thinker with more than 18 years of experience in risk management, compliance, and internal controls focused on information technology and data.

Some of the highlights of this episode include:

Rahul defines SaMD as software used to perform a medical purpose without being part of a hardware medical device. SaMD is capable of running on any general purpose platform, such as your Android or iOS mobile phone.
SaMD is different from software in a medical device (SiMD). SaMD is independent from hardware; SiMD is embedded in a physical medical device.
Also, there’s differences between SaMD and medical device data systems (MDDS). MDDS only transfers, stores, or displays medical device data, but it does not have an algorithm or business rule to help make medical decisions.
IEC 62304 impacts SaMD organizations and how they approach the risk of their solution. All SaMDs are not equal, and it’s important to understand the level of risk in every SaMD.
Companies should prepare for SaMD testing with a clinical evaluation to demonstrate a valid clinical association between SaMD’s output and targeted clinical condition.
Before thinking about designing and developing a product, a quality management system (QMS) should be established. Software companies need to adopt and modify their QMS to serve their product and its users, while fulfilling FDA requirements.
Rahul discusses the pros and cons of manual versus automated/electronic documentation and testing, including risk management for patient safety.
Best practices for SaMD testing are using agile and devops methodologies. Potential pitfalls are not testing continuously, even after the product is on the market.

Memorable quotes from Rahul Kallampunathil:

“Software as a medical device - it is software that is intended to be used for a medical purpose, and it performs that purpose without being part of a hardware medical device.”

“There is no physical device, in this case, that you can touch and feel. It’s purely software.”

“The nature of software - it’s something that you cannot touch or see. It’s all code. From a testing perspective, especially, there’s a lot of things that you need to pay attention to.”

“The quality management system or quality management process, that has to be established even before you think about the product, even before you design the product.”