Skip Navigation
caGrid and Infrastructure Overview —
National Cancer Institute   U.S. National Institutes of Health www.cancer.gov
 
Home » sharable » caGrid and Infrastructure Overview
Document Actions

caGrid and Infrastructure Overview


What is caGrid?

caGrid (or the Grid) is an Architecture development project that provides the core infrastructure and tooling needed to connect to the Grid - this is the ultimate target of the compatibility process. caGrid is the underlying network architecture that provides the basis for connectivity between all of the cancer community institutions, allowing research groups to tap into the rich collection of emerging cancer research data while supporting their individual investigations. caGrid manages and securely shares information and analytic resources using locally managed access control policies and by using strongly typed data objects in XML format.

Key Features and Benefits:

  • Sharing of resources (computational, storage, data, etc.)
  • Secure Access (global authentication, local authorization, policies, trust, etc.)
  • Open Standards Virtualization

 

Getting on the Grid: Advertising and Discovering Services

“Getting something on the Grid” – or “establishing a Grid node” – means meeting requirements for interoperability (through adoption or adaptation), and then connecting that interoperable service or data source to a Grid (internal or external). Grid services are “advertised” through an index. You can also connect to a Grid to “discover” services or data provided by others.

 

Infrastructure - the informatics backbone of caGrid

Core services – including data standards, shared vocabularies, and indexing – provide the critical elements needed to advertise and discover other Grid resources.

Biomedical Research Integrated Domain Group (BRIDG)
A collaborative effort of stakeholders from the Clinical Data Interchange Standards Consortium (CDISC), the HL7 Regulated Clinical Research Information Management Technical Committee (RCRIM TC), the National Cancer Institute (NCI), and the US Food and Drug Administration (FDA) to produce a shared view of the dynamic and static semantics that collectively define a shared domain-of-interest, i.e. the domain of clincial and pre-clinical protocol-driven research and its associated regulatory artifacts.

 
caCORE

Open-source software that helps to streamline informatics development throughout the cancer community.

  The Cancer Bioinformatics Infrastructure Objects (caBIO) Model

Biomedical data system built using a model-driven approach.

  Cancer Data Standards Repository (caDSR)

A database and tool set used to create, edit and deploy common data elements.

  Enterprise Vocabulary Services (EVS)

A set of services and resources that address NCI's needs for controlled vocabulary.

  NCICB Common Security Module (CSM)

Application security tools that address authentication, authorization and user provisioning.

  NCICB Common Logging Module (CLM)

A set of auditing and logging tools implemented in a flexible and comprehensive solution.

  caAdapter

caAdapter is an open source tool set that provides model mapping services in support of caCORE components and facilitates data mapping and transformation among different kinds of data sources including HL7 v2 messages, HL7 v3 messages, and Regulatory Data Sets.

 

Clinical Trials Object Data System (CTODS)
Enable the exchange of de-identified clinical trials data across multiple systems while supporting syntactic and semantic interoperability. CTODS provides a single, unified set of Application Programming Interfaces (APIs) that can access clinical data from multiple data sources.

 
 

cancer Bioinformatics Infrastructure Objects (caBIO)
An information model of cancer biomedical objects is created to facilitate the communication and integration of information from the various initiatives supported by caBIG and NCI. The information model is described in UML and semantically annotated with description logic concepts from EVS.

 

 

To Grid-enable a system (expose a compatible tool on the Grid) you must:

  • Use object types and information models registered in the caDSR. Develop object oriented APIs and data resources.
  • Define a Grid service interface that defines the functionality that you are exposing to the Grid. This grid service interface uses the same object types as your existing system, but represents them in a way that is platform and language neutral (e.g., using XML).
  • Complete Grid service implementation by mapping service invocations to API calls or queries into the existing system.
  • All of these activities are enabled through caGrid tools and infrastructure – adopting a caBIG™ compatible tool means much of the work has already been done for you – adaptation may take more effort.

diagram of caGRID

You cannot “get your tool on the Grid” unless you have: (1) adopted or adapted a tool that is caBIG™ compatible; (2) Installed caGrid software.

last modified 01-06-2009 03:00 PM