Population-Wide Analysis Bundle
Using SHRINE to perform federated queries of i2b2 data
This population-wide analysis bundle provides researchers with real-time access to data on large patient populations at multiple healthcare organizations. It includes i2b2, which enables query and analysis of data within an institution, and SHRINE (Shared Health Research Information Network), which is a federated query tool that connects different sites' i2b2 systems. In this bundle, patient-level data never leaves an institution. The patient data are stored locally within each site's i2b2 database, and only aggregate counts and statistics are shared with others in the network through SHRINE. The bundle also includes a common ontology called ACT (Accrual for Clinical Trials), which has been implemented in a SHRINE network with more than 50 institutions and 125 million patients.
Figure 1. High-level view of the bundle. The SHRINE Query Tool broadcasts queries to multiple i2b2 sites using a common ontology and returns real-time results.
Uses cases for this bundle include:
- Clinical trial optimization - Estimate the number of patients that can potentially be recruited for a trial based on inclusion and exclusion criteria. See how changes to those inclusion and exclusion criteria might affect a trial's ability to meet enrollment targets.
- Clinical trial recruitment - Identify sites that have patients who meet a trial's inclusion and exclusion criteria.
- Disease surveillance - Monitor outbreaks in infectious diseases.
- Health services research - Compare differences in standards of care across organizations.
- Rare disease studies - Find hospitals that have a sufficient number of patients to study a rare disease.
- Disparities research - Access diverse patient populations, including underrepresented groups.
- Epidemiology studies - Analyze population-wide trends.
- Pharmacovigilance - Identify rare adverse events related to a drug.
This bundle includes documentation on how to install and configure the following items:
- i2b2 - Local query tool
- Application Layer
- i2b2 Web Client
- Sample synthetic data
- SHRINE - Federated query tool
- Local components (database, application, SHRINE query tool)
- Optional hub components
- ACT Ontology - Common list of concepts shared across the network
A public demo of this bundle is available at the following URL:
Log in with the user demo and password demouser.
It consists of a 3-node SHRINE with Synthea demo data.
Figure 2. i2b2 components.
The SHRINE software consists of several parts (Figure 3). (1) At the site where investigators are forming queries (the Site Originating Query), there is a SHRINE Web Client and a SHRINE application called the Query Entry Point (QEP). The QEP authenticates the user, provides the Web Client with access to the ontology, sends queries to the SHRINE Hub, and polls the hub for results from sites. In SHRINE Version 3.0, the QEP does not have any dependencies on i2b2, except for using the i2b2 PM cell for authentication. It copies the ontology into a Lucene index to enable fast searches for concepts. In older versions of SHRINE, the Legacy Web Client used the i2b2 ONT cell to access the ontology. (2) The SHRINE Hub includes the main hub software and database that contains the configuration settings for the network. It also contains a Message-Oriented Middleware (MOM) component to support asynchronous communication across sites. (3) The sites that are running the queries and returning aggregate counts contain a SHRINE Adapter. This polls the SHRINE MOM for new queries and runs them on an i2b2 CRC cell. (This CRC cell also requires a PM and ONT cell to run, but these are not shown in the figure.) Usually sites that are running queries also have investigators that are forming queries. These sites have a single i2b2 instance along with the SHRINE Web Client, QEP, and Adapter.
Figure 3. SHRINE components.
The i2b2 and SHRINE components can be combined in different ways (Figure 4): (a) Most commonly, they are used to form a federated network, with a central SHRINE Hub, and each hospital having the items needed to both send queries to the network and respond to queries from other sites. Some sites also use the i2b2 Web Client to perform local queries that are not sent to other institutions. (b) An alternative approach is to use a central SHRINE Web Client and QEP. This simplifies the architecture of the network, but it requires sites to send their investigators to an external website to run queries, which might not be possible. (c) The same i2b2 instance at a site can participate in multiple networks by installing a SHRINE Adaptor for each network. (d) A single site can create a one-node network if they want to use the SHRINE Web Client as an alternative user interface for i2b2.
Figure 4. SHRINE configurations. (a) Federated network with a SHRINE Web Client at each site. (b) A centralized SHRINE Web Client. (c) A site participating in two SHRINE networks. (d) One site using the SHRINE Web Client as an alternative user interface for i2b2.
Key Technical Concepts
- Hub, node, and i2b2 architecture. A SHRINE bundle consists of nodes (for each distributed data source) and a hub (which coordinates communication to the hubs). Each node in the SHRINE setup will require both an installation of SHRINE and an installation of i2b2. The hub is a specially-configured SHRINE node and does not require i2b2.
- Ontologies in i2b2 and SHRINE. i2b2 data are organized into a hierarchy called an ontology. SHRINE 3.0 currently expects the data to follow the ACT ontology, a comprehensive ontology of 1.5 million terms developed for the ACT research network. Therefore each i2b2 instance in the SHRINE bundle must be configured for the ACT ontology.
- Certificates in SHRINE. Each SHRINE node generates a certificate that must be signed by the Hub and then stored in the keystore of both the Hub and that node. The Hub design eliminates a previous SHRINE requirement that all nodes have all other nodes' certificates.
- Firewall changes in SHRINE. SHRINE 3.0 uses a polling configuration, so SHRINE nodes do not need to make any firewall changes. (This differs from previous versions of SHRINE.) The SHRINE Hub must have a firewall exception so outside nodes can access the Hub base URL, in order to query the MOM.
- The data steward. The "data steward" is a component of the SHRINE software that supports detailed auditing of queries. Every SHRINE query must be assigned to a query topic (through the SHRINE application). Topics are created by users through the steward tool and can optionally require approval by an administrator before use. Then, administrators can view previous SHRINE queries in the steward tool, grouped by query topic.
- The AdapterMappings file. As discussed previously, i2b2 data is arranged into a hierarchy called an ontology, which is installed in the i2b2 database. SHRINE 3.0 includes its own version of the ACT ontology for network queries. The AdapterMappings file is an additional layer that allows the SHRINE version of the ontology to differ from the i2b2 version. It can be used for mapping local data, but it is generally not used because the i2b2 ontology itself can be used for mappings. Therefore this step is just to install a version of the file that maps the SHRINE version of the ACT ontology to the i2b2 version.
It is recommended to install SHRINE and i2b2 on separate machines, as they are both resource intensive. If you install them on the same machine, two versions of the Java JDK will need to be active (JDK 11 for SHRINE and JDK 8 for i2b2). So, a three-node SHRINE network requires a minimum of four virtual machines (one for each node and one for the Hub), but optimally seven (one for each SHRINE node, one for each i2b2, and one for the Hub).
Both platforms consist of a database layer, an application server layer, and a web-based client layer. i2b2 must be configured for use with the ACT ontology when used by this SHRINE bundle. High-level requirements for each of these are listed in the next subsections.
i2b2 requirements can be found here. A summary of the key requirements:
- Database: Oracle (>=11g), PostgreSQL (>=9), MSSQL (>=2012).
- OS: Windows, Mac, or Linux
- Software components: JDK 8, Wildfly 17, web server (no specific requirement)
SHRINE Nodes and Hubs
SHRINE requirements can be found here. A summary of the key requirements:
- Database: MariaDB >=5.5 or MySQL (preferred), MSSQL or Oracle (minimal support)
- OS: Linux
- Software components: JDK 11 (>=11.0.6), Tomcat 8.5 (for both web and application server)
Youtube Tutorial Videos
We have developed several Youtube tutorial videos that parallel the installation steps below.
- Install i2b2: https://www.youtube.com/watch?v=Oi9tlLVYXU8
- PostgreSQL ACT Ontology: https://youtu.be/np33ydjricg
- Synthea COVID19: https://youtu.be/RoMmL7-R14s
- SHRINE Node: https://youtu.be/TDVkf8N0R-E
There is a public demo of i2b2 available at https://www.i2b2.org/webclient/
- The latest version of i2b2 that is certified to work with SHRINE is v1.7.12a (as of 10/19/20).
- See compatibility matrix at https://open.catalyst.harvard.edu/wiki/display/SHRINE/SHRINE-i2b2+Compatibility+Matrix
- Binary distribution and quick install guide, under “download binary distribution”
- Or, download the source code from the same page.
- Follow the quick install guide (on https://www.i2b2.org/software/index.html) or the detailed install guide (https://community.i2b2.org/wiki/display/getstarted/i2b2+Installation+Guide). There are 3 components:
- It is essential to configure i2b2 with the ACT ontology, to be compatible with the current SHRINE 3.0 bundle. When installing i2b2 data, follow the instructions in the next section on installing the ACT ontology.
- Data (Chapter 3). Install the i2b2 database on MSSQL, Oracle, or Postgres. This provides many metadata tables for querying and authentication, as well as the actual core data tables.
- Server (Chapter 4). A Java program that runs in the Wildfly container which provides an API and data analytic methods on the database. It is divided into components called cells. SHRINE uses some of these cells: CRC to communicate to the database, ONT to provide the query ontology, and PM to manage authentication.
- Webclient (Chapter 5). A web interface to i2b2, which is not required for SHRINE but could be useful for local querying and testing (SHRINE is network-only)
Installing the ACT Ontology in i2b2
There is a public demo of the ACT ontology in i2b2 available at. https://dbmi-ncats-test01.dbmi.pitt.edu//webclient/
- 1. Install the ACT ontology (Metadata install). When installing the data for i2b2, each data installation script must have a db.properties file configured. A demo project with the ACT ontology can be installed by the i2b2 installer by simply changing db.project from demo to ACT in the Metadata and PM db.properties files. The Metadata install will install the ontology. See the documentation here (https://community.i2b2.org/wiki/display/getstarted/3.7.2+Set+Database+Properties)
- 2. Create an ACT project and add users to the project (Pmdata install). Repeat the above process with the db.properties file for the Pmdata. This will create the ACT project and add AGG SERVICE account and ACT user to the project. See also the documentation here: https://community.i2b2.org/wiki/display/RM/1.7.12a+Release+Notes#id-1.7.12aReleaseNotes-act-ontolog)
- 3. Add new dblookup rows (Hivedata install - happens always, no specific configuration needed) The hivedata for the ACT project (including CRC, Ontology and workplace) is inserted automatically when performing hivedata install. No specific configuration is needed. Or, this can be done manually, per the previously-referenced instructions: https://community.i2b2.org/wiki/display/RM/1.7.12a+Release+Notes#id-1.7.12aReleaseNotes-act-ontolog
- 4. Manually update the ACT user password from demouser to something more secure.
- 5. Update to latest version of ACT ontology (optional). The ACT ontology included in i2b2 is for demonstration purposes and might not be the latest. The latest version in production is available from https://dbmi-pitt.github.io/ACT-Network/ontology.html (see “Ontology Installation” and “COVID-19 Ontology”
- 6. Synthea demo data (optional). The i2b2-synthea data set provides some demo data in the ACT format that can also be installed. An alpha version of the i2b2-synthea data is available here: https://github.com/i2b2/i2b2-synthea
SHRINE node install
The SHRINE 3.0 install guide can be found here: https://open.catalyst.harvard.edu/wiki/display/SHRINE/SHRINE+3.0.0+Installation+Guide
It is divided into 14 chapters. Some notes on the steps for install are shown below:
- Chapters 1-5: Install JDK 11 (Java), Tomcat (the application server), and setup Tomcat to start automatically
- Chapter 6: Install MariaDB (a variant of MySQL), the SHRINE database (6.1), and configure database connections (6.2). Alternatively MSSQL or Oracle can be used but are not as well-supported.
- Chapter 7: Install the SHRINE software (.war file) into the Tomcat server.
- Chapter 8 and 9: Configuration.
- Create the shrine.conf config file in Tomcat.
- Create the i2b2 users.
- In shrine.conf:
- Set the URLs for the Hub and i2b2 connections.
- Set the nodeKey, which is just a short name for the node.
- Set the i2b2 hive credentials.
- Set a location/name for the keystore.
- Configure the data steward (chapter 9).
- Chapter 10: Install the ACT ontology. Because this was done when setting up i2b2, only step 10.2 (install the AdapterMappings file) is needed. Because the AdapterMappings file is generally not modified by local installations, this step is just to install a version of the file that maps the SHRINE version of the ACT ontology to the i2b2 version.
- Chapter 11: Optional step of changing the i2b2 "domain" so it is easier to determine the node from which queries originated.
- Chapter 12: Certificate exchange.
- The steps are, for each node:
- Generate a keystore (Chapter 12.0)
- Use the password and node name from your shrine.conf
- Create a certificate signing request (Chapter 12.1)
- Import the Hub CA certificate. Load each node's SHRINE CA certificate and CSR and sign the CSR. (Chapter 12.2)
SHRINE Hub Install
The SHRINE Hub is a special SHRINE node that coordinates communication between the nodes. To install it, follow the install instructions for a SHRINE node above and then the additional instructions below. The Hub does not require an i2b2 installation.
- Chapter 6: Additionally create Hub database tables in 6.3 - https://open.catalyst.harvard.edu/wiki/display/SHRINE/SHRINE+3.0.0+Chapter+6.3+-+Additional+Tables+for+the+Hub+Database
- Chapter 8: Additionally perform the other Hub configuration steps in 8.4 - https://open.catalyst.harvard.edu/wiki/display/SHRINE/SHRINE+3.0.0+Chapter+8.4+-+Configuring+a+Hub
- Chapter 12: Certificate exchange. The steps for certificates at the Hub are different from the nodes.
- Generate a CA certificate and distribute to all nodes
- Collect each node's CSR, sign them, store them in the local keystore, and distribute them back to the nodes.
- Example code to sign a CSR:
easyrsa import-req /tmp/shrine-node3.csr shrine-node3
Easyrsa sign-req server shrine-node3
- Chapter 13: Additional steps to add nodes to the hub
- A firewall port must be opened to the Hub's base URL
- When this is successful, nodes will be able to curl the Hub as in the first step in Chapter 13
- See the two "curl' commands listed as for Hub administrators
- A firewall port must be opened to the Hub's base URL
- No labels