Difference between revisions of "Industry SEND Progress Survey"

From PHUSE Wiki
Jump to: navigation, search
(Participation Needs)
m
 
Line 3: Line 3:
  
 
This page describes high-level project management details on the group, including purpose, milestones, attendees, and so on.<br />
 
This page describes high-level project management details on the group, including purpose, milestones, attendees, and so on.<br />
We are part of the FDA/PhUSE Computational Sciences Nonclinical Working Group. <br />
+
We are part of the FDA/PHUSE Computational Sciences Nonclinical Working Group. <br />
 
Learn more about the larger working group at [[Non-Clinical Road-map and Impacts on Implementation]].<br />
 
Learn more about the larger working group at [[Non-Clinical Road-map and Impacts on Implementation]].<br />
 
<br />
 
<br />
Line 12: Line 12:
 
===Identified Need/Challenge===
 
===Identified Need/Challenge===
 
   
 
   
An annual survey continues to be informative to multiple stakeholders including PhUSE and CDISC and its members. Questions are asked about the timing of SEND dataset creation, the relationship between the report and the SEND datasets, and the decision to create SEND datasets for every study or to create the datasets only when a study is known to be in the submission.
+
An annual survey continues to be informative to multiple stakeholders including PHUSE and CDISC and its members. Questions are asked about the timing of SEND dataset creation, the relationship between the report and the SEND datasets, and the decision to create SEND datasets for every study or to create the datasets only when a study is known to be in the submission.
  
 
===Vision===
 
===Vision===
Through responses to a survey, a picture of what is being done in the industry can be provided to all companies regardless of size and provide information for decision points.  In addition, the agency can use the survey as a barometer of SEND understanding, process development, and need for additional guidance in general or specific areas. Results are presented at PhUSE CSS and/or PhUSE Connect meetings.
+
Through responses to a survey, a picture of what is being done in the industry can be provided to all companies regardless of size and provide information for decision points.  In addition, the agency can use the survey as a barometer of SEND understanding, process development, and need for additional guidance in general or specific areas. Results are presented at PHUSE CSS and/or PhUSE Connect meetings.
  
 
===Project Scope===
 
===Project Scope===
Create an annual electronic survey sponsored by PhUSE with up to 15 multiple choice questions with an option to provide additional free text information.  Send that survey out to the PhUSE members (and CDISC list groups) requesting a 30 day response time.  Compile the responses and distribute to PhUSE members and make the results available on the PhUSE WIKI.
+
Create an annual electronic survey sponsored by PHUSE with up to 15 multiple choice questions with an option to provide additional free text information.  Send that survey out to the PHUSE members (and CDISC list groups) requesting a 30 day response time.  Compile the responses and distribute to PHUSE members and make the results available on the PHUSE WIKI.
  
 
==Plans==
 
==Plans==
Line 30: Line 30:
  
 
===Tasks===
 
===Tasks===
The project proposal is to create an electronic survey sponsored by the Nonclincal WG of PhUSE CSS collaboration.  The survey would contain up to 15 multiple choice questions with an option to provide additional free text information. Send that survey out to the PhUSE members requesting a 30 day response time. Compile the responses and distribute to PhUSE members and make the results available on the PhUSE WIKI.
+
The project proposal is to create an electronic survey sponsored by the Nonclincal WG of PHUSE CSS collaboration.  The survey would contain up to 15 multiple choice questions with an option to provide additional free text information. Send that survey out to the PHUSE members requesting a 30 day response time. Compile the responses and distribute to PHUSE members and make the results available on the PHUSE WIKI.
 
<br />
 
<br />
 
The areas to be covered by the questions would include but are not limited to:
 
The areas to be covered by the questions would include but are not limited to:
Line 42: Line 42:
 
* Management of controlled terminology – implement every release or select releases
 
* Management of controlled terminology – implement every release or select releases
 
<br />
 
<br />
The project will need a suitable survey tool and a small team to support question development, support the survey, tabulate the results and distribute a report. The results will also be posted on PhUSE wiki.
+
The project will need a suitable survey tool and a small team to support question development, support the survey, tabulate the results and distribute a report. The results will also be posted on PHUSE wiki.
  
 
===Conference Calls and Minutes===
 
===Conference Calls and Minutes===
Line 70: Line 70:
 
==Participation Needs==  
 
==Participation Needs==  
  
The team was established following the PhUSE CSS March 2017.<br /><br />
+
The team was established following the PHUSE CSS March 2017.<br /><br />
 
'''Call for participation!'''<br />
 
'''Call for participation!'''<br />
 
We have room for those interested in the status of SEND readiness across the industry and encourage individuals with the following areas of expertise to join and contribute to this effort:
 
We have room for those interested in the status of SEND readiness across the industry and encourage individuals with the following areas of expertise to join and contribute to this effort:
Line 107: Line 107:
 
