Original title: The Future of Safety for SaMD
Rhea Malhotra, Tanya Sharma, Krisha Patel, Satvika Sharma +6 · September 2026
Software inside an artificial organ must not fail, yet teams still test it using regular trials. This testing only spots mistakes engineers think to check for beforehand. For devices running inside people for months, the biggest dangers come from surprises nobody predicted. The researchers show how to use formal verification, a method that uses math to check computer code. Instead of guessing test cases, it proves the software obeys its rules across every single possible execution. If the math proof fails, it points out the exact sequence of inputs that breaks the program. These techniques are already used in trains, planes, and nuclear plants. They fit directly into existing medical software safety steps instead of replacing them.
Imagine you're cooking a meal from a new recipe. You taste as you go to see if it's coming out right. That works for the things you know to check, like salt or spice. But what if a burner turns on accidentally and you don't notice because you weren't watching for it? In this paper, the software is like the stove—testing only catches problems you thought to look for, but formal verification checks every possible way the stove could behave and guarantees the meal stays safe.
Artificial organs like heart pumps run software that can kill a patient if it fails—yet today's testing only catches bugs engineers already imagined. This paper shows how to use the same rigorous proof methods that protect planes and nuclear reactors, closing the gap so that no unexpected input can cause a fatal crash. For patients depending on these devices, it means the difference between guessing the software is safe and knowing it is.
The paper focuses on how to apply formal verification to artificial organs stage by stage, but does not report results from a specific case study or compare the approach against current testing methods in terms of defect rates or cost. It also does not quantify the effort required to write the formal specifications for a given medical device, which can be a significant practical barrier.
Ask anything about this paper. Answers come from its abstract, and say so when the abstract doesn't cover your question.
The Future of Safety for SaMD — Rhea Malhotra, Tanya Sharma, Krisha Patel et al.
Abstract licence: CC0
Explanation generated by Synthesis from the abstract — it is not the original paper. This is a preprint, so it hasn't necessarily been peer reviewed.