Florence eTMF vs Medidata eTMF(eTMF)

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.

Guide updated How we compare

Compare within eTMF

Study fit, side by side

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.
Read product profile

Medidata eTMF

Best for
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.
Read product profile

Compare the features

Both products use the same category definitions. Product order is editorial; products are not ranked.

Full eTMF feature comparison

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 featureFlorence eTMFMedidata eTMF
TMF Reference Model and inspection readiness
Feature 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.
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.

Source
About this support label

Missing/expired-document and milestone dashboards establish tracking; model alignment and inspector access are not described.

Supported

Medidata states full support for the DIA TMF Reference Model and dashboards for quality, timeliness and completeness; inspector access is not described.

Source
About this support label

The Reference Model and completeness dashboards are stated; inspector access is not described.

Document capture and AI automation
Feature definitions
Supported
Automated document capture, filing or processing is documented.
Extended support
AI classifies or indexes documents and extracts metadata or attribute values.
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.

Source
About this support label

Email capture and AI filing recommendations are stated; metadata extraction is not described.

Supported

The page describes auto-filing, intelligent placeholders and auto-naming, but no AI classification.

Source
About this support label

Auto-filing and placeholders establish base support; AI classification is not described.

CRO and site collaboration
Feature definitions
Supported
Document sharing or collaboration for CROs or sites is documented.
Extended support
A site eISF connection exchanges or files documents directly into the eTMF.
Extended support

Sponsors connect with each site's Florence eISF through SiteLink to collect, route and query site documents inside the eTMF.

Source
About this support label

SiteLink connects each site's eISF to collect and route documents inside the eTMF.

Supported

Medidata describes role-based collaboration across sponsors, CROs and sites with a site-focused experience, but no eISF connection.

Source
About this support label

Role-based sponsor/CRO/site collaboration is stated; an eISF connection is not described.

Integrations and platform
Feature definitions
Supported
Integration or data exchange with another system or application is described.
Extended support
Integration with a clinical-trial application plus an API for integration are both stated.
Extended support

Florence says its eTMF has an open API and can stand alone or connect to an existing eTMF; it has no CTMS of its own.

Source
About this support label

An open eTMF API and connections to an existing eTMF are stated.

Supported

eTMF is unified with Rave and Medidata CTMS, and CTMS monitoring visit reports file into the TMF automatically; no eTMF API is described.

Source
About this support label

Unified Rave/CTMS and automatic report filing establish base support; an eTMF API is not described.

Compliance and validation evidence
Feature 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.
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.

Source
About this support label

Part 11 records and signatures are stated; the SOC report is under NDA.

Supported

Medidata lists an ISO 27001:2022 certificate and a SOC 2+ Type II audit, and says its position statements cover 21 CFR Part 11 and EU Annex 11.

Source
About this support label

A certificate, audit and trial statements are listed; public certificate or report access is not established.

Adoption and track record
Feature definitions
Supported
Published product or wider-platform adoption, or a named clinical-research deployment.
Extended support
Product-specific study, customer, institution, site or participant figures plus a published country count establish international use.
Supported

Florence reports 88,000+ research sites and 600+ life science organizations on its platform; no eTMF-only count is published.

Source
About this support label

The site and organization adoption figures cover the wider platform.

Supported

Medidata reports 2,300 organizations across its whole platform; no eTMF-specific count is published.

Source
About this support label

The organization figure covers the whole platform rather than eTMF alone.

The guide update date reflects guide edits. Vendor statements are attributed in the evidence.

Keep the category in view

Compare these products with the other tools in the eTMF guide using the same feature definitions.

More eTMF comparisons featuring one of these products.