PhUSE: Pooling WHODrug B3 Format

Slides:



Advertisements
Similar presentations
Principal Statistical Programmer Accovion GmbH, Marburg, Germany
Advertisements

SDTM Implementation Guide Version 3.1.2
What’s New with CDISC Wayne R. Kubick CDISC CTO.
The Importance of CDASH
SEND Standard for the Exchange of Nonclinical Data
Kendle Implementation of Clinical Data Acquisition Standards Harmonization Dr Elke Sennewald Kendle 9th German CDISC User Group Meeting Berlin, 28 September.
An Introduction to Clinical Data Acquisition Standards Harmonization (CDASH) Loryn Thorburn © 2010 PAREXEL International | Confidential.
© 2008 Octagon Research Solutions, Inc. All Rights Reserved. 1 PhUSE 2010 Berlin * Accessing the metadata from the define.xml using XSLT transformations.
Requirements for Standardized Study Data: Update on Guidance Ron Fitzmartin, PhD, MBA Data Standards Program Office of Strategic Programs Center for Drug.
Bay Area CDISC Implmentation Network – July 13, 2009 How a New CDISC Domain is Made Carey Smoak Team Leader CDISC SDTM Device Team.
Monika Kawohl Statistical Programming Accovion GmbH Tutorial: define.xml.
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.
Beyond regulatory submission - Standards Metadata Management Kevin Lee CDISC NJ Meeting at 06/17/2015 We help our Clients deliver better outcomes, so.
23 August 2015Michael Knoessl1 PhUSE 2008 Manchester / Michael Knoessl Implementing CDISC at Boehringer Ingelheim.
Dominic, age 8, living with epilepsy SDTM Implementation Guide : Clear as Mud Strategies for Developing Consistent Company Standards PhUSE 2011 – CD02.
CBER CDISC Test Submission Dieter Boß CSL Behring, Marburg 20-Mar-2012.
© 2011 Octagon Research Solutions, Inc. All Rights Reserved. The contents of this document are confidential and proprietary to Octagon Research Solutions,
PhUSE SDE, 28-May A SAS based Solution for define.xml Monika Kawohl Statistical Programming Accovion.
How to process data from clinical trials and their open label extensions PhUSE, Berlin, October 2010 Thomas Grupe and Stephanie Bartsch, Clinical Data.
Contents Integrating clinical trial data Working with CROs
1CDISC 2002 RCRIM – Standard Domains Agenda NCI Presentation Standard Domains Working Group Goals Introduction to FDA Information Model (FIM) Discussion:
Confidential - Property of Navitas Accelerate define.xml using defineReady - Saravanan June 17, 2015.
ICH V1 An FDA Update Min Chen, M.S., RPh Office of Drug Safety Center for Drug Evaluation and Research FDA January 21, 2003.
MODULE B: Case Report Forms Jane Fendl & Denise Thwing April 7, Version: Final 07-Apr-2010.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
15th Informal US MedDRA User Group Meeting, October 28, 2011 Slide 1 Double the Impact with Half the Work: Linking MedDRA and WHO Drug Indication coding.
SDTM Validation Delaware Valley CDISC user network Ketan Durve Johnson and Johnson Pharmaceutical Reasearch and Development May 11 th 2009.
Alun, living with Parkinson’s disease QS Domain: Challenges and Pitfalls Knut Müller UCB Biosciences Conference 2011 October 9th - 12th, Brighton UK.
Dave Iberson-Hurst CDISC VP Technical Strategy
Research based, people driven CDISC ADaM Datasets - from SDTM to submission CDISC Experience Exchange and ADaM Workshop 15 Dec 2008 Zoë Williams, LEO Pharma.
Optimizing Data Standards Working Group Meeting Summary
How Good is Your SDTM Data? Perspectives from JumpStart Mary Doi, M.D., M.S. Office of Computational Science Office of Translational Sciences Center for.
© 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.
Submission Standards: The Big Picture Gary G. Walker Associate Director, Programming Standards, Global Data Solutions, Global Data Management.
Design of Case Report Forms
Principal Investigator ESTCP Selection Meeting
Introduction Review and proper registration of Human Gene Transfer protocols is very complex. A protocol goes through rigorous review by multiple Committees.
Dave Iberson-Hurst CDISC VP Technical Strategy
Observational Study Working Group
The Information Professional’s Role in Product Safety
FDA’s IDE Decisions and Communications
Principal Investigator ESTCP Selection Meeting
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Secondary Uses Primary Use EHR and other Auhortities Clinical Trial
Beyond regulatory submission - Standards Metadata Management Kevin Lee CDISC NJ Meeting at 06/17/2015 We help our Clients deliver better outcomes, so.
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.
Maintaining the Clinical & Nonclinical Study Data Reviewer’s Guides
Standard Analyses and Code Sharing Summary for the Best Practices for Data Collection Instructions Project Team Mary Nilsson 20 March 2017.
Traceability between SDTM and ADaM converted analysis datasets
In-Depth Report from Optimizing Data Standards Working Group
3rd Year Psychology Project PSY600
Patterns emerging from chaos
SDTM and ADaM Implementation FAQ
Fabienne NOEL CDISC – 2013, December 18th
PhUSE Computational Science Working Groups
Approaches to Implementing in Your Organization
Carolina Mendoza-Puccini, MD
Visualizing Subject Level Data in Clinical Trial Data
Overview of the Standard Analyses & Code Sharing Working Group
SDTM and ADaM Implementation FAQ
WG4: Standards Implementation Issues with CDISC Data Models
Best Practices for Data Collection Instructions
Development of Standard Scripts for Analysis and Programming
An FDA Statistician’s Perspective on Standardized Data Sets
Safety Analytics Workshop – Computational Science Symposium 2019
Crowd-Sourcing an Interactive Safety Review Package
Radiopharmaceutical Production
GL 51 – Statistical evaluation of stability data
Optimzing the Use of Data Standards Calling for Volunteers
Presentation transcript:

