How was CPT Developed and What Does it Look Like?

Slides:



Advertisements
Similar presentations
Participation Requirements for a Guideline Panel Co-Chair.
Advertisements

Policy Advisory Group (PAG) & Technical Advisory Committee (TAC) Leader Primer Presented by: Devin A. Jopp, Ed.D. President & CEO.
Recently Issued OHRP Documents: Guidance on Subject Withdrawal and Draft Revised FWA Secretary’s Advisory Committee on Human Research Protections October.
Tipologie di Audit e loro caratteristiche Riunione sottogruppo GCP-GIQAR 21 Marzo 2006 Francesca Bucchi.
RPS WG Update March 2015 Open Stakeholder Session Nancy Shadeed Health Canada.
Justina A. Molzon, MS Pharm, JD
MODULE B: Case Report Forms Jane Fendl & Denise Thwing April 7, Version: Final 07-Apr-2010.
© CDISC 2011 Joint Initiative Council 18 October 2011 Bron Kisler, VP, Strategic Initiatives, Current JIC Leader Rebecca D. Kush, PhD, President and CEO,
0 eCPIC User Training: Resource Library These training materials are owned by the Federal Government. They can be used or modified only by FESCOM member.
Bridging the Gap PREPARING SPORTS THERAPY STUDENTS FOR THE HEALTH CARE PROFESSION THROUGH REFLECTIVE PRACTICE BY DOMINIC GORE SENIOR E-LEARNING OFFICER.
Objectives and Guiding Principles for the Implementation Leader
Government-wide Performance Data Standards Discussion Document Performance and Personnel Management Dr. Jim Rolfes Program Director, Federal Performance.
Introducing the Common Protocol Template Copyright ©2015 TransCelerate BioPharma Inc., All rights reserved. 2 TransCelerate and the Common Protocol Template.
Accurate  Consistent  Compliant Contact: i4i the structured content company the structured content company.
November th FERCAP International Conference Nagasaki, Japan TransCelerate Overview.
© Copyright IBM 2007DIA ERS SIAC Presentation, January 2008 The HL7 RPS and SPL Standards - A High Level View Terry Hardin Sr. IT Architect Emerging Software.
DIA Trial Master File Reference Model
Copyright ©2015 TransCelerate BioPharma Inc., All rights reserved. 1 ​ The Implementation Toolkit is: – High level roadmap of activities designed to support.
​ Executive Summary Common Protocol Template (CPT)
PARTNERSHIP COMMUNICATIONS STRATEGY
Design of Case Report Forms
Paul Houston CDISC Europe Foundation Head of European Operations
Dave Iberson-Hurst CDISC VP Technical Strategy
Common Protocol Template (CPT)
One Approach to Bundled Payments
BAPI Communities.
Global Grid Forum GridForge
FUTURE EVOLUTION OF SHORT-TERM ECONOMIC STATISTICS
Remote Monitoring of Adverse Events
Accenture Accelerated R&D Standards Metadata Management – version control and its governance Kevin Lee CDISC NJ Meeting at 01/28/2015 We help our Clients.
Summary of Changes in CPT December 2017 Release
Why CPT? December 2017.
CPT Implementation Toolkit Executive Summary
CPT and Disclosure: Connecting Critical Processes
CPT Testimonials and Value Stories
Getting Started with the CPT Basic Word Edition
Objectives and Guiding Principles for the Implementation Leader
IT Considerations for CPT Implementation
Remote Monitoring of Adverse Events
Approaches to Implementing CPT in Your Organization
Introduction to TransCelerate
Common Protocol Template (CPT)
FRAMEWORK FOR BUSINESS ACTION ON WASH
Increased Efficiency and Effectiveness
Getting Started with the CPT Technology-Enabled Edition
BioMedBridges – Work Packages 2 & 12
Common Protocol Template (CPT)
CPT Testimonials and Value Stories
Why a Common Protocol Template?
How was the Common Protocol Template Developed and What Does it Look Like? November 2018.
CPT and Disclosure: Connecting Critical Processes
Implementation Toolkit Executive Summary
History and Evolution of CPT Releases
Getting Started with the Basic Word Editions (BWEs)
Introduction to TransCelerate
IT Considerations for CPT TEE Implementation
Clinical and Translational Science Awards Program
Approaches to Implementing in Your Organization
History and Evolution of CPT Releases
Carolina Mendoza-Puccini, MD
Objectives and Guiding Principles for the Implementation Leader
Objectives and Guiding Principles for the Implementation Leader
How was the Common CSR Template Developed and What Does it Look Like?
Core Competencies of a World Class Customer Advisory Board
EUnetHTA Assembly May 2018.
History and Evolution of CPT Releases
Productivity Loop PowerWriter A systematic approach to world-class
Optimzing the Use of Data Standards Calling for Volunteers
WORK STREAM TEAM DELIVERABLES
Draft Charter Community of Practice for Direct Access Entities
Presentation transcript:

How was CPT Developed and What Does it Look Like? December 2017

