top of page
Homepage
Book a demo →

What Is an eTMF System? Features to Look For and How to Choose One

Writer: myLaminin
myLaminin
5 hours ago
8 min read

Last updated: November 2026


Reviewed by Colin Spetz, Senior Software Engineer, myLaminin


A clinical trial sheds paper the way a busy kitchen sheds dishes. Protocol, consent forms, approvals, training records, monitoring reports, and a lot more. Regulators expect that trail to be complete, organized and ready for inspection at any time (not the week before an inspector turns up; any time). Most sponsors, CROs and research sites now keep it in an electronic trial master file (eTMF) system.


So what is one, really? An eTMF is the electronic form of the trial master file, the collection of essential records that shows a trial was run properly and that its data can be trusted. Regulators are pointed about what they want from it: validated systems, audit trails, role-based access, quality control, certified copies, and direct access for inspectors. ICH E6(R3) now talks about "essential records" and handles them in Appendix C. It applies in the EU from July 2025, and Health Canada implemented it in April 2026. Choosing one means weighing four things: its compliance controls, its quality-control workflows, how it connects with your CTMS and EDC, and how well it holds up for inspection readiness.


What is an eTMF?

A trial master file (TMF) is the set of essential records that lets someone evaluate how a clinical trial was conducted and how good its data is. ICH E6(R3) notes that the sponsor's records may be referred to as a trial master file, and the site's as an investigator site file (ISF).


An eTMF system is the software that stores, organizes, reviews and archives those records electronically. No binders. No filing cabinets. Your team uploads documents, tags them with metadata, runs quality checks, and hands monitors, auditors and inspectors controlled access.


On the site side, the electronic file usually goes by eISF. Plenty of teams want the two joined up, and we think they're right to: a document shared between sponsor and site should stay one document, not two copies quietly drifting apart.


How eTMFs are organized: the TMF Reference Model

Most eTMF systems are built around the TMF Reference Model, an industry standard published by CDISC. The current release is version 3.3.1, from August 2023. It sorts artifacts into zones and sections and flags each one as "core" or "recommended".


A successor is on its way. The CDISC TMF Standard Model v1 is in community review, and CDISC describes it as a new model rather than a revision of 3.3.1. Record groups and record types come in. The core/recommended split goes out. There's a new eClinical zone, and it covers medical devices, real-world evidence and the investigator site file. Release is planned for April 2027.


Our take: if you're signing a contract now, make the vendor explain how they'll carry you from 3.3.1 to the new model. A vague answer tells you plenty.


CDISC also publishes the eTMF Exchange Mechanism Standard, which covers moving TMF content from one eTMF system to another. Ask about that one in the same breath.


What regulators expect from an eTMF

ICH E6(R3)

The international good clinical practice guideline uses the term "essential records" and deals with them in Appendix C. What does it ask for? Records stored so they can be identified, with version history, search and retrieval. Filing done in a timely manner. And direct access for regulatory authorities whenever they request it.


Copies get a rule of their own. If a copy replaces an original, it has to be a certified copy: verified by a dated signature or generated through a validated process, and carrying the same information as the original, relevant metadata included.


For the record, the dates. E6(R3) Principles and Annex 1 took effect in the EU on 23 July 2025. FDA published it as final guidance in September 2025, and Health Canada implemented it on 1 April 2026.



EMA guideline on the trial master file

