Medical technology companies operate inside a regulatory system where the device class, software function, and quality management documentation determine what a firm must submit before it can sell a product. FDA guidance divides devices into Class I, II, and III, with regulatory control increasing across those categories [1]. Most Class I devices are exempt from Premarket Notification 510(k), most Class II devices require a 510(k), and most Class III devices require Premarket Approval [1]. For software functions that meet the device definition, the agency recommends documentation organized by Basic or Enhanced Documentation Level [3]. A company evaluating a supplier, partner, or acquisition target should therefore examine the same artifacts an FDA reviewer would request: classification rationale, software architecture and testing records, and quality system evidence tied to 21 CFR Part 820 as amended by the Quality Management System Regulation.

Device Classification Sets the Premarket Route

The first workflow distinction among medical technology companies is the regulatory route attached to the device category. FDA states that medical devices are classified into Class I, II, and III, and that regulatory control increases from Class I to Class III [1]. The classification regulation defines the regulatory requirements for a general device type, not for a single product line [1]. A manufacturer cannot choose its route freely; the device classification regulation determines whether a 510(k), a PMA, or an exemption applies to that general type [1].

This distinction matters for procurement and partnership decisions because it changes the evidence burden. Most Class I devices are exempt from Premarket Notification 510(k), while most Class II devices require that submission [1]. Class III devices are described as high risk devices that pose a significant risk of illness or injury and require Premarket Approval [1]. A company comparing two potential suppliers should first confirm the product code and classification for each device, then ask which premarket route the manufacturer followed. The source does not provide a current count of devices in each class or a list of exempt Class II devices, so those details remain unknown from the retrieved documentation [1].

Software Functions Require Documentation Level Decisions

For medical technology companies whose products include device software functions, FDA recommends a risk-based documentation approach. The guidance on premarket submissions for device software functions describes Basic and Enhanced Documentation Levels and identifies the information generally necessary to evaluate safety and effectiveness [3]. The guidance applies to software functions that meet the device definition under section 201(h) of the Federal Food, Drug, and Cosmetic Act [3]. It does not apply to automated manufacturing and Quality System software or software that is not a device [3].

The documentation elements include system and software architecture diagrams, software life cycle process summaries, and testing records. For Basic Documentation Level, FDA recommends a summary description of testing activities at the unit, integration, and system levels [6]. For Enhanced Documentation Level, the agency recommends a complete configuration management and maintenance plan in addition to the summary documentation requested for Basic [6]. A medical technology company evaluating a software-enabled device should ask whether the manufacturer can produce the architecture diagram, traceability information, and system level test protocol with expected results, observed results, and pass/fail determination [6].

What to Request in a Documentation Review

For a software-enabled device, request the system and software architecture diagram showing modules, layers, interfaces, data inputs, outputs, and flow, along with how users or external products interact with the system [6]. Request the system level test protocol including expected results, observed results, and pass/fail determination, plus the system level test report [6]. For the quality system, request evidence that the manufacturer has addressed the February 2026 QMSR amendment and the current computer software assurance guidance, including records of who performed testing and the date testing was performed [1][2]. For European products, request post-market surveillance documentation aligned with MDR or IVDR requirements [4].

QMSR and Computer Software Assurance Change Inspection Evidence

The Quality Management System Regulation became effective on February 2, 2026, amending the device current good manufacturing practice requirements of 21 CFR Part 820 and incorporating ISO 13485:2016 by reference [1]. On the same date, FDA stopped using the Quality System Inspection Technique for device inspections and began utilizing a different inspection approach [1]. For medical technology companies, this means the quality system evidence an inspector expects is now tied to the incorporated standard rather than the older QSIT framework [1].

FDA also issued revised guidance on computer software assurance for production and quality management system software on February 3, 2026 [2]. The guidance describes computer software assurance as a risk-based approach to establish confidence in automation used for production or quality management systems [2]. It identifies where additional rigor may be appropriate and describes testing activities that can provide objective evidence to fulfill regulatory requirements [2]. The guidance is nonbinding and does not establish legally enforceable responsibilities unless specific regulatory or statutory requirements are cited [2]. A company assessing a manufacturing partner should therefore ask whether the partner has mapped its software assurance evidence to the February 2026 guidance and the amended Part 820, not to the superseded September 2025 version [2].

Technical Documentation Gaps Cluster Around Cybersecurity and Post-Market Surveillance

NSF, a testing and certification organization, identifies five recurring technical documentation challenges based on its work with medical device manufacturers [4]. One observed gap is a lack of cybersecurity documentation, with manufacturers struggling to meet standards such as the IEC 81001-series and guidelines from NIST [4]. Another is post-market surveillance documentation falling short of MDR and IVDR requirements, resulting in nonconformities [4]. These observations come from NSF's client experience and are not presented as a statistically representative survey of the medical technology industry [4].

NSF also points to gaps in risk management documentation and recommends regular review against the current state-of-the-art [4]. The organization advises integrating risk management process interfaces with design and development, usability engineering, clinical evaluation, and biological evaluation [4]. For a company evaluating a European supplier, the practical question is whether the technical file includes current PMS documentation aligned with MDR or IVDR, not merely a legacy design dossier [4]. The source does not quantify how many manufacturers have each gap, so prevalence cannot be established from the retrieved material [4].

A Hypothetical Supplier Evaluation Workflow

A useful evaluation exercise is to model a hypothetical procurement team comparing two contract manufacturers for a Class II software-enabled monitoring device. The team would first request the product code and classification regulation for the device type to confirm the 510(k) route [1]. Second, it would ask for the software documentation level determination and the corresponding architecture diagram, life cycle summary, and system level test report [6]. Third, it would request evidence that the quality system reflects the February 2026 QMSR amendment and the current computer software assurance guidance [1][2].

This hypothetical is a suggested decision workflow, not a tested procurement method. The retrieved sources do not describe an actual evaluation conducted by any named buyer, and no source provides a scoring rubric or pass/fail threshold for supplier documentation. A team using this workflow would still need to resolve unknowns such as the specific device classification, the software risk level, and whether the supplier's technical file includes MDR or IVDR post-market surveillance documentation [4]. Those determinations depend on product-specific facts that are not present in the public documentation.