{"id":484958,"date":"2024-01-12T22:41:34","date_gmt":"2024-01-13T03:41:34","guid":{"rendered":"https:\/\/platohealth.ai\/what-medical-device-software-to-develop-under-qms\/"},"modified":"2024-01-13T02:38:14","modified_gmt":"2024-01-13T07:38:14","slug":"what-medical-device-software-to-develop-under-qms","status":"publish","type":"post","link":"https:\/\/platohealth.ai\/what-medical-device-software-to-develop-under-qms\/","title":{"rendered":"What Medical Device Software to Develop Under QMS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
\n

The line between the device and non-device components of medical device software can sometimes seem blurry. Making the wrong choice to not develop a software module under design controls may lead to expensive, time-consuming rework.<\/p>\n

How do you decide which parts of your device fall under your QMS umbrella, and which don\u2019t? And how do you account for changes to your device during development as well as its potential changes in the future?<\/p>\n

With good planning and forethought, you can lay the groundwork for a strategy that evolves with your device, keeps development on track and prepares you for any way the wind may blow.<\/p>\n

Join Orthogonal on February 2nd, 2024 at 12 PM EST<\/strong> as we tackle the challenge of determining when to develop software under design controls. You\u2019ll hear from expert speakers who have solved this challenge for businesses of all sizes, including venture-backed startups and Fortune 500 MedTech firms.<\/p>\n

You\u2019ll leave this webinar with:<\/p>\n