 |
Page History
| Scrollbar | ||
|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
| Page info | ||||
|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
| ||||
|
| Panel | |
|---|---|
|
Active Period
Active from September 9, 2009 to November 30, 2009
Issue/Problem Statement
Problem Statement: caBIG, NCI, cancer centers and other organization associated with caBIG need to be able to easily create and edit ("author") Terminologies. Although NCI has used various authoring tools in the past, they have proven too heavyweight for use in an easy, distributed environment. With the advent of distributed terminology publishing services (eg, LexEVS), the caBIG community will need to consider tools and services for AUTHORING terminologies.
Objectives
This group should produce (at least) two documents:
1) A list of prioritized requirements for a terminology authoring tool/service. The requirements can be (but do not have to be) layered. That is, high level conceptual requirements (eg, based on best practices) and lower level, implementation specific requirements for an NCI/caBIG implementation.
2) A table (a simplistic notion = a table like in consumer reports) of terminology authoring tools/services on the market that are ranked according to the criteria in #1 above. There should be some written text on the 5 highest priorities with an emphasis on how that tool or service can be brought into use by caBIG/NCI and in what time frame.
Deliverables
This section should provide the list of deliverables with their respective due dates.
Deliverable | Description | Due Date |
|---|---|---|
Draft List - Tools | Draft list of terminology authoring tools and environments | Oct 10 |
Draft List - Requirements | Stable draft of requirements/features that will be used to compare tools | Oct 19 |
Update at F2F in Atlanta | Tentative, if enough to show, and an appropriate slot exists | Oct 20 |
Draft Table - Tools vs Features | Draft table of tools/ environments vs features/requirements | Oct 30 |
Annotated Table - Tools vs Features | Annotated table of tools/ environments vs features/requirements | Nov 15 |
Final Documents | Final requirements/features and annotated table | Nov 30 |
Background and Purpose
caBIG has in place a critical component of semantic interoperability, a Terminology Service (LexEVS as an implementation at NCI) for serving or publishing terminologies. Another component necessary is a terminology authoring tool for creating and editing terminologies. caBIG will soon be ready for a distributed terminology services, one need is to provide a choices for terminology authoring service for those institutions (including NCI) which desire to author (as well as serve) terminologies in the context of caBIG (eg, served thru the caGrid). This document serves as a charter for a small group to do market research on possible terminology authoring tools that satisfy terminology authoring best practices and caBIG/NCI needs.
Group Organization, Roles, and Responsibilities
This section should provide an overview on the members of the small group and their roles and responsibilites.
...
Member Name
...
Role
...
Responsibilities
...
Sherri de Coronado
...
Coordinator
...
Lead, facilitate, set up meetings, meet deadlines
...
Larry Wright
...
Co-Coordinator
...
ditto
...
Cecil Lynch (Ontoreason)
...
VCDE contractor
...
Core Research and document production
...
Solbrig/ Pathak (Mayo)
...
VCDE contractor
...
Core Research and document production
...
Russ Hamm (Apelon)
...
VCDE contractor
...
Core Research and document production
...
Keith Campbell (Informatics Inc)
...
VCDE contractor
...
Core Research and document production
...
Stan Huff (Intermountain Healthcare)
...
volunteer
...
Provide domain expertise and end user viewpoint
...
James Cimino (NIH/Laboratory for Informatics Development)
...
volunteer
...
Provide domain expertise and end user viewpoint
...
Brian Davis
...
advisor
...
| |
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
Data Services
Please view the data services (as part of ECCF documentation) at: LexEVS 6.0 Platform Independent Model
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: | LexEVS GForge Docs archive, Files archive |
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. |
| Scrollbar | ||
|---|---|---|
|
Work to date:
Wikipedia site with list of authoring tools / 2007 survey of ontology tools
Draft of Requirements (Larry Wright, Sherri De Coronado and Gilberto Fragoso)
Gforge site
...
