1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice
You must be a registered member in order to post messages and view/download attached files in this forum.
Click here to register.

How to handle optional software feature that is part of a medical device, but not sold in the USA

Discussion in 'Medical Devices (21 CFR Part 820)' started by Thorsten Twellman, Nov 25, 2024.

Tags:
  1. Thorsten Twellman

    Thorsten Twellman New Member

    Joined:
    Nov 25, 2024
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Hello community,

    We are planning to add a new software feature (a complex image processing algorithm) to our software product that is sold in Europe (under MDR) and in the US (under the FDA). The specific feature is bound to a dedicated license key.

    We don't want to sell the feature/license key in the USA and only in the EU in the first step, so it should not be relevant to the FDA clearance process for the next version of our software product. Nevertheless, the feature is of course fully described in our technical documentation (functional specification, risk analysis, verification plan and report, etc.) that form the basis of for the clearance under MDR and FDA.

    How should we set up our technical documentation and communication for the FDA clearance of our software product? Do we have to make two versions of the full technical documentation (one for FDA and one for MDR) or is there a lean alternative?

    Thank you all!
    Thorsten
     
  2. yodon

    yodon Well-Known Member

    Joined:
    Aug 3, 2015
    Messages:
    211
    Likes Received:
    124
    Trophy Points:
    42
    Ultimately, I think you're going to have to say the feature is not available in the US. Probably a good topic for a pre-sub. You'd have to state an approach, you can't just ask them what the right approach is.