NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 16

changes.mady.by.user Unknown User (wileyal)

Saved on

compared with

New Version 17

changes.mady.by.user Unknown User (wileyal)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0
Wiki Markup
{scrollbar:icons=false}
h1. {
Scrollbar
iconsfalse
page-info

...

Panel
titleContents of this Page
Table of Contents
minLevel2

...

Panel
titleDocument Information
Author: Craig Stancl
Email: 
:title}
{panel:title=Contents of this Page}
{toc:minLevel=2}
{panel}
{panel:title=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.)

—

---

—

—

---

—

—

—

---

—

—

---

—

—

—

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.1. The focus is on the functionalities proposed by the stakeholders and target users to make a better product.

Design Scope

The scope of release LexEVS 6.1.

Please view the LexEVS 6.1 Scope document (URL to be provided)

GForge items

Please view the LexEVS 6.1 GForge items (URL to be provided)

Use cases

Links to available documents.

Solution Architecture

Please view the Proposed Solution Architecture at: LexEVS 6.1 Design Document - Solution Architecture

Cross product dependencies

Include a link to the Core Product Dependency Matrix.

  • No new dependencies exist for LexEVS 6.1.

Changes in technology

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

  • No new dependencies exist for LexEVS 6.1.

Assumptions

  • —
  • —

Risks

  • —
  • —

Detailed Design

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

Detailed Design - CTS 2 Alignment

Please view the detailed design: LexEVS 6.1 Design Document - Detailed Design - CTS 2 Alignment

Detailed Design - Java API

Please view the detailed design: LexEVS 6.1 Design Document - Detailed Design - Java API

Detailed Design - CTS 2 REST Services

Please view the detailed design: LexEVS 6.1 Design Document - Detailed Design - CTS 2 REST Services

Detailed Design - CTS 2 SOAP Services

Please view the detailed design: LexEVS 6.1 Design Document - Detailed Design - CTS 2 SOAP Services

Detailed Design - OWL 2 Support (Loader)

Please view the detailed design: LexEVS 6.1 Design Document - Detailed Design - OWL 2 Support (Loader)

Detailed Design - OWL 2 Support (Exporter)

Please view the detailed design: LexEVS 6.1 Design Document - Detailed Design - OWL 2 Support (Exporter)

Detailed Design - ISO 21090 Support

Please view the detailed design: LexEVS 6.1 Design Document - Detailed Design - ISO 21090 Support

Detailed Design - Tolven and caCIS Requirements Support

Please view the detailed design: LexEVS 6.1 Design Document - Detailed Design - Tolven and caCIS Requirements Support

 Services
{panel}

|| 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.1*. The focus is on the functionalities proposed by the stakeholders and target users to make a better product. 

h2. Design Scope

The scope of release LexEVS 6.1.

Please view the LexEVS 6.1 Scope document (URL to be provided)

h3. GForge items

Please view the LexEVS 6.1 GForge items  (URL to be provided)

h3. Use cases

Links to available documents.

h2. Solution Architecture

Please view the Proposed Solution Architecture at: [LexEVS 6.1 Design Document - Solution Architecture]

h3. Cross product dependencies

Include a link to the [Core Product Dependency Matrix|https://wiki.nci.nih.gov/x/hIx8].
* No new dependencies exist for LexEVS 6.1.

h3. Changes in technology

Include any new dependencies in the [Core Product Dependency Matrix|https://wiki.nci.nih.gov/x/hIx8] and summarize them here.
* No new dependencies exist for LexEVS 6.1.

h3. Assumptions

* ---
* ---

h3. Risks
* ---
* ---

h2. Detailed Design

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

h3. Detailed Design - CTS 2 Alignment

Please view the detailed design: [LexEVS 6.1 Design Document - Detailed Design - CTS 2 Alignment]

h3. Detailed Design - Java API

Please view the detailed design: [LexEVS 6.1 Design Document - Detailed Design - Java API]

h3. Detailed Design - CTS 2 REST Services

Please view the detailed design: [LexEVS 6.1 Design Document - Detailed Design - CTS 2 REST Services]

h3. Detailed Design - CTS 2 SOAP Services

Please view the detailed design: [LexEVS 6.1 Design Document - Detailed Design - CTS 2 SOAP Services]

h3. Detailed Design - OWL 2 Support (Loader)

Please view the detailed design: [LexEVS 6.1 Design Document - Detailed Design - OWL 2 Support (Loader)]

h3. Detailed Design - OWL 2 Support (Exporter)

Please view the detailed design: [LexEVS 6.1 Design Document - Detailed Design - OWL 2 Support (Exporter)]

h3. Detailed Design - ISO 21090 Support

Please view the detailed design: [LexEVS 6.1 Design Document - Detailed Design - ISO 21090 Support]

h3. Detailed Design - Tolven and caCIS Requirements Support

Please view the detailed design: [LexEVS 6.1 Design Document - Detailed Design - Tolven and caCIS Requirements Support]

{scrollbar:icons=false}