Hybrid Record System

Common examples include a chromatography system where electronic raw data is printed and signed, a paper batch record that references values in a control system, and electronic records signed with wet ink.

The record is the combination; neither half alone tells the full story.

Risks include printed summaries that omit electronic data such as reprocessing or failed injections, mismatched versions, signatures that cannot be linked to the electronic record and gaps in audit trail review.

Regulators note that paper printouts of electronic data are not true copies unless they preserve full content and meaning.

Define in procedures which part is the original record, how paper and electronic parts are linked with unique identifiers, how signatures apply, and how audit trails are reviewed alongside paper.

Control blank forms, issue them with unique numbers and reconcile them.

Reviewers should examine electronic raw data and audit trails, not just signed printouts. Review procedures should state what is checked and how.

Risk-based review focuses on data that affects product quality decisions.

Both parts must be retained for the required period and retrievable together. Electronic data must remain readable as systems change.

Destroying electronic raw data because a printout exists is a known data integrity failure.

Many sites treat hybrid systems as interim. Moving to fully electronic records with compliant signatures reduces linking risk but requires validation.

Prioritise processes where hybrid controls are weakest.

Pitfalls include uncontrolled printouts, transcribing values by hand, shared logins on instruments and assuming the paper signature covers changes made electronically later.

Audit hybrid records specifically during self-inspection.

• A defined list of which record elements are paper and which are electronic, approved in a procedure.
• Reliable linkage between a paper signature and the electronic record it approves, such as record ID and version.
• Controlled printouts so an uncontrolled copy cannot be mistaken for the original.
• Retention rules covering both media, including how audit trails are reviewed and kept.

Regulators such as the MHRA describe hybrid systems as harder to control than fully electronic or fully paper systems, so the controls deserve explicit documentation.

Many sites use hybrid records as a transition. Moving one workflow at a time, for example line clearance or weighing first, keeps the change manageable and lets each step be validated before the next.

Archived paper records keep their retention obligations after a workflow goes electronic, so the archive plan should be agreed before paper stops being produced.

V5 provides electronic batch records with attributable entries, audit trails and electronic signatures, which can replace paper steps and reduce the number of hybrid links a site must control.

V5 does not make a hybrid process compliant on its own. Sites define procedures and validate their configuration; regulated validated use is offered on Enterprise private cloud with IQ/OQ support.

List processes where an official record spans paper and software. For each, state which part is original, how they are linked, and who reviews the electronic part.

Close the weakest link first.

A wet signature on a printout should clearly identify the electronic record it approves, including version or unique identifier, so later changes to the electronic data can be detected.

Where electronic signatures are used, ensure they meet applicable requirements and cannot be separated from the record.

Uncontrolled forms allow records to be rewritten. Issue numbered forms from a controlled source, reconcile issued and returned forms, and investigate missing ones.

Templates should be version controlled and approved.

Balances, pH meters and other simple instruments often print results that are attached to paper records. Assess whether the printout captures all relevant data, including settings and identity.

Where instruments store data electronically, decide whether that data is the original record.

A QC analyst prints a chromatography summary and signs it. Audit trail review finds two reprocessed injections not shown on the printout.

The site updates its procedure to require electronic review of audit trails before signing, trains analysts and plans electronic signatures in the data system.

1. Confirm the applicable requirement, product scope and decision owner.
2. Map the current method and the records already available.
3. Define terms, responsibilities, evidence and exception handling in the approved procedure.
4. Pilot the method on one representative process and challenge a difficult exception.
5. Train affected roles, approve the change and monitor whether the method works as intended.
6. Review after significant change and retain a transparent history of decisions.

Scale the formality to risk and complexity. A small operation still needs clear responsibilities and reconstructable evidence, while a multi-site operation also needs harmonised definitions, governance and comparison rules.

• Can a reviewer identify the source, owner, method and current approved version?
• Do summaries reconcile to original records and include unfavourable or missing evidence?
• Are exceptions visible, assessed and linked to the affected material, product or process?
• Are actions assigned, overdue items escalated and effectiveness reviewed?
• Have changes in product, supplier, equipment, method or regulation triggered reassessment?
• Does the record distinguish system support from the decision an authorised person made?

• Approved scope, definitions and responsibilities for Hybrid Record System.
• Source records and identifiers that let a reviewer reconstruct the work.
• Methods, assumptions, calculations, exclusions and any data-quality limitations.
• Exceptions, investigations, decisions, approvals and resulting actions.
• Version history showing when the approach changed and why.

Records should be proportionate to the decision and usable by someone who was not present. Preserve original evidence and corrections rather than replacing it with an unexplained summary.

• Can users trace every summary value back to its source record and version?
• How are roles, permissions, signatures and corrections recorded?
• Can the workflow reflect our approved procedure without inventing a universal rule?
• What happens during an outage, and how are later entries distinguished?
• Can we test the highest-risk exception with realistic data before committing?
• Which decisions remain explicitly assigned to an authorised person?