Difference between revisions of "Best Practices for Data Collection Instructions"

From PhUSE Wiki
Jump to: navigation, search
m (Project Members)
m (Project Updates)
 
(7 intermediate revisions by the same user not shown)
Line 14: Line 14:
 
| Name  || Role || Organization || E-mail
 
| Name  || Role || Organization || E-mail
 
|-
 
|-
| Todd Bazin|| Project Leader ||Biogen|| [mailto:todd.bazin@biogen.com todd.bazin (at) biogen.com]
+
| Aimee Basile || Project Lead || Alkermes || Aimee.Basile@alkermes.com
 +
|-
 +
| Todd Bazin|| Co-Lead ||Biogen|| [mailto:todd.bazin@biogen.com todd.bazin (at) biogen.com]
 
|-
 
|-
 
|}
 
|}
Line 51: Line 53:
 
|-
 
|-
 
| Tina Lambert || Astellas || [mailto:Tina.Lambert@astellas.com Tina.Lambert (at) astellas.com]
 
| Tina Lambert || Astellas || [mailto:Tina.Lambert@astellas.com Tina.Lambert (at) astellas.com]
 +
|-
 +
| Nancy Brucken || Syneoshealth || [mailto:nancy.brucken@syneoshealth.com Nancy Brucken (at) syneoshealth.com]
 +
|-
 +
| Kim Musgrave || Amgen ||[mailto:kmusgrav@amgen.com Kim Musgrave (at) amgen.com]
 +
|-
 +
| Melvin Munsaka || AbbVie || [mailto:Melvin.Munsaka@abbvie.com Melvin Munsaka (at) abbvie.com]
 +
|-
 +
| Trisha Simpson || UCB || [mailto:trisha.simpson@ucb.com Trisha Simpson (at) ucb.com]
 +
|-
 +
| Mary Nilsson || Lilly ||[mailto:nilsson_mary_e@lilly.com Mary Nilsson (at) lilly.com]
 
|}
 
|}
  
Line 57: Line 69:
 
=== Project Updates ===
 
=== Project Updates ===
 
    
 
    
 +
'''July 2019'''<br>
 +
<br>
 +
Under the new leadership of Aimee, the PhUSE Best Practices for Data Collection Instructions Working Group was started in 2017 with the objective to develop detailed collection recommendations that would supplement existing CDASH completion instructions, as well as leverage the recommendations and code developed by the PhUSE Standard Analysis and Code Sharing Working Group.  While there are several domains that will benefit from comprehensive data collection guidance, the Best Practices for Data Collection Working Group has linked with the Standard Analysis and Code Sharing Working Group to tackle the adverse events domain in order to support their deliverable for standard treatment-emergent adverse event displays.  Based on this collaboration, we have a renewed resolve to complete our work, specifically around the collection of adverse events.  We are asking for volunteers to provide support for identifying the myriad ways adverse event data are collected (using surveys and interviews), and subsequently formulating a recommendation that supports both efficient data collection and the needs for analysis and displays.<br>
 +
<br>
 +
If you are interested in joining this project contact [mailto:workinggroups@phuse.eu working groups (at) phuse.eu]<br>
 +
<br>
 
'''November 2018'''<br>
 
'''November 2018'''<br>
 
<br>
 
<br>
Line 69: Line 87:
 
| Objective || Timeline
 
| Objective || Timeline
 
|-
 
|-
|Draft White Paper on what data is collected in Adverse Events?, what collection instructions are define related to AE data for Investigational site Personnel, How is the Treatment Emergence defined and calculated||Q22019
+
|Draft White Paper on what data is collected in Adverse Events?, what collection instructions are define related to AE data for Investigational site Personnel, How is the Treatment Emergence defined and calculated||TBD
 
|-
 
|-
|Final White Paper presented at CSS ||June 2019
+
|Final White Paper presented at CSS ||TBD
 
|}
 
|}
 
<br>
 
<br>

Latest revision as of 04:01, 12 July 2019

Project Overview