PhUSE: Pooling WHODrug B3 Format Marlo Searcy, RPh September, 2017

Agenda Project Overview Working Group Introductions Timelines & Meeting Structure Review of B2 vs. B3 Key Differences Start discussing/identifying options for pooling strategy

Project Overview In a March 2015 Federal Register Notice, the FDA encouraged sponsors to provide WHODrug Dictionary codes for concomitant medication data in investigational studies provided in regulatory submissions. The request indicated that codes should include the drug product trade name (where available), the active ingredient(s) and the Anatomical Therapeutic Chemical (ATC) Class. As indicated in the May 2015 Data Standards Catalog, the expectation for it's requirement begins March 2018. Additional information was provided in the October 2015 Study Data Technical Conformance Guide. Other regulatory agencies have communicated similar notices. In order to facilitate the population of active ingredients, the Uppsala Monitoring Centre, who maintains the WHODrug Dictionary, updated the dictionary (B3 and C3 formats) to improve the structure for multi-ingredient drugs. While this change will greatly improve the efficiency of reviewing, analysing and reporting medication data, it introduces several challenges when creating an integrated database.

Project Deliverables This project team will create a white paper outlining best practices for creating an integrated database with medication data collected in different formats (B3 format and whatever format was applied previously).

WG Introductions Introduce yourself … Does your organization plan to implement WHODrug B3? If so, when? What systems do you currently use to code medication data? What clinical data sources are coded at your organization (EDC systems, Drug Safety systems, other)? What do you see as the biggest challenge to B3 implementation and pooled submission?

Standard Medication Table Display PhUSE Standard Scripts Analysis Whitepapers WG is developing recommendation for standard WHODrug medication table display Leading proposal is an individual ingredient-based display (ATC not included) Preferable to have recommendation for standard table prior to tackling pooled table

