More content coming soon.
Web Client
The SHRINE web client is the users' gateway into a SHRINE network. The web client code was forked from the i2b2 web client several years ago allowing users who are familiar with the use of i2b2 to be comfortable using SHRINE. The first step in a user's interaction with SHRINE is to authenticate using his username and password to the i2b2 PM cell. Once this authentication occurs, the user's session information is included in all requests that the web client sends to the SHRINE Query Entry Point and is propagated throughout the network.
The web client can be used to browse the user's previous query history, navigate the network ontology, and to formulate and execute queries. All communication between the web client and the SHRINE network is performed via the SHRINE Query Entry Point.
Query Entry Point
The Query Entry Point (QEP) is the service entry-point into a SHRINE network. The QEP implements a subset of the i2b2 CRC messaging protocol and is therefore compatible with many components that have been written to produce and consume these messages (most notably including the SHRINE web client). The QEP also supports a SHRINE specific, RESTful API that is used by several of our tools including the Batch Query Tool and the Heartbeat monitor.
The QEP will authenticate all incoming requests according to the method specified in the QEP's configuration. In most cases, this involves checking with i2b2 PM cell to make sure that the credentials (i2b2 SessionKey) included with the request are valid. After authenticating the request, the QEP will forward that request on to the SHRINE Hub for broadcasting throughout the network.
Hub
Adapter
More content coming soon.
Overview
Content Tools