 |
Page History
| Wiki Markup |
|---|
{scrollbar:icons=false} |
| Page info | ||||
|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
| ||||
|
| Panel | ||
|---|---|---|
| ||
Author: Craig Stancl |
Revision History
Version | Date | Description of Changes | Author |
|---|---|---|---|
1.0 | 5/14/10 | Initial Version Approved via Design Review | Team |
Objectives
The objective of this release of the LexEVS API is to design and construct a reference implementation of the CTS2 specification, leveraging LexEVS as the basis for the design and code base.
This release will address support for value sets, mappings between code sets, support for creation of local extensions to code sets and support related to content creation and editing.
Scope of Work
This effort will focus on three major capabilities needed by LexEVS to fully support CTS2. Defining a specification and reference implementation of a new version of LexEVS that:
- Provides support for value sets
- Develops within LexEVS the ability to provide local extensions to code sets and maps among code sets
- Develops within LexEVS other capabilities called for in the CTS2 Specification.
Please view the project scope document at: LexEVS 6.0 Scope Document
Summary of Products and Services
Functional Description
Please view the functional description (as part of the design document) at: LexEVS 6.0 Design Document - Solution Architecture#Required CTS2 Functionality.
Technical Architecture
Please view the technical architecture (as part of the design document) at: LexEVS 6.0 Design Document - Solution Architecture#HighLevelArchitecture
Analytical Services
Please view the analytical services (as part of ECCF documentation) at: LexEVS 6.0 Platform Independent Model on GForge
Data Services
Please view the data services (as part of ECCF documentation) at: LexEVS 6.0 Platform Independent Model on GForge
Preliminary Deployment Plan
Please view the deployment plan document at: LexEVS 6.0 Implementation Plan Document
Stakeholder Summary
CBIIT Staff/Contractor Name | Role | Responsibilities |
|---|---|---|
George Komatsoulis | NCICB Application Infrastructure | Oversees NCICB Application Infrastructure |
Avinash Shanbhag | NCICB Application Infrastructure | Oversees NCICB caCORE Software Engineering |
Larry Wright/ Sherri de Coronado | EVS Product Managers | Directs EVS Projects |
Denise Warzel | CORE Product Line Manager | Trans-CORE requirement coordination |
Gilberto Fragoso | Associate Director EVS Infrastructure | Technical Direction |
Jason Lucas | EVS Software Project Manager | Project schedule and task management for EVS team |
Craig Stancl | Mayo Clinic Technical Lead | Technical Direction and Implementation |
Traci St.Martin | Mayo Clinic Project Manager | Project schedule and task management |
Larry Brem | SAIC caBIG ARCH and VCDE Technical Program Manager | Contract governance |
Document History
Item | Information |
|---|---|
Document Version: | Click the Info tab. View the Recent Changes or click the link to view the page history. |
Last Modified: | Refer to the first line displayed in the document window. |
Project GForge site: | |
Most current version: | Unless the display includes a notice that you are viewing a previous version, you are viewing the most current version of this Scope Document for the release indicated in the title. |
Revision history: | Click the Info tab. In the Recent Changes area, click the link to view the page history. |
Review history: | Click the Info tab. In the Recent Changes area, note the developer who made each change and the date and time. Refer to the Key People Directory for their roles. Click the link to view any page or to view the page history, and then click the link for a page. When the page opens, view the comments and changes made in that version. |
Related documents: | Confluence Wiki documents: LexEVS 6.0 Development Documents |
Project Information
CBIIT Management | Role | Responsibilities |
|---|---|---|
Larry Wright/ Sherri de Coronado | Co-Product Managers | Oversees development of the product: features, functions, definition of stakeholders, priorities within the scope, timeframe for release |
Avinash Shanbhag | Engineering Manager | Oversees NCICB caCORE software engineering practices, conducts design reviews, guides technical development |
Denise Warzel | Product Line Manager | Oversees NCICB caCORE product line. Responsible for overall product integration, major and minor release cycles. Supports Product Manager. |
| Wiki Markup |
|---|
{scrollbar:icons=false} |
