Web of Pharma · Data Integrity · ALCOA+
Original Principle in Data Integrity
How pharmaceutical teams preserve source data, true copies, metadata, and dynamic records from creation through inspection and retention.
answer
The original principle means that the record retained for GMP use is the first capture of the information or a verified true copy that preserves its content, meaning, context, and required metadata. Original data include source observations, raw instrument files, calculations, audit trails, and other evidence needed to reconstruct the activity.
A final report is usually a summary. The original record is the evidence from which that summary was created. In pharmaceutical quality systems, protecting the original means protecting the first reliable observation, measurement, calculation, decision, and history of change.
Original data are not limited to a paper sheet. They may be a signed batch record, an instrument file, a balance printout, a laboratory notebook, an electronic batch record, a chromatographic sequence, a controlled photograph, or a validated true copy. The correct form depends on how the data were generated and what is required to preserve their meaning.
For the broader framework, see the ALCOA data-integrity guide. This article explains original records, true copies, dynamic data, metadata, and practical controls for pharmaceutical operations.
What Does Original Mean in Data Integrity?
An original record is the first capture of information or the legally and procedurally controlled record that preserves the information in its original form. A true copy is an accurate reproduction that retains the content and meaning of the original and is verified through a controlled process.
First capture
Retain the record created at the point of measurement, observation, calculation, or action rather than only a later summary.
Raw data preserved
Keep source readings, injections, spectra, images, counts, calculations, and related files needed to reconstruct the activity.
Meaning intact
Do not remove units, sample identity, method, instrument, time, user, processing, or other context that gives the value meaning.
Dynamic content retained
Where data can be searched, reprocessed, recalculated, or interacted with, retain the dynamic record and its history—not only a static image.
True-copy control
Verify that a scan, reproduction, or migration is complete, accurate, readable, attributable, and protected from unauthorized change.
Metadata connected
Preserve date/time, user ID, instrument ID, method, audit trail, status, and other context required to interpret the source.
Version history visible
Keep the relationship between the original, corrected, superseded, and approved versions clear.
Controlled retention
Store originals or true copies securely for the required period with tested retrieval and authorized access.
Reviewable evidence
Make the source available to reviewers, investigators, auditors, and quality units without relying on an unverified summary.
Why Original Records Matter in Pharmaceuticals
Pharmaceutical quality decisions rely on a chain of evidence. Raw laboratory data support test results; test results support batch decisions; batch decisions support release or rejection. If the original source is replaced by a selected printout or manually retyped spreadsheet, important failures, adjustments, metadata, or processing history may disappear.
Preserving originals also makes investigations scientifically sound. When an out-of-specification result, deviation, complaint, or stability trend is reviewed, investigators need all relevant data—not only the result that was eventually reported. Original records reveal the sequence, variability, repeated attempts, and decisions that shaped the final outcome.
Original and true-copy controls operate within cGMP documentation, archival, computerized-system validation, laboratory controls, data governance, and quality-unit review.
For electronic records, the FDA’s data-integrity guidance distinguishes static records from dynamic records and explains why a printout may not preserve reprocessing, formulas, audit trails, or other information needed to reconstruct the activity.
Original Versus True Copy
| Record type | Original record example | When a true copy may be appropriate | Control needed |
|---|---|---|---|
| Paper batch record | Controlled form completed and signed during manufacturing. | Verified scan or certified reproduction used after controlled migration to an electronic archive. | Complete pages, readable entries, signatures, pagination, verification, and protection from alteration. |
| Balance or instrument output | Original electronic file or contemporaneous printout generated by the instrument. | Accurate image or report when it preserves all required data and the procedure accepts it. | Instrument identity, date/time, sample/material ID, units, operator, and validation of the copy process. |
| HPLC/CDS record | Dynamic raw data, method, sequence, integrations, metadata, audit trail, and processing history. | A validated export or true copy that preserves content and meaning for the intended review. | Retain source files, metadata, audit trail, software context, and any reprocessing history. |
| Laboratory notebook | Bound or controlled notebook containing the original observation and calculation. | Verified digital image or electronic record after an approved scanning process. | Page identity, completeness check, resolution, reviewer verification, and controlled access. |
| Photograph or video | Original file with capture time, device context, and associated record. | Validated copy embedded in a report while preserving the original file when required. | File integrity, metadata, chain of custody, version, and link to the activity. |
A true copy is not simply “a copy that looks similar.” It must be controlled and verified so the reproduction remains complete, accurate, readable, and traceable to the original.
Original Records in Paper-Based Operations
Paper remains an original record when the activity is first documented on the approved form, notebook, log, or printout. Site procedures should identify which paper record is official and prevent unofficial notes from becoming the only source of a GMP observation.
- Use controlled, numbered forms and notebooks issued through document control.
- Retain the original page, including blank, voided, or replaced pages when required by procedure.
- Keep corrections, signatures, dates, and reviewer comments visible and attributable.
- Do not replace the original with a rewritten “clean” version after an error.
- Reconcile pages, attachments, continuation sheets, labels, and supporting printouts.
- Verify scans or reproductions against the complete original before archiving.
- Protect paper from fading, moisture, chemicals, loss, and unauthorized removal.
- Maintain an index so the original can be retrieved with its associated records.
Original Electronic Data and Dynamic Records
Electronic data are original when the system first captures and stores them. The complete record may include more than the visible result: raw files, instrument settings, method versions, calculations, metadata, audit trails, user actions, and processing history may all be necessary to understand the result.
- Identify the source system that creates the data and define the official record.
- Retain native or validated formats that preserve the data’s meaning and functionality.
- Keep metadata such as user ID, date/time, instrument ID, method, sample, and status.
- Preserve audit trails showing creation, modification, deletion, reprocessing, and reason.
- Protect source data from unauthorized editing, deletion, overwrite, or uncontrolled export.
- Validate migration, backup, restore, and archival processes before relying on them.
- Test that archived files open correctly with available hardware, software, and readers.
- Keep the relationship between the raw file, report, calculation, and approval traceable.
Original Data Examples in Pharmaceutical Operations
HPLC and chromatography
The original record may include the raw data file, injection sequence, method and instrument settings, system suitability, integration parameters, audit trail, calculations, and analyst review. A final chromatogram alone may not preserve the full evidence.
UV, FTIR, and spectroscopy
Retain the spectrum or signal file, scan range, resolution, sample identity, instrument, method, processing, and relevant metadata. A cropped image can hide peaks, contaminants, or processing context.
Manufacturing and batch records
The original batch record includes actual entries, corrections, attachments, equipment printouts, line-clearance evidence, in-process results, and reviewer history. A transcribed summary does not replace the executed record.
Dispensing and weighing
Keep the original balance output or validated electronic transaction with material, lot, quantity, units, scale ID, date/time, operator, and verification. A manually typed quantity without source evidence is weaker than the original measurement.
Stability and environmental monitoring
Original records can include chamber logs, sample pull records, environmental readings, photographs, sample identity, time point, and analytical results. Preserve source observations and not only the trend chart.
Validation and qualification
Protocol readings, test outputs, calculations, deviations, raw files, and approvals form the source evidence for the final qualification or validation report. The report summarizes; it does not replace the original execution data.
Common Original-Principle Failures
Printout-only retention
Only a static report is kept even though the instrument created dynamic raw data and audit-trail history.
Manual retyping
Values are re-entered into a spreadsheet and the source printout or file is discarded.
Screenshot as source
A cropped image hides metadata, failed runs, processing settings, or the full sequence.
Uncontrolled export
Data are exported to an editable format that can be changed without preserving the original or audit trail.
Deleted failures
Aborted injections, failed tests, rejected calculations, or repeat attempts are removed from the retained record.
Unverified true copy
A scan or migration is accepted without checking page completeness, resolution, metadata, or file integrity.
Lost attachments
Printouts, labels, photographs, calculations, or continuation sheets are separated from the main record.
Ambiguous versioning
Superseded and approved records cannot be distinguished, or an old copy remains in use.
Backup mistaken for archive
A temporary system backup is treated as a controlled, retrievable, complete record for retention.
How to Protect Original Records
Map the data lifecycle
Identify where raw data are created, processed, reviewed, reported, transferred, archived, retrieved, and disposed.
Define the official source
For each workflow, state which paper, instrument, database, file, or system record is original and why.
Control true copies
Set verification, certification, resolution, metadata, indexing, and approval requirements for scans and reproductions.
Validate electronic use
Confirm that systems capture raw data, audit trails, calculations, metadata, and changes for the intended GMP workflow.
Secure and retrieve
Protect originals from loss or alteration and test archive retrieval with the hardware and software available during retention.
Review and improve
Sample source records, investigate gaps, and use CAPA when weaknesses are systemic or recurring.
Good control is risk-based. Critical laboratory, batch-release, stability, sterile-process, and validation data generally require stronger source-data and metadata controls than low-risk administrative information.
Original Record Audit Checklist
Use these questions during self-inspection, batch review, laboratory review, or computerized-system assessment:
- Is the first capture of the information identified and retained?
- Does the record include raw data, metadata, calculations, and processing history needed to reconstruct the activity?
- Are dynamic records retained in their native or validated equivalent format?
- Are printouts, exports, and screenshots used only when they preserve the required meaning and context?
- Are true copies verified for completeness, accuracy, readability, and traceability?
- Can reviewers connect the original record to its report, approval, batch, sample, or investigation?
- Are failed, aborted, rejected, and repeated events retained and assessed?
- Are versions, superseded records, and approved records clearly controlled?
- Are backups distinguished from controlled archives and tested for restoration?
- Can the original or true copy be retrieved and opened for the full retention period?
Support each answer with evidence such as source files, archive indexes, scan-verification records, audit trails, retrieval tests, system validation, and controlled procedures.
How Original Fits Into ALCOA+
Original is one part of ALCOA and ALCOA+. It works with attributable, legible, contemporaneous, accurate, complete, consistent, enduring, and available records. A record can be the first capture and still fail if it is unreadable, incomplete, altered without trace, or unavailable when needed.
For example, an original HPLC raw file needs a unique analyst identity, reliable time, readable method and result, complete metadata, accurate processing, consistent version history, enduring retention, and availability for review. The principles reinforce one another; “original” is not a permission to keep only an unorganized source file.
Key Takeaways
- The original record is the first capture or a verified true copy that preserves content and meaning.
- Original data may include raw files, metadata, calculations, audit trails, methods, and processing history.
- A readable printout or screenshot may still be incomplete when the source is dynamic.
- True copies require a controlled, documented verification process.
- Failed, aborted, repeated, and rejected events should not disappear from the source record.
- Secure retention and tested retrieval are part of protecting the original.
Conclusion
The original principle in data integrity protects the source of truth behind every pharmaceutical quality decision. It keeps the first observation, raw measurement, calculation, audit history, and approval evidence connected so reviewers can understand what happened and why.
Strong original-record practice combines controlled paper forms, native electronic data, complete metadata, verified true copies, validated migrations, secure archives, and reliable retrieval. When a report is supported by its true source rather than a selected or retyped version, the pharmaceutical quality system becomes more transparent, defensible, and inspection-ready.
Frequently Asked Questions
1. What is the original principle in data integrity?
It means retaining the first capture of data or a verified true copy that preserves the original content, context, meaning, metadata, and required history.
2. What is an original record in pharmaceutical manufacturing?
It is the first controlled record created during an activity, such as a batch entry, laboratory observation, instrument file, balance output, or approved electronic transaction.
3. What is a true copy?
A true copy is a complete and accurate reproduction verified through a controlled process so that it preserves the content and meaning of the original record.
4. Is a PDF always an original record?
No. A PDF may be a true copy or a useful report, but it may omit dynamic raw data, metadata, audit trails, formulas, or processing history contained in the source system.
5. Are printouts acceptable for laboratory data?
They may be acceptable when the printout is the original or a complete true copy for the relevant instrument. For dynamic systems, source files and associated metadata may also need to be retained.
6. What are examples of original raw data?
Examples include chromatographic files, spectra, instrument readings, sample counts, balance outputs, photographs, calculations, audit trails, and contemporaneous observations.
7. Should failed or aborted data be retained?
Relevant failed, aborted, rejected, and repeated events generally need to remain available for review and investigation. Removing them can hide the actual data history.
8. How is a scanned record made a true copy?
Use an approved process that verifies page completeness, resolution, readability, identifiers, signatures, attachments, file integrity, and traceability before the copy becomes the controlled record.
9. What is the difference between a backup and an archive?
A backup supports recovery after loss or failure; an archive is a controlled, retrievable record retained for the required period with content, meaning, security, and access preserved.
10. When does an original-record failure require CAPA?
Escalate when source data are routinely replaced, dynamic records are not retained, true copies are uncontrolled, critical metadata are lost, or the weakness is systemic or recurring.
.webp)