Proposed Standard Medication Table

WG Timelines and Meeting Structure Meeting schedule: 3rd Wednesday of the month? Other housekeeping? December meeting? Project Timelines: Draft White Paper December 2017? Final White Paper March 2018?

PhUSE Resources Pooling WHODrug B3 Format Wiki Page: http://www.phusewiki.org/wiki/index.php?title=Pooling_WHODrug_B3_Format

B2 vs. B3 Format – Key Differences Field Length: B2 generic names truncated at 45 CHAR, C truncated at 80 CHAR B3 generic names increased to 1500 CHAR, ATC to 110 CHAR Combination products: B2/C preferred generic name is the first entered trade name of their respective ingredients B3/C3 preferred generic name represent the substance or substance combination (separated by semi-colon, not w/).

B3 Combination Product

B2 vs. B3 Format – Key Differences Cont. Salt/Base relationships: B2/C salt variations of a combination product are located on separate Drug Record Numbers. B3/C3 salt variations of a substance (including combination products) are connected to the Preferred Base Name. Non-unique names: Non-unique names are made unique in the B2-format by the addition of /DRECNOSEQ1/ after the trade name. Non-unique names are made unique in the B3-format by the addition of [INGREDIENTS] after the trade name.

B3 Non-Unique Names

FDA Guidance Federal Register Data Standards Catalog “Although use of WHO Drug Dictionary codes are not required at this time, FDA now supports and encourages the use of WHO Drug Dictionary coded concomitant medications used in clinical trials.” “The codes should include the drug product trade name where available, the active ingredient(s) and the ATC class.” Data Standards Catalog Study Data Technical Conformance Guide Typically, WHO Drug is used to code concomitant medications. --DECOD should be populated with the generic name from the WHO dictionary, and --CLAS populated with the drug class, if the utilized dictionary codes drugs to a single class. When using WHODRUG, generally, --CLAS would not be filled because a drug may have multiple classes. However, one Anatomic Therapeutic Code (ATC) level 4 code could be mapped to --CLAS and the remainder of the ATC codes could be placed in SUPPCM.

SDTM Regulatory Submission & WHODrug

CDISC SDTM Implementation Guide (Version 3.2) For concomitant medications, populate CMDECOD with the drug's generic name and populate CMCLAS with the drug class used for the sponsor’s analysis and summary tables. If coding to multiple classes, follow Section 4.1.2.8.1, Multiple Values for an Intervention or Event Topic Variable or omit CMCLAS. For concomitant medications, supplemental qualifiers (see Section 8: 8.4, Relating Non-Standard Variables Values to a Parent Domain and Appendix C2 - Supplemental Qualifier Name Codes for more information) may be used to represent additional coding dictionary information, e.g. a drug’s ATC codes from the WHO Drug dictionary. However, by knowing the dictionary and version used, the reviewer will be able to obtain additional coding dictionary information. Note: The sponsor is expected to provide the dictionary name and version used to map the terms by utilizing the define.xml external codelist attributes.

CDISC SDTM Implementation Guide (Version 3.2) cont. 4.1.2.8.1 Multiple Values for an Intervention or Event Topic Variable If multiple values are reported for a topic variable (i.e., --TRT in an Interventions general-observation-class dataset or --TERM in an Events general-observation-class dataset), it is assumed that the sponsor will split the values into multiple records or otherwise resolve the multiplicity as per the sponsor’s standard data management procedures. For example, if an adverse event term of “Headache and Nausea” or a concomitant medication of “Tylenol and Benadryl” is reported, sponsors will often split the original report into separate records and/or query the site for clarification. By the time of submission, the datasets should be in conformance with the record structures described in the SDTMIG. Note that the Disposition dataset (DS) is an exception to the general rule of splitting multiple topic values into separate records. For DS, one record for each disposition or protocol milestone is permitted according to the domain structure. For cases of multiple reasons for discontinuation see Section 6.2 - DS Domain: Assumption 5, DS - Assumptions for DISPOSITION Domain Model for additional information.

