510(k) Software Documentation: What to Prepare Before You Submit

A 510(k) for a device with software needs the standard premarket notification content plus a software package sized to the device's risk. The package has ten elements, Basic and Enhanced documentation differ in three of them, and the work goes most smoothly when you produce it while you build.

In short

  • A 510(k) shows FDA that a device is substantially equivalent to a legally marketed predicate, and for a device with software it includes the documentation described in FDA's June 2023 guidance on device software functions.
  • That guidance lists ten documentation elements, from a documentation level evaluation to a list of unresolved anomalies, and the Enhanced level adds a software design specification, complete configuration management and maintenance plans, and unit and integration test protocols and reports.
  • 510(k)s go in through the eSTAR template and the CDRH Portal, so the practical job is to keep these records current during development, so that the submission is assembled from documents that already exist.

For a 510(k) that includes software, you prepare two sets of material. The first is what every premarket notification needs: device names and classification, proposed labeling, the comparison with a predicate device and a 510(k) summary or statement. The second is the software documentation FDA describes in its June 2023 guidance, Content of Premarket Submissions for Device Software Functions. That part has ten elements, and the detail each one needs depends on the documentation level, Basic or Enhanced, which you set from the risk of the device's software functions.

What is a 510(k), and where does software fit?

FDA describes a 510(k) as a premarket submission made to demonstrate that the device to be marketed is substantially equivalent to a legally marketed device. Substantial equivalence means the new device has the same intended use as the predicate and either the same technological characteristics, or different ones that do not raise different questions of safety and effectiveness. FDA says the determination is usually made within 90 days, and its order clears the device for commercial distribution.

Software enters the comparison as a technological characteristic. A new algorithm, a new platform or a new input can be the difference FDA has to evaluate. The software guidance applies to 510(k)s and also to De Novo requests, PMA applications and other premarket submission types, so the same package carries over if your pathway changes.

What does every 510(k) need?

21 CFR 807.87 sets the content of a premarket notification. The items that shape most software device submissions are:

  • The trade name and the common or classification name of the device.
  • The device's class and classification panel, or a statement that it is unclassified with the basis for that view.
  • Proposed labels, labeling and advertisements sufficient to describe the device, its intended use and directions for use.
  • A statement of how the device is similar to or different from comparable marketed devices, with supporting data.
  • For a significant change or a new intended use, data showing the effects on safety and effectiveness were considered.
  • A 510(k) summary or a 510(k) statement.
  • Financial certification or disclosure where clinical studies are used, and a statement that clinical studies followed the applicable rules.
  • A statement that all data and information submitted are truthful and accurate and that no material fact has been omitted.

The format is fixed. FDA's eSTAR page says all 510(k) and De Novo submissions, unless exempted, must use eSTAR, an interactive PDF form that guides applicants through preparing the submission, and must be submitted through the CDRH Portal. The portal will not accept an eSTAR marked incomplete. The page lists a 1 GB limit per attachment and 4 GB for the whole eSTAR.

Which software documents go into the 510(k)?

Table 1 of FDA's software guidance lists ten elements. Most are the same at both levels. Three differ.

  • Documentation level evaluation: a statement of the level and the rationale for it.
  • Software description: significant features, functions, analyses, inputs, outputs and hardware platforms.
  • Risk management file: a risk management plan, a risk assessment showing risks were appropriately mitigated, and a risk management report.
  • Software requirements specification, organized so the information traces to the risk file, design, architecture and tests.
  • System and software architecture design: detailed diagrams of modules, layers and interfaces, their relationships, data inputs, outputs and flows, and how users or external products, including IT infrastructure and peripherals, interact with the system.
  • Software design specification: not submitted at the Basic level, where it stays in the design history file and FDA may request it. At the Enhanced level, enough detail for FDA to understand how the design implements every requirement and traces to the SRS.
  • Development, configuration management and maintenance practices: at Basic, summaries of the life cycle plan and of configuration management and maintenance activities. At Enhanced, the complete configuration management and maintenance plans. At either level, a declaration of conformity to the FDA-recognized version of IEC 62304 can be used instead, covering the subclauses FDA names for each level.
  • Software testing as part of verification and validation: at Basic, a summary of unit, integration and system testing plus the system-level test protocol and report. At Enhanced, the unit and integration test protocols and reports as well.
  • Software version history: each tested version with its date, version number and a brief description of changes from the previous tested version.
  • Unresolved software anomalies: each remaining anomaly with an evaluation of its impact on safety and effectiveness.

