Data Integrity FDA - EMA Def
Data Integrity FDA - EMA Def
Data Integrity FDA - EMA Def
CGMP
FDA guidance (25591) April 2016
and December 2018
L.C.Clauss
L.C.Clauss 1 06/12/2023
Table of Content (1)
1. Definition and purpose
2. EU vs FDA requirements
3. FDA April 2016 and 2018 Guidance document
4. Data Integrity during development
5. Why Data Integrity Guidance from FDA?
6. FDA definition of Audit Trail
7. FDA definition of Back up
8. Computer and related system
9. FDA is concerned with the use of shared login accounts for computer systems
10. When does electronic data become a CGMP record?
11. How should blank forms be controlled?
12. Can electronic signatures be used instead of handwritten signatures for
master production and control record
13. The practice, also referred to as testing into compliance, is not consistent with
CGMP
L.C.Clauss Hisut Ltd 2 06/12/2023
Table of Content (2)
14. Typical issues with Password
15. Is it acceptable to only save the final results from reprocessed laboratory
chromatography?
16. Can an internal tip regarding a quality issue, such as potential data falsification,
be handled informally outside of the documented CGMP quality system?
17. FDA request that personnel should be trained in detecting data integrity issues
as part of a routine CGMP training program
18. FDA Warning letter Form 483
b. What is “metadata”?
Metadata is the contextual information required to understand data. A data value is by itself
meaningless without additional information about the data. Metadata is often described as data
about data. Metadata is structured information that describes, explains, or otherwise makes it
easier to retrieve, use, or manage data. For example, the number “23” is meaningless without
metadata, such as an indication of the unit “mg.” Among other things, metadata for a particular
piece of data could include a date/time stamp documenting when the data were acquired, a user
ID of the person who conducted the test or analysis that generated the data, the instrument ID
used to acquire the data, material status data, the material identification number, and audit trails.
Data should be maintained throughout the record’s retention period with all associated metadata
required to reconstruct the CGMP activity (e.g., §§ 211.188 and 211.194). The relationships
between data and their metadata should be preserved in a secure and traceable manner.
Audit trail review is similar to assessing cross-outs on paper when reviewing data. Personnel
responsible for record review under CGMP should review the audit trails that capture changes to
data associated with the record as they review the rest of the record (e.g., §§ 211.22(a),
211.101(c) and (d), 211.103, 211.182, 211.186(a), 211.192, 211.194(a)(8), and 212.20(d)). For
example, all production and control records, which includes audit trails, must be reviewed and
approved by the quality unit (§ 211.192). The regulations provide flexibility to have some
activities reviewed by a person directly supervising or checking information (e.g., § 211.188).
FDA recommends a quality system approach to implementing oversight and review of CGMP
records. 12
If the review frequency for the data is specified in CGMP regulations, adhere to that frequency
211.101(c) and (d), 211.103, 211.182, 211.186(a), 211.192, 211.194(a)(8), and 212.20(d)). For
example, all production and control records, which includes audit trails, must be reviewed and
approved by the quality unit (§ 211.192). The regulations provide flexibility to have some
How often should audit trails be
activities reviewed by a person directly supervising or checking information (e.g., § 211.188).
FDA recommends a quality system approach to implementing oversight and review of CGMP
records. 12 reviewed?
8. How often should audit trails be reviewed?
If the review frequency for the data is specified in CGMP regulations, adhere to that frequency
for the audit trail review. For example, § 211.188(b) requires review after each significant step in
manufacture, processing, packing, or holding, and § 211.22 requires data review before batch
release. In these cases, you would apply the same review frequency for the audit trail.
If the review frequency for the data is not specified in CGMP regulations, you should determine
the review frequency for the audit trail using knowledge of your processes and risk assessment
tools. The risk assessment should include evaluation of data criticality, control mechanisms, and
impact on product quality. 13
Your approach to audit trail review and the frequency with which you conduct it should ensure
that CGMP requirements are met, appropriate controls are implemented, and the reliability of the
review is proven.
See the audit trail definition in 1.c. above for further information on audit trails.
L.C.Clauss Hisut Ltd 13 06/12/2023
d. How does FDA use the terms “static” and “dynamic” as they relate to record formats?
For the purposes of this guidance, static is used to indicate a fixed-data record such as a paper
record or an electronic image, and dynamic means that the record format allows interaction
between the user and the record content. For example, a dynamic chromatographic record may
allow the user to change the baseline and reprocess chromatographic data so that the resulting
peaks may appear smaller or larger. It also may allow the user to modify formulas or entries in a
spreadsheet used to compute test results or other information such as calculated yield.
Is
Trueitcopies
acceptable to records
of dynamic electronic retain paper
may be made and printouts or static
maintained in the format of the
original records or in a format that allows for the content and meaning of the original records to
records
be preserved instead
if a suitable reader andof original
copying equipment electronic records
(e.g., software and hardware, including
media readers) are readily available (§§ 211.180(d) and 212.110).
from stand-alone computerized laboratory
10. Is it acceptable to retain paper printouts or static records instead of original
instruments
electronic records from such as an
stand-alone FTIR Instruments?
computerized laboratory instruments, (1)
such as
an FT-IR instrument?
A paper printout or static record may satisfy retention requirements if it is the original record or a
true copy of the original record (see §§ 211.68(b), 211.188, 211.194, and 212.60). During data
acquisition, for example, pH meters and balances may create a paper printout or static record as
the original record. In this case, the paper printout or static record, or a true copy, must be
retained (§ 211.180).
You must ensure that original laboratory records, including paper and electronic records, are
subject to second-person review (§ 211.194(a)(8)) to make certain that all test results and
associated information are appropriately reported. Similarly, in microbiology, a
contemporaneous written record is maintained of the colony counts of a petri dish, and the record
is then subject to second-person review.
For more information on static and dynamic records, see 1.d. in this guidance. For PET drugs,
see the guidance for industry PET Drugs—Current Good Manufacturing Practice (CGMP) for
discussion of equipment and laboratory controls, including regulatory requirements for records.
Yes, a CGMP workflow, such as creation of an electronic master production and control record
(MPCR), is an intended use of a computer system to be checked through validation (see
§§ 211.63, 211.68(b), and 211.110(a)). The extent of validation studies should be commensurate
with the risk posed by the automated system. When the same system is used to perform both
CGMP and non-CGMP functions, the potential for non-CGMP functions to affect CGMP
operations should be assessed and mitigated appropriately. 10
If you validate the computer system but you do not validate it for its intended use, you cannot
know if your workflow runs correctly. 11 For example, qualifying the Manufacturing Execution
System (MES) platform, a computer system, ensures that it meets its relevant requirements and
specifications; however, it does not demonstrate that a given MPCR generated by the MES
contains the correct calculations. In this example, validating the workflow ensures that the
intended steps, requirements, and calculations in the MPCR are accurate and perform properly.
This is similar to reviewing a paper MPCR and ensuring all supporting procedures are in place
before the MPCR is implemented in production (see §§ 211.100, 211.186, and 212.50(b) and the
guidance for industry PET Drugs—Current Good Manufacturing Practice (CGMP)).
L.C.Clauss Hisut Ltd 20 06/12/2023
Data created as part of a CGMP record must be evaluated by the quality unit as part of release
criteria (see §§ 211.22 and 212.70) and maintained for CGMP purposes (e.g., § 211.180). 9
Electronic data generated to fulfill CGMP requirements include relevant metadata required to
reconstruct the CGMP activity captured in the record. Invalidating test results to exclude them
from quality unit decisions about conformance to a specification requires a valid, documented,
scientifically sound justification. See, for example, §§ 211.160(b), 211.188, 211.192, and
212.71(b) and the guidance for industry Investigating Out-of-Specification (OOS) Test Results
for Pharmaceutical Production. Even if test results are legitimately invalidated on the basis of a
scientifically sound investigation, the full CGMP batch record provided to the quality unit would
include the original (invalidated) data, along with the investigation report that justifies
invalidating the result. The requirements for record retention and review do not differ depending
on the data format; paper-based and electronic data record-keeping systems are subject to the
same requirements.
L.C.Clauss Hisut Ltd 23 06/12/2023