Table of contents
At a glance
How do you check the status, currency and applicability of a GxP source?
Assess a GxP source by its issuer, document type, applicability, version and exact passage. FDA guidance is not a regulation. A standard can acquire legal significance if explicitly incorporated. A guideline should not be dismissed merely as optional reading either. Establish the legal and use context for the particular requirement. A draft or newly published document does not automatically supersede the applicable version.
- Status, recency, and applicability are three distinct validation questions.
- A secondary source may indicate a requirement but does not substitute for its thorough evaluation.
- Document the traceability from the primary source to your own validation evidence.
Check validity, version, and scope separately
A source may be current yet not belong to your process. An older source may still be highly relevant. A detailed guideline may be professionally useful without itself generating legal obligation. Therefore, always first assess the document type, then the temporal status, and finally the specific applicability.
The term GxP does not describe a single, globally harmonized regulatory framework. For example, Part 11 defines a specific scope for FDA record-keeping and submission requirements. In contrast, the EU GMP Guide assigns Annex 11 to the GMP guidelines. A reference list presenting both texts side by side without such categorization still does not explain why a specific function must be validated.
Document types with their actual context read
Interpret each document in its own legal framework. FDA guidance describes the agency’s position and identifies its non-binding character. Article 3(2) of Directive (EU) 2017/1572 calls for manufacturers and competent authorities to take account of detailed EU GMP guidelines when interpreting GMP principles. A standard published privately can also be incorporated by reference, as § 820.7 demonstrates for the FDA scope covered.
This internal comparison matrix is intended for source documentation purposes. It does not replace a comprehensive legal case-by-case assessment and does not transfer any medical device regulations to the manufacture of human medicinal products.
| Example | Visible Status | What follows | What does not follow from this |
|---|---|---|---|
| 21 CFR Part 11 | FDA Regulation with a dedicated scope of application | Verify exact paragraphs and scope | Every file generated for a US customer is automatically subject to Part 11. |
| FDA Scope and Application 2003 | Final, non-binding guidance | Consider the limits of enforcement policy and interpretation | The Guidance supersedes the regulatory text. |
| EU GMP Annex 11 | Guideline covered under the EU GMP Index | Classify within the applicable GMP framework | The PDF title alone establishes all legal consequences. |
| ICH Q9(R1), EMA Step 5 | Regional published guideline with status data | Relevant version and scope of application take into account | Every ICH date is automatically the same worldwide effective date. |
| ISO reference in §820.7 | A specific edition of the standard is incorporated by reference | Review specific incorporation and scope of regulation | Every version of the specification applies to every GxP system. |
| ISPE GAMP 5, 2nd Edition | Industry Guideline; public description | Properly assign methodological orientation | An unreviewed full text provides specific legal distribution obligations. |
Sources: [3] [4] [2] [5] [6] [9]
Maintain a source record up to and including own verification evidence
Capture author, title, official URL, edition, retrieval date, status, relevant authority, and the specific intended use. Expand the boundaries: What prerequisites does the section specify? Which portions have you actually reviewed? Which statement originates from the source and which represents your own implementation?
A good source trace does not end with the link. It connects the requirement to the relevant record or process and to the intended evidence. For joint validations across multiple regulatory frameworks, multiple separate normative anchors may be cited. This does not imply a requirement for two parallel records. What is essential is that the reader can verify the respective derivation.
A transferred export requirement to be reviewed step by step
Example: An internal list claims that Part 11 requires for each system a PDF/A export of all technical records for unlimited time. No specific primary source is provided for this combination. The team first breaks the statement down into four verifiable sub-claims: Scope, Format, Data Volume, and Deadline. Only after this breakdown is a dedicated export justification developed.
Section 11.10(b) requires the ability to generate accurate and complete copies in human-readable and electronic form for inspection, audit, and duplication by the FDA. Section (c) addresses protection and retrieval during the retention period. The 2003 FDA Guidance provides flexibility in enforcement of these Part 11 requirements (III.C.4 and III.C.5); the underlying record-keeping and retention obligations under the predicate regulations remain in effect. Copies must preserve both content and meaning. The Guidance lists PDF, XML, and SGML as examples, not as a requirement to use any specific file format.
| Partial claim | Primary inspection | Result of the inspection | Next intended action |
|---|---|---|---|
| For each system | §11.1; FDA 2003 III.B | No blanket application to every IT system | Relevant records and submissions are determined. |
| Strictly PDF/A | § 11.10(b); FDA 2003 III.C.4 | No universally defined PDF/A format specified herein | Evaluate suitable copies based on content, meaning, and intended use. |
| All technical protocols | Record Scope and Completeness | No justified universal list established solely by the term "complete" | Define the required data and contextual scope clearly and explicitly. |
| Unlimited time | §11.10(c) and applicable storage obligations | No unlimited general exemption period in this paragraph | Determine appropriate deadline and required retrievability. |
| Evidence is sufficient | Own testing criteria still open | Source verification is not a passed export verification | Verify representative exports with required inventory and error cases. |
Interpret date and change history accurately
Distinguish the publication date, technical revision date, expiry date, and retrieval date. In the currently referenced EMA version of ICH Q9(R1), the title page states 23 January 2025 and Corr.2. The history section notes a typographical correction; the date of entry into force of the regional version is cited as 26 July 2023. No technical revision Q9(R2) may be inferred from this.
The current EU-GMP Index continues to list Annex 11 with the revision dated January 2011. A later-dated file path alone does not constitute evidence of a technical amendment. When reviewing draft documents or consultation materials, verify the explicitly stated version status and the possibility of a subsequent final publication. The most recently dated file does not automatically satisfy current requirements for existing documentation.
Address gaps and inconsistent sources openly
If a secondary representation diverges from the primary source, first verify whether it refers to a different scope, a subsequent amendment, or merely an independent recommendation. Do not adopt any paragraph number until the corresponding text has been reviewed. A search excerpt may provide a useful starting point but often omits the conditions specified in the paragraph.
For access-restricted guidelines, the gap must be visibly maintained. The public ISPE description, for example, confirms the release and intent of GAMP 5, yet does not cover every individual section of the paid full text. Furthermore, a public reference to ISO 13485 in §820.7 does not replace a direct review of specific NDA requirements. Therefore, do not infer detailed obligations from a content heading alone.
Checklist prior to acceptance of a regulatory statement
This internal checklist is suitable for requirements, test plans, and internal training materials. It aims to enhance traceability without necessitating a comprehensive separate review for each simple reference.
- The source is attributable to the responsible authority or a clearly identified reference.
- Document type and status are explicitly recorded.
- Release, expiry date, and retrieval date are not confused.
- Product, activity, record, and legal jurisdiction are aligned with the intended use.
- The specific location including its limitations was reviewed.
- Literal requirements and internal implementation recommendations are distinguishable.
- Unread full texts and open current issues remain visible.
- The traceability demonstrates which own decision originates from the source.
Link source maintenance to professional changes
Assign responsibility for the source systems used and for changes within the respective application scope. The applicability may change due to a new product, an additional submission, or a different data process, even if no regulation has been amended. Conversely, not every editorial correction to source materials requires a complete new system test.
For SMEs, a concise and well-maintained list of actually used primary sites is more useful than an unmanageable archive of unverified documents. Document the affected claim, the impact on the process, and the resulting action upon any change. Maintain open remaining uncertainties, rather than deriving a final legal or system release from an automated source comparison.
Project experience and collaboration
Trace an internal requirement to the source that supports it
With your method and quality owners, we examine one internal requirement. What does the regulation say, what does guidance explain and which method did your organisation choose? If the source is clear, the wording may simply need clarification. A wrong reference or a different scope requires reassessment. We link the source, interpretation and implementation so your team can explain the requirement.
Frequently asked questions about Sources and their regulatory status
Is an FDA Guidance on the same level as CFR text?
No. The FDA Guidance referenced here denotes its non-binding nature and outlines the regulatory stance. The underlying regulatory text remains distinct from this. For a specific statement, you require both the relevant section of the regulation and a clear interpretation of what the Guidance actually addresses.
Does guidance imply that Annex 11 can be arbitrarily disregarded?
No. The Commission publishes Annex 11 as detailed GMP guidance under Article 47 of Directive 2001/83/EC. Under Article 3(2) of Directive (EU) 2017/1572, manufacturers and competent authorities take the detailed guidelines into account when interpreting GMP principles. Annex 11 is not a standalone statute. Within the relevant GMP scope, assess and document which provisions apply and how your process meets them.
Are ISO standards always voluntary?
Such a general statement would be incorrect. §820.7 explicitly includes a specific normative version through a reference within an FDA regulatory section. Review the specific inclusion and its scope. This example neither transfers medical device regulations to human medicinal products nor substantiates unreviewed details of the normative text.
Sources: [5]
Can a GAMP guideline establish a legal obligation?
GAMP 5 is a sectoral guidance document. Its methodological approach must be distinguished from applicable regulatory requirements. A specific obligation cannot be established solely on the basis of an unreviewed GAMP subheading. Clearly demonstrate which requirement exists and how the selected method supports its implementation.
Sources: [6]
Is the latest PDF file always relevant?
What does Corr.2 mean in ICH Q9(R1)?
The EMA edition dated 23 January 2025 includes this correction note. Its history references a typographical correction on page 19. It remains Q9(R1), not a new technical revision R2. Regional efficacy and correction history must be recorded separately.
Sources: [8]
Does a manufacturer's brochure serve as an adequate regulatory source?
A brochure may describe features or vendor-specific configurations. To derive a regulatory requirement, you should refer to the relevant primary source. Separate the obligation from the evidence, assessing whether the specific product and your configuration meet the requirement for the intended use.
Do Annex 11 and Part 11 always require separate documentation records?
Such a general directive does not necessarily follow. Shared evidence may be appropriate if its scope and relevant regulatory anchors are transparent and verifiable. However, differences in applicability and detailed requirements should be assessed. A common document title does not constitute complete coverage of both frameworks.
Does the FDA Guidance from 2003 include portions of Part 11?
No. It describes a limited scope of applicability and the interpretation of the scope. It is not a revocation act and explicitly confirms the continued applicability of requirements as well as the ongoing enforcement of the underlying record-keeping obligations. A general statement that Part 11 has thereby become voluntary would be inaccurate.
How do we handle an unavailable full text?
Clearly specify exactly what was read and which statement therefore remains open. A public summary may support the issuance or intended use, but cannot validate arbitrary detailed requirements. Until clarification is obtained, use a verifiable, more specific formulation, and label any proposed implementation approaches as such.
Sources and review date
Source date: 7 October 2026. eCFR notice period until 5 October 2026; EU Index and latest EMA version separately reviewed. Public ISPE product description reviewed; paid GAMP full text and ISO standard full text not reviewed. Tables are standalone work aids.
- 21 CFR Part 11 – Electronic Records; Electronic SignatureseCFR display until 05.10.2026; §§11.1–11.300.
- European Commission: EudraLex Volume 4Status as of 07.10.2026; Human medicinal products and veterinary law separated.
- FDA: Status of Part 11 Scope GuidanceAs final on 07.10.2026, conducted in September 2003.
- 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.
- 21 CFR §820.7 – Incorporation by reference§820.7(b): Integration of ISO 13485:2016 into the aforementioned QMSR area.
- ISPE: GAMP 5 Guide, 2nd EditionPublic publisher description and edition information; no access to paid full text.
- EU GMP Annex 11 – Computerised SystemsRevision January 2011; listed in the human medicinal product section. Principle, §§1–17.
- EMA: ICH Q9(R1) – Quality Risk Management, Corr.2EMA version dated 23 January 2025, Corr.2. This is Q9(R1), applicable in the EU since 26 July 2023. See sections 1–6, particularly 4.3 and 5.1–5.3.
- EU: Directive (EU) 2017/1572 – GMP principles and guidelines for medicinal products for human useArticle 3(1) and (2) address inspections and consideration of the detailed guidance referred to in Article 47 of Directive 2001/83/EC. The official German text was checked on 18 October 2026. Assess the framework for investigational medicinal products separately.
Sources checked: .
Jointly develop the specific evidence process
We assist you in deriving requirements from reliable primary sources, refining outdated or overly broad references, and clearly documenting the alignment to your own validation evidence.
- 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.

