this post was submitted on 10 May 2024
123 points (100.0% liked)
Technology
37754 readers
293 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The problem with this logic is the manufactures have no control over the iPhone update. The article didn't go into exactly what happened, but it could have been that the device worked fine at launch, but then Apple released an update which caused an issue in the app. Even if it didn't happen this way I could definitely see it happening. Using an app for critical life sustaining medical devices is like playing Russian Roulette, an update from Google or Apple can put you in the hospital, or worse.
You need an incredibly robust quality management system to even achieve certification (allowing you to place on the market) when creating systems which include life support function, or functions which potentially could kill a user. All potential changes both within and outside of the manufacturers' control MUST be assessed and constantly monitored so such issues CANNOT arise.
No one should be able to legally place an unsafe app on the market, or legally perform changes to the app without the necessary checks and balances.
Medical device approvals in most countries are definitely not the wild west. Although they are not perfect.