How to make sure that an eTMF is compliant to new TMF EMA Guideline?

January 14, 2019

18th December 2018 EMA published a long-awaited “Guideline on the content, management and archiving on the clinical trial master file (paper and/or electronics)”. The release acquired many questions regarding the new reality of TMF, that everyone working in the EU will have to deal with after the document’s effective date 18/06/2019.

How to make sure that an eTMF is compliant to the new TMF EMA Guideline?

Use our checklist(exact quotes from EMA Guideline paper):

  • Electronic TMFs should enable appropriate security and reliability, ensuring that no loss, alteration or corruption of data and documents occur
  • Access to the TMF should be based on a role and permission description that is defined by the sponsor and/or investigator/institution
  • At all times the storage area for the TMF documents (such as paper or electronic media archives and server rooms) should be appropriate to maintain the documents in a manner that they remain complete and legible throughout the trial conduct and the required period of retention and can be made available to the competent authorities of the Member States, upon request
  • The eTMF systems should be validated to demonstrate that the functionality is fit for purpose, with formal procedures in place to manage this process
  • All staff members involved in the conduct of the trial and using the system should receive appropriate training
  • Metadata applied to documents should be formally defined to ensure consistency across all documents
  • The TMF including the audit trail (for eTMF) should be archived appropriately to enable supervision after the clinical trial has ended
  • After archiving any alteration to the content of the trial master file shall be traceable

We’ve recently finished the re-designing process and now our system is not only functional but simply awesome.

Interested? Request a demo via the button on top of the page or drop us an email to bd@flexdatabases.com

Blog

July 7, 2026
Is Your EDC Really Modern If Someone Still Has to Re-Enter Every Serious Adverse Event?

Clinical industry has finally embraced AI, sponsors run decentralized trials and data is now collected in real time. But still one of the most critical workflows in every study – handling adverse events (AEs) – surprisingly depends on copy-paste. Most sponsors assume that if they have an Electronic Data Capture (EDC) system and a Pharmacovigilance […]

June 30, 2026
Validating AI in GxP Environments: The Flex Databases Approach to eTMF Compliance

The pharmaceutical industry faces a familiar paradox: the tools that promise to make regulatory compliance faster and smarter also introduce the most complex new compliance questions. Nowhere is this more visible than in AI-powered Trial Master File (TMF) management. At Flex Databases, we have developed a validation framework rooted in GxP principles, risk-based thinking, and […]

June 25, 2026
The Quiet Revolution in TMF: How AI Document Classification Turns Routine into a Background Task

AI in Trial Master File management has quietly stopped being a someday idea. It’s not a pilot and it’s not a roadmap promise – it’s something clinical teams reach for on an ordinary Tuesday. The interesting part isn’t that AI can file a document; it’s how calmly and predictably it does it now – with […]

June 24, 2026
Investigator Site File Management with Flex Databases

Managing Investigator Site Files across multiple sites is one of the more operationally demanding aspects of clinical trial oversight. Flex Databases addresses this with a dedicated ISF module built around three distinct user experiences (Sponsor, CRA, and Site) each tailored to the workflows and priorities of its audience. The Sponsor View: Study-Wide Visibility Sponsors access […]

Contact us

Get in touch to discuss compliance, implementation, demos, pricing

We are here for all of your questions! Tell us more about yourself and we will organize a tailored live demo to show how you can power up your clinical trials processes with Flex Databases.