May 12, 2016 Meeting Notes
From PHUSE Wiki
Meeting minutes of Nonclinical_Script_Assessment_Project
May 12, 2016
|Present||First Name||Last Name||Affiliation|
Action Items from previous meeting:
- Bill Varady will provide information on converting SAS to R. (R for SAS users)
- Bill H will add links to our wiki
- Fred Mura will see if he can share their sample SEND data.
- Bill Houser will ask Instem if they can supply their SEND data.
- no answer yet from Instem
- Bill Houser will add a couple SAS scripts.
- delayed due to legal concerns
- Kevin Snyder is working on getting some scripts for working with PK files
- Everyone should create their GitHub accounts and begin looking at the conventions
- Folder Structure: https://github.com/phuse-org/phuse-scripts/blob/master/folder_structure_proposed.txt
- Name Convention: https://github.com/phuse-org/phuse-scripts/blob/master/naming_conventions_proposed.txt
- Metadata Tags: https://github.com/phuse-org/phuse-scripts/blob/master/MetaData_template.md
- Simple Index: https://github.com/phuse-org/phuse-scripts/wiki/Simple-Index
Notes from this meeting:
- Discuss questions regarding the current GitHub conventions used by the clinical team. -no questions
- Are the status definitions useful and appropriate for us?
- Is it useful to prioritize script ideas? perhaps collecting names of who is willing to write, test, and use them?
- maybe later after we have some experience working together.
- 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?
- limiting our scope?
- talk to the vendors to understand their concerns? Bill H will ask them to join a future call.
- they can sell what we create.
- What should we aim for scripting languages (R) and output formats (PDF, HTML, etc)?
- let's consider standardization after we have more experiments.
- How do we appropriately use the data folder to facilitate script creation and testing?
- What are the legal concerns for you to contribute meaningfully? - only a concern for one company.
- 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