CCTS Discovery Architecture
From CTMS_WIKI
Contents |
Introduction
Background
The caBIG Clinical Trials Suite (CCTS) is an enterprise clinical trials system being designed primarily for use in trial sites. The suite is comprised of a collection of interoperable modules covering a broad range of key areas in cancer clinical trials management. These include patient registration via C3PR, patient scheduling via PSC, adverse events reporting via caAERS, lab analysis via LabViewer, and clinical data management via C3D. Integration between these applications is centered around five key scenarios: Study Creation, Register Subject, Load Labs in CDMS, Lab-driven AE Creation, and AE-Triggered Schedule Change. The implementation is based upon the caGrid infrastructure with caXchange as the Enterprise Service Bus for reliable message routing and GAARDS providing robust security.
Scope
This document is a work in progress used strictly for planning for the CCTS 2.0 release. Up until that release, it could be altered in any way.
Related Documentation
Requirements
| Req. ID | Requirement Description |
| CCTS-DISCOVERY-001 | Services must be able to be advertised to an IndexService |
| CCTS-DISCOVERY-002 | Service-level metadata should include all standard caGrid service-level metadata |
| CCTS-DISCOVERY-003 | Service-level metadata should include the semantics (e.g. metadata registered in the caDSR) |
Architecture
While the caDSR and GME provide for central registration and discovery of the semantics and syntactics of messaging models, the IndexService provides for the dynamic advertisement and discovery of running grid services. While this is not leveraged in any of the CCTS workflows, it is an important use case that the grid infrastructure satisfies and is thus supported by CCTS. While running, the grid services periodically update a centralized grid service (IndexService) that stores the metadata describing the service. This includes the service signature (method signatures), institutional metadata about service ownership, and the semantic metadata that is registered in the caDSR. This allows for clients to dynamically discover the service based upon any of these metadata attributes.
