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.

Design control requirements of Part 820

Discussion in 'Medical Devices (21 CFR Part 820)' started by talent.acquiring, Feb 5, 2019.

  1. talent.acquiring

    talent.acquiring New Member

    Joined:
    Feb 5, 2019
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Can someone please describe these requirements and how they are relevant to a Software Quality Engineer?
     
    talent.acquiring, Feb 5, 2019
    #1
  2. yodon

    yodon Well-Known Member

    Joined:
    Aug 3, 2015
    Messages:
    203
    Likes Received:
    119
    Trophy Points:
    42
    Pretty broad question so the answer may be a little high-level.

    Design Controls in 21 CFR 820 (https://www.ecfr.gov/cgi-bin/text-i...27aa75df2d32&mc=true&node=pt21.8.820&rgn=div5) comprise design inputs, outputs, V&V, reviews, and change management. Clearly, each of those is relevant to software. Design inputs are your requirements (which should include risk controls to be implemented in software!). Design outputs are your architecture documents, design documents, etc. V&V include your software system tests and such. Reviews, in the standard, are more typical of "stage gate" reviews (e.g., a transition between requirements and design might include an overall review of the requirements for completeness, etc. - not necessarily an individual document review). Changes are how you control changes once your baseline is established.

    Another good source of information is IEC 62304. The FDA has recognized this as a consensus standard so complying with it will provide compliance with FDA requirements.

    Does that help or did you have more specific questions?
     
    yodon, Feb 6, 2019
    #2