New FDA guidance on premarket submission for software: what happens now?

Software Documentation Elements 

Basic Documentation Level 

Enhanced Documentation Level 

Documentation Level Evaluation 

A statement indicating the Documentation Level and a description of the rationale for that level. 

Software Description* 

Software description, including overview of significant software features, functions, analyses, inputs, outputs, and hardware platforms. 

Risk Management File 

Risk management plan, risk assessment demonstrating that risks have been appropriately mitigated, and risk management report. 

Software Requirements Specification (SRS)* 

SRS documentation, describing the needs or expectations for a system or software, presented in an organized format, at the software system level or subsystem level, as appropriate, and with sufficient information to understand the traceability of the information with respect to the other software documentation elements (e.g., risk management file, software design specification, system and software architecture design chart, software testing). 

System and Software Architecture Design 

Detailed diagrams of the modules, layers, and interfaces that comprise the device, their relationships, the data inputs/outputs and flow of data, and how users or external products (including information technology (IT) infrastructure and peripherals) interact with the system and software. 

Software Design Specification (SDS)* 

FDA is not recommending the SDS as part of the premarket submission. Sponsor should document this information on the design via the DHF for the device. During premarket review, FDA may request additional information, if needed, to evaluate the safety and effectiveness of the device. 

SDS documentation, including sufficient information that would allow FDA to understand the technical design details of how the software functions, how the software design completely and correctly implements all the requirements of the SRS, and how the software design traces to the SRS in terms of intended use, functionality, safety, and effectiveness. 

Software Development, Configuration Management, and Maintenance Practices 

A summary of the life cycle development plan and a summary of configuration management and maintenance activities; 

OR 

A Declaration of Conformity to the FDA-recognized version of IEC 62304, including subclasses 5.1.1-5.1.3, 5.1.6-5.1.9, clause 6 and clause 8 among others as applicable. 

Basic Documentation Level, PLUS complete configuration management and maintenance plan document(s); 

OR 

A Declaration of Conformity to the FDA-recognized version of IEC 62304, including subclasses 5.1, clause 6, and clause 8 among others as applicable. 

Software Testing as Part of Verification and Validation 

A summary description of the testing activities at the unit, integration and system levels; 

AND 

System level test protocol including expected results, observed results, pass/fail determination, and system level test report. 

Basic Documentation Level, PLUS unit and integration level test protocols including expected results, observed results, pass/fail determination, and unit and integration level test reports. 

Software Version History* 

A history of tested software versions including the date, version number, and a brief description of all changes relative to the previously tested software version. 

Unsolved Software Anomalies * 

List of remaining unresolved software anomalies with an evaluation of the impact of each unresolved software anomaly on the device’s safety and effectiveness.