Sponsors and CROs that own and maintain the trial master file (TMF) and need an electronic TMF system.
Scope Sponsors and CROs that own and maintain the trial master file. Site-side eISF and eRegulatory binders are out of scope, except where the vendor also sells a sponsor or CRO eTMF (Florence). The collaboration feature notes describe how each eTMF exchanges documents with sites.
These notes describe the products in the eTMF guide.
Florence eTMF
Best for
Sponsors and CROs whose sites already use Florence eBinders and who want site documents to flow into the TMF
What to consider
Florence's strength is the site side: its eTMF connects to each site's Florence eISF through SiteLink, and Florence reports 88,000+ research sites on its network. It has an open API, Part 11 electronic signatures and a SOC 2 Type II report. Its public eTMF pages do not describe a TMF Reference Model structure or inspector access.
Sponsors already on Rave EDC and Medidata CTMS who want the TMF on the same platform
What to consider
Medidata eTMF supports the TMF Reference Model and is unified with Rave and Medidata CTMS, so monitoring visit reports file into the TMF automatically; Medidata states go-live in as little as six weeks. Its public page describes rule-based auto-filing rather than AI classification, and no eTMF-specific adoption figures are published.
Single and double checks describe documented support for an individual feature. Double checks use the extended definition for that feature. Unknown means the available evidence does not establish support.
Expand a feature definition or support note for context and its original source.
Florence eTMF vs Medidata eTMF (eTMF): category feature evidence and sources. Products are not ranked.
Category feature
Florence eTMF
Medidata eTMF
TMF Reference Model and inspection readinessFeature definitions
Supported
A TMF Reference Model structure or document completeness tracking is documented.
Extended support
A TMF Reference Model structure, completeness tracking and dedicated inspector access are all documented.
Florence eTMF
Supported
Florence shows missing and expired documents and milestone dashboards, but its public eTMF pages do not describe a TMF Reference Model structure or inspector access.
Missing/expired-document and milestone dashboards establish tracking; model alignment and inspector access are not described.
Medidata eTMF
Supported
Medidata states full support for the DIA TMF Reference Model and dashboards for quality, timeliness and completeness; inspector access is not described.
The Reference Model and completeness dashboards are stated; inspector access is not described.
Document capture and AI automationFeature definitions
Supported
Automated document capture, filing or processing is documented.
Extended support
AI classifies or indexes documents and extracts metadata or attribute values.
Florence eTMF
Supported
Florence syncs documents into the eTMF by email and in October 2026 announced AI classification that recommends document type and filing location for user approval; metadata extraction is not described.
Unified Rave/CTMS and automatic report filing establish base support; an eTMF API is not described.
Compliance and validation evidenceFeature definitions
Supported
Relevant trial compliance or security controls are stated, with their scope identified.
Extended support
Relevant trial controls and a publicly accessible ISO certificate or SOC audit report covering the product or vendor are documented.
Florence eTMF
Supported
Florence has an annual third-party SOC 2 Type II attestation (report under NDA), and its eTMF FAQ states Part 11-compliant electronic records and signatures.