Project Charter: LexEVS 6.1
Mayo Clinic
Biomedical informatics
LexEVS 6.1
project charter
Created by: Traci St.Martin
Date: January 28, 2011
Revision History
Date / Version / Description / Author /1/28/2011 / 1.0 / Project charter developed from SOW / Traci St.Martin
ta
1 Project Description
LexEVS is the infrastructure that provides terminology services for caBIG® and CBIIT as well as various external organizations such as NCBO, CDISC and FDA via multiple programming interfaces (SOAP, HTTP/XML, Java, etc.), caGrid services. It also underpins most EVS offerings such as subset reports and the EVS terminology browsers.
LexEVS 6.1 includes the following:
o Program management and technical expertise support
o Manage the design, development, integration and release of LexEVS 6.1
o Provide technical expertise as needed including conferences, presentations, phone responses and other communications
o Provide all the system level, integration and user acceptance testing support
o Provide all documentation both of the system design, standard technical documentation and those required by NCI’s ECCF process
o OWL2 Support
o Design, develop, integrate, test and deploy both a loader and an export capability that will be capable of integrating OWL2 data with the LexEVS system
o Design and develop SOAP and REST API Interfaces for the current Profiles
o Design, develop, integrate, test and deploy SOAP and REST interfaces for all of the CTS2 Profiles and all of the functions defined in those profiles
o Enhance LexEVS interfaces to support change sets and listings of value sets and terminologies
o Design, develop, integrate, test and deploy enhancements to LexEVS interfaces to support simple, efficient retrieval of versioning information, change sets and lists of value sets and terminologies.
o This is specifically focused on meeting requirements identified by Tolven to identify changes in resolved value sets resulting from version changes in referenced terminologies and to retrieve either change set or full value set listings, but requirements gathering and design should be of broader utility and not limited to simply meeting Tolven’s current requirements.
o Align with Final CTS2 Specification
o LexEVS is currently a reference implementation of the draft CTS2 spec.
o HL7 will be defining the final CTS2 spec.
o This task will focus on updating the LexEVS Reference Implementation to support any changes between the draft and final CTS2 spec
1.1 Project Scope
1.1.1 In Scope
The scope of work covers the following items as requested:
o CTS2 aligned REST & SOAP Services
o Update the LexEVS Model & Java API to have the required functionality to support the CTS2 Specification and the HL7 standard by developing other capabilities identified and required by the CTS2 final submission.
o Testing, Deployment, and bug fixes of LexEVS 6.1
o Successful promotion of LexEVS 6.1 through NCI tiers
o Updated 6.1 user documentation
o Updated 6.1 ECCF documentation
o BDA installation package
1.1.2 Out of Scope
o Creating a user interface.
o Analytical Grid Services
o Support for Browser team
o Support for 6.0
o Any major model changes
1.2 Project Deliverables
Description / Owner / Due DateAll code for 6.1 version / Traci / 10 days before project completion
All test cases and the results / Traci / 10 days before project completion
All design documentation / Traci / 10 days before project completion
All ECCF compliant documentation / Craig / 10 days before project completion
All installation scripts and release notes (deployment package) / Traci/Craig / 10 days before project completion
1.3 Proposed Timeline
Key Milestones / Key DatesInitial Design / February, 2011
Prototype 1 Release (Tolven) / March, 2011
Iteration 1 Release / April, 2011
Iteration 2 Release / May, 2011
Iteration 3 Release / July 2011
Final Release Candidate / August, 2011
NCI Development tier Complete / September, 2011
NCI QA tier Complete / October, 2011
NCI Stage tier Complete / November, 2011
NCI Production tier Complete / December, 2011
Project Closure / January 2012
2 Project Organization
2.1 Key Stakeholders
Identify business areas/resources which will be affected by this proposal and need to be consulted in its development and implementation. This also includes the project team.
Name / RoleLarry Wright, Sherri De Coronado / Product Managers (NCI)
Larry Brem / SAIC COTR
Michael Keller, James Peyton / BAH
Dr. Christopher Chute / Mayo Clinic Principal Investigator
Jim Buntrock / Mayo Clinic Biomedical Informatics Section Head
Scott Tabor / Mayo Clinic Clinical Informatics Unit Head
Traci St.Martin / Mayo Project Manager
Craig Stancl / Mayo Technical Lead
Scott Bauer, Sridhar Dwarkanath, Kevin Peterson, Harold Solbrig / Mayo Team
Jason Lucas / EVS Project Manager
Tracy Safran, Kim Ong, David Yee, Wil Garcia, Gilberto Fragoso, Rob Wynne / EVS Team
Russ Hamm / Programmer, Apelon
3 Resources
3.1 Resource Identification & Budget Overview
Resources (FTE) / Estimated Hours / NotesDr. Chris Chute / 104
Harold Solbrig / 40
Craig Stancl / 1456
Sridhar Dwarkanath / 1040
Scott Bauer / 1560
Kevin Peterson / 1560
TBN – analyst/programmer / 1456
Traci St.Martin / 832
Total / 8048
4 Risk Assessment
Potential Risks / Probability (H,M,L) / Impact(H,M,L) / Risk Plan / Risk Plan Owner
ECCF Process and/or Documentation will change and/or require significantly more effort / Medium / High / We will work closely with ECCF team to mitigate this risk / Craig/Traci
Scope of development exceeds estimation / Low / High / We will track our hours closely between plan & budget and escalate any possible pattern of overage. / Traci
21090 data type requirements were not included in scope for the new services – changing this to become in scope would push out our timeline. / Low / High / Work closely with CBIIT to mitigate this risk. / Traci
Requirements from Tolven/caCIS come late in the development cycle and impact our schedule / Medium / High / Meet with Tolven weekly to gather/confirm requirements. Provide iterative releases to ensure functionality meets their needs / Traci
More requirements from the EVS team for 6.1 could impact schedule / Low / High / We will work closely with Larry & Sherri to prioritize and mitigate this risk. / Traci
5 Assumptions/Constraints
§ The resources are available to utilize the existing expertise and team members for LexEVS and CTS2
§ We will utilize our development/testing environment to ensure stable code prior to NCI tier deployment
§ Systems Team at NCI will be available to meet the deployment schedule to deploy to the NCI tiers
§ BDA team is available to work with our team to assist in creating a compliant installation package
§ ECCF review process is defined and reviews occur in a timely manner
Page 3 of 6