Contents
On this page
- Quick answer
- The problem: a protocol amendment in a live multicentre trial
- Why a mid-study change is risky
- The standard the work had to meet
- How we approached it: separate what REDCap does from what the unit decides
- Methodology: change control for the amendment
- Reviewing the audit trail after the change
- UAE requirements we built in
- What we delivered
- How Pubrica can help
- Frequently asked questions
- Sources
InsightsInside the Lab
Guide
Inside the Lab: Implementing a Protocol Amendment in a Live REDCap Database for a UAE Multicentre Trial
A UAE hospital research unit had to change its live REDCap database mid-study after a protocol amendment, across several sites, without disturbing data already collected. This is the problem they brought us, how we approached it and what we delivered.
- REDCap
- Clinical trial data management
- Data integrity
- UAE
- Client
- UAE hospital research unit (anonymised)
- Study
- Multicentre clinical trial on REDCap
- Trigger
- Protocol amendment during data collection
- Deliverable
- Controlled change, updated data dictionary, change log and audit-trail review plan
At a glanceInside the Lab
Discuss your REDCap projectDiscuss your project
Quick answer
- A UAE hospital research unit needed to apply a protocol amendment to a live, multicentre REDCap database without affecting data already entered.
- We ran the change through a written request, impact assessment, approval, Draft-mode implementation and verification.
- Existing fields holding data were never renamed or recoded; new variables were added alongside them.
- The unit received an updated data dictionary, a change log linked to the amendment, site guidance and an audit-trail review plan.
The problem: a protocol amendment in a live multicentre trial
A hospital research unit in the UAE was running a multicentre clinical trial with its data collected in REDCap. Partway through recruitment, the protocol was amended. The amendment changed what the sites had to record, so the live database had to change too, while coordinators at several sites were still entering data.
The unit asked us to implement the amendment in a way that would stand up to a sponsor monitor or an inspector later: every change traceable to the amendment, nothing already collected altered or lost, and a clear record of which form version was live at each point in the study.
The unit and the trial are anonymised here. This article describes the problem, our method and what we delivered.
Why a mid-study change is risky
A clinical trial database changes constantly. Coordinators enter and correct data, monitors raise queries, data managers clean records, and protocol amendments add or retire fields. When an inspector or sponsor auditor asks why a value changed, or which version of a form was live in a given month, the answer has to come from the system and its documentation, not from memory.
REDCap (Research Electronic Data Capture) was designed with this in mind. Its original description lists user authentication and role-based security, and data attribution and audit capabilities, among its core features, with a logging module that shows all data transactions over the life of a project1. It is now used by a large international consortium of academic, non-profit and government partners2.
Having those features is the start, not the finish. An audit-ready clinical database also needs someone who reads the logs, a defined way to change a live project, and records that link each change to a reason and an approval. A protocol amendment tests all three at once. In a multicentre trial the risk multiplies: a careless change to a live form can break branching logic, invalidate validation rules or change what earlier REDCap audit trails show, at every site at the same time.
The standard the work had to meet
ICH E6(R3), the Good Clinical Practice guideline adopted in its final form in January 2025, places data integrity at the centre of trial conduct. At a general level it expects computerised systems used in trials to be fit for purpose, access to be controlled, and audit trails to make data changes traceable3. For studies under US FDA oversight, the October 2024 FDA guidance on electronic systems, records and signatures in clinical investigations explains how the agency applies these expectations, including to audit trails and access controls4. The underlying regulation, 21 CFR Part 11, sets the controls for electronic records5.
Table 1. Audit-trail and change-control expectations, and what they mean in a REDCap project
| Expectation | Source | What it means in practice |
|---|---|---|
| Secure, computer-generated, time-stamped audit trail of entries and changes | 21 CFR 11.10(e)5 | The REDCap logging module is switched on and not editable by study users |
| Changes must not obscure previously recorded information | 21 CFR 11.10(e)5 | Corrections are made as new entries, so the original value stays visible in the data history |
| System access limited to authorised individuals | 21 CFR 11.10(d); ICH E6(R3)53 | User rights are reviewed and accounts closed when staff leave |
| Revision and change control for system documentation | 21 CFR 11.10(k)5 | Every design change to a live project is logged, approved and traceable to a version |
| Traceable, reliable trial data | ICH E6(R3); FDA Q&A34 | Audit trails are reviewed, not only stored |
Whether Part 11 applies to a given study depends on the sponsor and the regulators involved. Many UAE investigator-initiated studies will never be submitted to the FDA, but sponsors often expect the same discipline.
An audit trail is not proof of compliance
REDCap keeps logs, but software alone does not make a study compliant. Compliance depends on how the hosting institution has validated and configured its REDCap instance, and on the study’s own procedures for access, review and change control34. Ask your REDCap administrator for the validation documentation before describing a project as compliant to a sponsor.
Need an audit-ready REDCap project?
Pubrica’s clinical data team sets up audit-trail review plans and change-control procedures for REDCap clinical trial databases, with documentation ready for monitors and auditors.
How we approached it: separate what REDCap does from what the unit decides
Four REDCap features carry most of the audit-trail and change-control load. Table 2 sets out what each one gives you and the gap your procedures must fill.
Table 2. REDCap features that support traceability, and the gaps they leave
| REDCap feature | What it records | What it does not tell you |
|---|---|---|
| Logging module | Data entries, changes, exports and administrative actions, with the user and a time stamp1 | Whether anyone reviewed the log, or whether a change was justified |
| Data history for a field | Earlier values of a field in a record, and who changed them | The clinical source for the correction |
| User rights | Who can view, edit, export or change the design1 | Whether those rights still match each person’s current role |
| Development, Production and Draft mode | A project moves from development to production; changes to a live project are prepared in Draft mode and then submitted | Why the change was needed, who approved it, and whether it was tested |
REDCap’s original workflow already separated a prototype stage, where the team tests and refines the forms, from production status for study data collection, and it allowed for mid-study form changes1. In current versions, design changes to a project in production are made in Draft mode and take effect only when submitted; depending on the institution’s settings, a REDCap administrator may need to approve them. We treat that gate as a technical safeguard that sits inside our own change-control procedure, not as a substitute for it.
Methodology: change control for the amendment
We treated the amendment as a controlled change to a validated system, not as a form edit. 21 CFR Part 11 expects revision and change control over system documentation, with a time-sequenced record of modifications5, and FDA guidance describes how audit trails and records apply to electronic systems in clinical investigations4. Our procedure has five steps.
- Request. The change is written down with its reason, the trigger (for example, a protocol amendment number), the instruments and fields affected, and the requester.
- Impact assessment. We check the effect on existing records, branching logic, calculated fields, reports, exports and the analysis plan. Renaming or recoding a field that already holds data is avoided; we add a new field instead.
- Approval. The data manager and, where required, the principal investigator or sponsor approve before any work starts. Changes that alter what is collected from participants may also need ethics committee approval first.
- Implementation and verification. The change is prepared in Draft mode, checked against the request and submitted. The checks follow the same approach as our pre-go-live testing, described in the REDCap database build guide.
- Record and communicate. We update the data dictionary version, the change log and the user guidance, and tell sites when the new version is live.
REDCap change-control checklist
- Change request records the reason, trigger and affected fields.
- Impact on existing data, logic, reports and exports has been assessed.
- No field holding data has been renamed or recoded.
- Approval is recorded before Draft-mode changes are made.
- Ethics approval is in place where the change affects what participants provide.
- Changes are verified against the request before submission.
- Data dictionary version, change log and site guidance are updated.
- Sites are told the date the new version went live.
Reviewing the audit trail after the change
Implementing the change was half the work. The other half was making sure the audit trail could be read afterwards, by the unit and by a monitor.
Audit trails are only useful if someone reads them. ICH E6(R3) frames data review as part of risk-proportionate trial oversight3, so we agree a review plan with the sponsor or principal investigator before go-live rather than reading every log line. The plan says who reviews, how often, which events are in scope and where findings are recorded.
Table 3. What we look for when reviewing REDCap logs
| Signal in the log | Why it matters | Our follow-up |
|---|---|---|
| Changes to key data (eligibility, primary outcome, adverse events) after initial entry | These fields drive safety and results | Confirm the change matches the source document or a resolved query |
| Edits to records that were already reviewed or locked | May undo earlier cleaning or monitoring | Ask the site for the reason and record it |
| Activity by accounts of staff who have left the study | Suggests access was not removed | Close the account and assess what was changed |
| Bulk data imports | Many values change at once | Check the import file and its approval |
| Unexpected or repeated exports of identifiable data | Confidentiality risk | Confirm the purpose with the data owner |
| Design changes in the log with no matching change request | Change control was bypassed | Raise a deviation and document it retrospectively |
Findings go into a dated review record, with actions and the person responsible. When a monitor or auditor asks how the audit trail is overseen, that record is the answer.
UAE requirements we built in
UAE sites must follow local health-data and research rules alongside GCP. Federal Law No. 2 of 2019 on the use of information and communications technology in health fields governs health data in the country6, and emirate-level health authorities, research ethics committees and institutions may add their own requirements on hosting, access, confidentiality and record retention. We confirm these with the institution’s research governance and information security teams before a project goes live.
For audit trails and change control, the practical points are that logs and change records are kept for as long as the study records they describe, that access reviews cover external staff such as CRO monitors, and that any change affecting participants is approved locally before it reaches REDCap.
Not legal advice
This section is a planning summary. Confirm hosting, retention and data-protection requirements with your legal and governance teams.
What we delivered
- A change request and impact assessment linking every database change to the amendment, covering existing records, branching logic, calculated fields, reports and exports.
- The amended instruments, prepared in Draft mode, verified against the request and submitted, with new variables added alongside existing fields rather than recoding fields that already held data.
- An updated data dictionary version and change log, so the unit can show which form version was live at any point in the study.
- Site guidance telling coordinators what changed and from which date.
- An audit-trail review plan agreed with the principal investigator, setting who reviews the logs, how often and which events are in scope.
The result for the unit was a documented, traceable path from the protocol amendment to every change in the database: the record a monitor asks for.
How Pubrica can help
Pubrica’s clinical data team builds and maintains REDCap databases for CROs and hospital research units, including mid-study changes, audit-trail review plans and the documentation monitors and ethics committees expect. If a protocol amendment is coming, involve us before the change reaches the live project. For how we build a database from the start, see our REDCap database build guide.
Pubrica team verdict
A protocol amendment is the moment a REDCap database is most likely to lose its audit trail. Route it through a written request, an impact assessment and an approval, add fields rather than recoding them, and leave a change log a monitor can follow.
Frequently asked questions
Yes. REDCap’s logging module records data entries, changes, exports and administrative actions with the user and time, and authorised users can view the data history of individual fields.
Not by itself. REDCap provides audit trails and access controls, but compliance depends on how the hosting institution validates and configures its instance and on the study’s own procedures.
Through change control: a written request linked to the amendment, an impact assessment, approval, implementation in Draft mode, verification against the request, and an updated data dictionary, change log and site guidance. Ethics approval of the amendment comes first where it changes what participants provide.
There is no single interval. We agree a risk-based plan with the sponsor or principal investigator that sets the frequency and the events in scope, such as changes to key data or locked records.
Yes. UAE sites must also follow local health-data and research rules, including Federal Law No. 2 of 2019 on ICT in health fields, plus ethics committee and institutional requirements.
Sources
Sources were checked on 19 November 2026. Requirements and guidance may change after that date; confirm the current version with the issuing body.
- 1Harris PA, Taylor R, Thielke R, Payne J, Gonzalez N, Conde JG. Research electronic data capture (REDCap): a metadata-driven methodology and workflow process for providing translational research informatics support. J Biomed Inform. 2009;42(2):377–381. https://doi.org/10.1016/j.jbi.2008.08.010
- 2Harris PA, Taylor R, Minor BL, Elliott V, Fernandez M, O’Neal L, et al. The REDCap consortium: building an international community of software platform partners. J Biomed Inform. 2019;95:103208. https://doi.org/10.1016/j.jbi.2019.103208
- 3International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use. ICH E6(R3) Guideline for Good Clinical Practice (GCP). Final version adopted 6 January 2025. https://database.ich.org/sites/default/files/ICH_E6%28R3%29_Step4_FinalGuideline_2025_0106.pdf
- 4US Food and Drug Administration. Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers. Guidance for industry; October 2024. https://www.fda.gov/media/166215/download
- 5US Code of Federal Regulations. Title 21, Part 11: Electronic Records; Electronic Signatures. Electronic Code of Federal Regulations. https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11
- 6United Arab Emirates Government. ICT in the health sector: legislation and policies. u.ae. https://u.ae/en/about-the-uae/whole-of-government-approach/digital-health/ict-in-the-health-sector
REDCap audit trailsREDCap change controlaudit-ready clinical databaseclinical trial data managementdata integrityICH E6(R3)
How to cite this article
Pick your referencing style and copy it. Your university or target journal may vary the punctuation, so check its guide if it has one.
Pubrica Clinical Data Team. (2026, November 19). Inside the Lab: Implementing a Protocol Amendment in a Live REDCap Database for a UAE Multicentre Trial. Pubrica. https://pubrica.com/insights/inside-the-lab/redcap-audit-trails-change-control-clinical-trials-uae/
This article is written to be learned from. Cite it if you are referring to what it says; if you are using the evidence behind it, cite the sources listed above instead.
Next steps
Need an audit-ready REDCap project?
Pubrica’s clinical data team sets up audit-trail review plans and change-control procedures for REDCap clinical trial databases, with documentation ready for monitors and auditors.
This article is general information for researchers, not legal, regulatory or funding advice. Check the current requirements of your journal, funder, ethics committee or regulator before you act on it.
More in Inside the Lab