CDISC’s CDASH team provides high level completion instructions related to the core data collection modules. The PhUSE Standard Analysis and Code Sharing Working Group has developed recommended displays (ie, tables and figures) and associated code for use for analysis for data common across therapeutic areas. For some data domains (e.g., adverse events, medical history, concomitant medications, study disposition, pregnancy, reasons for permanent discontinuations from study treatment), having more consistent collection instructions at a more detailed level will potentially lead to increased efficiency (site personnel won't have to learn as many collection methods) and fewer queries (less confusion by site personnel), and will enable sponsors to fully leverage the recommendations and code from the PhUSE Standard Analyses and Code Sharing Working Group. Collection and associated instructions may vary depending on whether the study is early vs late stage, as discussed in the February 2016 FDA guidance ('Determining the extent of safety data collection needed in late stage pre-market and post-approval clinical investigations'). However, reducing the extent of variation would be beneficial for medical research.

This project team will network with CDISC and the Standard Analyses and Code Sharing Working Group to ensure alignment.

Project Deliverables

The initial scope of the project is to create a white paper documenting challenges and gaps with the CDASH CRF completion as well as recommendations for a future version of CDASH. The white paper will be provided to CDISC for their consideration. The project team will focus on the following domains: Adverse Events, Medical History, Concomitant Medications, Pregnancy, and Reasons for Treatment and Study Discontinuation. The team will assess the opportunity to address other domains after the white paper is completed.

Project Leadership Team

Name Role Organization E-mail
Aimee Basile Project Lead Alkermes Aimee.Basile@alkermes.com
Todd Bazin Co-Lead Biogen todd.bazin (at) biogen.com

Project Members

Name Organization E-mail
Alec Vardy Jazz Pharma alec.vardy (at) jazzpharma.com
Aparna Kulkarni Novartis aparnakulkarni616 (at) gmail.com
Cathy Bezek Astellas Cathy.Bezek (at) astellas.com
Charity Quick RHO World Charity_Quick (at) rhoworld.com
Elizabeth Langevin Takeda Elizabeth.Langevin (at) Takeda.com
Farhan (CJ) Hameed Pfizer Farhan.Hameed (at) pfizer.com
Jeannine Hughes Boehringer-Ingelheim Jeannine.Hughes (at) boehringer-ingelheim.com
Jennifer Showalter Lilly jshowalter (at) lilly.com
Kit Howard CDISC khoward (at) cdisc.com
Lisa Houterloot PRA Health Sciences HouterlootLisa (at) prahs.com
Russ Newhouse Lilly newhouse_russell_d (at) lilly.com
Shannon Labout CDISC slabout (at) cdisc.org
Sharon Weller Lilly weller_sharon_m (at) lilly.com
Tina Lambert Astellas Tina.Lambert (at) astellas.com
Nancy Brucken Syneoshealth Nancy Brucken (at) syneoshealth.com
Kim Musgrave Amgen Kim Musgrave (at) amgen.com
Melvin Munsaka AbbVie Melvin Munsaka (at) abbvie.com
Trisha Simpson UCB Trisha Simpson (at) ucb.com
Mary Nilsson Lilly Mary Nilsson (at) lilly.com


Project Updates

July 2019

Under the new leadership of Aimee, the PhUSE Best Practices for Data Collection Instructions Working Group was started in 2017 with the objective to develop detailed collection recommendations that would supplement existing CDASH completion instructions, as well as leverage the recommendations and code developed by the PhUSE Standard Analysis and Code Sharing Working Group. While there are several domains that will benefit from comprehensive data collection guidance, the Best Practices for Data Collection Working Group has linked with the Standard Analysis and Code Sharing Working Group to tackle the adverse events domain in order to support their deliverable for standard treatment-emergent adverse event displays. Based on this collaboration, we have a renewed resolve to complete our work, specifically around the collection of adverse events. We are asking for volunteers to provide support for identifying the myriad ways adverse event data are collected (using surveys and interviews), and subsequently formulating a recommendation that supports both efficient data collection and the needs for analysis and displays.

If you are interested in joining this project contact working groups (at) phuse.eu

November 2018

This Project is working in collaboration with the Standard Analyses & Code Sharing White Papers project.

The scope for this first combined deliverable is to simply report the current variations in AE collection and analysis and why such variation exists.

Objectives and Timelines

Objective Timeline
Draft White Paper on what data is collected in Adverse Events?, what collection instructions are define related to AE data for Investigational site Personnel, How is the Treatment Emergence defined and calculated TBD
Final White Paper presented at CSS TBD


Project Content and Activities


Meeting Minutes