NIH | National Cancer Institute | NCI Wiki  

Unable to render {include} The included page could not be found.

Contents of this Page
Document Information

Author: Craig Stancl
Email: Stancl.craig@mayo.edu
Team: LexEVS
Contract: CBITT BOA Subcontract# 29XS223
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

Sign off

Date

Role

CBIIT or Stakeholder Organization

Reviewer's Comments (If disapproved indicate specific areas for improvement.)

Sherri de Coronado

5/15/2010

co-PO

CBIIT

approved

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.

GForge items

Please view the LexEVS 6.0 GForge items.

Use cases

Links to available documents.

Solution Architecture

Please view the Proposed Solution Architecture.

Cross product dependencies

Include a link to the Core Product Dependency Matrix.

  • No new dependencies exist for LexEVS 6.0.

Changes in technology

Include any new dependencies in the Core Product Dependency Matrix and summarize them here.

  • No new dependencies exist for LexEVS 6.0.

Assumptions

  • ECCF Data type requirements (21090) will be limited in scope. Guidance is not yet in place and approved 21090 data types to be used in services are not fully defined by CBIIT.
  • Any critical software defects found in LexEVS 4.2, 5.0, or 5.1 will be prioritized with assistance from COTR. We will attempt to fix non-critical issues as prioritized and as time permits.

Risks

  • ECCF Process and/or Documentation will change and/or require significantly more effort
  • ECCF Datatype (21090) requirements could require more effort than currently allotted
  • Unexpected Use Cases and/or Requirements could impact the schedule and/or budgeted level of effort
  • Out of scope feature requests could impact schedule

Detailed Design

The following sections specify how the design will satisfy the requirements.

Detailed Design - Associations (Mapping)

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - Associations (Mapping).

Detailed Design - Authoring

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - Authoring.

Detailed Design - Data Access Layer

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - Data Access Layer.

Detailed Design - Loader Post-Processor

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - Loader Post-Processor.

Detailed Design - Password Encryption

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - Password Encryption.

Detailed Design - Registry

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - Registry.

Detailed Design - Single Database Table Set

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - Single DB.

Detailed Design - Value Set Definition

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - Value Set Definition.

Detailed Design - XML Export

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - XML Export.

Detailed Design - XML Loader

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - XML Loader.

Detailed Design - ISO 21090 Datatypes (Analytical Services)

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - ISO 21090 Datatypes.

Detailed Design - Database Changes (2010)

Please view the detailed design: LexEVS Data Model (MS Word document).

Detailed Design - Model Changes

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - Logical Model.

Detailed Design - System Load Balancing

Please view the detailed design: LexEVS 6.0 Design Document - Detailed Design - System Load Balancing.

Detailed Design - OWL/RDF Exporter

Please view the detailed design: detailed design.

Implementation Requirements

Please view the detailed design: LexEVS 6.0 Design Document - Implementation Requirements.

  • No labels