Basic or Enhanced: which level applies?

FDA says Enhanced Documentation should be provided where a failure or flaw of any device software function could present a hazardous situation with a probable risk of death or serious injury to a patient, a user or others in the environment of use. The risk is assessed before risk control measures are applied. Basic Documentation applies everywhere else. The guidance notes that probable is meant to exclude purely hypothetical risks.

When you assess the level, the guidance asks you to consider known and foreseeable software hazards, reasonably foreseeable misuse, and the likelihood that device functionality is compromised by inadequate cybersecurity. FDA generally recommends Enhanced for constituent parts of combination products and for Class III devices, and for certain blood establishment software. If you are unsure, a Pre-Submission lets you get FDA feedback on the level before you file.

What should the software description answer?

The guidance gives a list of questions to address. They are worth answering in the first sprint, because the same answers drive the architecture and the risk file.

  • What is the software's role in the device: software-only, software that controls hardware, or an application that accompanies the device for data processing?
  • Who is the intended user: a patient, a caregiver, a healthcare professional or a combination?
  • What is the intended patient population, and does the software provide information for a specific disease or condition?
  • If it analyzes signals, patterns or images, what is the method: rule-based calculations, machine learning, a locked algorithm or an adaptive one?
  • For machine learning, what methods and frameworks were used, what data informed the model, what was done about bias and limitations, and how is the model made transparent to users?
  • Is the device interoperable, and if so, which products does it exchange data with and through which standards and interfaces?

For a modified device, the guidance asks for the number of the previous submission and the software changes since the last clearance, especially those that affect safety and effectiveness.

What else does a software device 510(k) usually carry?

  • Cybersecurity content. The software guidance points to FDA's separate cybersecurity guidance for it, and notes FDA may request additional architecture diagrams to address cybersecurity risks.
  • Interoperability information, for devices that exchange data with other products. FDA lists its guidance on interoperable medical devices among the related documents.
  • Human factors and usability work, where use errors could cause harm. FDA lists its human factors guidance among the related documents as well.
  • Labeling under 807.87, including directions for use that match what the software actually does.
  • Performance testing appropriate to the device, and clinical data if the comparison with the predicate needs it.

When does a software change need a new 510(k)?

FDA's 510(k) page says a new 510(k) is required when there is a significant change or modification to a legally marketed device's design, and that changes must follow the device quality system regulation in 21 CFR 820, with records kept. For software, FDA's October 2017 guidance, Deciding When to Submit a 510(k) for a Software Change to an Existing Device, helps manufacturers make that call for each software or firmware change.

This is why the version history and anomaly list matter after clearance too. Every release is a change you evaluate and document. For AI-enabled functions, FDA's framework for predetermined change control plans lets you get planned model changes authorized with the original submission, so they do not each need a new 510(k).

How do you prepare without a last-minute documentation crunch?

FDA's guidance does not prescribe a life cycle model. Waterfall, spiral and Agile are all acceptable, but it asks that design history file documentation stay synchronized with development, verification and validation. It warns that documentation created retrospectively, or long after the work, could raise concerns about whether the developer had adequate control of its design process. In practice:

  • Write the intended use and the documentation level rationale before the architecture is fixed.
  • Keep requirements, risks and tests in tools that link to each other, so a traceability report is a query you can run at any time.
  • Generate the version history from your release process and the anomaly list from your issue tracker, with a safety impact field filled in at triage.
  • Keep architecture diagrams in the repository and update them in the same pull request that changes the architecture.
  • Record off-the-shelf components, their versions and their known anomalies from the first dependency you add.
  • Do a dry run of the eSTAR months before submission to find the gaps while there is time to close them.

Where we fit

We build medical device software under an IEC 62304 process and produce the software documentation an FDA submission needs: the software description, requirements, architecture, risk file inputs, traceability, test records, version history and anomaly evaluations. The manufacturer owns the submission and files it. Onix Systems has built software since 2000 and has 370+ engineers. If you are preparing a 510(k) or inheriting a codebase that needs a documentation trail, talk to one of our engineers. Our free five-day technical audit ends with a written report on what your package has and what it still needs.