FREQUENTLY Asked Questions

What is the documentation required for a software-related submission?

View All FAQs
About the Author
Proxima CRO Team
Isabella Schmitt, RAC
Director of Regulatory Affairs
Ms. Schmitt has also served in additional regulatory affairs and clinical research roles in which she contributed to multiple regulatory submissions and clinical affairs projects across a wide range of indications.

Software-related documentation that you provide in your premarket submission should be consistent with the intended use of the Software Device, the Level of Concern, and the type of submission. This section describes the documentation that the FDA recommends you include in your premarket submission based on the Level of Concern. However, you should follow the recommendations in device-specific guidance, if available for your device. In general, the documentation provided in your submission should:

  • describe the design of your device
  • document how your design was implemented
  • demonstrate how the device produced by your design implementation was tested
  • show that you identified hazards appropriately and managed risks effectively
  • provide traceability to link together design, implementation, testing, and risk management.

These recommendations are keyed to the Level of Concern of your device and are predicated on your effective implementation and management of the QSR, including Design Controls.

FDA believes the recommended documents will generally be the same documents that you would normally generate during the development of a Software Device. Therefore, in a properly managed and documented medical device software development environment, the documents that you submit in response to the recommendations in this guidance may be copies of your product development documents.

Related Terms:
No items found.
Related FAQs:
More Questions? We're here to help!
SPEAK WITH A SPECIALIST