25
CTMS KC Successes and Challenges Robert Annechiarico Cross KC April 2009

CTMS KC Successes and Challenges Robert Annechiarico Cross KC April 2009

Embed Size (px)

Citation preview

CTMS KC Successes

and Challenges

Robert Annechiarico

Cross KC

April 2009

Agenda

• Accomplishments

• Next steps

• Challenges

• After this meeting, you should be able to answer:

• What does the CTMS KC Support?

• Have the Knowledge Centers increased community awareness and understanding of caBIG®?

• Have new tool adoptions been facilitated by the KCs?

• Is your KC creating a searchable knowledge base?

• Have the KC’s helped bridge new communities?

AccomplishmentsSummary

• Population and maintenance of the technology stack

• Wiki, forums, demo site, tracker, source code

• Increased awareness of the CTMS tools and work

• As measured by page hits over time

• Enhanced access to CTMS tools and resources

• Releases and documentation organized on the Wiki

• Setup and maintained demonstration site

• Development of an indexed, searchable knowledge base

• Content from forums, email exchanges

• Facilitation of adoption

• Hands-on deployment help, forum question responses

• Contribution to the overall cross-Knowledge Center effort

• Source code contribution white paper, review and validation of Wiki extensions, Standardize on Cross KC Wiki interface

AccomplishmentsWiki

• Tools

• CCTS, caAERS, C3PR, PSC, LabViewer, C3D Connector, caXchange

• Projects

• CTMS WS Community, BAM

• Knowledge Base

• KB Articles, FAQs

• Resources

• Demonstration Sites, Announcements, Feedback, Training, Presentations, Documentation Library, Outreach Efforts

AccomplishmentsKC Users

• A large user base to support – NEED TO SHOW OTHER KCs

• Indicators suggest growing interest in CTMS Knowledge Center

AccomplishmentsApplication Page Views

• NEED TO SHOW OTHER KCs• Proportional growth of individual application inquires• More sensitive measures are needed

Cross KC Wiki Activities

AccomplishmentsWiki – Tool Documentation

AccomplishmentsSetup and Monitor Forums

• 15 forums (General, developer/end user per tool, announcements)

• 97 topics, 254 posts

AccomplishmentsForums Activity

AccomplishmentsForum Examples and Evolution

SepSep OctOct NovNov DecDec JanJan FebFeb MarMarAugAug

About the CTMS KC ForumsThe CTMS Knowledge Center forums are used to post questions about anything related to the caBIG CTMS software products or the Knowledge Center…

About the CTMS KC ForumsThe CTMS Knowledge Center forums are used to post questions about anything related to the caBIG CTMS software products or the Knowledge Center…

Feedback: September 8-9 CTMS Face to FaceWELCOME to a discussion using the CTMS Knowledge Center wiki on the September 8 and 9 CTMS Face to Face meeting at St. Jude Children's Research Center in Memphis, TN.

Feedback: September 8-9 CTMS Face to FaceWELCOME to a discussion using the CTMS Knowledge Center wiki on the September 8 and 9 CTMS Face to Face meeting at St. Jude Children's Research Center in Memphis, TN.

Posting Clinical Trial Data on the GridGreetings,I have a few questions about posting clinical trial data on the grid…Data Sharing…HIPAA…grid…

Posting Clinical Trial Data on the GridGreetings,I have a few questions about posting clinical trial data on the grid…Data Sharing…HIPAA…grid…

Oracle space requirements?We would like to install stand alone caAERS for evaluation.I understand that the minimum memory requirements are 2 GB RAM and 36 GB Disk Space. How much of the disk space do folks set aside for the Oracle database?

Oracle space requirements?We would like to install stand alone caAERS for evaluation.I understand that the minimum memory requirements are 2 GB RAM and 36 GB Disk Space. How much of the disk space do folks set aside for the Oracle database?

Summary 3 Reports & anatomic sites…Why do C3PR and the NCI's requirements for the Summary reports differ? Are the NCI's disease sites just examples, not requirements, or is this list antiquated and likely to change shortly to be more like what is currently in C3PR?...

Summary 3 Reports & anatomic sites…Why do C3PR and the NCI's requirements for the Summary reports differ? Are the NCI's disease sites just examples, not requirements, or is this list antiquated and likely to change shortly to be more like what is currently in C3PR?...

