April 29, 2016 Meeting Notes

From PHUSE Wiki
Jump to: navigation, search

Meeting minutes of Nonclinical_Script_Assessment_Project

April 29, 2016

Present First Name Last Name Affiliation
Yes Kevin Snyder FDA
Yes Kevin Cahill EPL
Yes Bill Varady Boehringer-Ingelheim
Yes Bob Dorsam FDA
Yes Bob Friedman Xybion
Yes Chris Eley Pfizer
Yes Fred Mura PDS
Yes Hanming Tu Accenture
Yes Bill Houser Bristol-Myers Squibb

Meeting notes:

  1. Since last meeting, Kevin Snyder supplied an example in GitHub that uses SAS to create HTML output
  2. Today Kevin and Hanming guided us through the processes needed to use GitHub
    1. Create account on GitHub site
    2. Ask hanming (hanming.h.tu@accenture.com) to be a contributor
    3. Hanming will send an invitation that will come as email from "GitHub"
    4. If you don't see the invitation link in your email, you can accept the invitation from https://github.com/orgs/phuse-org/invitation
    5. You can download/clone a whole repository to your computer if you have a client for the repository. You can get either TortoiseSVN (http://blogs.wandisco.com/2011/10/17/how-to-install-tortoisesvn-and-make-your-first-repository-change/) or github desktop (https://desktop.github.com/). See the useful links at https://github.com/phuse-org/phuse-scripts/wiki/Read-Me-First-(Google-Code).
    6. Read other getting-started information here: https://github.com/phuse-org/phuse-scripts/wiki/Read-Me-First-%28Google-Code%29
    7. To see a list of contributed scripts
      1. get into GitHub and select the tab for the Wiki
      2. Look at the list on the right side and open the link for Simple Index
  3. When you have contributed a new script, create a YML metadata file so it can be added to the Simple Index
    1. Copy the metadata file for another script and put in your folder: <script-name>.tar_gz.yml
    2. Edit the copy to describe your script.
    3. The changes will appear in the index when Hnming runs his update script.
  4. Hanming explained that the script status choices are:
    1. Contribute
    2. Development
    3. Tested
    4. Qualified

Action Items:

Agenda for next meeting:

  1. Discuss questions regarding the current GitHub conventions used by the clinical team.
  2. Are the status definitions useful and appropriate for us?
  3. Is it useful to prioritize script ideas? perhpas collecting names of who is willing to write, test, and use them?
  4. Do we want to create a process to consult with vendors before creating a script to ensure we don't discourage them from creating more useful tools?
  5. What should we aim for scripting languages (R) and output formats (PDF, HTML, etc)?
  6. How do we appropriately use the data folder to facilitate script creation and testing?

Script Ideas:

  • We will need scripts to help with getting data in, relationships established, and ready to be processed and analyzed
  • SEND to tumor.xpt converter
  • Tool to assist in obscuring Test Article Identifiers, Study Numbers, and other sensitive information from SEND datasets