V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryMHRA GxP Data Integrity Guidance
Compliance · The complete guide

MHRA GxP Data Integrity GuidanceMHRA 'GxP' Data Integrity Definitions and Guidance for Industry

In short

MHRA’s March 2018 GxP guidance explains risk-based data governance, original records, metadata and review; it is not law, certification or device-specific guidance.

2,183 words · ~10 min read
Laboratory quality specialist compares an analytical record with electronic data
Original data, metadata and review give a reported result its meaning. Editorial illustration; not a customer photograph.
On this page
  1. 01Guidance explains data integrity expectations
  2. 02Start with the decisions the data support
  3. 03Apply ALCOA without reducing it to a slogan
  4. 04Distinguish raw data, metadata and reported results
  5. 05Preserve dynamic records and meaningful true copies
  6. 06Design the right recording environment
  7. 07Review audit trails according to criticality
  8. 08Control access and privileged administration
  9. 09Validate transfers, processing and retention
  10. 10Give management and process owners real duties
  11. 11Ask audit questions that reconstruct meaning
  12. 12Specify what a reviewer must be able to see
On this page · 12 sections
  1. 1Guidance explains data integrity expectations
  2. 2Start with the decisions the data support
  3. 3Apply ALCOA without reducing it to a slogan
  4. 4Distinguish raw data, metadata and reported results
  5. 5Preserve dynamic records and meaningful true copies
  6. 6Design the right recording environment
  7. 7Review audit trails according to criticality
  8. 8Control access and privileged administration
  9. 9Validate transfers, processing and retention
  10. 10Give management and process owners real duties
  11. 11Ask audit questions that reconstruct meaning
  12. 12Specify what a reviewer must be able to see
AI · Explain it for MY operation

How does MHRA GxP Data Integrity Guidance apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01Guidance explains data integrity expectations

The MHRA GxP Data Integrity Guidance and Definitions, Revision 1, March 2018, explains the UK regulator's interpretation of data integrity principles across relevant good-practice environments. It is guidance, not a standalone law, certification standard or software approval. It must be read alongside the applicable regulations and practice-specific requirements. A claim that a company is 'MHRA data integrity certified' is not supported merely by following this document.

The GOV.UK publication page was updated on 27 September 2021 to explain that the OECD advisory document on data integrity takes precedence for GLP in the relevant context. The March 2018 PDF itself has not thereby become a new revision. Record both the PDF version and the publication-page qualification when using it. Do not imply that one unchanged document is the sole current authority for every GxP discipline.

The PDF expressly excludes medical devices from its scope. Its data-governance concepts may inform thinking elsewhere, but device obligations need their own applicable basis, including current FDA QMSR where relevant. ISO 13485 readiness addresses that separate context. Similar principles across sectors do not make the legal scopes interchangeable.

02Start with the decisions the data support

The guidance treats data integrity as the completeness, consistency and accuracy of data across their lifecycle. Start with the decisions a record supports: product acceptance, patient safety, study conclusions, distribution suitability or another regulated activity. The consequences of unreliable data differ, so data criticality and inherent integrity risk should inform the control assessment rather than the record's file format alone.

A data integrity risk assessment should identify where data originate, how they are processed, which metadata give them meaning, who can change or exclude them, and where review and retention occur. This is not only an IT inventory. Paper worksheets, instrument files, hybrid records, outsourced data and informal temporary notes can all affect a regulated decision.

The guidance does not call for routine forensic investigation of every data item. Controls should be proportionate to criticality and risk. Proportionality does not justify ignoring significant weaknesses or removing original evidence. Explain the risk, control and residual gap with enough specificity that a reviewer can understand the assessment and the remediation priority.

03Apply ALCOA without reducing it to a slogan

Attributable, legible, contemporaneous, original and accurate are commonly abbreviated ALCOA. The guidance also addresses completeness, consistency, endurance and availability, sometimes expressed as ALCOA+. It states that there is no difference in expectations depending on which acronym is used. Adding a plus sign to a policy does not create a stronger system if the actual records remain incomplete.

Attribution means understanding who performed or recorded the activity, not simply seeing a shared username. Contemporaneity concerns recording at the time of the activity, not a later upload timestamp. Originality requires preserving the record and relevant context needed to reconstruct the observation. Accuracy needs appropriate controls over creation, processing, correction and interpretation, not only a final review signature.

Map each principle to the actual process. For a manual measurement, consider point-of-use recording, identifiable personnel, controlled corrections and the original worksheet. For an analytical system, consider raw data, metadata, processing history, access and review. These are distinct control questions; one generic checklist should not obscure the different failure opportunities.

04Distinguish raw data, metadata and reported results

The guidance defines raw data as the original first-capture record and emphasizes that metadata are integral to its meaning. Metadata may identify the operator, date, time, instrument, processing method, sequence or changes. A printed result can show a number while omitting the information necessary to understand how that number was produced.