AccomplishmentsDemo Tier

• Public tier at Duke

• Private (demo) tier at SemanticBits

• Weekly database restore

LabViewerLabViewer

caXchang

e

AccomplishmentsKnowledge Base

C3PR

caAERS

PSC

C3D

caXchange

AccomplishmentsTracker

• Bugzilla

• Bug tracking, issue tracking, use case tracking (not in heavy use yet)

• Identified gaps, usage scenarios

• Validated required changes locally

AccomplishmentsSource Code Repository

• Subversion

• Releases, source code, patches

• Not in heavy use yet

• Drafted code contribution white paper

• Background

• Code Contribution Mechanisms• Incubators• Patches• Direct Contribution

• Considerations• Project Ownership• Modularity• Core Contributions

• Recommendations

AccomplishmentsAdoption Assistance

Assisted a large number of organization through email and forums

Hands-on help extended by Knowledge Center to different adopters with installation and bug fixes

•Bill Dyer – CCTS installation incl. C3D connector and Loading Labs

•Ken Quinn (Roswell Park) – caAERS

•Rick Sanchegraw (Health. Missouri) – caAERS

•Farid Mohammad (Duke) - C3PR, caAERS

•Amish Shah (CALGB) – caAERS

•Bob – caAERS

•BAM team with their Wiki requirement

AccomplishmentsOutreach Effort

Presented and scheduled to present at various meetings and conferences, to name a few

•AMIA – Translational Informatics

•Society for Clinical Trials

•Bio-IT World

•ASCO

As a result we have been contacted by various groups and companies

•Rapid Pharmaceuticals

•Dental Practice based Research Network (PBRN)

Organized and provide support demonstration at with different groups within caBIG and outside caBIG

•Walter Reed Army Medical Center

•Different workspaces and conferences.

Next StepsSummary

• Enhance documentation

• Documentation versioning, homogenize templates

• Train the trainer (documentation to help cancer centers)

• Support new tools

• CDMS, COPPA, CTRP, PLT, CCTS 2.0

• Document processes

• SOPs for request handling, documentation versioning, etc.

• Leverage technology stack fully

• Bugzilla, SVN

• Monitor access more completely (e.g. Google Analytics)

• Wiki, forums, demo tier

Next StepsEnhance Wiki Content

• Documentation

• Convert additional documents to wiki content

• Version documents

• Homogenize templates

• Releases

• Additional releases – map releases to documentation versions

Next StepsSOPs

• Forum triage

• Request received, categorized, logged in tracker, assigned, etc.

• Wiki content editing

• Who can edit which parts of the wiki when?

• Reporting

• Issue reporting

• Site usage (forums, wiki, etc.)

• Use cases and prioritization

• Community code contribution

• Documentation versioning

• Tool release

Next StepsCustomer Analysis

• Usage

• Google Analytics

• Customer Feedback

• Cross-KC feedback form

Next StepsAdditional Tools

• Support for

• Documentation, training material, triaging and (maybe) fielding questions, demonstration tier, forums, etc.

• CDMS

• New Clinical Data management System procurement by NCI

• COPPA

• Enterprise services for Persons, Organizations, Protocol Abstractions, and their Correlations

• PLT

• Protocol Lifecycle Tracking

• CTRP

• Clinical Trials Reporting Program

Next StepsTrain the Trainer Materials

• Documentation to help organizations set up training programs and maintain CTMS tools

• Documentation

• Deployment and Administration Guidelines

• Training Guide

• Troubleshooting Guide

• External Resources Guide

• Presentations/Demonstrations

• An Overview of the CTMS Applications

• Setting Up a Training Program

• Troubleshooting Technical Problems

CTMS KC Challenges

• Building a critical mass of users

• Organize various application versions on the Wiki

• Currently varies with each tools

• Frequency and release numbers are not consistent

• Fielding requests from various channels and track them centrally using a tracking system

• Prepare and provide training material for the trainer

• Include code contributions from adopters to new application releases

• Establish best practices for

• Responding to issues

• Working on bug fixes and patches

• Creating FAQ’s

• Updating documentation

• Closing issues and collecting feedback

Questions and Answers