Professional Documents
Culture Documents
Dr. A. Amsavel
The Overview
• Introduction
• Requirements
• Types of GMP Documentation
• Purposes of GMP Documentation
• The Structure of Document Management
• Evaluation of the Documentation System
• The Document Management Cycle
• Tips to good documentation practices
• Warning letters and observations
• Summary & conclusion
What is Documentation ?
To Document each Activity you perform
Any Questions?
Good Documentation Practice
Dr. A. Amsavel
Index
Introduction
Definition
Documents required
Records to be maintained
Good Documentation practice
Why GDP is important
Proverb:
•A record of all calculations performed in connection with the test, including, for
example, units of measure, conversion factors, and equivalency factors;
•The signature of the person who performed each test and the date(s) the
tests were performed;
•The date &signature of a second person who is reviewed for accuracy,
completeness, and compliance with established standards.
?
Why do people sometimes fail to document activities or
events properly?
Record writing /Data Entry
Corrections to written
records must be made
properly.
DO NOT USE “write-
overs” (Don’t turn a
“6” or “9” into an
“8”.)
Never vary your
initials or signature
How to make Corrections
When an entry or calculation must be corrected, follow these steps:
•Draw a single line through the incorrect entry.
•Enter correct information above or to the side of the incorrect
entry.
•Write your initials and date of correction. Write justification if
possible
•When two people signed the original entry, and then another
changes the entry, the second person must also sign for the
change.
Weight of ingredient 14.5 kg 14.75 kg Ams 19.08.2016
Here’s how a corrected entry might look:
Illegible entry
Wrong entry
Good Documentation Practice
Lab record:
Enter enough details so the document can be
understood in the future.
Documents should be signed and dated by the
person who performed the test.
A reference to the identification of the sample
analysed should be included.
Good Documentation Practice
Witnessed / Checked/ reviewed by
• The second check : When one person performs the task and
the second person verifies that it has been performed
correctly.
• Double checking our work provides additional assurance that
no mistakes were made.
• The person who is the “verifier” must be clear as to what
they are verifying by affixing their signature to the
document.
• Examples: charging of raw materials ; Monitoring critical
parameters
Good Documentation Practice
Reviewer:
Must be verified by a second person
Signature of the person verified
Verify within a time frame
Review he documentation:
• BPRs, Test record, material issue, Cleaning
records, calibration and equipment
records, raw data, yield & Calculations etc
Good Documentation Practice
Review of the original records when the records are
complete / after complete analysis of a sample has been
performed.
All raw data, all printed / electronic data
Chromatogram, spectrum weight prints, This can be done on
a sheet/record where all results have been summarized
If a notebook is no longer used and unused pages are
remaining
Draw a line across the first unused page
Indicate “the remainder of the note book is not used”
Sign with date
Good Documentation Practice
Check the following during review:
Missing records and out-prints
Incomplete entries
Illegible corrections
Cross References
Deviations, if any investigation the impact on the product
Valid calibrations and service intervals of test equipment
Compliance with specifications, parameter ranges or
acceptance criteria including tighter customer
specifications
Good Documentation Practice
Examples of deviations are:
Incorrect charging of raw materials.
Temperature, pressure, vacuum parameters outside
defined limits.
Operating instructions not correctly followed.
Breakdown of equipment or failure of utilities.
Equipment out of calibration.
Records not adequately completed.
Temporary alteration to defined instructions
In Process Control Limits not achieved.
Extraneous contamination of API and intermediates
Any other unplanned event.
Good Documentation Practice