D
dhruv
Hi all,
I'm a product developer at a medical imaging startup and we are currently working on preparing our first 510k submission for a Class II device. I am the software engineering team lead managing the external software development resources as well as preparing the documentation for the submission.
The documentation burden for software seems insurmountable and intimidating. We have finished the first few docs, such as the Software Development Life Cycle SOP, Software Development Plan, Software Level of Concern, Software Description. Currently, I'm working through the SRS, SDS, Software dFMEA (hazard analysis), and Architecture Charts.
Seeing as how the FDA guidances don't seem to distinguish between important and less critical documentation, it is hard to tell what I should prioritize. Does anyone have strategies for how to do a 80/20 analysis on what to focus on first and what to leave for later stages? How complete is the FDA looking for the docs to be? What kind of holes do they usually focus on in the documentation? I want to focus on the submission and will have more time for supporting docs during the validation phase.
Any advice would be very quite helpful, as I am finding the documentation burden overwhelming,
Thank you,
Dhruv
I'm a product developer at a medical imaging startup and we are currently working on preparing our first 510k submission for a Class II device. I am the software engineering team lead managing the external software development resources as well as preparing the documentation for the submission.
The documentation burden for software seems insurmountable and intimidating. We have finished the first few docs, such as the Software Development Life Cycle SOP, Software Development Plan, Software Level of Concern, Software Description. Currently, I'm working through the SRS, SDS, Software dFMEA (hazard analysis), and Architecture Charts.
Seeing as how the FDA guidances don't seem to distinguish between important and less critical documentation, it is hard to tell what I should prioritize. Does anyone have strategies for how to do a 80/20 analysis on what to focus on first and what to leave for later stages? How complete is the FDA looking for the docs to be? What kind of holes do they usually focus on in the documentation? I want to focus on the submission and will have more time for supporting docs during the validation phase.
Any advice would be very quite helpful, as I am finding the documentation burden overwhelming,
Thank you,
Dhruv