How was the CPT 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 templates Input from SCRS (Society for Clinical Research Sites) Site Advocacy Group Section Content Identification of common wording in Core Backbone Review of GCP, ICH, and EU requirements Review of content from member company templates Legally approved 8-Apr-2017 Content development was a logical, thoughtful approach, acknowledging that not one member company protocol was preferred over another, as all meet the GCP and ICH requirements.  The main focus was to streamline the content to allow for consistency across the pharma industry. The structure of the Level 1 and 2 headers are intended to be used/adopted for use without changes.  If a section does not apply, retaining the heading and inserting “NA” or “Not applicable” will allow a consistent protocol structure for multiple sponsors across industry.  The impact will be that the Investigators, study staff and IRBs will be able to locate the same information in the same place and meaning the same thing across multiple protocols. The Level 3 headers and lower level headers can be adjusted as needed . GCP and ICH guidance was reviewed as the initial step for creating common core content.  A comparison of the content in the member companies protocols was completed as part of the development of the common core content. With intended focus on sites (investigators/coordinators), the core includes content to (1) evaluate whether a site has the patients/facilities/time to conduct a protocol, and (2) the specific information needed to conduct the protocol. Other items have been placed in appendices (including governance-related text) where they are accessible but do not impact the flow of the core information. The core content guidance provided with the template also suggests that the reader refer to the primary sources of information (e.g. IB), where possible, rather than bulk repetition in the protocol. This organization in the document has the added advantage of streamlining the protocol overall. This streamlining is expected to allow more efficient use of the protocol. ​ 

How was the CPT Developed? Initial Advisory Committee Engagement 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.” “…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)” eProtocol Advisory Committee Legally approved 8-Apr-2017 TransCelerate sponsored formation of the Electronic Protocol Advisory Committee to inform the initial 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. This Advisory Committee was designed to be similar to, but lighter version of, the Coalition for Accelerating Standards and Therapies (CFAST) structure. Input has been received from some eProtocol Advisory Committee members, and additional input is being requested. The intent is to promote “energy” around the idea of an eProtocol platform, and to drive alignment around end to end traceability, automation, and reuse. Through this Advisory Committee, TransCelerate workstreams will continue to get advice, and access to external “know-how.” The groups across the bottom of this slide are not directly involved in this Advisory Committee, but their outputs have been considered in developing the CPT, and their influence is considered via the other Advisory Committee channels. Tufts was consulted specifically regarding CPT project scope, priorities, and deliverables. The SPIRIT checklist was a key reference and influenced the creation of the text-based structure and content. A consultative meeting was held with the Budapest Working Group, with additional input pending. It is envisioned that additional advisors, such as HL7 and IHE, will be pursued as we move toward development of the machine-readable template “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

How was the CPT Developed? Final Template 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 information Legally approved 8-Apr-2017 Content development was a logical, thoughtful approach, acknowledging that not one member company protocol was preferred over another, as all meet the GCP and ICH requirements.  The main focus was to streamline the content to allow for consistency across the pharma industry. The structure of the Level 1 and 2 headers are intended to be used/adopted for use without changes.  If a section does not apply, retaining the heading and inserting “NA” or “Not applicable” will allow a consistent protocol structure for multiple sponsors across industry.  The impact will be that the Investigators, study staff and IRBs will be able to locate the same information in the same place and meaning the same thing across multiple protocols. The Level 3 headers and lower level headers can be adjusted as needed . GCP and ICH guidance was reviewed as the initial step for creating common core content.  A comparison of the content in the member companies protocols was completed as part of the development of the common core content. With intended focus on sites (investigators/coordinators), the core includes content to (1) evaluate whether a site has the patients/facilities/time to conduct a protocol, and (2) the specific information needed to conduct the protocol. Other items have been placed in appendices (including governance-related text) where they are accessible but do not impact the flow of the core information. The core content guidance provided with the template also suggests that the reader refer to the primary sources of information (e.g. IB), where possible, rather than bulk repetition in the protocol. This organization in the document has the added advantage of streamlining the protocol overall. This streamlining is expected to allow more efficient use of the protocol. ​ 

What Does the CPT Look Like? The Model Libraries group and store point and click content used to populate the template Core streamlined, focused on site needs Core Protocol Backbone Common Level 1 & 2 Headings Common text Used across all phases Focus on investigators Libraries Healthy Volunteer Patient Common Text can be used “as is”- relevant across study types Therapeutic Area Libraries (various) Endpoint Definitions modeled for TAs/indications Legally approved 8-Apr-2017 Backbone contains the protocol information common to all phases, populations, and therapeutic areas. The core is streamlined and focused on the sites’ needs. Libraries group and store content to be inserted into the core backbone and contain specific information related to therapy, country, study population (e.g., patient, healthy volunteer) needs.   Appendices provide additional information that can be accessed when needed (e.g., abbreviations, company specific content). Appendices are omitted if not applicable. Highlight that the template is for all TAs. Additional content available for some specific therapeutic areas. Appendices to apply as applicable Appendices Non-study specific info, items triggered by event A sustainable Governance Model is in development Common Protocol Template and Guidance Governance Model Implementation Toolkit Materials

What Does the CPT Look Like? CPT Editions 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 2015 Technology Enabled Edition An MSWord-based template with add-ins Automation to leverage “point and click” protocol text, Capture of protocol-level metadata to facilitate content reuse and extraction Initial Public Release: June 2016 For Microsoft Windows-based usage, not compatible with Apple iOS. Legally approved 8-Apr-2017

What Does the CPT Look Like? Tech-Enabled Edition CPT Panel Filter: select participant and therapeutic area libraries Folder: navigate to all libraries Instructional Text Box Panel: section-specific guidance Additional Content Box: (D1) Navigate to library text. Click once to preview content (D2); click twice to add to protocol. Add-Ins Add Variables: Reuse content Example Text Tools: Convert example text to protocol text, remove example text About: Link to guides for use & implementation, releases Libraries/Instructions/Content: Pop out instructional text box and Toggle CPT Panel Manage Variables: Add custom variables Data Tools: Export variables and text to XML; import variables E F G H I J A,B C D1 Legally approved 8-Apr-2017 J D2

Thank you