# Presentation: 352910

## caBIG Workspace Overview, Scope and Needs

- February 19 & 20

**caBIG Workspace Overview, Scope and Needs**
**Architecture**

## Workspace Breakout Session - Goals

- Learn about the relevant projects at the NCICB and at other Cancer Centers
- Review the needs and interests of participating pilot Cancer Centers
- Evaluate existing and recommended projects as the basis for defining universal architectural guidelines for caBIG
- Define approach for interacting with Domain Workspaces
- Discuss group coordination and future meeting schedule
- Draft action plan summarizing conclusions

## Purpose of this Presentation

- Start today’s discussion from a common understanding
- 	- Overview of caBIG Workspaces in general (structure and operations)
- Set the stage for the Workspace specific discussions
- 	- Understand the scope and needs of the Architecture Workspace

## Workspace Definition - Generic

- Areas where caBIG pilot project activities are grouped and coordinated
- Encompass activities with a common focus, addressing identified Cancer Center needs
- Create products and solutions including tools, standards, data and documentation
- Share and test products and solutions amongst pilot participants
- Develop products and solutions which will ultimately be open and shared among the cancer research community

## Workspace Types

- There are two types of Workspaces – Domain and Cross Cutting
- Architecture is a Cross Cutting Workspace

## Workspace Roles

**Developer**
- 	An NCI-designated Cancer Center selected and funded by NCICB to participate in a specific Workspace to undertake software or solution development activities.
**Adopter**
- 	An NCI-designated Cancer Center selected and funded by NCICB to undertake formal testing, validation and application of products or solutions developed by Workspace Developers.
**Workspace Working  Group**
- 	A group of NCI-designated Cancer Center members (and other invited stakeholders) funded to provide guidance and support for Workspace activities.  The Working Group includes representatives from the Developer and Adopter teams.

## Workspace Roles

**Cross Cutting **
**WORKSPACE**

**Architecture**

**Vocabularies & Common Data Elements**

**Cross Cutting ****WORKSPACE**

**Developer**

**Developer**

**Adopter**

**Developer**

**Developer**

**Adopter**

**Developer**

**Developer**

**Developer**

**Developer**

**Developer**

**Workspace**
**Working Group**

**Workspace**
**Working Group**

**Workspace**
**Working Group**

**Domain **
**WORKSPACE**

**Clinical Trial Mgmt System**

**Integrative Cancer Research**

**Tissue Banks & Pathology Tools**

**Workspace**
**Working Group**

**Workspace**
**Working Group**

**Adopter**

**Developer**

**Developer**

**Adopter**

**Developer**

**Developer**

**Adopter**

**Domain **
**WORKSPACE**

**Domain **
**WORKSPACE**

## Workspace Principles of Participation

- Support the spirit, vision, goals and principles of the caBIG initiative as a whole
- Collaborate effectively with other Workspace participants and groups to support specific and overarching goals
- Collaborate effectively with other Workspaces and Working Groups (Workspace and Strategic levels) to support specific and overarching goals
- Undertake activities with integrity and objectivity
- Perform activities in a consensus driven manner
- Respect and capitalize on the skills and merits of individual participants
- Act in accordance with the caBIG Oversight Board and Master Contractor guidelines and processes

## Workspace Communications 

- The success of the caBIG network relies on communication and coordination between caBIG participants
- Mechanisms will be established to ensure effective communications both within Workspaces and between Workspaces/Working Groups
- e.g., Face-to-face meetings
- e.g., Electronic Program Updates
- e.g., Web-based tools
- The Cross Cutting Workspaces and the Strategic Level Working Groups address issues of common concern across caBIG and will promote communications across Workspaces

## Workspace Performance

- As part of undertaking Workspace activities, Workspace participants are asked to:
- Perform in accordance with their contracts and charters
- Meet agreed work plans, milestones and deliverable schedules
- Support processes as delineated by the caBIG coordination and oversight groups, including those for performance planning, monitoring and reporting
- Support the vision, goals and principles of caBIG
- Perform activities within agreed scope and budget

## Workspace Coordination

- Workspace participants are responsible for the coordination of their Center level caBIG related projects and activities according to agreed Statements of Work and contracts
- Overarching coordination of Workspace activities is undertaken by the Master Contractor (contracting team appointed by NCICB)
- Workspace participants are asked to support processes established by the Master Contractor to ensure the coordination of caBIG activities

## Workspace Participants - Architecture

## Architecture Workspace Scope

- This Cross Cutting Workspace assists in bringing new architectural developments and standards to caBIG, acts as an interface to IT communities developing novel architectures, develops architectural whitepapers describing new opportunities, and provides architectural expertise and solutions to other Workspaces
- These efforts will ultimately:
- Provide for interoperability between caBIG systems
- Facilitate standardized architecture across the caBIG project
- Promote the use of recognized architectural standards

## Architecture: Center Needs

**Example needs within the Workspace, from August 2003 Cancer Center Cooperative Development Meetings.**
- Need object namespace resolution
- Stable annotation space with linkable APIs
- Want to see software for research use built to widely-available standards
- caBIG Language standards and adoption
- Too many data stovepipes - department data not well integrated
- Lack of consensus in common objects and data structures

## Needs-driven

- Architectural recommendations should be based upon designs/prototypes that attempt to meet the requirements of the Domain Workspaces
- Must absorb and convey semantic content being defined in Vocabulary/CDE Workspace

## Architecture Workspace: Potential Products

- Documented alignment of needs and possible technology solutions
- Experimental designs for possible data grid architecture
- Prototype/proof of concept implementation based upon Domain Workspace requirements
- Formal guidance on caBIG Architectural standards
- Assistance services for Domain Workspace implementations

## Path Forward

- Share perspectives, backgrounds
- Discuss tasks, priorities
- Review communication, coordination mechanisms
- Set overall workspace agenda for coming year