<big>[http://www.phusewiki.org/wiki/images/4/45/2017_PhUSE_Survey_Results_.pdf Survey Results] presented at the US CSS event, Silver Spring, March 2017</big>
 
<big>[http://www.phusewiki.org/wiki/images/4/45/2017_PhUSE_Survey_Results_.pdf Survey Results] presented at the US CSS event, Silver Spring, March 2017</big>
  
==2015 Survey Results (presented at PhUSE CSS 2016)==
+
==2015 Survey Results (presented at PHUSE CSS 2016)==
  
 
<br/> Survey Tool Output File With Results
 
<br/> Survey Tool Output File With Results

Latest revision as of 09:52, 10 October 2019


Welcome to the site for the Industry SEND Progress Survey project group.

This page describes high-level project management details on the group, including purpose, milestones, attendees, and so on.
We are part of the FDA/PHUSE Computational Sciences Nonclinical Working Group.
Learn more about the larger working group at Non-Clinical Road-map and Impacts on Implementation.

Project Overview

Across the Pharmaceutical Industry worldwide there is a variety of understanding of SEND and approaches to SEND implementation. Generally, the larger companies have had the resources to follow SEND through its first announcement to the issuance of the SEND Guidance document which set the due dates for SEND to be used for submission of the studies started on or after the due date.

Identified Need/Challenge

An annual survey continues to be informative to multiple stakeholders including PHUSE and CDISC and its members. Questions are asked about the timing of SEND dataset creation, the relationship between the report and the SEND datasets, and the decision to create SEND datasets for every study or to create the datasets only when a study is known to be in the submission.

Vision

Through responses to a survey, a picture of what is being done in the industry can be provided to all companies regardless of size and provide information for decision points. In addition, the agency can use the survey as a barometer of SEND understanding, process development, and need for additional guidance in general or specific areas. Results are presented at PHUSE CSS and/or PhUSE Connect meetings.

Project Scope

Create an annual electronic survey sponsored by PHUSE with up to 15 multiple choice questions with an option to provide additional free text information. Send that survey out to the PHUSE members (and CDISC list groups) requesting a 30 day response time. Compile the responses and distribute to PHUSE members and make the results available on the PHUSE WIKI.

Plans

Milestones

  • Survey Jan 2017
  • Survey Jan 2018
  • Survey Jan 2019


Tasks

The project proposal is to create an electronic survey sponsored by the Nonclincal WG of PHUSE CSS collaboration. The survey would contain up to 15 multiple choice questions with an option to provide additional free text information. Send that survey out to the PHUSE members requesting a 30 day response time. Compile the responses and distribute to PHUSE members and make the results available on the PHUSE WIKI.
The areas to be covered by the questions would include but are not limited to:

  • General progress to being SEND ready i.e. 25%, 50%, 75%, Complete
  • Timing for SEND dataset creation i.e. at end of study or at time of submission
  • Creation of SEND dataset for submission only or also for other data mining/visualization process/historical control
  • Use of outside consultant or SEND software vendor to assist with implementation
  • Involvement in the SEND project of support groups such as Quality Assurance
  • Role of person signing to verify that data has been QC’d to the source data
  • Estimate of additional resources needed to support/manage SEND
  • Management of controlled terminology – implement every release or select releases


The project will need a suitable survey tool and a small team to support question development, support the survey, tabulate the results and distribute a report. The results will also be posted on PHUSE wiki.

Conference Calls and Minutes


File:Minutes 17-May-2018 PhUSE Survey Team notes 17-May-2018.pdf

File:Survey team minutes 21 June 2018.docx

File:2019.Survey.build.xlsx

File:Minutes 19July2018.docx

File:2019.Survey.build 19 July 2018.xlsx

File:Paper Template US Connect 19.doc

File:Survey one page summary 2018 results.docx

File:Survey abstract 2018 results.docx

File:Survey team minutes 29 nov 2018.docx

File:Survey team minutes 20 Dec 2018.docx

Survey completed 17 Jan 2019 and mailed out on 18 Jan 2019.

Participation Needs

The team was established following the PHUSE CSS March 2017.

Call for participation!
We have room for those interested in the status of SEND readiness across the industry and encourage individuals with the following areas of expertise to join and contribute to this effort:

  • Toxicologists
  • FDA reviewers
  • IT vendors (with a special interest in the data quality aspect of SEND)
  • Nonclinical data managers (with focus on the fitness for use aspect of SEND data)
  • Biostatisticians (currently working or planning to work of SEND data)

What is the commitment?

  • Time (minimum of 1 hour every two weeks for team meetings, up to 3 hours / month)
  • Expected to contribute, not just be a spectator
  • Contribution of viewpoints and content
  • Wiki - creating/reviewing page content

If you would like to participate, please contact the co-leads for this group:

Lou Ann Kramer (lkramer@cdisc.org)
Bob Friedman (bfriedman@xybion.com)
Jance Fiori (jfiori@lilly.com)



Project Participants

Participants:
Bob Friedman, Xybion
Janice Fiori, Eli Lilly
Lou Ann Kramer, CDISC

SEND Survey Results 2017 (Presented at PhUSE CSS 2018)

Survey Results presented at the US CSS event, Silver Spring, March 2018


SEND Survey Results 2016 (Presented at PhUSE CSS 2017)

Survey Results presented at the US CSS event, Silver Spring, March 2017

2015 Survey Results (presented at PHUSE CSS 2016)


Survey Tool Output File With Results File:PhUSE SEND Survey - Final Results.pdf

2017 March Survey Results

Industry SEND Readiness Survey - 2017 Slide Deck