Pharmaceutical Research Protocol (Vulcan UDP), published by HL7 International / Biomedical Research and Regulation. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/vulcan-udp-ig/ and changes regularly. See the Directory of published versions
05 Protocol Preparation
Protocol Preparation
To fully leverage this guidance, protocols natively aligned to ICH M11 in a digital format are ideal. There are also valuable use cases where transformation of a legacy protocol is required, such as pooling historical protocols to enable analytics.
ICH M11 aligned protocols can be created in several ways:
- Creating an ICH M11 aligned protocol that is
- Document based – via implementation of the TransCelerate CPT (see below)
- Document based - utilizing the ICH M11 Protocol Template draft
- Digital - via implementation of USDM
- Converting/reformatting existing historical protocols.
If You Are Starting With The TransCellerate CPT:
During preparation for earlier UDP connectathons it was noted that a significant number of sponsors had implemented the TransCelerate Common Protocol Template (CPT). The most recent versions of the CPT have reflected ongoing alignment with ICH M11 drafts. To support end-users, there is a mapping tool highlighting which CPT sections and content are aligned with the ICH M11 draft template. This mapping is based on the March 2025 published draft of the ICH M11 Template.
Where the Data Type entry is “Valid Value”, the corresponding Value entry in the specification table will indicate the list of acceptable values. (See example below)
Figure 1: Specification table
Detailed steps – by approach:
New Draft Protocol Approach:
- Open ICH M11 Template with CPT Mappings (Section Headings ONLY) and save an instance of it with your protocol identifier.
- Review the M11 authoring conventions within the red instructional text to understand which text is universal, universal conditional, or optional throughout the template; where headings can be deleted or added, etc.
- Begin to complete/draft content per the M11 red instructional text describing the intended section content. Draft new content and incorporate existing content elements from your base company or CPT templates based on the section mappings.
- Where the template indicates specific values are expected, utilize the ICH M11 Technical Specification_Updated Step 2_2025 reference document.
- Finally, per template guidance, remove all instructional text and mapping comments, update formatting inconsistencies and update Table of Contents
Historical Protocol Approach:
- May or may not begin with a CPT-based protocol
- Recommend using .docx files (vs PDF) to make cutting/pasting content easier
- Guidance provided may be used in any way to support identifying & transferring content from the existing protocol into the ICH M11 template
Steps:
- Open ICH M11 Template with CPT Mappings (Section Headings ONLY) and save an instance of it with your protocol identifier.
- SourceReview the M11 authoring conventions within the red instructional text to understand which text is universal, universal conditional, or optional throughout the template; where headings can be deleted or added, etc.
- Begin to copy and paste content from the source protocol into the appropriate sections of the M11 template
- Use CPT section mapping comments in the M11 template or alternatively the M11 red instructional text describing the intended section content to aid in this process
- We suggest highlighting text and headings in the source protocol once it has been copied into the M11 Template to help account for all the content.
- Where the template indicates specific values are expected, utilize the ICH M11 Technical Specification_Updated Step 2_2025 reference document.
- You will no doubt be faced with making judgement calls on where certain content elements align with the ICH M11 template.
- Finally per template guidance, remove all instructional text and mapping comments, update formatting inconsistencies and update Table of Contents
NOTE: Although not a long-term solution, document-based ICH M11 protocols may be transformed into FHIR using AI/ML (artificial intelligence/machine learning) and LLM (large language models). Long-term strategy involves digitally native, ICH M11-aligned protocols primed for exchange in FHIR.