Sponsors and CROs who have traditionally managed their Trial Master Files (TMFs) on paper have seen significant improvements when migrating to an electronic Trial Master File (eTMF) system. However, the exchange of TMF content between sponsors, CROs and other stakeholders has remained challenging as they often use systems provided by different eTMF vendors.
The TMF Reference Model has partially solved this problem. The model is an emerging standard that has provided a common structure for essential TMF documents. However the problem of exchanging TMFs between different vendor systems remains due to the lack of a common exchange standard. The eTMF Exchange Mechanism Team, a sub-group of the TMF Reference Model project has published a draft specification for the transfer of TMF data between different eTMF systems (read Charter HERE).
How does it work?
The published specification includes a specification document, exchange.xml file and a XSD Schema. The source eTMF system would output the artifacts contained within a predefined folder structure with an accompanying exchange.xml file which provides an inventory of the files being transferred. When a system exports an exchange.xml file and related attributes, there should be a validation of the XML file using the exchange.xsd schema provided as part of the standard. When the receiving system imports the exchange.xml file, it will perform the same checks (validation of XML and verification of checksums). Once all checks have passed, the system will import the artifacts and file them against the relevant TMF RM artifact numbers within the system.
What are some potential use cases?
- Final eTMF transfer to sponsor from CRO for archiving
- Interim transfer of eTMF content to central eTMF or other trial management system
- Migration of eTMF content following merger and acquisition
- Migration of eTMF content following upgrade or change of eTMF system
- Long term archiving of eTMF content and associated metadata
What is the path forward?
The eTMF-EMS team have published their draft specification (specification document and Exchange.xml) which is currently being reviewed by participants from all major eTMF vendors, sponsors and CRO’s (click to enlarge). This will be followed by internal vendor testing phase where eTMF vendors will validate if TMF packages can be exported and imported using the proposed specification. The final step is to perform a Proof-of-Concept using a real world migration scenario involving Sponsors, CROs and eTMF Vendors.
Regular news regarding the eTMF Exchange Mechanism Standard can be found on our EMS News page. If you have any queries regarding the Exchange Mechanism Standard, please contact us using the form below.
1Standard: the term is used here in its general sense i.e. “used or accepted as normal or average; viewed as authoritative and so widely read”. Currently, the specification will not be authorized or published by a recognized standards body, though this may be considered at a future time. Following the closure of the OASIS eTMF Technical Committee prior to finalization of an eTMF standard, this is the only eTMF technical standard under development at this time and has the support of all major eTMF vendors.