Distinguish source observations, processed results and the final report. An analytical value can depend on sample preparation, acquisition parameters, integration or other processing decisions. Preserve the applicable evidence and traceability between those stages. A final report alone should not automatically be declared the complete original record merely because it is easier to store or review.

Where data are excluded, retain the original evidence and a scientifically valid justification according to the applicable context. The guidance discusses limits and practice-specific distinctions, including pharmacovigilance. Do not turn its discussion into a universal permission to delete inconvenient observations. A reviewer should be able to see what was excluded, why and who assessed the decision.

05Preserve dynamic records and meaningful true copies

A dynamic record can allow interaction with the data, such as reprocessing or examining underlying analytical information. A static representation may show only a selected view. The guidance explains that a true copy must preserve the meaning of the original, including relevant metadata and functionality. Converting every dynamic dataset to PDF without assessment can lose information needed for review or reconstruction.

A verified copy may be suitable where it preserves what the original requires, but that conclusion needs a documented basis. Define the original record, the intended copy, the verification method and what functions or metadata must remain available. The appropriate decision depends on the record's nature; this article does not declare all paper copies inadequate or all electronic exports sufficient.

The audit evidence readiness checklist can help organize retrieval questions. Use it alongside the actual data and procedures. A readable online document or printed sample is an explanatory resource, not a true-copy qualification for a manufacturer's records. Full guide access remains behind the existing email form.

06Design the right recording environment

The guidance emphasizes making reliable recording practical. Provide controlled forms or appropriate systems at the point of activity, adequate space and time, and clear instructions. Avoid forcing personnel to remember observations until a later desk entry. Management should examine whether production targets or local habits encourage retrospective completion or selective reporting.

For paper systems, consider controlled blank forms, identifiable records, correction rules and reconciliation where appropriate. For hybrid workflows, define which document is the original, how later transcription is checked and what happens to the contemporaneous source. A later kiosk transcription should remain identifiable as later transcription; retaining and reconciling the original observations is different from pretending the later timestamp is the event time.

The guidance discusses limited justified use of scribes where contemporaneous recording by the performer is impractical, such as certain operational circumstances. Do not generalize that into permission for routine retrospective completion. Define the justified arrangement, attribution and verification. The practical objective is a reliable account of the activity, not completion of fields at any cost.

07Review audit trails according to criticality

An audit trail records relevant changes and actions so data history can be reconstructed. The guidance discusses controls preventing users from altering or disabling it and consideration of privileged actions. Audit-trail availability is not enough: review must focus on the events relevant to the regulated decision and the assessed risk.

The e-signature and audit trail review checklist illustrates questions about attribution, changes and review. It does not mean every keystroke or log-on must be manually reviewed for every batch. The guidance supports a risk-based approach, including suitable exception reporting where justified. Define what is reviewed, by whom, when, and how issues affect the decision.

For legacy systems with limitations, identify the gap and appropriate interim controls, such as controlled supporting logs where suitable. Document the risk, responsible owner and remediation plan, and demonstrate progress. A compensating procedure should not become an indefinite assertion that missing system capability is harmless. Review whether the interim control actually preserves the relevant evidence.

08Control access and privileged administration

User access should support individual attribution and appropriate authority. Shared credentials can obscure responsibility; unrestricted administrator rights can permit changes outside normal review. Define who needs which privileges, how access is granted and removed, and how conflicts between data creation, administration and review are handled in the actual organization.

The guidance recognizes the importance of system administration and supplier responsibilities. Evaluate whether privileged activity is visible and whether regulated users can alter critical configuration, time settings or historical records without appropriate control. Separate technical support from authority to approve the regulated result. An administrator's successful repair is not a product-disposition decision.

A small organization may need a practical arrangement rather than a large dedicated team, but should document how oversight and accountability are maintained. Do not claim that one universal role-separation chart is mandated for every system. Assess the actual opportunities for unobserved change and the evidence that mitigates them, including supplier or external-service access.

09Validate transfers, processing and retention

Data transfer and migration can change meaning if identifiers, timestamps, units, relationships or processing context are lost. The guidance expects appropriate verification and control for these operations. Define the source, destination, transformation, acceptance criteria and reconciliation. Testing that a file opens does not prove that all relevant data and metadata transferred correctly.

Processing should remain traceable to the original data and the relevant parameters. If processing is repeated with changed settings, preserve the history needed to understand the changes. A final passing report should not conceal earlier processing attempts that affect interpretation. Review the applicable system and method rather than assuming every reprocessing event is either improper or automatically acceptable.

Retention must preserve availability and meaning for the required period. Backup supports recovery; archive supports retained record access. The guidance distinguishes those purposes. Test retrieval and readability, including metadata and necessary dynamic functionality, after archival or supplier changes. A successful backup job does not demonstrate that a historical regulated record can be reviewed correctly.

