Page History
Wiki Markup |
---|
{scrollbar:icons=false} h1. {page-info: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 {panel} || 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. h2. 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]. h3. GForge items Please view the [LexEVS 6.0 GForge items|https://gforge.nci.nih.gov/tracker/?group_id=491]. h3. Use cases Links to available documents. h2. Solution Architecture Please view the [Proposed Solution Architecture|LexEVS 6.0 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.0. 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.0. h3. 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. h3. 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 h2. Detailed Design The following sections specify how the design will satisfy the requirements. h3. Detailed Design - Associations (Mapping) Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - Associations (Mapping)]. h3. Detailed Design - Authoring Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - Authoring]. h3. Detailed Design - Data Access Layer Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - Data Access Layer]. h3. Detailed Design - Loader Post-Processor Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - Loader Post-Processor]. h3. Detailed Design - Password Encryption Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - Password Encryption]. h3. Detailed Design - Registry Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - Registry]. h3. Detailed Design - Single Database Table Set Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - Single DB]. h3. Detailed Design - Value Set Definition Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - Value Set Definition]. h3. Detailed Design - XML Export Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - XML Export]. h3. Detailed Design - XML Loader Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - XML Loader]. h3. Detailed Design - ISO 21090 Datatypes (Analytical Services) Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - ISO 21090 Datatypes]. h3. Detailed Design - Database Changes (2010) Please view the detailed design: [LexEVS Data Model (MS Word document)|https://gforge.nci.nih.gov/docman/view.php/491/21567/LexEVS%206.0%20Data%20Model%202010.doc]. h3. Detailed Design - Model Changes Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - Logical Model]. h3. Detailed Design - System Load Balancing Please view the detailed design: [LexEVS 6.0 Design Document - Detailed Design - System Load Balancing]. h3. Detailed Design - OWL/RDF Exporter Please view the detailed design: [detailed design|LexEVS 6.0 Design Document - Detailed Design - OWL RDF Exporter]. h2. Implementation Requirements Please view the detailed design: [LexEVS 6.0 Design Document - Implementation Requirements]. {scrollbar:icons=false} |