SPRING DISCOUNT
Get 30% off on toolkits, course exams, and Conformio yearly plans.
Limited-time offer – ends April 25, 2024
Use promo code:
SPRING30

Tag: "interoperable software as medical device" - Expert Advice Community

Guest

Guest

Create New Topic As guest or Sign in

HTML tags are not allowed

Assign topic to the user

  • Accessories and standalone SaMD

    Could you please provide advise on the following scenario: We are currently working with a medical device class III and in order to fulfil the medical device`s intended purpose, a SaMD is developed and defined as an accessory. There is a strong architecture segregation according to a risk based approach and 62304 that ensure the SaMD to be class II based on the FDA: ...an accessory has the same class as the “parent device”, unless there are different risks for the accessory and the parent device. The accessories are then independently classified according to these risks... Is it possible to assume a similar approach will comply with the MDR regulation?   Based on this assumption: Is it possible to reuse the same accessory with other Medical Devices with different classifications, most of them class II and have its own DHF? Is it possible to develop the accessory as a standalone SaMD as an interoperable software as medical device, with interface description, interoperable specification/residual risks etc..and with its own DHF? Is this scenarion feasible in the current MDR regulation? Thank you