Credo 2004 Staffing issues

1
Credo 2004Staffing issues

• Tony Rose, John Fox

2
Key Questions

• Do we have sufficient (human) resource to
• Support our clinical partners?
• Complete the pilot trials on schedule?
• Address any local requirements?
• If not, what are our options?

3
What are we committing to?

• Three trial sites
• Refinement/localization of the TA prototype
• plus other CREDO services
• Integration with the local DB infrastructure
• Development of common dataset

4
Existing commitments

• Ongoing release cycle (6 monthly)
• Public repository of PROforma content
• Public download for Tallis
• Clinical strength DB support (2005)?
• Multiple concurrent users, etc.

5
Other plans / commitments (1)

• Major upgrades to Tallis
• Data model (incl. complex data types)
• UI redesign
• Composer (usability, condition editor)
• Web components (control panel)
• Terminology integration
• Research directions to improve functionality
• Support for goals
• New generation language (TARGET)
• Speech and dialogue (HOMEY)
• Communication support (LB)

6
Other plans / commitments (2)

• Completion of CREDO content
• 20 thus far?
• Slow start, but gathering speed
• Integration with other resources
• Immediate next steps
• NICE genetics risk assessment
• Others to be discussed (see JF slide)

7
Existing resources

• TGR
• VP (until May 2004)
• CH (currently 80)
• RS (currently 80)
• AHR (currently 50)
• MW (from March 2004)
• Robert Dunlop (20)?
• JF (20)
• Additional staff

8
Potential resources

• Technical developer
• from Q3 2004 (best case scenario)
• Content developer
• from Q3 2004 (best case scenario)
• Training/support for clinical partners? (Clinical
  Research Associate)
• from Q3 2004 (best case scenario)

9
Conclusions

• Go, but set priorities
• Spend time getting the planning right
• Short-term plans may change (iterative
  development)
• but overall strategy should not
• Solicit feedback to help set priorities
• Trial centre users, Tallis download users
• Content development
• Last 20 takes 80 of time