If you read one regulatory document on eTMFs, honestly, make it this one. The European Medicines Agency's TMF guideline (EMA/INS/GCP/856758/2018, effective June 2019) is the most detailed regulatory text on the subject. Validation comes first: eTMF systems should be validated to show they're fit for purpose. Security follows, with individual user accounts, secure passwords and role-based permissions (restricting access to randomization codes is the guideline's own example). Every upload and every deletion goes into an audit trail, stamped with the date, time and user. Backups run regularly, with periodic test restores, because a backup nobody has ever restored is closer to a hope than a plan. Metadata gets formally defined, and any migration gets verified.


Quality control is meant to be risk-based: checking that documents were filed on time, indexed correctly and complete, and it also covers reviewing the audit trail itself, a step that's easy to skip. The TMF should be readily available and directly accessible to authorities. Once the trial closes, the eTMF is archived with its audit trail, read-only. Under the EU Clinical Trials Regulation, the TMF is kept for at least 25 years after the trial ends.


One requirement deserves more airtime than it gets.


The guideline says the investigator's part of the TMF must stay under the investigator's control, independent of the sponsor. Designing how sponsor and site share documents? Start there.


21 CFR Part 11 (United States)

For trials under FDA oversight, 21 CFR Part 11 governs electronic records and signatures. These are the clauses that bite hardest on an eTMF:


  • 11.10(d): access limited to authorized individuals

  • 11.10(e): secure, computer-generated, time-stamped audit trails, where changes don't obscure earlier information

  • 11.10(b): accurate copies, in both human-readable and electronic form

  • 11.50 and 11.70: electronic signatures that show the signer's name, the date and time, and what the signature means (review or approval, say), linked to their records so they can't be copied or removed


Health Canada

Closer to home for us. In Canada, sponsors must keep clinical trial records for 15 years under the Food and Drug Regulations (C.05.012), and Health Canada's guidance GUI-0100 expects any electronic system used to capture, manage or archive trial information to be adequately validated.


eTMF features to compare

Bring this into every vendor demo. Don't let anyone skip a line.


  1. A TMF Reference Model structure that can bend toward the upcoming TMF Standard Model.

  2. QC workflows that check completeness, correct filing, indexing and timeliness, with reason codes whenever a document is rejected.

  3. Completeness and timeliness tracking, so you spot what's missing or late before an inspector does.

  4. An audit trail over every upload, change, review, approval and deletion. Every one.

  5. Role-based access, blinding and unblinding restrictions included.

  6. Part 11-compliant electronic signatures.

  7. Certified copy support, backed by a validated scanning and verification process.

  8. Defined metadata, plus search across studies, sites and document types.

  9. An eISF connection that keeps site and sponsor documents in sync and records when sites received and accessed each version.

  10. Inspector access that's read-only, with the audit trails still visible.

  11. Validation documentation from the vendor.

  12. CTMS and EDC integration, so study milestones, site status and documents stay linked.

  13. Archiving and export, audit trail and all, in a format that will last 15 to 25 years.

  14. AI assistance with a human in the loop: suggested classifications or QC findings, where every suggestion is logged and a person confirms each one.


We'd push back hard on any vendor who treats the logging half of number 14 as a nice-to-have. An AI suggestion that leaves no trace is a hole in your audit trail with a nicer interface.


How to choose an eTMF system

Where do we even start? With your obligations, not the demo. List the regulations your trials fall under (ICH E6(R3), Part 11, the EU CTR, Health Canada) and turn each one into a requirement you can test a system against.


Who's going to use it? Sponsors, CROs, sites, monitors and auditors, each needing different access. Check how the system handles every role, including site staff who should see their own site's records and nothing else.


What counts as proof? Evidence, not assurances. Request the vendor's validation package and a SOC 2 Type II or similar security report. Then have them show you an inspector's read-only view, audit trail included. If producing that view takes a support ticket, you've learned something.


Standalone or connected? A standalone eTMF means copying documents over from your CTMS and EDC. A connected platform files them where they're created. We build the second kind, so discount our enthusiasm as you see fit.


How do we kick the tires? With real documents. Pilot on a closed or test study and push documents through the whole cycle: upload, classify, QC, sign, export, archive. Picture a site uploading a consent form with the wrong version date. Does QC catch it? How is the rejection recorded, and what does the audit trail show afterwards?


And two decades out? Retention is measured in decades, not contract terms. Confirm how you'll get your records and audit trail out, in a usable format, for the full retention period.


Implementing an eTMF: what to plan for

Nothing glamorous here. Order matters, though.


  • File plan. Configure it against the TMF Reference Model and your own SOPs.

  • Metadata and naming rules. Agree them before migration starts, not halfway through.

  • Existing content. Migrate it, verify it, and document the verification.

  • QC rules. Decide which documents need 100% review and which can be sampled based on risk.

  • Training. By role, with the training records kept in the TMF.

  • SOPs. Filing timelines, certified copies, QC, access reviews, archiving.

  • A mock inspection. Before the first real one.



eTMF in myLaminin

myLaminin puts eTMF and eISF document management in the same platform as our CTMS and EDC. That matters most at the handoff between site and sponsor. A site document can be filed straight into the eTMF without anyone downloading, emailing or re-uploading it. It's copied, not moved, so the site keeps its own version under its own control, which is exactly what the EMA asks for. The file's integrity is checked on the way across, the site can file a redacted version where it needs to, and both records are linked to each other in the audit trail. Trial documents, consent, eCRFs and safety events all hang off the same participant record, and every module writes to one tamper-evident audit trail. The trial file suggests classifications and QC findings, and each AI suggestion is recorded in the audit trail, whether it was accepted, changed or declined. Electronic signatures follow 21 CFR Part 11, with re-authentication.



FAQ

What is an eTMF in clinical trials?

An eTMF (electronic trial master file) is the electronic collection of a clinical trial's essential records, such as protocols, approvals, consent forms and monitoring reports, kept in a system that supports quality control, audit trails and inspection.


What is the difference between an eTMF and an eISF?

The eTMF holds the sponsor's essential records for a trial. The eISF (electronic investigator site file) holds the site's records, which must stay under the investigator's control. Many teams connect the two so shared documents stay in sync.


What is the TMF Reference Model?

It's an industry standard from CDISC for organizing trial master file content. The current version is 3.3.1, and its successor, the CDISC TMF Standard Model v1, is planned for release in April 2027.


How long must a TMF be kept?

Under the EU Clinical Trials Regulation, at least 25 years after the end of the trial. In Canada, sponsors must keep clinical trial records for 15 years. Check the rules in each country where your trial runs.


Does an eTMF need to be validated?

Yes. The EMA expects eTMF systems to be validated to show they are fit for purpose, and ICH E6(R3) expects computerized systems to be validated based on risk.


Sources


Comments

bottom of page