Table of contents
At a glance
When do Part 11 controls also apply to a medical device QMS process?
FDA’s CSA guidance explains that Part 11 generally also applies when a record required by Part 820 is maintained electronically. Identify the record and contents the QMSR process requires, then assess its electronic use, record controls and any signatures. The guidance describes enforcement discretion for certain Part 11 requirements but does not remove the underlying obligations. A routine technical log does not become a required QMSR record merely because of its file type.
- From the required record to electronic use of work.
- Responsibility for logging, system validation, and signature function to be separately verified.
- Do not consider enforcement discretion as the elimination of predicate rules.
1. Begin with the required documentation
An electronic complaint management system may include required complaint records, internal tasks, and technical diagnostic data. These objects do not automatically serve the same regulatory purpose. Therefore, identify the specific process and the required documentation upfront. Assign the relevant regulatory source to each element, rather than applying a single Part 11 label to the entire product.
In the applicable medical device scope, the current §820.35 includes additional requirements for certain records, particularly in the context of complaints and service. Additional requirements arise from the QMSR framework and the referenced standard. The complete standard mapping must be verified at the relevant text; a brief software description does not substitute for this work.
Sources: [1]
2. Verify actual electronic use
Part 11 covers electronic records that are created, modified, maintained, archived, retrieved, or transferred under FDA record-keeping requirements. Certain electronic submissions to the FDA are also included, even if individual records are not explicitly referenced in a specific FDA regulation. Therefore, considering only internal retention obligations would be incomplete.
The FDA Scope Guidance from 2003 emphasizes actual use. The mere presence of an electronic record does not automatically establish its validity. Question whether decisions are based on electronic data, their status values, or their potential for modification. Either a U.S. customer or a server location alone does not address either the predicate rule or Part 11 question.
3. Maintain a specific record inventory
The own matrix shows an exemplary complaint process in the appropriate QMSR scope. It describes the assignment method and not a complete mandatory catalog. In particular, the necessary content must be determined completely for your process and the relevant standard requirements.
A technical object may contain multiple required components. Conversely, a required record may be distributed across databases, equipment, and supplementary documents. The professional purpose of the record guides the evaluation; file extension or table name serves only as an indication of the technical implementation.
| Object | Purpose of the document | Mandatory reference | The following inspection |
|---|---|---|---|
| Complaint record | Required details and handling of the individual case | Appropriate QMSR requirements including §820.35 | Assign electronic content, changes, and availability responsibility |
| Assurance Result | Demonstrate compliance of a required software function | Relevant validation requirements within the QMSR framework | Assess electronic evidence and its complete context |
| Routine Start Log | Technical start without use as required evidence | In the example, there is no corresponding record purpose. | Not solely due to electronic storage, assign Part 11. |
| Error log import | Single justification for the absence of a required case | Significance initially open | Assess technical necessity, not indiscriminately exclude |
4. Derive controls from content and intended use
Has the electronic record scope been clarified, review the applicable Part 11 controls. Within the closed system, this may include access restrictions, appropriate copies, protection and retrievability, as well as traceable changes. The specific applicability and FDA enforcement policy should be considered separately.
The "closed" attribute is not generically determined by whether the system is hosted in the cloud or on a local server, but rather by control of access being exercised by the individuals responsible for the content. For open systems, additional considerations are outlined in §11.30. Therefore, avoid an architectural shortcut: a tenant name does not provide sufficient content control nor full implementation of all relevant controls.
5. Example: Complaint with supplemental file
A manufacturer records complaint R-24 electronically. The dataset includes the proposed case details; a image file documents the reported defect. A technical assessment and a decision on further actions are added. For this case, it is assumed that these components collectively provide the necessary evidence.
The table incorporates three amendments. What remains decisive in each case is which statement must be retained. The removal of a file is not solely justified because the dataset formally appears complete. Conversely, a technical reimplementation does not automatically necessitate a new substantive decision if the content and its assignment remain unchanged.
| Activity | Required justification | Planned control | Limit of the statement |
|---|---|---|---|
| Complete defect image | The image clearly belongs to R-24 | Check assignment and retrieval using the actual case | No evidence of all conceivable file formats |
| Correct erroneous product identification | Original and corrected relationship remains traceable | Evaluate authorization and change justification | No blanket immutability of all fields |
| Assessment approval | The individual responsible and the nature of the action are clearly defined. | Verify actual authorization/signature function | A status name alone does not constitute a Part 11 signature. |
| Export record | Required content remains completely understandable | Match dataset, relevant attachment, and context | A single overview PDF is not automatically sufficient. |
6. Evaluate signatures as a standalone function
A record may be Part 11 relevant without requiring every edit to be electronically signed. Determine which action, according to applicable requirements or your procedure, carries significance. If an electronic signature is used, the relevant requirements must be individually assessed.
Part 11 requires that for signed records, the name, date, time, and meaning of the signature must be displayed in any human-readable form (§ 11.50) and must be linked to the record (§ 11.70). For non-biometric signatures, specific requirements apply to identification components and consecutive time periods during which controlled system access is maintained. A standard login or any status change does not automatically validate the signature function; a specific implementation may integrate multiple requirements.
Sources: [2]
7. Do not confuse implementation policy with an exemption
The FDA Scope Guidance from 2003 outlines Enforcement Discretion for certain Part 11 requirements. Part 11 was not rescinded by this guidance. The underlying requirements remain relevant. The CSA Guidance from 2026 explicitly clarifies that the stated discretion regarding Part 11 system validation does not eliminate the corresponding validation requirements within the QMSR framework.
For your decision, this means: specifically define the record scope and the required safeguards. A general note such as "FDA does not require validation anymore" would be incorrect. Similarly, every technical log cannot be treated equally. The Guidance explicitly highlights the difference between required validation evidence and routine logs that do not serve this purpose.
8. Checklist for concurrent assessment
Summarize the results in a clear and structured mapping. A process may include multiple record types and various signature actions. These differences should remain visible, without requiring a separate documentation record for each source. Shared evidence may address different requirements, provided the mapping is clearly defined.
The following internal checklist supports the closure process. It neither replaces a comprehensive QMSR assessment nor the evaluation of specific Part 11 implementation. It primarily prevents the substitution of a product name or a general supplier statement for actual record review.
- Applicable medical device process and mandatory sources determines.
- Required record contents including relevant documentation are captured.
- Actual electronic usage and submissions considered.
- System boundary and appropriate controls justified.
- Signatory actions are individually evaluated for their significance.
- Required evidence from purely technical supplemental logs is distinguished.
- Open questions, responsible parties, and actions documented.
Project experience and collaboration
Link the electronic record to its purpose under the QMSR
With QA and process owners, we select required evidence and trace how it is created, reviewed and retained electronically. A technical startup log may have little bearing on the question, while a specific test report may provide the necessary validation evidence. We map record controls and, where applicable, signature functions to actual use. If records span media or systems, we also test how they are linked. Your designated owners make the regulatory determination.
Frequently asked questions about Electronic records under QMSR and Part 11
Does Part 11 apply additionally to the QMSR?
Generally yes, if a record required under Part 820 is maintained electronically. This is as stated in the FDA-CSA Guidance. Therefore, the assignment begins with the required record and its actual use. The mere installation of a QMS product does not automatically convert any technical information into a regulated record.
Does a paper printout of Part 11 render the requirement obsolete?
Not automatically. It is essential that the regulated activity is actually supported by appropriate documentation and that the paper record contains the required content. When electronic data are used to support decisions, the significance of those data cannot be simply eliminated through an additional printout.
Are all technical logs regulated records?
No. A routine start log without a demonstrable purpose for validation evidence or a relevant data loss can be interpreted differently from a log that documents required validation evidence or a relevant data loss. Assess the specific use case. The file type "Log" is neither an automatic inclusion nor exclusion rule.
Sources: [4]
Are Assurance Evidence themselves Part 11 relevant?
If appropriate electronic records are maintained in the relevant QMSR context, Part 11 may be applicable. CSA explicitly references this linkage. Determine the required evidence and the information it provides; not every casually generated technical file automatically qualifies.
Sources: [4]
Is a cloud application considered a closed system?
This cannot be determined solely from the hosting model. Part 11 defines "closed" based on access control by personnel responsible for the content. Verify the actual responsibilities and controls, including relevant administrative access.
Sources: [2]
Must every change be electronically signed?
A universal signing obligation for every change does not arise solely from Part 11. Determine the applicable requirement and the significance of the action. Traceable change controls and electronic signatures are related but not identical functions.
Sources: [2]
Does an approved status constitute an electronic signature?
The name of the status is insufficient. Verify personnel assignment, meaning, display, linking, and the relevant signature controls. A specific workflow action may implement a signature, but it must actually meet the applicable requirements.
Sources: [2]
Does Enforcement Discretion relieve the validation obligation?
Do we need separate validations for QMSR and Part 11?
What question should we ask first when considering a new application?
What specific documentation is required for which regulated process? Following this, we address the required content, actual electronic usage, and appropriate controls. This approach is more robust than the general question of whether the entire product is labeled as Part 11-compliant by the manufacturer.
Sources and review date
Source date: 7 October 2026. Regulatory requirements, guidelines, and industry practices must be categorized separately. Tables, figures, and case examples are to be considered standalone reference materials; they do not constitute completed product testing.
- 21 CFR Part 820 – Quality Management System RegulationCurrent QMSR text, effective 2 February 2026. See sections 820.1, 820.7, 820.10, 820.35 and 820.45.
- 21 CFR Part 11 – Electronic Records; Electronic SignatureseCFR display until 05.10.2026; §§11.1–11.300.
- FDA: Part 11 – Scope and ApplicationFinal guidance. The PDF is dated August 2003 and the status page September 2003. See sections I and III.A–C.
- FDA: Computer Software Assurance for Production and Quality Management System SoftwareFinal guidance of 3 February 2026. Non-binding recommendations for production and quality management system software in the medical device sector.
Sources checked: .
Jointly develop the specific evidence process
We support you with specific record assignment and the linking of QMSR process requirements to appropriate electronic controls.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