10Give management and process owners real duties

Senior management influences culture, resources and incentives. A data-governance policy should have meaningful endorsement and practical implementation. Quality personnel coordinate risk and review; process owners understand the data generated in their work; IT and suppliers support technical controls. Data integrity cannot be delegated entirely to a validation department while operating practices remain unexamined.

The guidance discusses appropriate notification to regulatory authorities where significant data integrity incidents are identified. Treat this as guidance linked to the applicable regulatory context, not a newly invented universal notification law. Establish escalation to qualified personnel who assess the incident, its scope and the applicable reporting or notification duties. Preserve the assessment and rationale.

For remediation, distinguish immediate containment, scope assessment, root cause, corrective actions and evidence of effectiveness. A training-only response may be inadequate if the underlying form, access model or performance pressure remains unchanged. Assess whether related systems or processes share the same vulnerability rather than limiting the review to the first discovered record.

11Ask audit questions that reconstruct meaning

Select a regulated decision and trace it to original data, metadata, processing, review and retention. Ask what the reviewer could actually see at approval time. For a hybrid record, follow the original observation into later transcription and reconciliation. For a dynamic analytical record, compare the retained dataset with the report and determine whether relevant history remains available.

Review an access change, excluded result, migration and legacy-system gap. Ask who made the decision, what evidence supported it and whether the risk assessment matches the actual process. Potential weaknesses include shared credentials, retrospective entries without source evidence, static exports losing dynamic meaning, unreviewed critical changes, inaccessible archives and remediation plans with no demonstrated progress.

The data integrity feature page and pharmaceutical sector page offer related commercial context. They are not evidence of MHRA certification or of a customer's compliance. This article explains the guidance and practical assessment questions; the responsible organization owns its regulated records, controls, validation and approvals under the applicable framework.

12Specify what a reviewer must be able to see

Data review should be designed around the regulated decision. Identify the relevant original data, critical metadata, processing history, changes, exclusions and supporting observations. A reviewer who sees only a selected summary may be unable to assess completeness. The guidance does not require the same review depth for every record; explain the risk-based selection and how exceptions are handled.

Check whether the review occurs at the appropriate point in the process and whether the reviewer has the necessary access. A procedure can require audit-trail review while the assigned person lacks permission to view the trail. Likewise, an outsourced provider can supply a report while withholding the source information needed for the customer's decision. Resolve those practical mismatches in the access and agreement arrangements.

Review evidence should identify the scope and outcome, including significant issues and their assessed effect. A signature alone may not explain whether the reviewer examined the relevant changes or only confirmed that a report existed. Define the record of review in a way that supports later reconstruction without turning it into an uninformative exercise in collecting more signatures.

When the risk assessment changes, reassess the review design. A new processing function, increased configurability or changed outsourcing arrangement can alter the opportunities for unnoticed data change. Keep the rationale and resulting controls current instead of assuming that a review procedure approved years earlier remains appropriate for a changed system.

Frequently asked questions

Q.Is MHRA data integrity guidance a certification standard?+

No. It is regulatory guidance explaining relevant expectations and must be read with applicable requirements. It does not establish a company or software certification.

Q.Does the guidance cover medical devices?+

The March 2018 PDF explicitly excludes medical devices. The publication page also notes OECD precedence for GLP; use the applicable framework for the actual activity.

Primary sources

  • MHRA publication page, including 2021 GLP qualification — reviewed 9 Oct 2026
  • MHRA GxP Data Integrity Guidance and Definitions, Rev 1 March 2018 — reviewed 9 Oct 2026

Further reading

  • E-Signature and Audit Trail Review Checklist
    Assess attribution and meaningful review.
  • Audit Evidence Readiness Checklist
    Test complete original-data retrieval.
Software that covers MHRA GxP Data Integrity Guidance
V5 Ultimate (21 CFR Part 11)
V5 Ultimate gives FDA-regulated manufacturers bound e-signatures, an audit trail, authority checks and printed-copy controls. An…
V5 Ultimate GxP Software
Part 11 and Annex 11 controls, audit trails and validation evidence your QA team reviews and approves. IQ/OQ support is available…
Talk to us about MHRA GxP Data Integrity Guidance

Want to see how MHRA GxP Data Integrity Guidance could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
PharmaceuticalMedical DevicesBlood & TissueVet Pharma
Inside V5
  • → 21 CFR Part 11 — signatures and audit history your team can validate.
Example reports
V5Ultimate

Sample report

Compliance Readiness Assessment

Quality system

Compliance Readiness AssessmentView on screen or print
V5Ultimate

Sample report

Validation Support Pack

Quality system

Validation Support PackView on screen or print
→ All example reports
Regulatory anchors
  • MHRA GxP Data Integrity (Mar 2018)
Related terms
  • → Data Integrity
  • → Audit Trail
  • → 21 CFR Part 11
  • → EU Annex 11

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC