...

This documentation is written without specific regards to the actual informatics network in which SHRINE is deployed. For network-specific information and configuration, please contact the support personnel appropriate to your network.

Considerations Before You Begin

We design SHRINE with default values for most settings to minimize customization. However, SHRINE supports some high-level customizations to better fit your institutions' practices.

Database

SHRINE provides schemas for downstream nodes that support mysql/mariadb, Oracle, and MS SQL server. See XXX.

Authentication

By default SHRINE uses the i2b2 PM cell to authenticate and authorize users. See XXX. Starting in SHRINE 4.0 SHRINE can be configured to use Shibboleth. See XXX.

Considerations for a Hub and Network

We only supply a mysql/mariadb schema for the hub's database.

SHRINE uses message-oriented middleware to support reliable asynchronous communication. By default a SHRINE network needs no additional configuration, but can be configured to use AWS SQS or Kafka to minimize the impact of hub maintenance. See XXX.