/
November 2018 How  was the Common Protocol Template  Developed and What Does it Look Like? November 2018 How  was the Common Protocol Template  Developed and What Does it Look Like?

November 2018 How was the Common Protocol Template Developed and What Does it Look Like? - PowerPoint Presentation

myesha-ticknor
myesha-ticknor . @myesha-ticknor
Follow
344 views
Uploaded On 2019-11-01

November 2018 How was the Common Protocol Template Developed and What Does it Look Like? - PPT Presentation

November 2018 How was the Common Protocol Template Developed and What Does it Look Like How was the Common Protocol Template CPT First Developed Structure and Content Structure Level 1 and 2 Headings ID: 761903

template protocol cpt common protocol template common cpt text edition word content information basic study structure developed core click

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "November 2018 How was the Common Protoc..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

November 2018 How was the Common Protocol Template Developed and What Does it Look Like?

How was the Common Protocol Template (CPT) First Developed? Structure and Content Structure – Level 1 and 2 Headings Main focus - Streamlined structure for logical flow Review of structure (Table of Contents) of anonymized member company templatesInput from SCRS (Society for Clinical Research Sites) Site Advocacy Group Section ContentIdentification of common wording in Core BackboneReview of GCP, ICH, and EU requirements Review of content from member company templates

eProtocol Advisory Committee “…to inform the development of a common human readable and electronic protocol template and provide a forum for key stakeholders to inform future direction and provide know-how (Committee Charter)” “EMA has not agreed to take up a position on the Advisory Committee…..Happy to provide comments on any draft templates…” Other Advisors or Influencers FDA 18-Mar-2016: “Today we’re announcing a draft clinical trial protocol template developed by the Food and Drug Administration (FDA) and National Institutes of Health (NIH) that should help with that. …..We are aware of other efforts in this area, including one undertaken by TransCelerate Biopharma Inc. ( TransCelerate ), which has issued a common protocol template intended to be the basis for a forthcoming electronic protocol. Although our initial target audiences differ, we plan to collaborate with groups like TransCelerate to help ensure consistency for the medical product development community.” How was the CPT Developed? Initial Advisory Committee Engagement

Focus on sites (investigators/study staff) to have access to protocol information. CPT Structure and Content will provide value to Investigators, site staff, IRBs, regulators The same information is located in the same place and means the same thing across Sponsors Locked text (Level 1 and 2 Headings) is not to be modified or removed. “Not Applicable” is inserted if a section is not applicable. Specific information to evaluate the ability to conduct a protocol, e.g. does the site have the patient population. Refer to primary sources of information (e.g. Investigator Brochure) instead of duplicating information in the protocol.Model sections and text located in Appendices to be accessible, but will not impact the flow of the core protocol-specific informationHow was the CPT Developed? Final Template

What Does the CPT Look Like? Participant Libraries Core Protocol Backbone Common Level 1 & 2 Headings Common text Used across all phases Focus on sites (investigators/study staff) Healthy Volunteer Patient Therapeutic Area Libraries (various) Appendices Non-study specific info, items triggered by event Implementation Toolkit Materials Core streamlined , focused on site needs Appendices to apply as applicable Libraries group and store point and click content used to populate the template Endpoint Definitions modeled for TAs/indications A sustainable Governance Model is in development Common Protocol Template and Guidance Governance Model Common Text can be used “as is”- relevant across study types Pediatric

Basic Word Edition A document based template for use across phases and study types Use as-is or modify current format template to reflect CPT content Initial Public Release: December 2015Technology Enabled EditionAn MSWord-based template with add-insAutomation to leverage “point and click” protocol text Capture of protocol-level metadata to facilitate content reuse and extractionInitial Public Release: June 2016For Microsoft Windows-based usage, not compatible with Apple iOS. What Does the CPT Look Like? CPT Editions

What does the CPT Look Like? Basic Word Edition Word documents; No installation needed. Locate the Basic Word Edition files on the TransCelerate CPT WebsiteUnder” Common Protocol Template Tools and Resources,” click on the blue bar “Basic Word Edition Template and Guidelines” to reveal all of the available resources. To download the CPT BWE, click on “Basic Word Edition Core Template.” Participant and Therapeutic Area Libraries are also available. To download any of the files, click on the file and “Save As” to add the files to your desktop or local drive.Start authoring your protocol.

What does the CPT Look Like? Basic Word Edition 8 Instructional text provided as red hidden text available by toggling paragraph marks “Start” and “stop” of common text is indicated in green font “Start” and “stop” of common text is indicated in green font

What Does the CPT Look Like? Tech-Enabled Edition It still looks like paper….but its not!9The Technology Enabled Edition of the Common Protocol Template (CPT) avoids media breaks by capturing structured and unstructured information in variables available for export and reuse downstream. Common layout of contentLibraries make model content availableInformation is captured in variables Export variables to XML or Excel for reuse in other processes

Thank you