21 CFR Part 11 compliance: the requirements and EU Annex 11 compared
Since 20 August 1997, 21 CFR Part 11 has set the conditions under which the FDA accepts electronic records and electronic signatures. It covers the records that the agency’s regulations require a maker to keep, once the maker keeps them in electronic form, and the electronic records it submits to the agency. Records that meet it may replace paper records, unless a rule requires paper, and signatures that meet it count as handwritten signatures.
This guide turns the rule’s scope into questions to answer about each record, then quotes each control and signature requirement from the official text, with what to do and the evidence to keep. It then sets Annex 11 of the EU’s good manufacturing practice (GMP) guidelines and the UK’s rules beside it. They ask for most of the same controls in medicines manufacturing, so one list of controls, mapped to all three, can serve the US, the EU and the UK.
21 CFR Part 11 in brief
- Part 11 covers records in electronic form that an FDA regulation requires, and electronic records submitted to the agency (11.1(b)).
- Closed systems need the eleven controls in 11.10. Open systems need those controls and more, such as document encryption and digital signatures (11.30).
- A signed electronic record shows the signer’s printed name, the date and time of signing, and what the signature means (11.50).
- Each electronic signature belongs to one person, and the organisation certifies its electronic signatures to the FDA in a letter signed by hand (11.100).
- Under its 2003 guidance, the agency does not intend to take enforcement action on Part 11’s own validation, audit trail, record retention and record copying requirements, as the guidance explains them. It intends to enforce the rule’s other requirements, and every requirement of the rules that call for the records.
- Those rules ask for controls of their own: controls on who can change records, accuracy checks and back-ups on a drug maker’s computer systems (21 CFR 211.68(b)), and validated production and quality system software for a device maker (ISO 13485 subclauses 4.1.6, 7.5.6 and 7.6, which Part 820 incorporates).
- In the EU, Annex 11 of the GMP guidelines covers the computerised systems used in medicines manufacturing.
- In the UK, the same Annex 11 applies, with the MHRA’s guidance on data integrity beside it.
Does Part 11 apply to your records? The scope test
This part applies to records in electronic form that are created, modified, maintained, archived, retrieved, or transmitted, under any records requirements set forth in agency regulations. This part also applies to electronic records submitted to the agency under requirements of the Federal Food, Drug, and Cosmetic Act and the Public Health Service Act, even if such records are not specifically identified in agency regulations. However, this part does not apply to paper records that are, or have been, transmitted by electronic means.
The FDA’s 2003 guidance on the rule reads its scope narrowly. It calls the record rules behind it “predicate rules”: the requirements of the Federal Food, Drug, and Cosmetic Act, the Public Health Service Act and the agency’s regulations other than Part 11. For a drug maker, the GMP rule on computer systems is 21 CFR 211.68(b):
Appropriate controls shall be exercised over computer or related systems to assure that changes in master production and control records or other records are instituted only by authorized personnel. Input to and output from the computer or related system of formulas or other records or data shall be checked for accuracy. The degree and frequency of input/output verification shall be based on the complexity and reliability of the computer or related system. A backup file of data entered into the computer or related system shall be maintained except where certain data, such as calculations performed in connection with laboratory analysis, are eliminated by computerization or other automated processes. In such instances a written record of the program shall be maintained along with appropriate validation data. Hard copy or alternative systems, such as duplicates, tapes, or microfilm, designed to assure that backup data are exact and complete and that it is secure from alteration, inadvertent erasures, or loss shall be maintained.
So a drug maker’s own rule asks it to control changes to records, check input and output for accuracy and keep a backup of the data. Where computerisation does away with some data, the rule asks for a written record of the program with validation data. The 2003 guidance on Part 11’s controls changes none of this.
For a device maker, Part 820 has incorporated ISO 13485 since 2 February 2026. The agency’s computer software assurance guidance of February 2026 says the 2003 enforcement discretion on validation “expressly does not apply to validation requirements for computer software used as part of production or the quality management system arising under Subclauses 4.1.6, 7.5.6, and 7.6 of ISO 13485.” Our guide to ISO 13485 and the FDA’s quality management system regulation sets out what Part 820 adds to the standard.
The scope questions, with what each answer means
Answer these questions for each record.
| Question about the record | What the answer means | Source |
|---|---|---|
| Does a predicate rule require you to keep it, or do you submit it to the FDA? | If neither, the record is outside Part 11, even when you keep it electronically. | The 2003 guidance |
| Do you keep it in electronic form in place of paper? | Part 11 applies. | 11.2(a); the 2003 guidance |
| Do you keep it on paper and electronically? | Part 11 applies if you rely on the electronic version to carry out regulated work. The agency recommends that you decide in advance which version you rely on, and document the decision, for example in a standard operating procedure. | The 2003 guidance |
| Do you use a computer only to print a paper record that meets the predicate rule, and rely on the paper? | The agency would generally not treat this as using electronic records, so Part 11 does not apply. | The 2003 guidance |
| Is it a paper record that you send, or have sent, by electronic means? | Part 11 does not apply. | 11.1(b) |
| Do you submit it to the FDA in electronic form? | Part 11 applies, even if no regulation names the record. | 11.1(b) |
| Do you sign it electronically where a predicate rule asks for a signature or initials? | The signature rules in 11.50 to 11.300 apply. | 11.1(c); the 2003 guidance |
| Did the system run before 20 August 1997, did it meet the predicate rules then, and does it meet them now? | The agency does not intend to enforce Part 11 for that system, if you also hold documented evidence that it is fit for its intended use. | The 2003 guidance |
| Do the people responsible for the records control who can access the system? | If they do, it is a closed system: apply 11.10. If they do not, it is an open system: apply 11.30 as well. | 11.3(b)(4) and (9) |
The rule also makes a maker’s systems available for inspection:
Computer systems (including hardware and software), controls, and attendant documentation maintained under this part shall be readily available for, and subject to, FDA inspection.
What to do. List each record that a predicate rule requires you to keep or submit. For each one, record the answers to these questions, the system that holds it, and whether you rely on its paper or its electronic version.
Evidence to keep. The record list, with the predicate rule, the system and the answers for each record, approved and kept current.
What the FDA enforces: its 2003 guidance on scope and application
The FDA published guidance on Part 11’s scope and application in September 2003, while it re-examined the rule. It set out where the agency would use enforcement discretion:
we do not intend to take enforcement action to enforce compliance with the validation, audit trail, record retention, and record copying requirements of part 11 as explained in this guidance. However, records must still be maintained or submitted in accordance with the underlying predicate rules, and the Agency can take regulatory action for noncompliance with such predicate rules.
The guidance also covers systems that were operational before 20 August 1997, the date Part 11 took effect. The agency does not intend to enforce any of the rule’s requirements for such a system if it met the predicate rules then, meets them now, and you hold “documented evidence and justification that the system is fit for its intended use”. A system changed since then in a way that would stop it meeting the predicate rules should get Part 11 controls.
It names the controls the agency intends to enforce: limits on system access, operational system checks, authority checks, device checks, training, written accountability policies, controls over systems documentation, the matching controls for open systems, and the signature requirements in 11.50, 11.70, 11.100, 11.200 and 11.300. It adds: “Note that part 11 remains in effect and that this exercise of enforcement discretion applies only as identified in this guidance.” The agency’s guidance list still shows it as final.
For the four requirements under discretion, the guidance asks for a decision based on risk. On validation it says:
We recommend that you base your approach on a justified and documented risk assessment and a determination of the potential of the system to affect product quality and safety, and record integrity. For instance, validation would not be important for a word processor used only to generate SOPs.
What to do. Write a risk assessment for each system that holds Part 11 records. Use it to set how far you validate the system, whether it needs an audit trail, and how you keep and copy its records. Apply the enforced controls in full.
Evidence to keep. The dated risk assessment for each system, with the decisions it supports.
Other FDA guidance on electronic systems
- For device makers: Computer Software Assurance for Production and Quality Management System Software, February 2026. Its page says it “describes a risk-based approach to establish confidence in the automation used for production or quality management systems”, and that it supersedes the version of 24 September 2025.
- For medicines makers: Data Integrity and Compliance With Drug CGMP: Questions and Answers, December 2018.
- For clinical trials: Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers, October 2024, written for sponsors, clinical investigators, institutional review boards and contract research organisations, among others.
What a Part 11 failure means under US law
Section 11.2(a) lets a maker use electronic records in place of paper “provided that the requirements of this part are met”. On our reading, where a record does not meet Part 11, that permission does not cover it, so the record may not meet the predicate rule that requires it. The consequences then follow from that rule. For a drug maker:
The failure to comply with any regulation set forth in this part and in parts 211, 213, 225, and 226 of this chapter in the manufacture, processing, packing, or holding of a drug shall render such drug to be adulterated under section 501(a)(2)(B) of the act and such drug, as well as the person who is responsible for the failure to comply, shall be subject to regulatory action.
For a device maker:
The failure to comply with any applicable requirement in this part renders a device adulterated under section 501(h) of the Federal Food, Drug, and Cosmetic Act. Such a device, as well as any person responsible for the failure to comply, is subject to regulatory action.
The agency developed its data integrity questions and answers for drug makers “in response to an increase in findings of data integrity lapses in recent inspections”.
Where to start. Begin with the controls the agency says it intends to enforce: limits on access (d), operational, authority and device checks (f) to (h), training (i), the signature policy (j), control of systems documentation (k)(1), the matching open-system controls, and the signature rules in 11.50 to 11.300. Then add each control your predicate rule asks for, such as accuracy checks and back-ups for drugs, or software validation for devices.
The Part 11 checklist: every control in plain words, with the evidence to keep
Work through this list for each system that holds Part 11 records. The sections that follow quote each control and say what to do.
| Control | What it asks, in plain words | Does the FDA intend to enforce it? (2003 guidance) | Evidence to keep |
|---|---|---|---|
| 11.10(a) Validation | Show that the system works accurately, reliably and as intended, and can tell when a record is invalid or altered | No; validation your predicate rule asks for still applies | The risk assessment, the validation plan and the validation report |
| 11.10(b) Copies | Produce accurate and complete copies, readable by a person and in electronic form, for the agency to inspect | No | The procedure for producing copies and a record of the test |
| 11.10(c) Protection of records | Keep records accurately and readily retrievable for the whole retention period | No; your predicate rule’s retention duties still apply | The retention schedule, and retrieval and restore test records |
| 11.10(d) System access | Let only authorised people into the system | Yes | The list of users and roles, and the records of access granted and removed |
| 11.10(e) Audit trails | Log the date and time of each entry and action that creates, changes or deletes a record, keep the earlier entry readable, and keep the log as long as the record | No for the computer-generated audit trail; your predicate rule’s duties on dates, times and changes still apply | The audit trail settings for each system and the risk assessment behind them |
| 11.10(f) Operational checks | Make the system enforce the permitted order of steps where order matters | Yes | The configuration and the sequence test |
| 11.10(g) Authority checks | Let only authorised people use the system, sign, change a record or carry out each operation | Yes | The permissions for each role and the test results |
| 11.10(h) Device checks | Where it matters, check that data and instructions come from a valid source, such as a permitted terminal | Yes | The list of permitted devices and the record of the check |
| 11.10(i) Training | Confirm that people who build, maintain or use the system have the education, training and experience for their tasks | Yes | Training records and a record of each person’s qualifications for their role |
| 11.10(j) Accountability | Hold each person accountable, in a written policy, for actions under their electronic signature | Yes | The policy and each signer’s dated acknowledgement |
| 11.10(k) Systems documentation | Control who receives, reads and uses system documents, and keep an audit trail of their revisions | Yes for (k)(1); no for (k)(2), the revision audit trail | Document control records and the revision history of each system’s documentation |
| 11.30 Open systems | Where the people responsible for the records do not control access, add measures such as document encryption and digital signatures | Yes, for the controls that match the enforced 11.10 controls | The classification of each system with its reason, and the encryption and signature settings |
| 11.50 Signed records | Show the signer’s printed name, the date and time, and the meaning of each signature, in every form a person reads | Yes | A screen capture and a printout of a signed record from each system |
| 11.70 Signature links | Link each signature to its record so no one can cut, copy or move it by ordinary means | Yes | The test record |
| 11.100 One person per signature | Give each signature to one person only, check the person’s identity first, and certify your signatures to the FDA | Yes | The identity check for each signer, the register of signatures issued, and a copy of the certification |
| 11.200 Signature components | For signatures not based on biometrics, ask for two components, such as an identification code and a password, and apply the session rules | Yes | The signature settings and their validation tests |
| 11.300 Codes and passwords | Keep each code and password pair unique, review issued codes, replace lost tokens, report misuse attempts and test tokens | Yes | The procedure, the password settings, records of lost tokens and their replacements, the alerts and how you handled them, and token test records |
The eleven controls for closed systems, quoted, with what to do
Section 11.10 sets the controls for a closed system, one where the people responsible for the records control access to it (11.3(b)(4)):
Persons who use closed systems to create, modify, maintain, or transmit electronic records shall employ procedures and controls designed to ensure the authenticity, integrity, and, when appropriate, the confidentiality of electronic records, and to ensure that the signer cannot readily repudiate the signed record as not genuine. Such procedures and controls shall include the following:
(a) Validation of systems
Validation of systems to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records.
The 2003 guidance places this control under enforcement discretion. Validation that a predicate rule requires still applies, and the guidance adds: “Even if there is no predicate rule requirement to validate a system, in some instances it may still be important to validate the system.”
What to do. For each system that holds Part 11 records, use the risk assessment to set how far to validate it, then validate it to that plan. If you make devices, the agency’s computer software assurance guidance of February 2026 sets out a risk-based approach for software used in production and the quality system.
(b) Copies for inspection
The ability to generate accurate and complete copies of records in both human readable and electronic form suitable for inspection, review, and copying by the agency. Persons should contact the agency if there are any questions regarding the ability of the agency to perform such review and copying of the electronic records.
Enforcement discretion. The guidance recommends copies of records “held in common portable formats when records are maintained in these formats”, or copies made by established conversion or export methods in a more common format such as PDF or XML, and copies “that preserve the content and meaning of the record”.
What to do. Test that each system can produce a complete copy of its records, readable by a person and in electronic form, and write down how to produce one during an inspection.
(c) Protection of records through the retention period
Section 11.10(c) requires “Protection of records” for their “accurate and ready retrieval throughout the records retention period”. Enforcement discretion. The guidance says the agency does not intend to object if a maker archives records to paper, microfilm or a standard electronic format such as PDF, as long as the maker meets the predicate rules and the records keep their content and meaning.
What to do. Set each record’s retention period from its predicate rule, and test that you can retrieve archived records and restore back-ups within that period.
(d) Limits on system access
Limiting system access to authorized individuals.
What to do. Give each user their own account, grant access by role, and remove access when someone leaves or changes role.
(e) Audit trails
Use of secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete electronic records. Record changes shall not obscure previously recorded information. Such audit trail documentation shall be retained for a period at least as long as that required for the subject electronic records and shall be available for agency review and copying.
Enforcement discretion for the computer-generated audit trail. The predicate rules on dates, times and the sequence of events still apply, as do the requirements “for ensuring that changes to records do not obscure previous entries”. The guidance adds: “Audit trails can be particularly appropriate when users are expected to create, modify, or delete regulated records during normal operation.”
What to do. Switch on the audit trail in each system where users create, change or delete regulated records, and keep it as long as the records. Where your risk assessment finds no audit trail necessary, record the other control you use.
(f) Operational system checks
Use of operational system checks to enforce permitted sequencing of steps and events, as appropriate.
What to do. Where steps must happen in order, such as review before approval, set the system to enforce that order.
(g) Authority checks
Use of authority checks to ensure that only authorized individuals can use the system, electronically sign a record, access the operation or computer system input or output device, alter a record, or perform the operation at hand.
What to do. Set permissions so that only authorised people can sign, change a record or carry out each operation, and test them.
(h) Device checks
Use of device (e.g., terminal) checks to determine, as appropriate, the validity of the source of data input or operational instruction.
What to do. Where only certain terminals or instruments may send data or instructions, set the system to check where each input comes from.
(i) Education, training and experience
Determination that persons who develop, maintain, or use electronic record/electronic signature systems have the education, training, and experience to perform their assigned tasks.
What to do. Check that each person who builds, maintains or uses a system has the education, training and experience for their tasks.
(j) Accountability for electronic signatures
The establishment of, and adherence to, written policies that hold individuals accountable and responsible for actions initiated under their electronic signatures, in order to deter record and signature falsification.
What to do. Write a policy that holds each person accountable for actions taken under their electronic signature, and have each signer read it before they first sign.
(k) Control of systems documentation
Use of appropriate controls over systems documentation including:
- (1) Adequate controls over the distribution of, access to, and use of documentation for system operation and maintenance.
- (2) Revision and change control procedures to maintain an audit trail that documents time-sequenced development and modification of systems documentation.
The agency intends to enforce paragraph (k)(1). The 2003 guidance places (k)(2), the audit trail of documentation changes, under enforcement discretion with the other audit trails.
What to do. Control who can read and change system manuals, configuration records and procedures, and keep their revision history.
Open systems: the extra controls in 11.30
An open system is one where the people responsible for the records do not control access to it (11.3(b)(9)). Section 11.30 asks for more:
Persons who use open systems to create, modify, maintain, or transmit electronic records shall employ procedures and controls designed to ensure the authenticity, integrity, and, as appropriate, the confidentiality of electronic records from the point of their creation to the point of their receipt. Such procedures and controls shall include those identified in § 11.10, as appropriate, and additional measures such as document encryption and use of appropriate digital signature standards to ensure, as necessary under the circumstances, record authenticity, integrity, and confidentiality.
Under the 2003 guidance, the agency intends to enforce the open-system controls that match the closed-system controls it enforces. Section 11.3(b)(5) defines a digital signature as “an electronic signature based upon cryptographic methods of originator authentication”.
What to do. Decide for each system whether it is closed or open, and record the reason. For an open system, add document encryption and digital signatures where the records need them.
Electronic signatures: what Part 11 requires, with what to do
Part 11 treats an electronic signature that meets its rules as equal to a handwritten one:
Where electronic signatures and their associated electronic records meet the requirements of this part, the agency will consider the electronic signatures to be equivalent to full handwritten signatures, initials, and other general signings as required by agency regulations, unless specifically excepted by regulation(s) effective on or after August 20, 1997.
What a signed record must show (11.50)
Signed electronic records shall contain information associated with the signing that clearly indicates all of the following:
- (1) The printed name of the signer;
- (2) The date and time when the signature was executed; and
- (3) The meaning (such as review, approval, responsibility, or authorship) associated with the signature.
Section 11.50(b) puts these items under the same controls as the record and requires them in any form a person reads, such as a display or a printout.
What to do. Check that every signed record shows the signer’s printed name, the date and time, and the meaning of the signature, on screen and when printed.
Linking signatures to records (11.70)
Electronic signatures and handwritten signatures executed to electronic records shall be linked to their respective electronic records to ensure that the signatures cannot be excised, copied, or otherwise transferred to falsify an electronic record by ordinary means.
What to do. Test that no one can cut, copy or move a signature onto another record by ordinary means.
One person per signature, identity checks and the letter to the FDA (11.100)
Each electronic signature shall be unique to one individual and shall not be reused by, or reassigned to, anyone else.
Before an organisation issues an electronic signature, it verifies the person’s identity (11.100(b)). It also certifies its signatures to the agency:
Persons using electronic signatures shall, prior to or at the time of such use, certify to the agency that the electronic signatures in their system, used on or after August 20, 1997, are intended to be the legally binding equivalent of traditional handwritten signatures.
Section 11.100(c)(1) requires a handwritten signature on the certification and allows electronic or paper form. The FDA’s page on letters of non-repudiation gives two sample letters, one for named people and one that covers a whole company, and says: “Sending a physical copy is now optional.” On request, a maker gives further certification or testimony that a specific electronic signature is legally binding (11.100(c)(2)).
What to do. Verify each person’s identity before you issue an electronic signature, never reassign a signature, and send the certification before or when your people first sign.
Signature components (11.200)
For electronic signatures not based on biometrics, 11.200(a) requires that they:
- (1) Employ at least two distinct identification components such as an identification code and password.
In one continuous session of controlled access, the first signing uses all the components, and later signings use at least one component that only the signer can use (11.200(a)(1)(i)). Signings outside such a session each use all the components (11.200(a)(1)(ii)). Only its genuine owner may use a signature, and the organisation must run signatures so that anyone else who tries to use one would need the “collaboration of two or more individuals” (11.200(a)(2) and (3)). A signature based on biometrics must work only for its owner (11.200(b)).
What to do. Set each system to ask for two components, such as an identification code and a password, and to apply these session rules. Check that no one shares a signature.
Identification codes and passwords (11.300)
Where signatures use an identification code with a password, 11.300 requires controls that:
- keep each combination unique, “such that no two individuals have the same combination of identification code and password” (a);
- check, recall or revise issued codes and passwords periodically, for example for password ageing (b);
- deauthorise lost, stolen or compromised tokens and cards, and issue replacements under “suitable, rigorous controls” (c);
- prevent unauthorised use and report any attempt “in an immediate and urgent manner” to the system security unit and, as appropriate, to management (d);
- test tokens and cards when issued and periodically (e).
What to do. Write a password and token procedure that covers each of the five points, and set each system to alert security staff to unauthorised attempts.
EU GMP Annex 11: the EU rules for computerised systems
In the EU, Commission Directive (EU) 2017/1572 sets the principles of GMP for medicines for human use. Article 9(2) sets the core duty for electronic records:
When electronic, photographic or other data processing systems are used instead of written documents, the manufacturer shall be required to first validate the systems by showing that the data will be appropriately stored during the anticipated period of storage. Data stored by those systems shall be made readily available in legible form and shall be provided to the competent authorities upon request. The electronically stored data shall be protected, by techniques such as duplication or back-up and transfer to another storage system, against unlawful access, loss or damage of data, and audit trails shall be maintained.
Article 3(2) tells makers and inspectors to take the Commission’s detailed GMP guidelines into account when they interpret those principles. Volume 4 of EudraLex holds the guidelines, and Annex 11, on computerised systems, is one of them. Its cover page gives Article 47 of Directive 2001/83/EC as the legal basis for publishing it, and its current text is the January 2011 revision, with 30 June 2011 as its deadline for coming into operation.
The application should be validated; IT infrastructure should be qualified.
Where a computerised system replaces a manual operation, there should be no resultant decrease in product quality, process control or quality assurance. There should be no increase in the overall risk of the process.
The annex covers every computerised system used in GMP-regulated work. These sections ask for more than Part 11 does, or set a shared control in different terms:
- Risk management (section 1). “decisions on the extent of validation and data integrity controls should be based on a justified and documented risk assessment of the computerised system.”
- Suppliers and service providers (section 3). A formal agreement with any third party that provides, installs, configures, validates, maintains, modifies or retains a system, “and these agreements should include clear statements of the responsibilities of the third party”. A risk assessment decides whether to audit a supplier (3.2).
- An inventory (section 4.3). “An up to date listing of all relevant systems and their GMP functionality (inventory) should be available.”
- User requirements and data migration (sections 4.4 and 4.8). User requirements traceable through the life cycle, and checks that migrated data “are not altered in value and/or meaning”.
- Accuracy checks and back-ups (sections 6 and 7.2). A second check on critical data entered by hand, and regular back-ups whose restore the maker checks during validation and monitors periodically.
- Audit trail reasons and reviews (section 9). “For change or deletion of GMP-relevant data the reason should be documented. Audit trails need to be available and convertible to a generally intelligible form and regularly reviewed.”
- Periodic evaluation (section 11). Systems “should be periodically evaluated to confirm that they remain in a valid state and are compliant with GMP.”
- Incidents (section 13). A report and assessment of every incident, and the root cause of each critical incident.
- Electronic signatures (section 14). Signatures that “have the same impact as hand-written signatures within the boundaries of the company”, stay “permanently linked to their respective record” and “include the time and date that they were applied”.
- Batch release (section 15). Only Qualified Persons certify the release of batches in the system, with an electronic signature.
- Business continuity and archiving (sections 16 and 17). Tested arrangements that keep critical processes running if a system breaks down, and checks that archived data stay accessible, readable and intact.
The European Commission consulted on a revised Annex 11 from 7 July to 7 October 2025, with a revised Chapter 4 on documentation and a new Annex 22 on artificial intelligence. Its consultation page says the revised annex “strengthens controls related to the assurance of data integrity, audit trails, electronic signatures, and system security”. The EudraLex Volume 4 page still lists the 2011 revision as Annex 11.
What to do. If you make or import medicines for the EU, check each system against each Annex 11 section, starting with the inventory, the risk assessment and the supplier agreements. Then read the draft of the revised annex on the Commission’s consultation page, and list where your data integrity controls, audit trails, electronic signatures and system security do not yet meet it, the four areas the Commission says the revision strengthens.
Evidence to keep. The system inventory, the risk assessments, the supplier agreements, audit trail reviews, periodic evaluation reports, and a dated list of gaps against the draft.
The UK: Annex 11 and the MHRA’s data integrity guidance
Regulation C17 of the Human Medicines Regulations 2012 keeps the Commission’s GMP guidelines in force in the UK as they applied immediately before IP completion day, which the European Union (Withdrawal Agreement) Act 2020 sets at 31 December 2020 at 11.00 p.m.:
Unless replaced by principles or guidelines published under paragraph (1), principles and guidelines published or adopted by the European Commission under the second, third, fourth or fifth paragraph of Article 47, or Article 84, of the 2001 Directive, as they applied immediately before IP completion day, continue to apply on and after IP completion day (subject to any amendments or modifications published under paragraph (1)).
Annex 11 is one of those guidelines, and its January 2011 revision was the text in place on that day. The licensing authority may publish its own guidelines, which may replace, amend or modify the Commission’s (regulation C17(1) and (2)).
In Great Britain, regulation B17(3) also keeps the principles of the earlier GMP directive, Commission Directive 2003/94/EC, with the changes in Schedule 2A. Its Article 9(2) asks the maker to “first validate the systems”, to keep data available “in legible form”, to protect it against loss or damage, and to maintain audit trails, with the licensing authority in place of the competent authorities.
The MHRA’s GxP data integrity guidance of March 2018 covers good laboratory, clinical, manufacturing, distribution and pharmacovigilance practice. It says it “does not extend to medical devices”. On audit trails it says:
Audit trails (identified by risk assessment as required) should be switched on. Users should not be able to amend or switch off the audit trail. Where a system administrator amends, or switches off the audit trail a record of that action should be retained.
It asks makers to record the reason for any change, and to include a documented audit trail review in routine data review “where this is determined by a risk assessment”. On signatures it says:
An inserted image of a signature or a footnote indicating that the document has been electronically signed (where this has been entered by a means other than the validated electronic signature process) is not adequate.
Its section 6.1 lists the ALCOA attributes: data should be attributable, legible and permanent, contemporaneous, original or a certified true copy, and accurate.
What to do. If you make medicines for the UK, apply Annex 11 as in the EU, then check audit trails and signatures against sections 6.13 and 6.14 of the MHRA’s guidance.
Evidence to keep. Audit trail settings that users cannot switch off, audit trail review records, and a check that no system accepts an inserted image as a signature.
How one set of controls can serve the US, EU and UK
Part 11 and Annex 11 share most of their controls, so the same validation, access, audit trail and signature controls can meet both, with a short list of additions for each market. The table is Panacea’s own reading of the two texts, side by side. Where a row pairs provisions that ask for different things, its cells say how. In the UK, the Annex 11 column applies under regulation C17(3), with the MHRA’s guidance beside it.
Part 11 and Annex 11, topic by topic: our reading
| Topic | 21 CFR Part 11 | EU GMP Annex 11 |
|---|---|---|
| What it covers | Electronic records that an FDA regulation requires, and electronic submissions (11.1(b)) | Computerised systems used in GMP-regulated work (Principle) |
| Legal force | A regulation; the 2003 guidance sets enforcement discretion for four kinds of requirement and for systems in use before 20 August 1997 | Guidelines that makers and inspectors take into account (Directive 2017/1572, Article 3(2)); Article 9(2) of the Directive is law |
| Risk management | Not in the rule; the 2003 guidance recommends documented risk assessments | Section 1 |
| Validation | 11.10(a) | Sections 4.1 to 4.8 |
| Inventory of systems | None | Section 4.3 |
| Suppliers and service providers | None | Section 3 |
| Copies and printouts | 11.10(b) | Section 8 |
| Retention, back-up and archiving | 11.10(c) | Sections 7 and 17 |
| Access and authority | 11.10(d) and (g); 11.300 for codes and passwords | Section 12 |
| Audit trails | 11.10(e): computer-generated and time-stamped | Section 9: by risk, with the reason for each change and regular review |
| Checks on the source of data input | 11.10(h), device checks | Section 5, built-in checks on data exchanged with other systems |
| Enforced sequence of steps | 11.10(f) | None |
| Second check on data entered by hand | None (for drugs, 21 CFR 211.68(b) asks for checks on input and output) | Section 6 |
| Training | 11.10(i) | Section 2 |
| Change control | 11.10(k), control of systems documentation and its revisions | Section 10, changes to the system and its configuration; section 4.2, change control records in validation |
| Periodic evaluation | None | Section 11 |
| Incidents | 11.300(d), reports of attempts to misuse codes and passwords | Section 13, every incident |
| Business continuity | None | Section 16 |
| Electronic signatures | 11.10(j), 11.50, 11.70, 11.100 and 11.200 | Section 14: the same impact as a handwritten signature within the company, a permanent link to the record, and the time and date |
| Certification to the regulator | 11.100(c), a letter to the FDA | None |
| Batch release | None | Section 15 |
What to do. Keep one inventory of computerised systems (Annex 11, section 4.3). For each system, keep one list of the controls in this table that apply to it, each mapped to the setting or procedure that meets it. Add the US-only items for systems that hold Part 11 records, and the EU and UK items for systems used in GMP work.
Evidence to keep. The inventory, and for each system its control list with the source of each control, kept current.
Questions about Part 11 and Annex 11
What is 21 CFR Part 11?
It is the FDA’s regulation on electronic records and electronic signatures, Part 11 of Title 21 of the Code of Federal Regulations. It sets the criteria under which the agency considers electronic records and signatures “trustworthy, reliable, and generally equivalent to paper records and handwritten signatures executed on paper” (11.1(a)). The FDA published it on 20 March 1997, and it took effect on 20 August 1997.
What is a predicate rule?
The FDA’s 2003 guidance uses the term for the requirements of the Federal Food, Drug, and Cosmetic Act, the Public Health Service Act and FDA regulations other than Part 11, which set the records to keep or submit. Its examples include the drug good manufacturing practice regulations (Part 211), the device quality rule (Part 820) and good laboratory practice (Part 58). Part 11 applies only where a predicate rule requires the record, or where you submit it to the agency.
Does Part 11 apply to medical device makers?
Yes, for records that Part 820 or another FDA rule requires, once a maker keeps them electronically. The agency’s computer software assurance guidance says: “If a manufacturer maintains in electronic form a document required under Part 820, then Part 11 generally applies.” Part 820 also asks for validated software in production and the quality system, through subclauses 4.1.6, 7.5.6 and 7.6 of ISO 13485, which it has incorporated since 2 February 2026. The final rule for the device quality management system regulation adds: “Manufacturers can choose to develop electronic records and electronic methods for denoting approval.”
What covers a device maker’s electronic records in the EU and UK?
Annex 11 covers medicines. For devices, the EU’s Medical Device Regulation presumes that a quality management system in conformity with the relevant harmonised standards meets the requirements they cover (Article 8(1)), and the European Commission lists EN ISO 13485:2016 among those standards. In Great Britain, an approved body must presume that quality systems which implement the relevant designated standards meet the requirements (Directive 93/42/EEC, Annex II, Section 3.3, as Great Britain applies it), and the MHRA names ISO 13485 among those standards. In the standard, subclauses 4.1.6, 7.5.6 and 7.6 cover validation of software used in production and the quality system, and clause 4.2.5 covers control of records.
Do I have to tell the FDA that I use electronic signatures?
Yes. Section 11.100(c) requires a certification, signed by hand, that you intend your electronic signatures to be the legally binding equivalent of handwritten ones, before or when you first use them. The agency’s page on letters of non-repudiation gives two sample letters, one for named people and one for a whole company.
Is there 21 CFR Part 11 compliant software?
Part 11 puts its duties on the “Persons who use” closed and open systems (11.10 and 11.30), so they stay with the organisation that keeps the records. A supplier can build in features the rule names, such as audit trails, authority checks, signature display and linking, and two-component signatures. The rest stays with you: validating the system for your use, the signature policy (11.10(j)), training (11.10(i)), identity checks (11.100(b)), the password and token procedure (11.300) and the certification to the FDA (11.100(c)). In the EU, Annex 11 asks for a formal agreement with each supplier, and a risk assessment decides whether to audit it (section 3).
Does the FDA still use its 2003 guidance on Part 11?
Yes. It appears as final guidance on the FDA’s guidance list. It narrows the records that count as Part 11 records and names the requirements the agency does not intend to enforce: validation, audit trails, record retention, record copying, and systems in use before 20 August 1997 that meet its conditions.
What is the difference between 21 CFR Part 11 and EU Annex 11?
Part 11 is a US regulation for the electronic records that FDA rules require, across FDA program areas, with exceptions for records under some food rules (11.1(f) to (p)). Annex 11 belongs to the EU’s GMP guidelines for medicines and covers the computerised systems used in GMP work. Beyond the shared controls, the EU text adds risk management, supplier agreements, an inventory, periodic evaluation, incident management, business continuity and batch release by a Qualified Person. The US rule adds the certification letter and detailed controls for signature components and passwords.
Is the EU revising Annex 11?
The European Commission consulted on a revised Annex 11, with a revised Chapter 4 and a new Annex 22 on artificial intelligence, from 7 July to 7 October 2025. Its consultation page links the draft. The EudraLex Volume 4 page still lists the January 2011 revision as the current text.
What does ALCOA mean?
The MHRA’s data integrity guidance says data should be attributable to the person generating the data, legible and permanent, contemporaneous, original or a certified true copy, and accurate. It adds that data should also be complete, consistent, enduring and available throughout the lifecycle.
More guides
- 21 CFR Parts 210 and 211 · EU GMPGMP and cGMP for pharmaceuticals: the FDA, EU and MHRA requirementsRead the guide
- 21 CFR Part 806 · EU MDR · UK MDR 2002Field safety corrective action and medical device recalls: the US, EU and UK rulesRead the guide
- 21 CFR Part 860 · EU MDR Annex VIIIMedical device classification: class 1, 2 and 3 under the FDA, EU and MHRA rulesRead the guide
Sources
United States
- 21 CFR Part 11, Electronic Records; Electronic Signatures, eCFR, up to date as of 17 November 2026: https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11
- 21 CFR 210.1: https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-210/section-210.1
- 21 CFR 211.68: https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-211/subpart-D/section-211.68
- 21 CFR 820.10: https://www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-820/subpart-A/section-820.10
- Federal Register, Electronic Records; Electronic Signatures, final rule, 62 FR 13430, 20 March 1997: https://www.federalregister.gov/documents/1997/03/20/97-6833/electronic-records-electronic-signatures
- Federal Register, Medical Devices; Quality System Regulation Amendments, final rule, 89 FR 7496, 2 February 2024: https://www.federalregister.gov/documents/2024/02/02/2024-01709/medical-devices-quality-system-regulation-amendments
- FDA, Part 11, Electronic Records; Electronic Signatures, Scope and Application, September 2003: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/part-11-electronic-records-electronic-signatures-scope-and-application
- FDA, Letters of Non-Repudiation Agreement: https://www.fda.gov/industry/getting-started-esg-nextgen/letters-non-repudiation-agreement
- FDA, Computer Software Assurance for Production and Quality Management System Software, February 2026: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/computer-software-assurance-production-and-quality-management-system-software
- FDA, Data Integrity and Compliance With Drug CGMP: Questions and Answers, December 2018: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/data-integrity-and-compliance-drug-cgmp-questions-and-answers
- FDA, Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers, October 2024: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/electronic-systems-electronic-records-and-electronic-signatures-clinical-investigations-questions
European Union
- Commission Directive (EU) 2017/1572, EUR-Lex: https://eur-lex.europa.eu/eli/dir/2017/1572/oj/eng
- European Commission, EudraLex Volume 4, Good Manufacturing Practice guidelines: https://health.ec.europa.eu/medicinal-products/eudralex/eudralex-volume-4_en
- EudraLex Volume 4, Annex 11, Computerised Systems, revision January 2011: https://health.ec.europa.eu/document/download/8d305550-dd22-4dad-8463-2ddb4a1345f1_en?filename=annex11_01-2011_en.pdf
- European Commission, stakeholders’ consultation on Chapter 4, Annex 11 and a new Annex 22, 2025: https://health.ec.europa.eu/consultations/stakeholders-consultation-eudralex-volume-4-good-manufacturing-practice-guidelines-chapter-4-annex_en
- Regulation (EU) 2017/745 on medical devices, consolidated text of 9 November 2026, EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02017R0745-20261109
- Commission Implementing Decision (EU) 2021/1182 on harmonised standards for medical devices, consolidated text of 17 June 2026, EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02021D1182-20260617
United Kingdom
- The Human Medicines Regulations 2012 (SI 2012/1916), regulations 8, B17 and C17 and Schedule 2A, legislation.gov.uk: https://www.legislation.gov.uk/uksi/2012/1916/contents
- Commission Directive 2003/94/EC, EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32003L0094
- European Union (Withdrawal Agreement) Act 2020, section 39, legislation.gov.uk: https://www.legislation.gov.uk/ukpga/2020/1/section/39
- MHRA, Guidance on GxP data integrity, March 2018: https://www.gov.uk/government/publications/guidance-on-gxp-data-integrity
- The Medical Devices Regulations 2002 (SI 2002/618), Schedule 2A, paragraph 13, legislation.gov.uk: https://www.legislation.gov.uk/uksi/2002/618/schedule/2A/paragraph/13
- MHRA, Medical devices: conformity assessment and the UKCA mark: https://www.gov.uk/guidance/medical-devices-conformity-assessment-and-the-ukca-mark
General information, not legal advice. We read every source above in November 2026 and check them each month; the date at the top of the page shows the last review.