Regulatory Open Forum

 View Only
  • 1.  FDA - Changes to Software and Special 510(k)

    This message was posted by a user wishing to remain anonymous
    Posted 25-Jan-2021 17:21
    This message was posted by a user wishing to remain anonymous

    Hi RAC Community,
    I have a question regarding change to SaMD and opinions on weather a Special 510(k) is needed.

    The SaMD in question was recently 510(k) cleared and we have not yet started selling the software in the US. The device is used to analyze MRI images and aid in the diagnosis of a liver condition. The dieses is not life-threatening.
    Recently we have realized that the device is producing a false positive (a very high value compared to the predicate's value) result for a certain image (only one image that was not part of the validation dataset used for 510(k) submission). The reason for this anomalous result was due to resizing of the image that is done before the SaMD does the analysis. To fix this anomaly and avoid a false positive result we are changing this resizing tool. As result of this modification there is a minor change in the sensitivity, specificity, negative and positive percent agreement values of the device. There is no change to the core software that does the analysis; no change to the intended or indication of use; no change in the technology of the device; and no new risk have been identified.

    My question is do we require to submit a special 510(k) for this change or a letter to file will be sufficient?

    Thanks


  • 2.  RE: FDA - Changes to Software and Special 510(k)

    Posted 26-Jan-2021 07:28
    Hello Anon,

    You probably already have, but you should got through the FDA's guidance document when a change is being made to a software to follow on through if a new 510(k) would be required.  There are many factors to consider on this point, including the original issue, why change was made, and the overall impact of the change.  Off the top of my head because the performance criteria has changed, I might say a conservative regulatory approach would be to submit a new 510(k).  Although the indications for use and other parameters may not have changed, if performance has changed this might mean a new submission.

    ------------------------------
    Richard Vincins RAC
    Vice President Global Regulatory Affairs
    ------------------------------



  • 3.  RE: FDA - Changes to Software and Special 510(k)

    Posted 26-Jan-2021 08:09
    I'm seconding Richard's point. Here's the link to that guidance. We use if for every software release.
    https://www.fda.gov/regulatory-information/search-fda-guidance-documents/deciding-when-submit-510k-software-change-existing-device

    ------------------------------
    Timothy Roloff
    Sr. Regulatory / Quality Engineer
    Pewaukee WI
    United States
    ------------------------------



  • 4.  RE: FDA - Changes to Software and Special 510(k)

    This message was posted by a user wishing to remain anonymous
    Posted 26-Jan-2021 08:38
    This message was posted by a user wishing to remain anonymous

    Thank you Richard and Timothy for your feedback.
    I have gone through the FDA guidance document for software change. The questions that I am unable to figure out in the guidance document are
    • "intent to significantly improve the safety or effectiveness" and
    • "significantly affect clinical functionality or performance specifications".
    Our intent is improve the safety of the device, not significantly but small improvement, which has a minor statistical changes in performance specification with no effect on clinical functionality. What is a "significantly" improvement of safety and performance specification?

    And if we do have to submit a new 510(k), can we submit a Special 510(k) instead of the Traditional 510(k), if the changes qualifies for it?

    Thanks for you inputs


  • 5.  RE: FDA - Changes to Software and Special 510(k)

    This message was posted by a user wishing to remain anonymous
    Posted 26-Jan-2021 08:38
    This message was posted by a user wishing to remain anonymous

    510(k)'s are not usually generated for bug fixes.


  • 6.  RE: FDA - Changes to Software and Special 510(k)

    Posted 26-Jan-2021 16:56

    Remediation of diagnostic devices always seems to be tricky, even when the object of the diagnostic device is a non-life-threatening disease.  While it is certainly important that we make a good-faith effort to apply FDA's 510(k) decision-making guidance already discussed, I would also add that it is equally (if not more) important to remember that, at the end of the day, regardless of the thought-paradigms in the guidance documents, FDA ultimately looks at these scenarios through the lens of public health and welfare.

    Though a device's false positives may indeed only be for a non-life-threatening liver disease, FDA will nonetheless require full consideration of the associated and reasonably foreseeable risks.  Specifically, in the case of false positive liver diagnoses, it is important to be sure to understand the reasonably foreseeable severity of harm (if any) and probability of harm (if any) stemming from a patient's and physician's false beliefs that the patient has a liver disease, when in fact the patient does not actually have such disease.

    A primary risk in false positive scenarios can be related to the unnecessary administration of medical treatment (e.g., certain drugs, medical procedures, etc.), and to the emotional stress for the patient.  Disease treatment and emotional stress can be significant even, for a non-life-threatening disease.  Consequently, design changes made to control such risk might be viewed by FDA as an intent to "significantly" improve the safety or effectiveness, or to "significantly" affect clinical functionality or performance specifications.

    One way to get insights about the meaning of "significantly" in a given context is to do so in correlation with the ranking scales in the firm's risk management process, and also perhaps in correlation with FDA's Health Hazard Assessment (HHE) / Health Risk Assessment (HRA) tool.

    Because the compliance risk of a wrong 510(k) decision can be significant, the Sponsor may find it beneficial to appropriately consult the agency on the issue to be sure a proper decision is made.  Remember also that such transparency with FDA will inevitably lead to a discussion and consideration of the need (or lack thereof) for a recall (FDA uses the HRA for that).  Whether or not the Sponsor will find such transparency acceptable depends, at least in part, on the Sponsor's philosophy regarding its public health obligations.



    ------------------------------
    Kevin Randall, ASQ CQA, RAC (U.S., Europe, Canada)
    Principal Consultant
    ComplianceAcuity, Inc.
    Ridgway, CO
    United States
    www.complianceacuity.com
    © Copyright 2020 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------