Recording Data
Corrections
GDP at RTP
Signatures
Data Integrity
100

The time when it is acceptable to sign for activities you did not perform, witness, or have not verified.

NEVER

100
The person who is responsible for making corrections.

The original performer

100

It Means it Didn't Happen

If you didn't sign for it

100

The correct and best format to use for date

DDMMMYYYY

100

Must be evaluated before making corrections

Impact to product quality

200

Must be completed before physically advancing to the next step.

PMX Ticket/Record Signatures

200

Must be provided when making a correction

A reason/comment/note

200

Yearly mandatory document for ensuring attributability

Signature Log Book

200

GMP time sources that can be used for recording time for GMP activity 

• Validated computer systems with time synchronization
• Qualified equipment/instruments where time is automatically synchronized to a time server through network time protocol (NTP)
• Networked clocks or other time sources where changing the time is inaccessible to someone other than an administrator.

200

When you can make corrections without being considered a data integrity lapse

Contemporaneous/time of error

300

The activity to be done every time before advancing the ticket or batch record.

Review the page for completeness/accuracy.

300

The Acronym for corrections

CLIDE (correct, line-out, initial/sign, date/time, explain)

300

Your first course of action if you are unsure on a GDP issue.

Check the SOP PRD-94123 RTP-PRD-Good Documentation Practices

300

Signature type for a trained and/or qualified individual that executes a task.

Performed By

300

Must be notified if data integrity errors occur.

QA shopfloor support/Supervisors

400

True/False

Can you complete non-signature PMX steps under another employee's login?

False

Even when not signing for a step the person performing the step must be the Network ID logged into that station.

400

Must be part of corrections on omission errors 

• Document the evidence, or a reference to the evidence, that supports the occurrence of the task or missing information.
• Document the reason for the initial data omission.
• Initial and date the entry.
• Obtain a QA countersignature.

400

Notes added to GMP documentation and records (in both paper and electronic formats) provided the actions do not modify the process or affect the basis or the intent of the original instructions.

Clarification

400

Signature type for trained and/or qualified individual to confirm original records (or true copies) for accuracy, legibility, consistency, completeness, and compliance according to a defined process or procedure.

Reviewed By

400

These are documentation requirements for manual calculations

Manual calculations, units of measure, conversion factors, and equivalency factors must be clearly documented.

500

An unexpected occurrence identified during a GMP activity, where there is no defined procedural response in place that assures quality is not impacted.

Deviation

500

Required Approvers for any change from our standard process

QA/TSMS

500

Required for corrections impacting product quality, omissions, process change, made during/after review, or a clarification.

QA Countersignature

500

The difference between the witnessed by and verified by signature types

Real time observation

500

Errors where QA must determine if there is sufficient supporting data to indicate that data correction is appropriate when data has the potential to impact product quality

Raw data erroneously recorded out of acceptable limits where exceeding the limit has the potential to result in a product quality issue

Time and/or date data supporting the execution of a time critical GMP activity erroneously documented