ICH E6(R3), the revised guideline for Good Clinical Practice, was adopted by ICH on 6 January 2025. It has applied in the EU since 23 July 2025 and in the UK since 28 April 2026. For anyone running or supporting clinical trials with electronic systems (EDC, eCOA, IRT, eTMF, safety databases, laboratory systems), it is the biggest change to GCP expectations in years.
The previous version, E6(R2), covered computerised systems in a few short clauses. E6(R3) gives them a dedicated section, sets out the data life cycle around them, and is explicit about who is responsible. This article summarises what changed and what to do about it.
The short answer
- Computerised systems now have their own section (4.3), within a new section 4 on data governance that also covers the full data life cycle (4.2).
- Validation is risk-based and lifelong. The responsible party owns the validation status of a system from first use until decommissioning, with effort proportionate to the system’s impact on participants and on the reliability of results.
- Audit trails must be reviewed, not just switched on. Review of data, audit trails and other metadata should be a planned, risk-based activity.
- Responsibility follows whoever deploys the system, sponsor or investigator, and sponsors must also consider systems at sites that hold source records, such as electronic health records.
- Security and user management are spelled out, from access reviews to backup, disaster recovery and penetration testing.
In the UK
The UK implemented ICH E6(R3) on 28 April 2026, the day the Medicines for Human Use (Clinical Trials) (Amendment) Regulations 2025 (SI 2025/538) took full effect. Under the amended regulations, compliance with the ICH E6 GCP principles is a legal requirement in the UK. The rest of the guideline, including the section 4 detail on computerised systems summarised below, explains how those principles can be met, so it remains the practical benchmark for sponsors, sites and laboratories.
The MHRA has published UK-specific annotations to ICH E6(R3), which explain where UK law or practice differs from the guideline text, and guidance on complying with ICH E6 in the UK. Trials applied for before 28 April 2026 have transitional arrangements, so check which rules apply to each study.
Where the requirements sit
| Topic | What E6(R3) expects | Where |
|---|---|---|
| Validation | Risk-based approach covering the whole life cycle; standard functionality, trial-specific configuration and interfaces all validated; documentation retained | 4.3.4 |
| Audit trails and metadata | Audit trails and logs not disabled, interpretable and reviewable; unambiguous date and time stamps (for example UTC) | 4.2.2 |
| Data and metadata review | Planned, risk-based review, adjusted as the trial progresses | 4.2.3 |
| Data transfer and migration | Validated or reconciled transfers that preserve integrity and confidentiality, including metadata | 4.2.5 |
| Security | Security controls maintained throughout the data life cycle; backup, disaster recovery and periodic testing | 4.3.3 |
| User management | Access based on role and blinding; revoked when no longer needed; periodically reviewed; history retained | 4.3.8 |
| System release | Trial systems only activated at a site after that site’s approvals are in place | 4.3.5 |
| Sponsor duties | A record of the important systems in each trial, with their use, interfaces, validation status and owner | 3.16.1(x) |
| Investigator duties | Secure, attributable access and protection of data in systems the site deploys | 2.12.9–2.12.10 |
What is genuinely new
Proportionality is built in. E6(R3) bases validation on a risk assessment of the system’s intended use, the importance of its data and its potential to affect participants and results. That is a licence to do less on low-risk systems, but only if the risk assessment is documented and defensible.
Configuration counts as much as the product. Validation covers protocol-specific configuration, edit checks, calculations and interfaces, not just the vendor’s standard functionality. For a SaaS EDC, the vendor’s validation is a starting point; the trial build is still yours to verify.
Systems “developed by other parties” are still your responsibility. The responsible party must ensure systems are validated as fit for purpose even when a vendor or CRO built them. Supplier assessment and access to validation evidence become essential.
Audit trail review becomes a planned activity. Inspectors increasingly ask not only whether audit trails exist, but who reviews them, how often and what they look for. E6(R3) makes that expectation explicit.
Site systems are in scope. Sponsors should assess, when selecting sites, whether site systems holding source records are fit for purpose or whether known issues can be mitigated. Investigators who deploy systems specifically for trials must meet the section 4 requirements in proportion to the risk.
A practical checklist
For sponsors and CROs:
- Keep a register of the important computerised systems in each trial, with their purpose, interfaces, validation status and owner.
- Base validation effort on a documented risk assessment, and validate trial-specific configuration as well as the standard product.
- Assess suppliers, and agree how you will access their validation evidence and be told about defects.
- Define which audit trails and metadata are reviewed, by whom and how often, and record the review.
- Review user access periodically, especially where blinding depends on it.
- Test backup and disaster recovery, and document data transfers and migrations, including reconciliation.
For investigator sites and laboratories:
- Know which of your systems hold trial data or source records, and be ready to show they are fit for purpose.
- Make sure every user has their own attributable account and that access matches delegation.
- For systems you deploy specifically for a trial, apply the section 4 controls in proportion to the risk.
Laboratories analysing trial samples should expect sponsors to ask these questions of their LIMS and instrument systems, which is where GCLP and E6(R3) meet.
How we can help
We help sponsors, CROs and laboratories put E6(R3) into practice: gap assessments of computerised systems against section 4, risk-based validation of EDC, eCOA, eTMF, LIMS and SaaS platforms, supplier assessments, and audit trail review procedures that stand up to inspection.