Sign off |
Date |
Role |
CBIIT or Stakeholder Organization |
Reviewer's Comments (If disapproved indicate specific areas for improvement.) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The purpose of this document is to collect, analyze, and define high-level needs for and designed features of the National Cancer Institute Center for Biomedical Informatics and Information Technology (NCI CBIIT) caCORE LexEVS Release 6.0. The focus is on the functionalities proposed by the stakeholders and target users to make a better product. The use case documents show in detail how the features meet these needs.
Design Scope
The scope of release LexEVS 6.0 is to support the Common Terminology Services 2 (CTS 2) specification and will focus on three major capabilites by LexEVS to fully support CTS 2:
- Provide support for Value Sets.
- Develop within LexEVS the ability to provide local extensions to code sets and maps among code sets.
- Develop within LexEVS other capabilities called for in the CTS2 Specification.
Please view the LexEVS 6.0 Scope document found at: https://wiki.nci.nih.gov/display/EVS/LexEVS+6.0+Scope+Document
GForge items
Please view the LexEVS 6.0 GForge items at: https://gforge.nci.nih.gov/tracker/?group_id=491
Use cases
Links to available documents.
Related requirements
One heading for each item.
Solution Architecture
Proposed technical solution to satisfy the requirements.
Cross product dependencies
Include a link to the Core Product Dependency Matrix.
Changes in technology
Include any new dependencies in the Core Product Dependency Matrix and summarize them here.
Assumptions
List any assumptions.
Risks
List any risks.
Detailed Design
Specify how the solution architecture will satisfy the requirements. This should include high level descriptions of program logic (for example in structured English), identifying container services to be used, and so on.
Implementation Requirements
Training and documentation requirements
One heading for each item.
Download center changes
List the needed changes. |