1.8 Release Notes

i2b2 1.8 Release includes ACT/OMOP V41 Ontology download with easy ANT script install for MSSQL and ORACLE databases, a newly redesigned i2b2 Web interface, and bug fixes.

Highlight of Features

Top New Features

Community-Contributed Features

Detailed Documentation on New Features

ACT Version-4.1 OMOP Ontology data load

ACT V41OMOP metadata and CRC scripts along with OMOP views are now available for load into i2b2 db schema.

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

Ontology tables load process.

1. Download and extract the new install zip package from "Download Binary Distribution" section of https://www.i2b2.org/software
2. Edit the  edu.harvard.i2b2.data\Release_1-7\NewInstall\Metadata\db.properties file to update the project properties to 'ACT-OMOP'; example: db.project=ACT-OMOP
3. From the edu.harvard.i2b2.data\Release_1-7\NewInstall\Metadata folder, run the ant command: ant -f data_build.xml db_metadata_load_data
1. This will execute the SQL scripts from the edu.harvard.i2b2.data\Release_1-7\NewInstall\Metadata\act\scripts\<db type> folder and will create and load ACT-OMOP Ontology metadata tables 
4. You can now verify the new Ontology by logging into the web client.

OMOP views and Concept dimension load process

1. From the edu.harvard.i2b2.data\Release_1-7\NewInstall\Crcdata folder, run the ant command: ant -f data_build.xml db_demodata_load_data
1. This will execute the  BUILD_ACT_OMOP_Views _<dbtpye> script from the edu.harvard.i2b2.data\Release_1-7\NewInstall\crcdata\act-omop\scripts\<db type> folder and will create the OMOP views under the Views section in the database.
2. In addition, the corresponding ACT-OMOP concept_dimension data is populated by executing the scripts form the crcdata.zip folders.

              2.  You can now run queries against the OMOP data from the webclient

Totalnum counts execution

Load and execute file totalnum_usp/sqlserver/totalnum_fast_prep_OMOP.sql and run the following command:

exec totalnum_fast_prep_OMOP 'observation_fact','dbo','@

When finished, verify by checking that c_totalnum columns in your ontology tables contain numbers. These total counts will be visible in the ontology browser in the web client for 2b2 users with DATA_AGG user permission.

ACT OMOP Totalnum Scripts

Totalnum Scripts (patient counting scripts) have been updated to improve the counter's performance on both multiple ontology tables and very large(>1.5 million) ontologies  such as ACT medications. Debug messages have also been added for troubleshooting and profiling purposes. Support for multiple fact tables has been added and bugfixes have been made.

Totalnum Scripts Setup

1. If upgrading, create the totalnum and totalnum_report tables. In Release_1-7/Upgrade/Metadata, run the ant upgrade script.
   ant -f data_build.xml upgrade_tables_release_1-7-12a
2.  In the Release_1-7/NewInstall/Metadata/ run the ant script to create the stored procedures. 
   ant -f data_build.xml create_metadata_procedures_release_1-7 
3. Set privileges: If using multiple schemas, the stored procedure should be run from the metadata schema. Make sure the stored procedure can read the tables in the crcdata schema (observation_fact, visit_dimension, patient_dimension) and can both read an update ontology tables in the metadata schema (including table_access). 
4. If using multiple fact tables, the recommended approach is to create a fact table view as the union of all your fact tables. (This is essentially going back to a single fact table, but it is only used for totalnum counting. This is needed to correctly count patients that mention multiple fact tables within a hierarchy.)

       e.g., 
          create view observation_fact_view as
          select * from CONDITION_VIEW 
          union all
          select * from drug_view
   
   If running the counting script in SQL Server, add the wildcard flag, to ignore multifact references in the ontology:
         e.g. exec RunTotalnum 'observation_fact_view','dbo','@','Y'
   This is automatically accounted for in the other database platforms.
   Note this approach does not work if you have conflicting concept_cds across fact tables.

5. Run the stored procedures on your database. This can be done in two ways:
   • Run the ant command to execute the data_build.xml file with below specified target 
     POSTGRESQL : ant -f data_build.xml db_metadata_run_total_count_postgresql
     ORACLE : ant -f data_build.xml db_metadata_run_total_count_oracle
     SQL SERVER : ant -f data_build.xml db_metadata_run_total_count_sqlserver   
   • Execute the RunTotalNum  stored procedure manually against your database from a SQL Client. This can take several hours for large databases or large ontologies.  Examples are below.

When finished, verify it is complete by checking that c_totalnum columns in your ontology tables contain numbers (not nulls). These total counts will be visible in the ontology browser in the web client.

Parent folders will get counts (of all patients with facts in the leaves) except for ontology folders derived from visit_dimension or patient_dimension. These cannot be rolled up because of the way these terms are defined in the ontology. They will have no count at all (not a zero).

Improved CRC scripts execution Process

Prior to 1.8 release, CRC scripts via ANT execution command supported single CRC zip folder structure. 1.8 release will support multiple CRV zip folder execution. The databuild.xml has been modified for this process.

Changelog

Database Drivers

The JDBC drivers were updated to the following versions.

Supported Db Server versions

Supported software versions

Supported Operating Systems

CentOS versions 6 (deprecated) or 7 (highly recommended) 

Windows 7-2019

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.