Class submission requirements There are currently 3 options for submitting WHODrug ATC Class information based on the SDTM Implementation Guide v3.2: One single class selected Multiple Classes No Classification

UMC SDTM CMDECOD CMDECOD may be up to 1500 CHAR Supplemental dataset should be utilized when CMDECOD is longer than 200 CHAR Text should be truncated between words, after the semicolon closest to 200 CHAR

UMC CMCLAS Example

Pooling Option 1 Medication data for studies coded in B2 (or other proprietary dictionary) and studies coded in B3 are summarized separately. This approach may be acceptable when no specific medication analysis is done for the study, and standard concomitant medication table is simply appended to the submission. Approach would require approval by FDA reviewer.

Pooling Option 2 Aggregate medication table contains mixed data summarized by Generic text from both B2 (or other proprietary dictionary) and B3. This approach may be acceptable when no specific medication analysis is done for the study, and the standard concomitant medication table is simply appended to the submission. Same combination product may be listed twice (e.g. B2 trade and B3 ingredients) Approach would require approval by FDA reviewer.

Pooling Option 3 Studies coded in B2 (or other proprietary dictionary) are recoded in WHODrug B3 from Generic level up (creation of a filing-specific B2/Other-B3 Generic Bridge). This approach would be reserved for submissions where specific medication analyses are included or where B3 is required by the FDA reviewer.

Pooling Option 4 For studies coded in B2, B2 drug codes are submitted to the UMC CAT (Change Analysis Tool). UMC CAT suggestions are used to up-version the B2 data to B3. UMC suggestions for deleted terms may require review and modification. This approach would be reserved for submissions where specific medication analyses are included or where B3 is required by the FDA reviewer.

Pooling Option 5 Studies coded in B2 (or other proprietary dictionary) are recoded in WHODrug B3 from verbatim medication term. This approach requires significant resources and would be reserved for submissions where specific medication analyses are included or where B3 is required by the FDA reviewer.

Other Pooling Options?

Doing now what patients need next Questions? Doing now what patients need next

Backup Slides

CDASH User Guide

ADaM CDISC ADaM Occurrence Data Structure (OCCDS) (Version 1.0)

ADaM CDISC ADaM Occurrence Data Structure (OCCDS) (Version 1.0)

ADaM Table

ATC Codes ATC = Anatomical Therapeutic Chemical classification Official hierarchical classification system maintained by the WHO Collaborating Centre for Drug Statistics Methodology in Oslo, Norway. Unofficial classifications added to WHODrug by the UMC. Allows for grouping of active substances based on the organ or system on which they act, and/or their therapeutic, pharmacological and chemical properties (Drug Class). Each preferred drug name can be associated with one or multiple ATC codes (WHODrug does not have the concept of ‘primary path’)

ATC Levels The official ATC hierarchy consists of five levels. The first level in the ATC system is represented by 14 anatomical main groups. The second level further classifies active substances according to pharmacological/therapeutic properties (therapeutic main group). The third and the fourth ATC levels are chemical/pharmacological/therapeutic subgroups. The fifth levels represent active substances, and is not included in WHODrug (equivalent to Drecno Concept)

ATC Level 1

ATC Hierarchy Example Official ATC Classification for Morphine (5th level not included in WHODrug)

ATC Considerations ATC codes are not always complete to the 4th level. There are a significant number of Preferred Names that have only the ATC3 level, some with only the ATC2 level assigned and a few with only the ATC1 level. WHODrug does not specify a primary ATC code for each generic preferred name. Some sponsor companies select a single ATC code for each record based on indication or dosage form information. Many companies do not. In the current version of B3, drugs can have up to 26 ATC classes assigned. ATC Code text field 110 CHAR in B3

UMC US User Group Poll October 2016

UMC US User Group Poll October 2016

Ibuprofen example