Regulatory Open Forum

 View Only
  • 1.  Software and cyber security for 510(k)

    Posted 30-May-2023 08:22

    We have a device that is going to be connected to wifi of the hospital and my question is would it be ok for the device to update its software using wifi?
    What guidances and regulations should I be looking into? And what about cyber security
    And if we update the software from the hospital wifi, would the old version be considered as a silent recall? My thought is this would be a silent recall - just want to confirm it with industry peers.
    Thanks!



    ------------------------------
    Lulu Zhang
    Regulatory Affairs Manager/ PRRC
    Canada
    ------------------------------


  • 2.  RE: Software and cyber security for 510(k)

    Posted 30-May-2023 10:06

    Hi Lulu

    Yes, it's ok to use most any technology that works and is convenient for your users.

    Yes, read the cybersecurity guidances. They are very important in a situation like this. Also basic risk management.

    No, there is no US concept of silent recall. An ordinary upgrade is not a recall, and if you're doing an actual recall you aren't usually allowed to be silent about it. This guidance may help clarify the difference: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/distinguishing-medical-device-recalls-medical-device-enhancements



    ------------------------------
    Anne LeBlanc
    United States
    ------------------------------



  • 3.  RE: Software and cyber security for 510(k)

    Posted 30-May-2023 10:55

    Hi Lulu, What is the reason for the update, what functionality changed, what is the difference between old version and new version, all these will help you understand what kind of action is required. It is a good practice to document the thought process and reference guidance what is the decision in such cases. 
    when a manufacturer remotely updates or patches the software of a medical device for safety concerns and defects It mandates a recall. 
    If it is just an enhancement then it is not a device recall, again enhancement definition has to be met according to recall guidance shared by Anne (Distinguishing Medical Device Recalls from Medical Device Enhancement)



    ------------------------------
    Raje Devanathan
    Amerisource Bergen
    TPIreg, Innomar Strategies
    Senior Manager - Regulatory Affairs, Medical Devices
    rdevanathan@tpireg.com
    3470 Superior Court
    Oakville ON L6L0C4
    Canada
    ------------------------------



  • 4.  RE: Software and cyber security for 510(k)

    Posted 30-May-2023 11:38

    Thank you Raje.
    I suppose it will be an enhancement.
    Thank you!



    ------------------------------
    Lulu Zhang
    Regulatory Affairs Manager/ PRRC
    Canada
    ------------------------------



  • 5.  RE: Software and cyber security for 510(k)

    Posted 30-May-2023 11:37
    Edited by Silu Zhang 30-May-2023 11:39

    Thank you so much Anne! This is really helpful.



    ------------------------------
    Lulu Zhang
    Regulatory Affairs Manager/ PRRC
    Canada
    ------------------------------



  • 6.  RE: Software and cyber security for 510(k)

    Posted 31-May-2023 07:45
    Hi Lulu!

    Welcome to this exchange.  So, besides the recall versus enhancement issue noted by the others, be sure to review FDA guidance on when to submit a new 510k for a device change or software change to ensure the change does not require a new 510k (assuming this is a 510k classed device).

    Hope the rest of your spring went well since we last spoke!





  • 7.  RE: Software and cyber security for 510(k)

    Posted 31-May-2023 08:05

    Thank you, Ginger, for the heads up. Yes, sometimes it might be a new 510(k) submission.
    What a wonderful and pleasant surprise to meet you here! 
    You are always helpful!
    Spring is good, and I can't wait to start summer with all the water activities for kids.
    Take care and enjoy the summer. :)



    ------------------------------
    Lulu Zhang
    Regulatory Affairs Manager/ PRRC
    Canada
    ------------------------------



  • 8.  RE: Software and cyber security for 510(k)

    Posted 31-May-2023 08:10

    Dear Lulu, 

    in my eyes this would be a wireless function of the device. You for sure need to specify the function and the risk associated with failure, disruption, or delay of communciation. The risks of wirelss functions are defined in AAMI TIR69.
    You as well need to define the Quality of Service and state if the wireless function is secured by enabling the security features embedded in the wireless technology or by other means.
    Last but not least, you have to add the following in the labeling: QoS, frequency, power, operating distance, security and risks and mitigations about wireless use included.



    ------------------------------
    Frederike Brühschwein-Mandic
    Senior Consultant
    Düdingen
    Switzerland
    ------------------------------