search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
Regulatory


and in predicting the risk of developing diseases,” is how Dr Sonja Marjanovic, director for healthcare innovation, industry and policy at RAND Europe puts it – a reasonable point when you recall that the robust use of big data can cut the average ER stay by up to 40%. Yet, whatever its rising authority, it’s equally clear that regulators have traditionally battled to fit the SaMD peg into a hole long shaped by physical medical devices – a problem that’s long stymied how insiders have been able to actually use medical software in practice. Now, however, with new, flexible regulation appearing on the horizon, SaMD could soon take a spot alongside more old-fashioned medical devices – with potentially revolutionary consequences for patients.


Software, hard work It’s hard to overstate how quickly SaMD – as a medical concept, if not a regulatory reality – has developed over recent years. Boasting a global market expected to reach $86bn by 2027, it’s increasingly proving its usefulness everywhere from MRIs to CT scans. Understand the proliferation of medical information over recent years and this jump makes sense; with around 30% of the world’s data now being generated by the healthcare industry, it was probably inevitable that insiders would seek to exploit it for the benefit of patients. In practice, SaMD includes a wide variety of different technologies. At the simpler end, an example could involve a piece of software that sends images from an MRI machine to a doctor’s smartphone. A more sophisticated use case might be software that collects data from X-rays and CT scans to create 3D models, which can then be used to develop a patient treatment plan. Yet for all the usefulness of SaMDs in theory – it’s not for nothing that industry leaders like Pfizer are investing heavily in medical software – regulation has typically been a barrier to their versatility. In large part, this can be understood by the very name ‘Software as a Medical Device’. Sometimes framed by regulators as fundamentally similar to their physical cousins, Dr Zuzanna Marciniak-Nuqui, an analyst at RAND Europe, suggests that this unsubtle approach has left SaMD providers struggling to exploit the inherent benefits software can offer. And despite being what Nick Fahy, a third RAND expert, calls a “moving target” – meaning they can easily be updated, hardly news to anyone who’s used an app before – older regulations have tended to treat software as rigidly as a hip replacement. Combined with other challenges, notably around trying to squeeze software into the long-standing regulatory frameworks initially developed for hardware, it’s perhaps unsurprising that Stephen Gilbert, professor of Medical Device Regulatory Science at the Else Kröner Fresenius Center, Dresden Technical University, should say that older SaMD regulations are less “flexible” than they might be. All


Medical Device Developments / www.nsmedicaldevices.com


the same, it’d be wrong to imply that SaMDs don’t need any regulatory oversight whatsoever. As Marciniak- Nuqui says, some researchers argue that software errors relate to many preventable health problems. This intuitively makes sense: lose a patient’s data, or code an algorithm in such a way that it recommends the wrong dosage, and the consequences could be serious. Nor is this merely a hunch. In a 2017 study, five electronic medical record systems were recalled in the US after it was uncovered that they displayed the medical information of the wrong patients, among other errors.


Flexibility and security


Given these twin tensions – unleashing the power of SaMDs while preserving patient safety – how should regulators proceed? The FDA’s so-called Digital Health Software Precertification (Pre-Cert) programme may offer an answer. First announced in 2019, the FDA released its final report on their clinical decision support software in September 2022 – and Gilbert is clearly pleased with the results. “There’s an interesting and nuanced position,” he argues, suggesting that it’s “pro-innovation and certainly pro-development.” What, then, does the Pre-Cert programme offer SaMDs? In effect, it removes the ‘medical device’ label from many medical software products – along the way freeing them from the excruciating regulatory rules developers have had to follow until now.


How the FDA decides which medical software comes under their classification of ‘non-device’ speaks elegantly to the way in which regulators are balancing flexibility and security. For one thing, the software can’t be used in an emergency, but must rather provide supportive advice – which may enhance doctors’ decision making, and therefore patient’s health, but isn’t strictly necessary to take lifesaving actions. From there, the ‘non-device’ software can’t use AI to analyse images, nor should it create a situation where a doctor unthinkingly follows what the technology says as


19


For the FDA to classify a SaMD product as a non- device it must generate insights that help doctors’ make decisions, but cannot make decisions about patient care itself.


l i g h t p o e t/Shutterstock.com


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140