...

1.8.1 Release Notes

i2b2 1.8.0 Release introduces two major improvements to the platform that enhance usability and applicability: a redesigned and completely rewritten i2b2 Web Interface to improve the user experience, and 1 Release builds on the rewritten web interface introduced in 1.8 with new features and new administration tools, it introduces a powerful new data export module, and it adds core support for the OMOP data model on Postgres databases (adding to MSSQL and Oracle databases . These changes represent a major step forward in i2b2.in 1.8). 

Highlight of Features

Top New Features

Community-Contributed Features

Detailed Documentation on New Features

Data Exporter extension for i2b2

i2b2 Users can now create regular i2b2 queries using the webclient breakdown Data Request feature. The Options presented in the breadkdown are configurable in the database HIVE_CELL_Params to export a specific data set.export patient data for a patient set. The workflow involves breakdowns in the webclient, which allow users to request exports and data managers to generate exports. The export types and options are fully configurable in the database. Detailed documentation on set up can be found here: Data Exporter Set-up

The below steps describe the overall process:

• User logs into i2b2 webclient and runs a regular i2b2 query, checking the desired Data request breakdown option when running the query.
• E-mail is sent to the data manager and the User, informing them that the user's data request has been made.
• User selects a breakdown request option and selects run query.
• Email is sent to the data Manager
• The manager logs in and rerun reruns the user query by selecting with the Data Export breakdown selection to generate the export flat files.
• The generated export flat file is stored in a configurable location specified  in the HIVE_CELL_Params setting.on the i2b2 server.
• An e-mail Email is sent to the user manager confirming the file extract and how to access the files (which can be shared with the requester).

Steps to upgrade:

First, install the new war file. Next, upgrade the database. Because the upgrade requires loading some new content from the NewInstall, we have created an ant target to upgrade the data tables: upgrade_tables_release_1-8-0 This should be run from Upgrade/CrcData, e.g., ant f data_build.xml upgrade_tables_1 8-0 

Detailed upgrade instructions can be found here: Upgrade to version 1.8.1

ACT - V4.1 Ontology

The V4.1 Ontology includes total of includes  19 ontologies- 3 new and 11 updated and 5 unchangedSee ENACT Version 4.1 info for installation instructions.

Metadata and CRC zip files are provided to load the latest ENACT Version-4.1 ontology into your db schema using ANT scripts.

The CPT4 ontology table is not included with i2b2 due to AMA restrictions on redistribution of CPT code information. Contact the ACT ENACT team to get a copy if your institution is an AMA member.

...

1. Download and extract the newinstall zip package from "Download Binary Distribution" in the top section of https://www.i2b2.org/software
2. Edit the  edu.harvard.i2b2.data\Release_1-8\NewInstall\Metadata\db.properties file  file to update the project properties to 'ACT' ; db.project=ACT
3. From the edu.harvard.i2b2.data\Release_1-8\NewInstall\Metadata folder, run the ant command: ant -f data_build.xml db_metadata_load_data. This will execute the SQL scripts from the edu.harvard.i2b2.data\Release_1-8NewInstall\Metadata\act\scripts\<db type> folder to create and load the metadata tables 
4. From the edu.harvard.i2b2.data\Release_1-8\NewInstall\crcdata folder, run the ant command: ant -f data_build.xml db_demodata_load_data. This will execute the SQL scripts from the edu.harvard.i2b2.data\Release_1-8NewInstall\crcdata\act\scripts\<db type> folder to create and load the concept_dimension tabledimension 
5. Run  Run the scripts from the edu.harvard.i2b2.data\Release_1-8\NewInstall\Metadata \<dbtype>\scripts folder to load the  the Schemes, Table_access and QT_breakdown tables .access tables
6. You can now verify the new Ontology by logging into the webclient

Additional details on the ontology are available at this link.

ACT i2b2 on OMOP for Postgres database

ACT i2b2 on OMOP functionality uses ACT Ontology in the front-end and enables the i2b2 Software to run against Postgres database that uses the OMOP CDM architecture.  Documentation on loading the OMOP metadata, CRC tables, and CRC OMOP Views required to query the OMOP tables can be found here:  i2b2-on-OMOP With ENACT-OMOP Ontology v4.1

For historical reference on old 2018 OMOP installation , refer to OMOP Home on i2b2 Community Wiki

...

For enabling use of an OMOP database with i2b2, follow the instructions in the install guide for a new install of i2b2 using the i2b2-OMOP install option. The documentation here will guide you through this process. i2b2-on-OMOP With ENACT-OMOP Ontology v4.1

For historical reference on old 2018 OMOP installation , refer to OMOP Home on i2b2 Community Wiki

Changelog

Database Drivers

The JDBC drivers were updated to the following versions.

Supported Db Server versions

Supported software versions

Supported Operating Systems

 Rocky linux 8 and 9, CentOS versions  7

...

Unofficially, MacOS and other flavors of Linux are likely to work.

i2b2 Server and Client Changes

New Features and Improvements

i2b2 Database Changes

New Features and Improvements

Bug Fixes

Notes for Developers

For Java 11 install, if you change the xsd (REST API message definitions), then you will need to regenerate gensrc via JAXB in Java 8. In the i2b2-core cell directory for which you're regenerating the XSD-Java, run the ant target "jaxb_gen" on Java 8 and then build as usual using Java 11.

...