Release Management
Space shortcuts
Space Tools
Skip to end of metadata
Go to start of metadata

Printable version of this release note

i2b2 Release 1.7.10

Release Date: May 14, 2018

Release Summary

Release 1.7.10 contains several new enhancements to the i2b2 kernel, many of which improve the security around signing into the i2b2 Web Client. We have included some Auditing features like logging all successful and attempted logins into the i2b2 Web Client or keeping a log of all the Admin functions performed with the Admin Module.

Highlight of Features

  • Log admin and sign on activity
  • Lock users out after a specific number of failed login attempts
  • Require users to change passwords after a specified interval of time
  • Prevent users from using the same password when required to change it.
  • Enforce complex password requirements defined by the i2b2 Administrator.
  • Custom SQL Breakdowns
  • Temporal query made simple
  • Single sign-on
  • Improve datasource validation

Installation Note

The 1.7.10 Release Notes apply to you if you are upgrading your existing i2b2 system from an earlier version of the i2b2 software.

Type of installWhere you need to go next
Upgrading an existing i2b2 (currently installed at your site)
Please go to the  Upgrade Notes section for the details about upgrading your i2b2 software. 
Upgrading your i2b2 in a SHRINE networkPlease read the information in the SHRINE Networks section before proceeding.
Installing a new instance of i2b2. (Never installed it before)We recommend you refer to the i2b2 Installation Guide found on the i2b2 Community Wiki. The install guide will take you through the entire installation process.

If you run into issues or have questions you can reach out to the community by emailing the google group called i2b2 Install Help.


SHRINE Networks

WARNING

Release 1.7.10 has not been tested within a SHRINE network. Therefore, i2b2 Release 1.7.10 should not be installed within a SHRINE network. It can be installed independently of SHRINE. However because it has not been tested with SHRINE we can not guarantee all of the new enhancements will continue to work correctly when implemented within a SHRINE environment.

Upgrade Notes

Information about upgrading i2b2 to version 1.7.10 can be found in this section of the release notes.

 

i2b2 Components

In release 1.7.10 the following i2b2 components contain changes and therefore need to be updated when upgrading your i2b2 environment.

  • i2b2 Database
  • i2b2 Server (kernel)
  • i2b2 Web Client

 

Database Drivers

The JDBC drivers were updated to the following versions.

DriverNew Version
ojdbc8.jarOracle 1 2.2.0.1
postgresql-42.1.4.jarpostgres 42.1.4
mssql-jdbc-6.2.2.jre8.jarsql server 6.2.2

 

Upgrade Paths

The i2b2 now provides two options for upgrading your i2b2 server.

  1. Continue to download the source code provided in the zip file released on www.i2b2.org/software
  2. Install the precompiled JAR files onto your existing i2b2 server to upgrade it to 1.7.10.

Both are acceptable paths to upgrade your i2b2 server and depending on which you choose will determine where you need to go to obtain the appropriate files. The location of the upgrade files for each component is outlined below.

 

Upgrade Software

DescriptionWhere to find itRequirements
Upgrade i2b2 database to 1.7.10 Software page (i2b2 Website)Download i2b2createdb-1710.zip file under Source Code
Upgrade i2b2 Web Client to 1.7.10 Software page (i2b2 Website)Download i2b2webclient-1710.zip file under Source Code  
Upgrade i2b2 Server to 1.7.10 (Source Code) Software page (i2b2 Website)Download i2b2core-src-1710.zip file under Source Code  
Upgrade i2b2 Server to 1.7.10 (JAR files) Upgrade to Release 1.7.10 from 1.7.09c page (Community Wiki)See Technical Details section on the i2b2 Upgrades page and upgrade documentation on Upgrade to latest version page.


Upgrade Documentation

DocumentationWhere to find itWebsite
Database changes included in this release (star)Database Changes 
List of core changes included in this release (star)Change Summary - i2b2 Kernel (Core Software) 
List of Web Client changes included in this release (star)Change Summary - i2b2 Web Client 
Details about the new features (star)Details about New Features in Release 1.7.10 
Technical details and notes about upgrading the i2b2 serverUpgrade i2b2 pagei2b2 Community Wiki
Upgrade Instructions (server)Upgrade to latest version page (Instructions section)i2b2 Community Wiki
Core documentation - Technical doc for i2b2 cellsi2b2 Documentation zip file (i2b2core-doc-1710.zip)i2b2 Website/software

(star) These sections are located within this document. All other documents are external pages either on the community wiki or on the i2b2 Website.

Database Changes

Release 1.7.10 involves a few changes to the i2b2 Database. Some are simple an addition to the sample data that is included in the demo data that is delivered with the software while others are changes to the database structure to support new features that are included in 1.7.10

Crcdata Tables

QT_BREAKDOWN_PATH

  • Added new breakdowns for the new SQL Query Breakdown feature

QT_QUERY_RESULT_TYPE

  • Added new breakdowns for the new SQL Query Breakdown feature
  • Added new column to support roles based access for the new SQL Breakdowns
    • New column name = QT_ROLE_CD

Pmdata Tables

PM_USER_LOGIN table

  • Remove the primary key
  • Added the PM_USER_LOGIN_IDX index

Change Summary - Release 1.7.10

Did you know?

  • Changes to the i2b2 server & database are listed under i2b2 Kernel (Core) Software
  • Changes to the i2b2 Web Client are listed under i2b2 Web Client Software
  • Additional information about the new features can be found in the Feature Details - Release 1.7.10 section located this Change Summary section.

i2b2 Kernel (Core Software)

New Features and Improvements

 

key summary

JQL and issue key arguments for this macro require at least one Jira application link to be configured

 

Bug Fixes

key summary

JQL and issue key arguments for this macro require at least one Jira application link to be configured

 

i2b2 Web Client Software

New Features and Improvements

 

key summary

JQL and issue key arguments for this macro require at least one Jira application link to be configured

 

Bug Fixes

key summary

JQL and issue key arguments for this macro require at least one Jira application link to be configured

 

Feature Details - Release 1.7.10

Release 1.7.10 has many new features and for the purpose of this document we have grouped them into one of the following four categories:

  1. Auditing improvements
  2. Password management improvements
  3. Query improvements
  4. Miscellaneous improvements

Auditing improvements

The auditing improvements are part of a larger group of enhancements that are labeled in JIRA as "Security enhancements". There are only two auditing features and both involve keeping an audit trail of information for maintaining security. Right now the audit trail is limited to the i2b2 Admin module and the process of logging into the i2b2 Web Client.

 

The auditing improvements are strictly server and database security enhancements to capture the information for auditing purposes. The audit information is logged in the PM_USER_LOGIN table for both features. Due to different security requirements on who can access this type of database information we have chosen to not include a way for i2b2 users to view or print the audit information from within the i2b2. This decision may be reviewed again for a future release. For now, if a site wants to obtain the logged information they can query their i2b2 database and retrieve the information directly from the PM_USER_LOGIN table.

 


Log number of attempted logins

JIRA Issue: CORE-285

All successful and failed login attempts to sign into the i2b2 Web Client will be logged in the PM_USER_LOGIN table.

Highlights of New Feature

  • No additional setup is needed to turn the enhancement on
  • Even when a user is locked out the system will log when they attempt to access the system
 
Sample data from PM_USER_LOGIN table

  • The first row shows on 4/16/2018 at 11:12 in the morning the demo user tried to sign into the Web Client.
    • The "BADPASSWORD in ATTEMPT_CD column tells me they entered the wrong password and they were not successful logging in.
  • The second row shows one minute later the same user was able to enter their password successfully and log into the Web Client.

 


Log Admin Functions

JIRA Issue: CORE-286

Functions performed within the Admin module will be logged within the PM_USER_LOGIN table.

 

 
EXAMPLE

For the purpose of this documentation, the basic steps an i2b2 Admin rakes to add a new user outlined below:

Step 1: Signs into the i2b2 Web Client & select the Administrator project

Step 2: Selects Manage Users from the navigation panel

Step 3: Clicks on Add User button

Step 4: Enters information about the user and clicks on Save.

Step 5: Clicks on Manage Users to refresh the list and display the new user in the navigation panel.

 

As each step was performed, the service and USER_ID was logged in the PM_USER_LOGIN table along with the date & time (server side).

 

Password management improvements

The improvements to managing passwords are the other enhancements that are part of the larger group of "Security enhancements". There are four new features that are designed to help sites improve security of their i2b2 by improving how their user passwords are managed within the i2b2. The site administrators will now have control over requiring users to change passwords, use complex passwords, and lock users out for entering the wrong password too many times. 

4 New Features Include

  1. Account lockout
  2. Mandatory password change
  3. Prevent repeat passwords
  4. Enforce complex passwords

Account Lockout

JIRA Issue: CORE-287

Accounts are locked and users are not able to sign into the i2b2 after a specific number of failed login attempts have been made.

Highlights of New Feature

  • 2 new global parameters
    1. PM_LOCKED_MAX_COUNT
    2. PM_LOCKED_MAX_WAIT_TIME
  • Account lockout threshold and wait time is defined by the site Administrator.
  • Users are locked-out when the defined number of failed attempts have been reached.
  • Once locked
    • user receives a lockout message
    • user must wait a preset period of time
  • Successful login resets the number of failed logins

 

New Parameters

Two new Global Parameters were created as part of the new lockout feature. These parameters must be defined in the PM_GLOBAL_PARAMS table for users to be locked out after the defined number of failed attempts and number of minutes they must wait before attempting to try again.

 

PM_LOCKED_MAX_COUNT Parameter
  • Threshold for failed sign-in attempts
  • The value is inclusive. i.e. if you enter 4 then the 4th time the user enters the wrong password they will receive the error message and their account will be locked.

 

 

 

PM_LOCKED_WAIT_TIME Parameter
  • Number of minutes an account is locked before a user can sign in again.

 

 


 

Mandatory Password Change

JIRA Issue: CORE-287

Require users to change passwords after a specified interval of time. The i2b2 Administrator controls the number of days allowed before a password must be changed. If a user attempts to sign on after their password has expired, the i2b2 Change Password window will open and the user must change their password before they can sign on. Once the user changes their password, the system will calculate the next expiration date for that user.

Highlights of New Feature

  • Require users to change passwords
  • i2b2 Admins control how often (interval)
  • Change password window will open when password expired
  • 2 new parameters; 1 global & 1 user
  • The system uses the value in the global parameter to calculate the next expiration date and adds the appropriate user parameter to the table.

 

Summary of password expiration process

 

New global parameter is set (entered via the i2b2 Admin module).

Password expiration feature is turned on.

ALL user passwords are now expired.

User attempts to sign into the i2b2 Web Client; they are prompted to enter a new password

User enters a new password & successfully signs into the i2b2 Web Client.

Using the value defined in the global parameter and the date the user has signed on the system calculates the next expiration date for that user.

Once the new expiration date has been calculated the system will add a user parameter to the appropriate user with the correct expiration date.

 

 

New Parameters

Two new parameters were created as part of the Mandatory password change feature. Both parameters are called PM_EXPIRED_PASSWORD however one is set within PM_GLOBAL_PARAMS and the other within PM_USER_PARAMS. Each parameter has a different function in the password expiration process and is further defined below.

 

Table: PM_GLOBAL_PARAMS

The new Global Parameter called PM_EXPIRED_PASSWORD must be added to the PM_GLOBAL_PARAMS table to define the password change interval. Once this parameter has been set the mandatory password change feature will be turned on. If this parameter is not added as a global parameter then passwords will never expire.

 

 

 

Highlights of global parameter PM_EXPIRED_PASSWORD
  • Global Parameter PM_EXPIRED_PASSWORD
  • Turns the feature on
  • Defines password change interval
  • Affects ALL users

 

 

Table: PM_USER_PARAMS

The new user parameter, PM_EXPIRED_PASSWORD, is automatically added to the PM_USER_PARAMS table the first time a user successfully changes their expired password. When they change their password, the system will look to the PM_EXPIRED_PASSWORD parameter in the PM_GLOBAL_PARAMS table to see the change interval defined and then calculate the new expiration date to add to the user parameter.

 

 

Highlights of user parameter PM_EXPIRED_PASSWORD
  • User Parameter PM_EXPIRED_PASSWORD
  • Date password will expire for user
  • Added by system when password changed 1st time
  • Can be manually added / edited to a future date for user accounts don't want to expire

 

 

 

As soon as you add the PM_EXPIRED_PASSWORD to your PM_GLOBAL_PARAMS table, ALL passwords will expire except the i2b2 AGG_SERVICE_ACCOUNT. To prevent service accounts from expiring you need to add the user parameter as soon as the feature is turned on or even before it. Set the expiration date for a date in the distant future. The following steps outline how to do this.

  1. Log into i2b2 Admin Module
  2. Click on Manage Users in the left Navigation tree to expand the list of users
  3. Locate the user who is your service account
  4. Click on their name to expand it
  5. Click on Params
  6. Click on Add New Parameter button located on the right side of the page
  7. Add the PM_EXPIRED_PASSWORD parameter (example shown below).
  8. At Parameter Value enter a date far enough into the future that the password will not expire anytime soon.
  9. Click Save.

 

 


 

Prevent repeat password

JIRA Issue: CORE-300

Users are no longer allowed to use their current password as their new password when required to change it. 


Highlights of New Feature

  • No additional setup is needed
  • New password can't be same as current password
  • Warning message displayed if user enters same password

 

 


 

Enforce Complex Passwords

JIRA Issue: CORE-288

Passwords must meet complexity requirements defined by the i2b2 Administrator. The requirements will be enforced when users change their passwords for the Change Password Window. However, when an i2b2 Administrator is setting up a new user in the i2b2 Admin Module the requirements are not required when entering or editing the password in User Management.

Highlights of New Feature

  • New global parameter
  • i2b2 Administrator defines requirements for complexity
  • Requirements are enforced when users change passwords
  • User receives Warning message if new password doesn't meet requirements

 

 

 

New parameter

A new Global Parameter was created to support the Enforce Complex Passwords feature. The new parameter defines the complexity requirements for the passwords and once it has been entered into the PM_GLOBAL_PARAMS table the feature will be turned on for all users. This means all users will be required to follow the new requirements the next time they change their password. Again, the only exception is when the password is set by the i2b2 Administrator from within the i2b2 Admin Module.

 

Global Parameter: PM_COMPLEX_PASSWORD

Table: PM_GLOBAL_PARAMS

 

 

 

Complex Requirement Variables

Setting the parameter value for PM_COMPLEX_PASSWORD

  • Each password requirement is defined as an independent variable.
  • However, the variables are concatenated into a single string and stored in the VALUE column of the PM_GLOBAL_PARAMS table


The table shown below lists each of the variables and the associated requirement that will be enforced.

VariablesRequirement
(?=.*[0-9])Numbers (0-9)
(?=.*[a-z])Lower case letters (a-z)
(?=.*[A-Z])Upper case letters (A-Z)
(?=.*[!@#$%^&+=])Special characters (!@#$%^&+=)
(?=\S+$).{8,}Password is a string and must be 8 characters

The (?=\S+$).{8,} variable is always required when setting the PM_COMPLEX_PASSWORD parameter. The system needs to know that password is a string and the length of password. You do have the option to change the length to be greater or lesser than 8 characters.

 

The requirements can be used in any combination.  For instance, if the passwords must be 8 characters and contain at least 1 lower case letter and 1 number then the parameter value will be:

(?=.*[0-9])(?=.*[a-z])(?=\S+$).{8,}

 

If all the requirements in the table were to be used, the following would be entered as the Parameter Value:

(?=.*[0-9])(?=.*[a-z])(?=.*[A-Z])(?=.*[!@#$%^&+=])(?=\S+$).{8,}

 

 


 

Query improvements

The following two new improvements have been made to queries. 

  1. SQL Query Breakdown
    • Custom breakdowns based on SQL query
    • 4 new breakdowns provided in the demo data as examples
  2. Temporal Query made simple
    • New simple mode available
    • Streamlined

SQL Query Breakdowns

Standard demographic breakdowns have been available in the i2b2 for a long time. For instance, when running a query you can select breakdowns like Gender patient breakdown or Race patient breakdown.  Users have also been able to add their own custom breakdowns provided they added the breakdowns in all the appropriate places. In release 1.7.10 we are introducing SQL query breakdowns, which are basically your normal query breakdowns except they have a SQL query built within it. The i2b2 demo data that is delivered with 1.7.10 has been updated to include the following four new SQL query breakdowns 

  1. Length of stay breakdown
  2. Top 20 medications breakdown
  3. Top 20 diagnoses breakdown
  4. Inpatient and outpatient breakdown

 

Now that SQL queries can be run within a breakdown it has become necessary to provide the appropriate level of security to these breakdowns as we would a standard query. Therefore, we have taken the appropriate steps to enable sites to restrict custom breakdowns to a defined role. If the user does not have the appropriate role for the project they are logged into then they will not be able to see the breakdown listed when running a query.

The new SQL breakdowns included in 1.7.10 are restricted to the Limited Data Set (DATA_LDS) role.

 

For the most part setting up a new custom query breakdown will continue to be the same in that you still need to add the breakdown to the following places before you can begin using it.
  1. QT_QUERY_RESULT_TYPE table
  2. QT_BREAKDOWN_PATH table
  3. CRCApplicationContext.xml file

 

** New ** Additional Setup Steps for SQL Breakdown
There are two additional steps that need to be taken if you want to set up a SQL Query breakdown.
  1. Add SQL query into the QT_BREAKDOWN_PATH table
    • SQL statement goes into the VALUE column
  2. Add the correct access level into QT_QUERY_RESULT_TYPE table
    • The role goes into USER_ROLE_CD column

 

Sample Data: Snapshot of the Length of stay breakdown included in demo data

Define SQL in the QT_BREAKDOWN_PATH table

 

 

SELECT length_of_stay            AS patient_range,
   COUNT(DISTINCT a.PATIENT_num) AS patient_count
FROM visit_dimension a,
   DX b 
WHERE a.patient_num = b.patient_num
GROUP BY a.length_of_stay 
ORDER BY 1

 

Define the appropriate access level in QT_QUERY_RESULT_TYPE table

 

 

Running a Query and Viewing Results
  • Provided you have the correct access when you click on the Run button in the Query Tool, the Run Query window will display.
  • The list of Result Types, including the SQL breakdowns will display.

 

  • Check off the different breakdowns the results on the Graph Results tab will display as follows:


 

  • Click on the Query Report tab to view and print the results of your query.

 


 

Temporal Query made Simple

Running a temporal query in earlier versions of the i2b2 could be cumbersome and difficult to use. The way the screens were laid out would make it hard to remember population constraints, it was complicated, difficult to learn and hard to comprehend temporality.

In 1.7.10 temporal queries have been made simple by developing a Simple Temporal Query mode. This new mode has streamlined features; displays ordering of events and population constraint on same page.

 

Simple vs Advanced Mode

Simple mode does not support the following features

  • Non-linear temporal sequences
  • Multiple Panels
  • Number Restrictions

 

Highlights of New Simple Temporal Query mode

Query Timing list has been updated
  • Non-Temporal Query: Treat all groups independently
  • Non-Temporal Query: Selected groups occur in the same financial encounter
  • Temporal Query: Define sequence of Events

 

 

Tutorial Available
  • As soon as you select Temporal Query: Define sequence of Events the simple temporal query mode will display.
  • At this point you can either start the Tutorial or begin your query by dragging over an observation.



All events are on the same page page
  • Add Hypertension into Observation A and Acute Myocardial Infarction into Observation B.

 

 

Relationship Editor
  • Can edit the relationships without leaving the page.
  • Simply click on the text in between the two observations
  • The Temporal Relationship window will open with the observations visible behind it

 

 

Easily Change Order of Observations
  • Swapping position of Observations by dragging the panel

 

 

Adding population constraints (optional)
  • Can add population constraints without leaving the page.
  • Simply click on Show Constraining Population located at the bottom of the view
  • The standard 3 panel query view will open on the bottom half where you can add your patient sets.

                 

 

 

Switching to advanced mode
  • Click on Switch to Advanced Temporal Query to change your mode and query into the old temporal query.

 

 

Preserving query between switches
  • Queries will be preserved when switching between simple and advanced. The only exception is when a query doesn't meet the simple criteria (i.e. multiple panels, non-linear temporal sequences, number restrictions)

 

Miscellaneous improvements

Single sign-on location for Web Client and Admin Module

JIRA Issue: WEBCLIENT-226

 

The i2b2 Admin module no longer needs to be setup on the i2b2 server and results in the following benefits.

  • i2b2 Administrators will log in from the same location as the i2b2 Web Client.
  • Easier installation and maintenance. Will only install the i2b2 Web Client.

To sign into the i2b2 Admin module, Administrators will go to the same location as their i2b2 Web Client and enter their login credentials.  Provided their user is setup as an Admin they will be able to select "Administrator" from the list of projects in the project dialog. The Administrator project will launch the Admin module.

 

 


Improve datasource validations

JIRA Issue: CORE-129

On certain occasions a database connection in a pool would go bad and the i2b2 would continue to use the connection which would cause errors in the i2b2. To resolve this problem database connections will now be validated and checked that the connection is valid. If a connection in the pool goes bad the i2b2 will not continue using it.

 

MSSQL Example
<validation> 
     <validate-on-match>true</validate-on-match> 
     <check-valid-connection-sql>SELECT 1 FROM DUAL</check-valid-connection-sql> 
     <use-fast-fail>true</use-fast-fail> 
 </validation> 

 



i2b2 Release 1.7.09c

Release Date: January 12, 2018

Release Summary

Release 1.7.09c is a small release, however if you are a SHRINE user it does contain at least two important fixes that are necessary for you to run SHRINE queries without any issues.

  1. Date constraints on SHRINE queries are not save on the local i2b2 side. This causes a problem when users re-run the query as they will receive different results because the constraint no longer exists.
  2. Error would be returned if a query was still running when a user tried to view it in Previous Queries

Some other improvements include some minor bug fixes to the i2b2 Web Client

  • Cosmetic issues with the way information is displayed in the Web Client
  • New icons for the Wise plugin
  • Fix for possible null pointer when cancelling a query

Installation Notes

The 1.7.09c Release Notes apply to you if you are upgrading your existing i2b2 system from an earlier version of the i2b2 software.

Type of installWhere you need to go next
Upgrading an existing i2b2 (currently installed at your site)
Please go to the Upgrade Notes section for the details about upgrading your i2b2 software. 
Upgrading your i2b2 in a SHRINE networkPlease read the information in the SHRINE Networks section before proceeding.
Installing a new instance of i2b2. (Never installed it before)We recommend you refer to the i2b2 Installation Guide found on the i2b2 Community Wiki. The install guide will take you through the entire installation process.


If you run into issues or have questions you can reach out to the community by emailing the google group called i2b2 Install Help.

 

 

SHRINE Networks

       SHRINE Release 1.22.8 has been tested with i2b2 1.7.09c Release and has been approved by the SHRINE Team.

 

Upgrade Notes

Information about upgrading i2b2 to version 1.7.10 can be found in this section of the release notes.

 

i2b2 Components

In release 1.7.10 the following i2b2 components contain changes and therefore need to be updated when upgrading your i2b2 environment.

  • i2b2 Server (kernel)
  • i2b2 Web Client

 

Upgrade Paths

The i2b2 now provides two options for upgrading your i2b2 server.

  1. Continue to download the source code provided in the zip file released on www.i2b2.org/software
  2. Install the precompiled JAR files onto your existing i2b2 server to upgrade it to 1.7.09c.

Both are acceptable paths to upgrade your i2b2 server and depending on which you choose will determine where you need to go to obtain the appropriate files. The location of the upgrade files for each component is outlined below.

 

Upgrade Software

DescriptionWhere to find itRequirements
Upgrade i2b2 Web Client to 1.7.09c Software page (i2b2 Website)Download i2b2webclient-1709c.zip file under Source Code  
Upgrade i2b2 Server to 1.7.09c (Source Code) Software page (i2b2 Website)Download i2b2core-src-1709c.zip file under Source Code  
Upgrade i2b2 Server to 1.7.09c(JAR files) Upgrade to 1.7.09c page (Community Wiki)See Technical Details section on i2b2 Upgrades page and Upgrade documentation on Upgrade to 1.7.09c.



Upgrade Documentation

DocumentationWhere to find itWebsite
List of core changes included in this release (star)Change Summary - i2b2 Kernel (Core Software) 
List of Web Client changes included in this release (star)Change Summary - i2b2 Web Client 
Technical details and notes about upgrading the i2b2 serverUpgrade i2b2 pagei2b2 Community Wiki
Upgrade Instructions (server)Upgrade to 1.7.09c (Instructions section)i2b2 Community Wiki
Core documentation - Technical doc for i2b2 cellsi2b2 Documentation zip file (i2b2core-doc-1710.zip)i2b2 Website/software

(star)  These sections are located within this document. All other documents are external pages either on the community wiki or on the i2b2 Website.

 

Change Summary - Release 1.7.09c

Did you know?

  • Changes to the i2b2 server & database are listed under i2b2 Kernel (Core) Software
  • Changes to the i2b2 Web Client are listed under i2b2 Web Client Software
  • Additional information about the new features can be found in the Feature Details - Release 1.7.09c section located this Change Summary section.

i2b2 Kernel (Core Software)

Bug Fixes

CORE-235 – Previous query panel - find terms by patient number is returning incorrect results

CORE-273 – SHRINEACT queries with date constraints are losing the constraints on i2b2ACT side

CORE-276 – get Query result instance id not found error on a running query

CORE-279 – Single panel exclusion query returns error

 

i2b2 Web Client Software

Bug Fixes

WEBCLIENT-217 – Integers & fractional numbers can be entered for Max Time to Wait in Query Tool

WEBCLIENT-218 – Create new icons for the Wise plugin

WEBCLIENT-219 – Update text in alert message that appears when running a query without a name

WEBCLIENT-220 – Web Client possible null pointer

WEBCLIENT-221 – Fix three cosmetic issues with way information displays in Web Client

 

Tasks

WEBCLIENT-222 – Include new file for value box improvements

 

 



i2b2 Release 1.7.09b

Release Date: August 22, 2017

1.7.09b Release Summary

Release 1.7.09b fixes a problem where some users were not able to log into the i2b2 Admin module after installing version 1.7.09a. The logon problem only affected those users who downloaded the zip file from the i2b2 Software page. Users who downloaded the code directly from the i2b2 repositories do not have the issue.

The reason it only affects the zip file from i2b2.org/software is because we repackage the zip file from the i2b2-core-src repository to include the Admin module. When we add the Admin folder to the i2b2core-src-xxxx.zip file we have to modify some of the configurations. During this process one of the files was inadvertently updated using the wrong syntax to comment out some of the code. Release 1.7.09b fixes this problem with configuration file.

 
important Important

This release does not contain any changes to the standard i2b2 code. It is simply a modification to a configuration file that fixes a problem with not being able to log in to the Admin module.

If you downloaded 1.7.09a directly from the i2b2 repositories on gitHub then you do not have the issue with the configuration file and therefore you do not need to update your i2b2 with Release 1.7.09b
 
info Note

The i2b2 JIRA issue (WEBCLIENT-216) contains detailed information on the issue and the resolution. Attached to the JIRA issue is a document that outlines how to manually fix the file (only necessary if you don't want to download and install 1.7.08b).

Additional information on how to install the Admin on your i2b2 Server can be found in the INSTALL-README.md file located in the i2b2-webclient repository.

The bug fix (JIRA issue) included in this release can be found in the Change Summary - i2b2 Web Client Software section.

Installation Notes

  • This release note applies to you if you installed 1.7.09a and are not able to log into the i2b2 Admin module.
  • If you are installing 1.7.09b from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.09b does not contain code changes to any of the i2b2 software components. The release contains a fix to how a configuration file was packaged up wit the i2b2 Software.

Change Summary - i2b2 Web Client Software - Release 1.7.09b

Bug Fixes

  • [WEBCLIENT-216] - Some users are not able to log into the Admin Module



i2b2 Release 1.7.09a

Release Date: July 20, 2017

1.7.09a Release Summary

Version 1.7.09 of the i2b2 Software was incomplete when released. This resulted in errors being returned when compiling the Ontology Cell. Release 1.7.09a is the completed version of 1.7.09.

The bug fix (JIRA issue) included in this release can be found in the Change Summary - i2b2 Core Software section.

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.09a from an earlier version of i2b2.
  • If you are installing 1.7.09a from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.09a contains changes to the following software components:

  • i2b2 Server (core software)

Change Summary - i2b2 Core Software - Release 1.7.09a

Bug Fixes

  • [CORE-268] - Ontology cell fails to build when installing 1.7.09



 

i2b2 Release 1.7.09

Release Date: June 16, 2017

1.7.09 Release Highlights

  • Querying multiple observation fact tables
  • Support for the OMOP Common Data Model (CDM)
  • Minor bug fixes - see release notes for details

1.7.09 Release Summary

The standard i2b2 star schema only allows for one fact table, the observation_fact table. We have heard from the community there is a need to be able to search multiple fact tables with a single query. In release 1.7.09, the i2b2 has been updated to accommodate this growing need.

This new feature enables the i2b2 to adapt to the needs of the Patient Centered Outcome Research Institute (PCORI) network. It also supports the Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM).

The i2b2 Community Wiki has additional information about multi-fact tables and i2b2 on OMOP. The following links will take you to their respective space on the wiki.


A complete list of all the bug fixes and new features can be found in the Change Summary sections.

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.09 from an earlier version of i2b2.
  • If you are installing 1.7.09 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.09 contains changes to the following software components:

  • i2b2 Data
  • i2b2 Server (core software)
  • i2b2 Web Client

Change Summary - i2b2 Core Software - Release 1.7.09

New Features

  • [CORE-240] - Run queries using derived fact tables (Multi-fact table & OMOP)

Improvements

  • [CORE-262] - Clean up connection handling

Bug Fixes

  • [CORE-228] - Exception when running parallel queries using Postgres
  • [CORE-237] - Cant build timeline when db is postgres
  • [CORE-246] - Entries being written to the PM user session log at the same time will cause a query to error
  • [CORE-247] - PDO requests with empty filter list not working
  • [CORE-252] - Remove hard-coded timeout setting for medium and large queues
  • [CORE-253] - Multiple queues are created on startup
  • [CORE-254] - Queue startup needs to flush any previously running queues
  • [CORE-256] - OMOP Temporal queries with Excluded concepts dont work
  • [CORE-257] - Remove "dbo" from the ICD9-ICD10 install scripts (SQL Server)
  • [CORE-258] - OMOP: Error returned when trying to view details of an item on the timeline
  • [CORE-263] - PostgreSQL Error: Too many parameters specified for RAISE
  • [CORE-264] - OMOP Data Scripts - valueflag_cd is misspelled in the create_omop_views.sql
  • [CORE-265] - OMOP Data Views: Need to add a view for the Provider table
  • [CORE-266] - When multi-fact property not found, an ERROR is logged; should be INFO

Change Summary - i2b2 Web Client Software - Release 1.7.09

New Feature

Bug Fixes

  • [WEBCLIENT-154] - upon temporal query event selection, not able to drag and drop concept into anchoring observation if there are more than 3 grouppanels
  • [WEBCLIENT-207] - Max queries allows values <=0
  • [WEBCLIENT-210] - Cancelling the first query of a session causes error
  • [WEBCLIENT-211] - Query cancel causes prior query to be deleted
  • [WEBCLIENT-212] - PHP proxy does not support ports in automatic detection

Improvement / New Feature Details

Multi-fact tables

As stated earlier the standard i2b2 star schema only allows for one fact table, however [CORE-240] enables the crc to query multiple fact tables.

The setup is fairly simple; In the crc.properties file you will find a new parameter called queryprocessor.multifacttable, and when this parameter is set to true the crc will query all the fact tables you have setup.

The parameter is delivered with the value set to false, which means the multi-fact table feature is turned off and the CRC will behave as it has always done (prior to this release).

important Important
This same parameter is used by the i2b2 on OMOP project. For more information on this project please see the i2b2 on OMOP project space on the i2b2 Community Wiki.

Custom Value Choosing Handling

We are working on re-developing the way the lab value chooser works in the web client. The new implementation will allow for custom lab value handling in a modularized way. WEBCLIENT-206 is laying the ground work for this re-design. Users will not notice a difference on how they select lab values.

info Note
We are working on re-developing the way the lab value chooser works in the web client. The new implementation will allow for custom lab value handling in a modularized way. WEBCLIENT-206 is laying the ground work for this re-design. Users will not notice a difference on how they select lab values.



 

i2b2 Release 1.7.08b

Release Date: December 13, 2016

1.7.08b Release Summary

Release 1.7.08b fixes a bug in the CRC regarding when a query finishes running the BATCH_MODE in the QT_QUERY_INSTANCE table says PROCESSING INSTEAD OF FINISHED.

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.08b from an earlier version of i2b2.
  • If you are installing 1.7.08b from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.08b contains changes to the following software components:

  • i2b2 Server

Change Summary - i2b2 Core Software - Release 1.7.08b

Bug Fixes

  • [CORE-245] -BATCH_MODE says PROCESSING even though query finished running



 

i2b2 Release 1.7.08a

Release Date: November 23, 2016

1.7.08a Release Summary

Release 1.7.08a is primarily focused on fixing and improving the queueing process. The main issue addressed in this release is a fix for an issue that was introduced in 1.7.08; An error was returned when a query timed out and moved on to the medium queue. Although the query continued to run it was misleading to users as they were informed it generated an error an was therefore no longer running. A number of other issues were uncovered during the development and testing of this release. A complete list of each issue can be found in the section titled Change Summary - i2b2 Core Software

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.08a from an earlier version of i2b2.
  • If you are installing 1.7.08a from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.08a contains changes to the following software components:

  • i2b2 Server
  • important Important
    The changes to the queueing process were thoroughly tested against an Oracle and SQL Server database. Minimal testing was done against a PostgreSQL database.
  • i2b2 Web Client
info Note
The Web Client contains only one minor fix to the wording of an error message. Upgrading to the new Web Client is not essential for this release. Please see the Change Summary - i2b2 Web Client Software section to see what was changed.

Change Summary - i2b2 Core Software - Release 1.7.08a

Improvements

  • [CORE-241] - Queries will immediately move to the next queue when timeout is < or = to 0

Bug Fixes

  • [CORE-236] - Error returned when query times out
  • [CORE-242] - Queries are stuck in queue when previous query results in an error
  • [CORE-243] - Queries do not stop running when they time out of the large queue
  • [CORE-244] - Statuses are not updated when query times out or an error occurs

Change Summary - i2b2 Web Client Software - Release 1.7.08a

Bug Fixes

  • [WEBCLIENT-205] - Update date constraint warning message (patient_dimension)



 

i2b2 Release 1.7.08

Release Date: October 7, 2016

1.7.08 Release Summary

Release 1.7.08 contains a number of new features as well as bug fixes. Below are a few highlights of the changes included in this release. Information about the other changes can be found in the sections that follow this one.

JBoss Updated to WildFly

In order to address some of the security vulnerabilities that exist in some JBoss installations, the i2b2 Server has been upgraded to use WildFly. In 2014 Red Hat renamed their JBoss Application Server to WildFly and their latest version (WildFly 10) addresses the known security vulnerabilities.

info Note

The Third Party Software Changes section contains additional information on upgrading WildFly as well as other 3rd party software.

Although we recommend upgrading to WildFly, we do recognize that some sites may not be in a position to upgrade their existing JBoss 7. In the section labeled i2b2 Property Settings for WildFly 10 and JBoss 7 we have documented all the places you will need to modify the paths in order to use 1.7.08 with your existing JBoss 7. We have also included some additional information that you will need to be aware of before using 1.7.08 with your existing JBoss,

SQL Server: Option to Improve Query Performance

New parameter to use temp table constraint instead of 'WITH' clause.

Large data warehouses that contain broad and deep ontologies run the risk of CRC queries having a slow response time. In this release (1.7.08) a new parameter has been added to the crc.properties file. This new parameter allows a site to use a temp table instead of a 'WITH' clause when running a CRC query.

Additional information about this new feature can be found in the Improvement / New Feature Details section under the SQL Server: Option to Improve Query Performance heading.

Improvements to the Processing of Queueing Queries

In the Previous Query display, new statuses provide users with additional information that accurately reflects the current status and location of the query. The new statuses are:

  • SMALL_QUEUE
  • SMALL_QUEUE_RUNNING
  • MEDIUM_QUEUE
  • MEDIUM_QUEUE_RUNNING
  • LARGE_QUEUE
  • LARGE_QUEUE_RUNNING

In addition to updating the status of queries, an additional feature was added to the Web Client that makes these statuses visible to users. The query status can be seen in Previous Queries as well as in Show Query Status.

A complete list of all the statuses as well as additional information about this new feature can be found in the Improvement / New Feature Details section under the Improvements to the Processing of Queueing Queries heading.

SHRINE Approval

Shrine ApprovalSHRINE Release 1.21.2 has been tested with i2b2 1.7.08 Release and has been approved by the SHRINE Team

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.08 from an earlier version of i2b2.
  • If you are installing 1.7.08 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.08 contains changes to the following software components:

  • Database Scripts
  • i2b2 Server
  • i2b2 Web Client

Third Party Software Changes

In release 1.7.08 the i2b2 Server has been updated to use the following versions of third party software. These updates were done to address some security concerns with the third party software used by the i2b2

  1. Apache Ant has been upgraded to 1.9
  2. Apache Axis2 has been upgraded to 1.7.1
  3. Java JDK has been upgraded to 8.0
  4. JBoss has been upgraded to WildFly 10

3rd Party Software Versions and Links

The following table contains all the information needed to update your 3rd party software. In addition to the version information, the table contains links both to the Vendor's documentation as well as the appropriate chapter in the i2b2 Installation Guide located on the i2b2 Community Wiki.

3rd Party Software Version Download Link Vendor Documentation i2b2 Installation Guide i2b2 Notes
Apache Ant 1.9 Apache Ant 1.9 Software Ant's manual and API documentation is included in the binary distribution.
Apache Axis2 1.7.1 Axis2 1.7.1 Software Installation Guide Apache Axis2 Download the WAR Distribution File
Java JDK 8.0 JDK 8 Software Java JDK Reminder: Update your JAVA_HOME environment variable to point to JDK 8.0
WildFly 10 WildFly 10 Software Getting Started Guide

i2b2 Property Settings for WildFly 10 and JBoss 7

warning Warning
As stated earlier, the i2b2 team made the decision to upgrade to WildFly 10 and JDK 8 in order to address known security vulnerabilities with JBoss. In order for the i2b2 server (1.7.08) to work correctly, we recommend you update your environment to use WildFly 10 and JDK 8. However, if you are currently using JBoss 7 and do not want to upgrade your environment to use WildFly there are a few things you need to be aware of.
  1. Release 1.7.08 was not tested with JBoss 7, therefore we cannot guarantee the stability of the release if you continue to use JBoss 7. We can however confirm the i2b2 server (1.7.08) was tested with WildFly 10 and JDK 8 and does work correctly.
  2. JDK 8 does not work with JBoss 7. If you are upgrading to JDK8 then you have to upgrade to WildFly

If you are upgrading to WildFly and JDK 8 you need to do these upgrades before you upgrade your i2b2 server code.

The property settings delivered with i2b2 version 1.7.08 are pointing to WildFly. For those sites that are currently using JBoss 7 and are not ready to upgrade to WildFly 10 you will need to change the path information to point to JBoss 7. The files and properties that need to be modified are in the next section.

WildFly Property Modifications

CRC Cell Property Changes

File Name: crc_application_directory.properties
Location: edu.harvard.i2b2.crc/etc/spring/

WildFly 10 path: edu.harvard.i2b2.crc.applicationdir=/opt/wildfly-10.0.0.Final/standalone/configuration/crcapp
JBoss 7 path: edu.harvard.i2b2.crc.applicationdir=/opt/jboss-as-7.1.1.Final/standalone/configuration/crcapp

File Name: build.properties
Location: edu.harvard.i2b2.crc/

WildFly 10 path: jboss.home=/opt/wildfly-10.0.0.Final
JBoss 7 path: jboss.home=/opt/jboss-as-7.1.1.Final

File Repository Cell Property Changes

File Name: fr_application_directory.properties
Location: edu.harvard.i2b2.fr/etc/spring/

WildFly 10 path: edu.harvard.i2b2.fr.applicationdir=/opt/wildfly-10.0.0.Final/standalone/configuration/frapp
JBoss 7 path: edu.harvard.i2b2.fr.applicationdir=/opt/jboss-as-7.1.1.Final/standalone/configuration/frapp

File Name: build.properties
Location: edu.harvard.i2b2.fr/

WildFly 10 path: jboss.home=/opt/wildfly-10.0.0.Final
JBoss 7 path: jboss.home=/opt/jboss-as-7.1.1.Final

Identity Management (IM) Cell Property Changes

File Name: im_application_directory.properties
Location: edu.harvard.i2b2.im/etc/spring/

WildFly 10 path: edu.harvard.i2b2.im.applicationdir=/opt/wildfly-10.0.0.Final/standalone/configuration/imapp
JBoss 7 path: edu.harvard.i2b2.im.applicationdir=/opt/jboss-as-7.1.1.Final/standalone/configuration/imapp

File Name: build.properties
Location: edu.harvard.i2b2.im/

WildFly 10 path: jboss.home=/opt/wildfly-10.0.0.Final
JBoss 7 path: jboss.home=/opt/jboss-as-7.1.1.Final

Ontology Cell Property Changes

File Name: ontology_application_directory.properties
Location: edu.harvard.i2b2.ontology/etc/spring/

WildFly 10 path: edu.harvard.i2b2.ontology.applicationdir=/opt/wildfly-10.0.0.Final/standalone/configuration/ontologyapp
JBoss 7 path: edu.harvard.i2b2.ontology.applicationdir=/opt/jboss-as-7.1.1.Final/standalone/configuration/ontologyapp

File Name: build.properties
Location: edu.harvard.i2b2.ontology/

WildFly 10 path: jboss.home=/opt/wildfly-10.0.0.Final
JBoss 7 path: jboss.home=/opt/jboss-as-7.1.1.Final

PM Cell Property Changes

File Name: build.properties
Location: edu.harvard.i2b2.pm/

WildFly 10 path: jboss.home=/opt/wildfly-10.0.0.Final
JBoss 7 path: jboss.home=/opt/jboss-as-7.1.1.Final

Server-Common Changes

File Name: build.properties
Location: edu.harvard.i2b2.server-common/

WildFly 10 path: jboss.home=/opt/wildfly-10.0.0.Final
JBoss 7 path: jboss.home=/opt/jboss-as-7.1.1.Final

Workplace Cell Property Changes

File Name: workplace_application_directory.properties
Location: edu.harvard.i2b2.workplace/etc/spring/

WildFly 10 path: edu.harvard.i2b2.workplace.applicationdir=/opt/wildfly-10.0.0.Final/standalone/configuration/workplaceapp
JBoss 7 path: edu.harvard.i2b2.workplace.applicationdir=/opt/jboss-as-7.1.1.Final/standalone/configuration/workplaceapp

File Name: build.properties
Location: edu.harvard.i2b2.workplace/

WildFly 10 path: jboss.home=/opt/wildfly-10.0.0.Final
JBoss 7 path: jboss.home=/opt/jboss-as-7.1.1.Final

Change Summary - i2b2 Core Software - Release 1.7.08

Improvements

  • [CORE-214] - Upgrade JBoss to WildFly
  • [CORE-216] - Change GetTermInfo from a like clause to an equal clause
  • [CORE-221] - Improvements to the queuing process when running a query
  • [CORE-229] - Provide updated JDBC drivers used by Oracle, PostgreSQL, and SQL Server

New Features

  • [CORE-218] - New web service to retrieve the db lookup settings in the configuration files
  • [CORE-226] - New parameter to use temp table constraint instead of 'WITH' clause
  • [CORE-227] - Add ability to send parameters with string based variables as varchar instead of nvarchar

Bug Fixes

  • [CORE-151] - Modifiers associated to inactive terms appear as active in hierarchical tree
  • [CORE-184] - Generated SQL is not escaping single quotes correctly if a space exists between multiple values in C_DIMCODE
  • [CORE-206] - Query failing to time out into processing queue
  • [CORE-208] - qt_privilege primary key
  • [CORE-211] - Some large queries are remaining in the medium queue
  • [CORE-220] - SqlServer Age at Visit incorrect for 24, 80, 81 and 89
  • [CORE-230] - SQL Server: Issue with non-clustered index on temp tables

Documentation

  • [CORE-188] - Unable to change AGG_SERVICE_ACCOUNT password

Change Summary - i2b2 Web Client Software - Release 1.7.08

Improvements

  • [WEBCLIENT-133] - Restrict ability to add Date Constraint if a panel contains any age concepts.
  • [WEBCLIENT-192] - Improvements to queued queries in status window

New Features

  • [WEBCLIENT-191] - ADMIN: Add the ability to view DB_LOOKUP settings for each cell
  • [WEBCLIENT-198] - Parameters/Configurations for Web Client

Bug Fixes

  • [WEBCLIENT-98] - Updating the "Annotate" option is not reflecting on mouse hover
  • [WEBCLIENT-157] - Concept codes are displayed in tooltip even when the option is not selected
  • [WEBCLIENT-160] - Previous query panel right click menu is not not functional under Find tab and menu option display is persistant once displayed
  • [WEBCLIENT-161] - Max queries option under Previous queriesl/ontology terms panel allowing non integer and blank values
  • [WEBCLIENT-170] - Query run without selecting any run option is putting the query in processing queue
  • [WEBCLIENT-171] - query run with long name( more than 42 characters) is resulting in query time out and with larger number is giving sql error
  • [WEBCLIENT-175] - Group buttons at bottom of Query Tool will sometimes "disappear" after Printing the Query Report
  • [WEBCLIENT-180] - Set Modifier Value is not always an option when adding a previous query to the Query Tool
  • [WEBCLIENT-181] - Web Client doesn't fully logout when logging out after the timeout message
  • [WEBCLIENT-184] - "Not" does not appear if Group 4 or greater is excluded
  • [WEBCLIENT-189] - Modifiers repeat when prompted to increase number of terms in web client
  • [WEBCLIENT-190] - Modifiers associated to inactive terms appear as active in hierarchical tree
  • [WEBCLIENT-193] - Admin appears to crash when clicking on DB-Lookup for IM cell
  • [WEBCLIENT-195] - Fix names and fields that display on each of the new DBLookup pages
  • [WEBCLIENT-197] - New date constraint warning appears even if demographics are not in panel
  • [WEBCLIENT-199] - db_lookup

Change Summary - i2b2 Community Plugins - Release 1.7.08

Bug Fixes

  • [PLUGINS-17] - Plugins manifest is pointing to the wrong URL

Improvement / New Feature Details

View and Update the DB_LOOKUP Tables

JIRA ISSUES:
      [CORE-218] - New web service to retrieve the db lookup settings in the configuration files
      [WEBCLIENT-191] - ADMIN: Add the ability to view DB_LOOKUP settings for each cell

Release 1.7.08 added the ability to view current database connections defined in the DB_LOOKUP tables for each i2b2 cells. Administrators can also edit existing values and add new entries into the tables. This new feature resides within the i2b2 Admin Module. The DB_LOOKUP tables are specific to each i2b2 cell. To access the list of values in a specific cell you need to expand Manage Cells in the Navigation Tree on the left of the page. Then select the cell to expand further, once this is done you will see DB-Lookup as an option. Clicking on DB-Lookup will display the DBLookup List page. This page will display all the values in a table format.

The following screen shot shows all the entries in the CRC_DB_LOOKUP table.

To add a new entry into the DB_LOOKUP table simply click on the Add New DBLookup button that appears above the table of existing values. The page will be updated to a form with fields to capture the information to be stored in the DB_LOOKUP table.

To edit an existing entry, click on its Name located in the Navigation Tree on the left. The page will be updated to show the values currently filed in the DB_LOOKUP table. Make any changes and click on Save to save your edits.

Improvements to the Processing of Queueing Queries

JIRA ISSUES:
      [CORE-221] - Improvements to the queuing process when running a query
      [WEBCLIENT-192] - Improvements to queued queries in status window

In the i2b2, there are three queues a query may be placed into when it is run. The length of time a query waits in each queue is defined in the crc.properties file.

  1. Small Queue
  2. Medium Queue
  3. Large Queue

In the Web Client, the status of a query can be seen in Previous Queries. The status would be PROCESSING, ERROR, or COMPLETED. None of these statuses would provide information on which queue the query was in. Database administrators would have to view the query in the QT_QUERY_INSTANCE table to see the queue information. The statuses and queue information were often ambiguous which would make it challenging to trouble shoot any issues.

To address this issue, new statuses have been added in Release 1.7.08. These new statuses provide users with additional information that accurately reflects the current status and location of the query. The new statuses are:

    QUEUED ERROR COMPLETED PROCESSING SMALL_QUEUE MEDIUM_QUEUE LARGE_QUEUE MEDIUM_QUEUE_RUNNING LARGE_QUEUE_RUNNING RUNNING

In addition to updating the status of queries, an additional feature was added to the Web Client that makes these statuses visible to users. The query status can be seen in Previous Queries as well as in Show Query Status.

SQL Server: Option to Improve Query Performance

JIRA ISSUES: [CORE-226] - New parameter to use temp table constraint instead of 'WITH' clause

Large data warehouses that contain broad and deep ontologies run the risk of CRC queries having a slow response time. In this release (1.7.08) a new parameter has been added to the crc.properties file. This new parameter allows a site to use a temp table instead of a 'WITH' clause when running a CRC query. In some environments, using a temp table allows the query to run more efficiently and process the request faster.

Parameter Name: edu.harvard.i2b2.crc.setfinderquery.constraintlogic
Located in: crc.properties file
Behavior:

Value Behavior
TEMP or TEMPTABLES Temp tables will be used when building queries.
WITH Current query logic is used

If the parameter is missing from the crc.properties file, the system will current query logic (WITH clause).

Important
This change only affects SQL Server databases. Both PostgreSQL and Oracle do not have the capabilities of using temp tables. They will continue to use the WITH clause.

Date Constraint Improvements

JIRA ISSUES: [WEBCLIENT-133] - Restrict ability to add Date Constraint if a panel contains any age concepts.

In the i2b2, the CRC will use the START_DATE in the OBSERVATION_FACT table when running a query with a date constraint defined on a panel. This can present a problem if at least one of the items in the panel is an age concept and the patient demographics are stored in the PATIENT_DIMENSION table. The problem is ages that are stored in the PATIENT_DIMENSION table will not have a START_DATE and therefore the date constraint is not valid.

General i2b2 users do not know whether or not an age has a start date and if they select a date constraint their query may not return the expected results. This becomes a bigger issue when you are using the i2b2 in a larger network in which some sites may store it in the PATIENT_DIMENSION and others in the OBSERVATION_FACT. This scenario will definitely result in misleading results and the user will be unaware of the discrepancy.

To avoid any confusion or misleading results, users can no longer add a date constraint if at least one item in the panel is an age concept. The following message will appear when attempting to set a date constraint on a panel with an age concept: Date constraints are not allowed for age related concepts. This panel contains at least one age related concepts, therefore a date constraint can not be set for this panel."

Web Client Configurations

JIRA ISSUES: [ WEBCLIENT-198] - Parameters/Configurations for Web Client

In Release 1.7.08, a new configuration file has been added to the i2b2 Web Client. This file allows site administrators to customize the text on the login screens, default user id and password values, as well as how obfuscated results display in the i2b2 Web Client.

       File Name: i2b2_ui_config.js        File Location: /webclient/js-i2b2/

Parameter Description Default Value
titleLogoSrc Logo that appears in toolbar when logged into the i2b2 Web Client. "assets/images/title.gif"
loginHeaderText Text in the header bar of the login box "i2b2 Login"
loginUsernameText Text for the username input of the login box. "Username:"
loginDefaultUsername Default text inside the username input. "demo"
loginPasswordText Text for the password input of the login box. "Password:"
loginDefaultPassword Default text inside the password input. "demouser"
loginHostText Text for the PM cell dropdown of the login box. "i2b2 Host:"
obfuscatedDisplayNumber The number to display after the plus/minus for obfuscated results.
Please see the important note at end of this table.
3
useFloorThreshold If true, any result below floorThresholdNumber shows as '{floorThresholdText} {floorThresholdNumber}'
If false, floor threshold will not be used when displaying values in the i2b2 Web Client.
false
floorThresholdNumber Threshold for the low number of results 10
floorThresholdText Text that is prefixed before {floorThresholdNumber} (include trailing space) "Less Than "
Important
The calculation for the real obfuscation value continues to be controlled by the server and is based on the value defined in the CRC properties file. The obfuscatedDisplayNumber parameter in the i2b2_ui_config.js simply defines what number to display to the user when viewing the query results.

SQL Server: New Connection Parameter to Pass in String Based Variables

JIRA ISSUES: [CORE-227] - Add ability to send parameters with string based variables as varchar instead of nvarchar

Prior to release 1.7.08, parameters are sent in as Unicode (nvarchar) instead of varchar. SQL Server then has to explicitly convert the nvarchar to varchar in the query. The effect is that SQL Server optimizer may have to use an index scan instead of an index seek (which is faster).

To address this issue, we have added a new connection parameter to be used when i2b2 uses PreparedStatements to pass in string based variables in SQL Server. The following connection parameter is to be added to the datasource definition.

Connection Parameter: connection-property name="sendStringParametersAsUnicode"
Added To: datasource definition
Behavior:

Value Behavior
false String based variable will be sent as varchar
true Current logic is used; String based variable will be sent in Unicode (nvarchar)

Example:        <connection-property name="sendStringParametersAsUnicode" >false</connection-property>

Updated JDBC Drivers

JIRA ISSUES: [CORE-229] - Provide updated JDBC drivers used by Oracle, PostgreSQL, and SQL Server

Included in release 1.7.08 are updated JDBC drivers for Oracle, PostgreSQL and SQL Server. The new version of JDBC drivers are optional and will not be installed automatically.

Important
Sites that choose to upgrade their JDBC drivers will be required to also updated the datasource files for all of their cells.

Information on Updating Drivers

This section contains some general information and key points to keep in mind when updating your JDBC drivers.

Location of JDBC Jar files

Your current JDBC jar files reside in the following directories:

  1. ${jboss.home}/standalone/deployments/${axis2.war.name}/WEB-INF/lib
  2. ${jboss.home}/standalone/deployments
New Version of JDBC

There are three new jar files, one for each type of supported databases.

  1. Oracle = ojdbc7.jar
  2. PostgreSQL = postgresql-9.4-1209.jar
  3. SQL Server = sqljdbc42.jar
Update Existing i2b2 Instance

A script to deploy the new jar files has been included in the 1.7.08 Release. Once you have updated your server with the latest code you can run one of the following commands to deploy the new jdbc jar files:

Linux Command
      ant copy_new_jdbc_jar
Windows Command
      %ANT_HOME%\bin\ant.bat copy_new_jdbc_jar
Warning
If you choose to install the new JDBC jar files you also need to update your datasource files with the new driver information. This needs to be done for each cell in the i2b2 hive.

i2b2 Release 1.7.07c

Release Date: June 7, 2016

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.07c from an earlier version of i2b2.
  • If you are installing 1.7.07c from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

SHRINE Approval

Release 1.7.07c does not include any server changes and therefore does not affect SHRINE installations. This release does not need to be tested with the latest version of the SHRINE Software.

Upgrade Notes

i2b2 Release 1.7.07c contains changes to the following software components:

  • i2b2 Web Client
  • i2b2 Server - Admin code only
important Important
The Admin changes can be found in the i2b2core-src-1707c zip file located on the software page of the i2b2.org website. Please note that the other server components are included in this file. If you are upgrading from 1.7.07 then you do not need to update your i2b2 server as there are no changes. If you are upgrading from a release prior to 1.7.07 then you do need to install these other components.

Third Party Software Changes

No changes to third party software are included in release 1.7.07c

Change Summary - i2b2 Web Client Software - Release 1.7.07c

Bug Fixes

  • [WEBCLIENT-186] - Timeout message not returned when query runs longer than the defined 180 secs


 

i2b2 Release 1.7.07b

Release Date: March 1, 2016

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.07b from an earlier version of i2b2.
  • If you are installing 1.7.07b from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

SHRINE Approval

Release 1.7.07b does not include any server changes and therefore does not affect SHRINE installations. This release does not need to be tested with the latest version of the SHRINE Software.

Upgrade Notes

i2b2 Release 1.7.07b contains changes to the following software components:

  • i2b2 Web Client
  • i2b2 Server - Admin code only
important Important
The Admin changes can be found in the i2b2core-src-1707b zip file located on the software page of the i2b2.org website. Please note that the other server components are included in this file. If you are upgrading from 1.7.07 then you do not need to update your i2b2 server as there are no changes. If you are upgrading from a release prior to 1.7.07 then you do need to install these other components.

Third Party Software Changes

No changes to third party software are included in release 1.7.07b

Change Summary - i2b2 Web Client Software - Release 1.7.07b

Bug Fixes



 

i2b2 Release 1.7.07

Release Date: January 15, 2016

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.07 from an earlier version of i2b2.
  • If you are installing 1.7.07 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

SHRINE Approval

Shrine ApprovalSHRINE Release 1.20.1 has been tested with i2b2 1.7.07 Release and has been approved by the SHRINE Team

Upgrade Notes

i2b2 Release 1.7.07 contains changes to the following software components:

  • i2b2 Community Plugins
  • i2b2 Data
  • i2b2 Server
  • i2b2 Web Client

Third Party Software Changes

No changes to third party software are included in release 1.7.07

Change Summary - i2b2 Core Software - Release 1.7.07

Improvements

  • [CORE-118] - Increase number of queries that can be run in the "lifetime" of the database
  • [CORE-187] - Split the observation_fact_demo_insert_data script into smaller scripts
  • [CORE-194] - Split the icd10_icd9_diagnoses_insert_data script into smaller scripts
  • [CORE-201] - Update i2b2 demo data scripts to support Microsoft SQL Server 2012

Bug Fixes

  • [CORE-182] - Wrong datatype defined for some date fields in PostgreSQL create script(s)
  • [CORE-199] - PM Cell is not sending admin role unless a project is associated to the user
  • [CORE-202] - Some concepts in concept_dimension have synonym name
  • [CORE-203] - Restore requirement to look at M_APPLIED_PATH when retrieving modifier info from the Ontology Cell
  • [CORE-204] - Duplicate data in GitHub repo i2b2-data

Change Summary - i2b2 Web Client Software - Release 1.7.07

Improvements

  • [WEBCLIENT-143] - Add .HideBreak() & .getXNodeValNoKids() methods to webclient/js-i2b2/hive/hive_helper.js
  • [WEBCLIENT-144] - Concepts with a line break in their name are not displaying correctly in the Timeline
  • [WEBCLIENT-145] - Add reference for jquery-1.11.3.min.js in /webclient/default.htm
  • [WEBCLIENT-146] - New drop down that will display the list of plugins
  • [WEBCLIENT-155] - Add 'Delete Temporal Relationship' option to the define order of events screen
  • [WEBCLIENT-163] - Excluding a panel will now display 'NOT' in front of each item
  • [WEBCLIENT-168] - Add the ability to expand the Query Status view
  • [WEBCLIENT-172] - Add 'Close' button to new Plugins Menu
  • [WEBCLIENT-173] - Right-Click "Display" menu to load Previous Query

New Features

Bug Fixes

  • [WEBCLIENT-75] - Cannot delete event from temporal query once added in the webclient
  • [WEBCLIENT-100] - Bar graph overlaps number of patients when large patient set is displayed
  • [WEBCLIENT-102] - Print Query doesn't display name if printing a previous query
  • [WEBCLIENT-118] - Announcements do not display correctly in Internet Explorer
  • [WEBCLIENT-122] - Clicking on Login button with missing or invalid username/password is not displaying the right error message
  • [WEBCLIENT-125] - Wrong icon appears when dragging previous temporal query to Workplace View
  • [WEBCLIENT-127] - Breakdowns for obfuscated results are not displaying the obfuscation indicator (±3) in Graph Results
  • [WEBCLIENT-130] - Change Password link show to accounts logged in via AD
  • [WEBCLIENT-132] - Demographics (1 patient set) plugin
  • [WEBCLIENT-135] - Some metadata terms with special characters will not run in the query tool
  • [WEBCLIENT-136] - Date Constraints lost in webclient when executing a query created in workbench
  • [WEBCLIENT-138] - Timeline bugs
  • [WEBCLIENT-139] - Find - Search by Names for non-existent term does not return a message
  • [WEBCLIENT-142] - "Missing resource" error is being logged because prevQuery.jpg file is missing from /images/
  • [WEBCLIENT-147] - previous query run results tab displaying obfuscated indicator as '0±3' for counts <3
  • [WEBCLIENT-149] - Query rerun is failing when run as query-in-query
  • [WEBCLIENT-150] - Find - After Searching, the disappearing "Searching..." text logic is incorrect
  • [WEBCLIENT-151] - New events in temporal query not populating existing temporal relationships
  • [WEBCLIENT-152] - Creating multiple New Events without expanding Define Order of Events dropdown is broken
  • [WEBCLIENT-153] - Previous Queries with special characters do not run in Query Tool
  • [WEBCLIENT-158] - Minor typos in the webclient
  • [WEBCLIENT-176] - Blank Page opens in new tab when opening the i2b2 Plugin Gallery

Change Summary - i2b2 Community Plugins - Release 1.7.07

Improvements

  • [PLUGINS-12] - Export XLS: Add field to define delimiter when exporting data to .csv file

New Features

  • [PLUGINS-15] - Set up production repositories for all plugins

Bug Fixes

  • [PLUGINS-6] - Export XLS: Data does not appear in exported files
  • [PLUGINS-7] - CARE-Concept: Data does not appear in the exported files
  • [PLUGINS-8] - CARE-Observation: Data does not appear in the exported files
  • [PLUGINS-10] - CARE-Concept plugin doesn't display marital statuses
  • [PLUGINS-11] - CARE-Observation: Marital Statuses are not displaying
  • [PLUGINS-16] - Fix issue with double quotes in the manifests for several plugins


 

i2b2 Release 1.7.06

Release Date: August 12, 2015

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.06 from an earlier version of i2b2.
  • If you are installing 1.7.06 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.06 contains changes to the following software components:

  • i2b2 Server
  • i2b2 Web Client
  • i2b2 Workbench

Third Party Software Changes

No changes to third party software are included in release 1.7.06

Change Summary - i2b2 Core Software - Release 1.7.06

Bug Fixes

  • [CORE-149] - JDBC calls to interrupted threads throw sqlexceptions - Queries do not leave medium queue
  • [CORE-165] - Timeline filter not working if database is SQL Server
  • [CORE-180] - SHRINE queries will not run once i2b2 is updated to 1.7.05

Documentation Updates

  • [CORE-179] - Difference between documentation and table concept_dimension

Change Summary - i2b2 Web Client Software - Release 1.7.06

Bug Fixes

  • [WEBCLIENT-110] - Temporal queries do not print unless a population is defined
  • [WEBCLIENT-115] - IE Compatibility tag missing end tag and not within the header
  • [WEBCLIENT-116] - Graph Results display as "undefined" for obfuscated users
  • [WEBCLIENT-117] - Query Tool displays behind Query Status and Graph Results tabs
  • [WEBCLIENT-120] - Print query does not work in Internet Explorer for Previous Temporal Queries
  • [WEBCLIENT-121] - Previous temporal queries do not run in Internet Explorer
  • [WEBCLIENT-123] - Order of events not maintained when running a previous temporal query
  • [WEBCLIENT-124] - Clear in Query Tool does not clear correctly for Temporal Queries
  • [WEBCLIENT-126] - Only able to view the first two events when previous temporal query is added to the query tool


 

i2b2 Release 1.7.05

Release Date: May 6, 2015

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.05 from an earlier version of i2b2.
  • If you are installing 1.7.05 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.05 contains changes to the following software components:

  • Database Scripts
  • i2b2 Server
  • i2b2 Web Client
  • i2b2 Workbench

Third Party Software Changes

No changes to third party software are included in release 1.7.05

Change Summary - i2b2 Core Software - Release 1.7.05

Bug Fixes

  • [CORE-149] - JDBC calls to interrupted threads throw sqlexceptions
  • [CORE-156] - PM may not send the correct cell information when multiple projects and cells defined
  • [CORE-158] - JBoss server log contains password information when debug is turned on
  • [CORE-159] - Inconsistency in JBoss711Final and Install documentation
  • [CORE-166] - Hard coded references to I2B2DEMODATA in CRC install files
  • [CORE-167] - Metadata data install error
  • [CORE-169] - SHRINE Previous Queries: Path displays in Query Tool instead of item name
  • [CORE-174] - concept_dimension.concept_cd is nullable in postgresql implementation
  • [CORE-177] - Workbench may be using the wrong cell data when multiple projects and cells defined

Change Summary - i2b2 Web Client Software - Release 1.7.05

New Features

  • [WEBCLIENT-78] - Ability to refresh in PQ and workplace
  • [WEBCLIENT-80] - New view: Find Previous Queries
  • [WEBCLIENT-89] - New Graph Results view to display patient breakdowns in a graph

Improvements

  • [WEBCLIENT-85] - Display error message to user in Find for previous queries
  • [WEBCLIENT-86] - Indicator needed to inform users the system is searching when doing a Find
  • [WEBCLIENT-88] - Category names in Find (Previous Queries) can be misleading
  • [WEBCLIENT-103] - Add text wrapping capabilities to the i2b2 Web Client

Bug Fixes

  • [WEBCLIENT-73] - Wrong name displays when renaming a previous query in Workplace
  • [WEBCLIENT-76] - Update the I.E. Emulation that is defined in the Web Client <meta> tag
  • [WEBCLIENT-81] - Not able to select item from pop-up menu in Previous Queries
  • [WEBCLIENT-83] - Need message to say no results found
  • [WEBCLIENT-84] - Not able to search Previous Queries if "Any Categories" is selected
  • [WEBCLIENT-90] - Query Results not cleared when clear query in Query Tool
  • [WEBCLIENT-91] - Items are not staying with the pointer when dragged to another i2b2 view (Firefox only)
  • [WEBCLIENT-92] - Refresh icon needs to updated to one with transparent background
  • [WEBCLIENT-93] - Update the message that appears to users in Graph Results if using I.E. 7 or 8
  • [WEBCLIENT-94] - ONT - Containers Dragable by Default
  • [WEBCLIENT-95] - Help is not displaying in the Web Client
  • [WEBCLIENT-97] - Selecting temporal constraint selection "Same encounter" is not changing selection at the individiual group level
  • [WEBCLIENT-99] - Find view is not resizing properly
  • [WEBCLIENT-101] - Date picker calendar does not close unless you choose a date
  • [WEBCLIENT-105] - Previous Queries appear to be missing value constraints when dropped in Query Tool
  • [WEBCLIENT-106] - Observation details are missing when viewed in Timeline
  • [WEBCLIENT-107] - Graph Results panel temporarily attached to bottom of Show Query Status panel
  • [WEBCLIENT-108] - Value constraint window doesn't open in I.E. 11
  • [WEBCLIENT-109] - Web Client may be using the wrong cell data when multiple projects and cells defined
  • [WEBCLIENT-112] - Find Terms: Search by Code does not display results returned


 

i2b2 Release 1.7.04

Release Date: November 13, 2014

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.04 from an earlier version of i2b2.
  • If you are installing 1.7.04 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.04 contains changes to the following software components:

  • Database Scripts
  • i2b2 Server
  • i2b2 Web Client
  • i2b2 Workbench

Third Party Software Changes

No changes to third party software are included in release 1.7.04

Change Summary - i2b2 Core Software - Release 1.7.04

Improvements

  • [CORE-134] - Improve appearance of tooltips in Ontology Views
  • [CORE-136] - Jump to terms does not display modifiers
  • [CORE-142] - Add ability to add metadataxml to a modifier from within Edit Terms view
  • [CORE-144] - Add ability to expand inactive folders to view its children

Bug Fixes

  • [CORE-61] - The crc_loader (triggered via a web service) does not correctly load data into the patient dimension
  • [CORE-65] - Ontology term sorting order is case sensitive (should be case insensitive)
  • [CORE-106] - The tooltip boxes don't always close in the Timeline view
  • [CORE-107] - Duplicate concept appears multiple times in Timeline view
  • [CORE-108] - Times in the tooltips are not always updated
  • [CORE-109] - The contrast of the different bars of color in the timeline needs to be higher.
  • [CORE-110] - Full concept not displayed when hovering over it in the timeline
  • [CORE-112] - Remove hard coded link from the workbench code
  • [CORE-113] - Browser spelled incorrectly in error message returned
  • [CORE-114] - Date of birth column is displaying the date and time
  • [CORE-115] - Can't edit value constraints in timeline view
  • [CORE-130] - SQL stored procedure not inserting required data into PROJECT_ID
  • [CORE-131] - FRC Error - Unable to get 'destdir' from File Repository Cell
  • [CORE-132] - commons-dbcp.jar and commons-pool.jar are not present in i2b2 WEB-INF/lib directory
  • [CORE-139] - DEMO Data: Alkaline Phosphatase (ALP) lab tests are missing from Navigate Terms view
  • [CORE-145] - Users with LDS access can view de-identified data (i.e. reports)
  • [CORE-148] - Values no longer visible in timeline view
  • [CORE-150] - Left and Right arrows in previous queries not working correctly
  • [CORE-152] - Wrong approval displays when selecting an approval to edit in the Admin Tool
  • [CORE-153] - Only the first item in each section of a project request appears in the Admin Tool
  • [CORE-155] - Base code doesn't display in the Edit Term Wizard

Change Summary - i2b2 Web Client Software - Release 1.7.04

Improvements

  • [WEBCLIENT-67] - Add ability to expand inactive items to view its dependents / children

Bug Fixes

  • [WEBCLIENT-13] - Data & admin roles specified in Project Request plug-in are listed 'undefined' in admin detail view
  • [WEBCLIENT-50] - New Events for temporal queries are mislabled after using 'Clear'
  • [WEBCLIENT-64] - Can't drop previous temporal query into query tool if span of time defined in query
  • [WEBCLIENT-65] - Date constraint not available for Groups over Group3
  • [WEBCLIENT-72] - Synonyms issue in 1.7.04 release


 

i2b2 Release 1.7.03a

Release Date: August 28, 2014

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.03a from an earlier version of i2b2.
  • If you are installing 1.7.03a from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.03a contains changes to the following software components:

  • i2b2 Web Client

Third Party Software Changes

No changes to third party software are included in release 1.7.03a

Change Summary - i2b2 Web Client Software - Release 1.7.03a

Bug Fixes

  • [WEBCLIENT-68] - Panel timing on anchoring observations can be changed to treat independently or same encounter
  • [WEBCLIENT-69] - Print Query is only including the information for the first group / panel
  • [WEBCLIENT-70] - The concept associated with a modifier is not printing when you print the query


 

i2b2 Release 1.7.03

Release Date: August 20, 2014

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.03 from an earlier version of i2b2.
  • If you are installing 1.7.03 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.03 contains changes to the following software components:

  • i2b2 Server
  • i2b2 Web Client

Third Party Software Changes

No changes to third party software are included in release 1.7.03

Change Summary - i2b2 Core Software - Version 1.7.03

Bug Fixes

  • [CORE-143] - Do not require M_APPLIED_PATH when retrieving modifier information from the Ontology Cell

Improvements

  • [CORE-135] - Edit tool to file C_PATH and C_SYMBOL when adding new item
  • [CORE-141] - Remove carriage returns / line feeds from metadataxml when filing a term in Edit Terms view

Change Summary - i2b2 Web Client Software - Release 1.7.03

Bug Fixes

  • [WEBCLIENT-63] - Temporal Queries: Wrong description is displaying in the list of constraints for "On or After"
  • [WEBCLIENT-66] - Wrong operator sent for some temporal relationships

Improvement / New Feature Details

Edit tool to file C_PATH and C_SYMBOL when adding new item

JIRA ISSUES: [CORE-135]

In the i2b2 metadata table there are two columns (C_PATH and C_SYMBOL) that are used exclusively by the Ontology Mapping tool. Prior to release 1.7.03 these columns were not populated when you added a new term via the Edit Terms view. This situation has been rectified in that these columns will now be populated with the appropriate data when creating a new container, folder, term, or modifier from within the Edit Terms view.

Edit Tool view: Line feeds removed from Metadataxml

JIRA ISSUES: [CORE-141]

In the Edit Terms view users can create terms that have values associated to them. These values are stored in the C_METADATAXML column in the custom metadata table. Prior to release 1.7.03 when you created or edited a term with values in the Edit Tool view, the metadata was stored in the table with carriage returns / line feeds. This change improves the way the metadataxml if filed into the table by removing all line feeds from the data before filing it into the C_METADATAXML column



 

i2b2 Release 1.7.02

Release Date: July 1, 2014

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.02 from an earlier version of i2b2.
  • If you are installing 1.7.02 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.02 contains changes to the following software components:

  • Database Scripts
  • i2b2 Server
  • i2b2 Web Client
  • i2b2 Workbench

Third Party Software Changes

No changes to third party software are included in release 1.7.02

Change Summary - i2b2 Core Software - Version 1.7.02

Improvements

  • [CORE-95] - Password Management Enhancement
  • [CORE-123] - Update demo patient MRNs and sites

Bug Fixes

  • [CORE-26] - "Your account does not have access to any i2b2 projects" in admin webclient
  • [CORE-36] - Attempt to add a new CEL via the admin webclient fails
  • [CORE-80] - Date restrict on non obs_fact values not added to generated SQL
  • [CORE-86] - Ontology contains bad XML
  • [CORE-91] - PostgreSQL: Error executing CRC stored procedure CREATE_TEMP_PROVIDER_TABLE
  • [CORE-92] - Wrong user name entered in PM's datasource file for PostgreSQL and SQL Server examples
  • [CORE-93] - compare integer with varchar
  • [CORE-94] - Wrong built SQL statement causing SQLSyntaxErrorException at GetPDOFromInputList request
  • [CORE-97] - User and cell confguration (data) in the Admin module does not display in some browsers
  • [CORE-98] - Patient breakdown result types are not working when querying a PostgreSQL database
  • [CORE-99] - Cell data changes made in i2b2 Admin are not saved
  • [CORE-100] - Error executing CRC stored procedure CREATE_TEMP_PROVIDER_TABLE (PostgreSQL)
  • [CORE-101] - Error occurs when expanding an Encounter set in Previous Queries
  • [CORE-102] - PM datasource file has the wrong username listed in the example
  • [CORE-103] - Error returned from the CRC when running a query with result type of Encounter set
  • [CORE-116] - On Amazon Demo site, the Visit Detail AGE does not work
  • [CORE-120] - Change Password displaying in Managers Tool View
  • [CORE-125] - Query using concepts from the clinical trials folder always returns zero patients

Change Summary - i2b2 Web Client Software - Release 1.7.02

Improvements

Bug Fixes

  • [WEBCLIENT-27] - Wrong icon appears when dragging folder to Workplace View
  • [WEBCLIENT-43] - ontology cell concept navigation "Show Synonymous Terms" checkbox inconsistency
  • [WEBCLIENT-46] - Renaming shared folders doesn't work in the webclient
  • [WEBCLIENT-47] - "Delete Concept" in I2B2 web app deletes the first occurrence of the concept, not the one selected
  • [WEBCLIENT-51] - Only 1 temporal relationship sent in xml even though multiple are defined
  • [WEBCLIENT-52] - Modifier folders/containers don't work with i2b2 v1.7 and PostgreSQL
  • [WEBCLIENT-54] - When an item in the Term Navigator has more than a certain number of elements underneath, the arithmetic in the 'Need more items' dialog box is incorrect
  • [WEBCLIENT-55] - With error in data source the client runs on forever
  • [WEBCLIENT-58] - Operators do not default correctly when adding a temporal relationship
  • [WEBCLIENT-59] - Print Query not working in Chrome browser

Tasks

  • [WEBCLIENT-61] - Disable changing passwords on the demo site

Improvement / New Feature Details

Password Management

JIRA ISSUES: [CORE-95] and [WEBCLIENT-56]

In release 1.7.02, i2b2 users are now able to change their password from within the i2b2 Web Client and Workbench. Previously to this release, users did not have the ability to change their own password. They would have to notify their administrator who would have to change it for them in the i2b2 administration module. This new feature adds a layer of security in that the user can manage their own password and not have the added risk of other users (i.e. the admin) knowing their password.

important Important
If a user is setup to log into the i2b2 using either Active Directory or LDAP authentication methods then they will not be able to change their password from within the i2b2 Web Client or Workbench. If they need to change their password they will need to contact their site administrator and follow the protocols established at their institution.

This feature is only available for those users that log in with the standard i2b2 Authentication method.

In the i2b2 Web Client, a new option called Change Password now appears in the Web Client's toolbar.

Clicking on Change Password will open the i2b2 Change Password window.

In the i2b2 Workbench, a new button labeled Password has been added to the i2b2 desktop title bar.

Clicking on Password will open the Set Password window.

The functionality to change your password is the same regardless of whether you access the change password window from within the i2b2 Web Client or the workbench. There are basically three steps:

  1. Enter your current password.
  2. Enter a new password for your user.
  3. Retype your password.

Once you do the above three steps and click on OK the system will verify you entered your "current" password correctly and the password you entered at the New Password and Retype Password fields match. Provided everything is correct your new password will be saved.

info Note
Once you change your password you will need to log out of the Web Client or Workbench and log back in using your new password.


 

i2b2 Release 1.7.01

Release Date: February 4, 2014

Installation Notes

  • This release note applies to you if you are upgrading to 1.7.01 from an earlier version of i2b2.
  • If you are installing 1.7.01 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7.01 contains changes to the following software components:

  • Database Scripts
  • i2b2 Server
  • i2b2 Web Client

Third Party Software Changes

No changes to third party software are included in release 1.7.01

Change Summary - i2b2 Core Software - Version 1.7.01

Improvements

  • [CORE-88] - Confusing error message logged for non-Oracle users

Bug Fixes

  • [CORE-83] - Trying to build and compile i2b2 Server on Fedora Core 20 with Wildfly 8.0.0
  • [CORE-85] - Fresh install fails on PM Module and admin screen
  • [CORE-87] - Installation process needs to put database drivers in i2b2.war/WEB-INF/lib
  • Data Install: The stored procedures for PostgreSQL for the CRC Loader was enhanced and optimized.
  • Server Install: JDBC Drivers not copied correctly. When installing i2b2 server-common, the JDBC drivers were not copied into the i2b2.war/WEB-INF/lib directory.
  • CRC-Loader: Importing Visit Dimension Data. When using the CRC Loader, some primary key data such as inout_cd, location_cd, length_of_visit, etc, was not being imported correctly.

Documentation

  • [CORE-58] - Workbench 1.6 and default install
  • [CORE-77] - I2B2 installation Guide fixes
  • [CORE-90] - Install Documentation: Wrong schema configurations documented for a PostgreSQL database

Change Summary - i2b2 Web Client Software - Release 1.7.01

Bug Fixes

  • [WEBCLIENT-48] - Web client gets into non-functional state
  • Clicking on the Clear button does not return the Query Tool to the default settings. When a temporal query is created, and a user clicks on the clear button to start a new query, the Temporal Constraint is changed to "Define sequence of events" and it should default to "Treat all groups independently.
  • Date constraints not being stored with the previous query. When a date constraint was defined on a query the previous query would not maintain the constraint when you would use it to run another query.


 

i2b2 Release 1.7

Release Date: December 20, 2013

Installation Notes

  • This release note applies to you if you are upgrading to 1.7 from an earlier version of i2b2.
  • If you are installing 1.7 from a computer running the i2b2 Workbench, ensure that the workbench and all eclipse applications are closed prior to installing this release.
  • If you are installing a new instance of i2b2 we recommend you refer to the installation documentation found on the i2b2 community wiki. This documentation will guide you through the entire installation process.

Upgrade Notes

i2b2 Release 1.7 contains changes to the following software components:

  • Database Scripts
  • i2b2 Server
  • i2b2 Web Client
  • i2b2 Workbench

Third Party Software Changes

In release 1.7 the i2b2 Server has been updated to use the following versions of third party software.

  1. JBoss has been upgraded to 7.1.1
  2. Apache Ant has been upgraded to 1.8.2
  3. Apache Axis2 has been upgraded to 1.6.2
warning Warning
Only the i2b2 Server was upgraded to use the above versions of JBoss, Ant, and Axis2. The i2b2 Workbench will continue to use the previous versions. As a result, the source codes for the server and the workbench client have different plug-ins for the commons.

Server edu.harvard.i2b2.server-common

Client edu.harvard.i2b2.common

Change Summary - i2b2 Core Software - Release 1.7

Improvements

  • Find Terms: New feature called "Jump to Term in Tree"
  • Previous Query: Filter list by user
  • Previous Query: Search Previous Queries View
  • Previous Query: Page through previous queries by date
  • Database: PROJECT_ID Column added to PATIENT_MAPPING and ENCOUNTER_MAPPING tables (support for new IM cell)
  • Demo Data: Updated PATIENT_MAPPING table to support the new IM cell.

New Features

  • Temporal Queries (New Temporal Query Tool View)
  • Identity Management Cell (IM)
  • Identity Management Tables
  • Managers Tool View
  • OpenEMPI Support
  • Patient Mapping View
  • Patient Sets View
  • PostgreSQL Database Support
  • Workplace Find View

Bug Fixes

  • [CORE-5] - CRC build from source deposits i2b2Common-core.jar in wrong directory
  • [CORE-70] - I2b2 compilation of CRC Cell fails
  • [CORE-74] - Typo in i2b2_config_data.js of admin interface
  • [CORE-81] - No PATIENT_NUM in OBSERVATION_FACT_PK (conflict with documentation)

Documentation

  • Architecture, design and messaging documents for the new Identity Management (IM) Cell.
  • Design documentation for the new Temporal Query Tool plug-in.
  • User guide for the new Temporal Query view.
  • Documentation for the new views (Patient Set, Patient Mapping, Managers Tool, and Find in Workplace).
  • [CORE-8] - Suggestions for improvements to installation documents
  • [CORE-75] - CRC_Design.pdf page numbers are broken, all page numbers are set to 1 of 1, 2 of 2, etc. instead of 1 of xx
  • [CORE-78] - Errors in I2B2 Hive Installation Guide v 1.7.0

Tasks

  • [CORE-45] - Establish CRCLoader project (eclipse) from exiting ant build file failed

Change Summary - i2b2 Web Client Software - Release 1.7

New Features

  • Temporal Queries (Modification made to existing Query Tool)

Documentation

  • [WEBCLIENT-40] - Webclient: documentation should state that php and curl are prerequisites for the webclient

Improvement / New Feature Details

Temporal Queries

The temporal query is a new type of query introduced in release 1.7. There are two components to these queries that make them a little more complex than the type of queries available prior to 1.7 (classic i2b2 queries).

The first component to these queries is the list of events defined by the user.

The second component is the relationship between the events. This relationship is referred to a Temporal Relationship, which is best described as how the different events relate in regards to the time in which the event(s) occurred.

Users can also define a patient or event population in which they wish to run the temporal query against. This step is optional and is not required in order to run the temporal query.

The process in which temporal queries are defined is slightly different in the i2b2 Web Client and the i2b2 Workbench. In the i2b2 Web Client the existing Query Tool view has been modified to accommodate Temporal Queries while a new view called Temporal Query Tool view has been created for the i2b2 Workbench.

The new Temporal Query Tool view and the modifications to the existing Query Tool view extend the query functionalities provided by the classic Query Tool view.

It is important to note that while the manner in which users setup a temporal query is different in each of the clients the overall functionality is the same.

The following two sections will describe how to run Temporal Queries in the i2b2 Web Client and the i2b2 Workbench.

i2b2 Web Client: Temporal Queries

In the i2b2 Web Client there are five basic steps in defining a temporal query in the Query Tool view.

  1. Change Temporal Constraint to Define sequence of Events.
  2. Define Population in which events occur (optional step).
  3. Define Events
  4. Define order of events (temporal relationships)
  5. Run the query
info Note
For detailed information about creating Temporal Queries please see the Temporal Query help file located on-line from within the i2b2 Web Client.
Step 1: Change Temporal Constraint

The first step is to change the Temporal Constraint to Define sequence of Events.

Step 2: Define Population in which events occur

Once you have changed the Temporal constraint to be Define sequence of Events a new Page selection box will appear below the Temporal Constraint section. The default page will be Population in which events occur. It is on this page you will define your population requirements.

Step 3: Define Events

The events are the first component of a temporal query. There are no restrictions on the number of events you wish to define. The only requirement is that you have to define at least two events.

To define the events simply click on the Page selection box and select Event 1 from the drop-down list.

The groups and constraints for the events work in the same manner as they did for a traditional i2b2 query. Simply drag the items you want to include in Event 1 to the appropriate groups.

Once you have added your items to the groups you can click on the Page selection box and select Event 2 from the drop-down list. This will change the page to display the groups for Event 2.

If you need to add a third event you can click on the New Event button located next to the Page selection box.

Step 4: Define Order of Events (Temporal Relationship)

As stated earlier the second component of a temporal query is the relationship between the events (temporal relationship). In the i2b2 Web Client this is done on the Define order of events page, which is accessed by clicking on the Page selection box and selecting Define order of events from the drop-down list.

The page will display as follows:

Step 5: Run Query

In the Web Client running a query works the same regardless of whether or not it is a Temporal Query or a traditional i2b2 query. By clickin on the Run Query button, the i2b2 client will send the request to the i2b2 server which will run the query as defined.

i2b2 Workbench: New Temporal Query Tool View

In the i2b2 Workbench there are three pages or steps in defining and running a temporal query in the new Temporal Query Tool view.

  1. Page 1: Define Population
  2. Page 2: Define Temporal Relationships
  3. Page 3: Review and Submit Query

i2b2 Workbench: New Temporal Query Tool View

Define Date Constraints and Exclusions in Temporal Query Tool View

Defining the Date Constraints
Exclude Panel

Each page as well as defining constraints is further defined in the next few sections.

info Note
For detailed information about using the Temporal Query Tool view, please see the help file for this view which is available on-line from within the i2b2 Workbench.
Page 1: Define Population

On this page you will define your population requirements.

Page 2: Define Temporal Relationships

As stated earlier there are two components to a temporal query; (1) List of events and (2) the relationship between the events.

The second page is where you will define both the events and their relationship.

Page 3: Review and Submit

On this page the name of the query will default and if you wish to rename it you can do so at this point. Whatever is entered here will be the name given to the query when it is run. In addition you can select the Analysis Types that you want when running the query.

Defining Date Constraints and Exclusions in Temporal Query Tool View

There are some minor differences in terminology or layout that needs to be noted in this release note.

Defining the Date Constraints

In the classic Query Tool view you can only define date constraints on the group / panel level. In the new Temporal Query TOol view you can now define a date constraint on either the query or group levels. If you define it on the query level it will default the same date constraint for all the groups and the date constraint on the panel level will not be available for selection.

If you want to define it on the panel level select Group-Specific. Go to the group you wish to define the constraint and click on the column that displays No Date Constraints.

Exclude Panel

The ability to exclude all items in a group does exist in the new Temporal Query Tool view. However, the method in which it is defined differs between the classic Query Tool view and the Temporal Query Tool view.

In the existing Query Tool view ("Classic") the exclusion constraint was defined by clicking on the button labeled Exclude.

In the Temporal Query Tool view (New) the exclusion constraint was rolled into the window for defining the Occurrence constraint.

The Specify Occurrence Constraints windows will open when you click on the box that displays the occurrence constraint. To set the exclusion constraint you need to select "= 0 (No Occurrences)" from the drop-down list.

The above option is equivalent to the Exclude feature in the classic Query Tool view.

Previous Query: Filter list by user

New in release 1.7 is the ability to filter the list of previous queries by the user who created the query. In the options dialog (Options Icon) window there is a new field called Get previous queries for user. The default is all users and can be changed to a specific user by clicking on the down arrow to display the drop-down list. Once you select the user and click on OK, the Previous Queries view will refresh and display only those previous queries created by the selected user.

important Important
In i2b2 only managers are allowed to view queries for another user, therefore this feature is only available to those users who have the role of MANAGER defined for the project. If a user does not have the manager role then this field will be inactive and unavailable for selection.

Previous Query: Search Previous Queries View

In release 1.7 the ability to search the Previous Queries view has been added. The functionality is very similar to Find Terms view except it will search the Previous Queries view instead of Navigate Terms view. Users can search any of the three levels;

  1. Previous Query (name)
  2. Previous Query Result
  3. Patient

Previous Query: Page through previous queries by date

Users can now retrieve the next or previous grouping of previous queries by the date in which the query was created.

The Previous button (Previous Button) will retrieve the group of previous queries that occur prior to the date displayed in the date / time field.

The Next button (Next Button) will retrieve the group of previous queries that occur after the date displayed in the date / time field.

Identity Management Cell (IM)

A new cell called the Identity Management (IM) Cell was developed in release 1.7. This new cell contains Protected Health Information (PHI), which can be used to identify patients. The IM cell is used to manage this PHI in a manner consistent with the HIPAA privacy rule. The patient data will be available only as a HIPAA defined "Limited Data Set" to most of the hive.

The full functionality of the IM cell will be developed in stages. The initial framework and key services are released as part of the 1.7 release. Some of the key features being released in 1.7 are:

  1. New tables to store identifiers from different sites, and patients that are included in a project.
  2. Audit controls are implemented that are in compliance with the HIPAA privacy rules.
  3. Services developed to set and validated an AES key for encrypting and decrypting patient MRNs in the IM cell.
  4. Unencrypted patient identifiers sent in the PDO can be processed through the IM cell to retrieve all site IDs for the patient and project.

In addition to the above features, the i2b2 Worbench (eclipse client) has two new views that were created to support the new IM cell. These new views, called Patient Mapping and Admin Tool are further defined in the following two sections called Patient Mapping View and Admin Tool View.

Managers Tool View

The Managers Tool view was developed in release 1.7 and works in conjunction with the IM Cell. It currently has two main functions.

  1. Set and / or validate that the project key is defined in the IM Cell.
    • The project key is used by the IM cell to decrypte the patient id"s that are encrypted.
    • The Set Key is used to define the key in the IM cell.
    • The Validate Key is used to verify the key is set.
    important Important
    If you are using the IM cell and your patient identifiers are encyrpted the you need to set the Project key in the IM cell. It is important to note that if you restart your i2b2 server or in the case of the VM image restarting the virtual machine then you will need to re-enter the project key.

    The project key for the i2b2 demo project is: i2b2demodatakey1

    In the VM image you need to log into the i2b2 Workbench as the i2b2 Admin user.

    User ID: i2b2
    Password: demouser

  2. View the audit information.
    • As part of the IM cell an audit table was created to track when a patient in the IM cell was accessed. This new view allows Project Managers or Administrators to run a report to see that audit information. The report can be run for a particular user, patient, or all audit information for the project you are logged into.

Patient Sets View

In release 1.7 a new view called Patient Sets was created. This new view will display a list of Patient sets that were created when a query was run. It is similar to the Previous Queries view except it only displays the patient sets and not the previous query or other result sets (i.e. Encounter sets, Number of patients, etc).

The patient sets can be expanded to display a list of patients.

Users can drag an entire patient set or a single patient to other views in the i2b2 Workbench.

Users can also perform a search in which they can search by the name of the patient set or for a list of patient sets that contain a specific patient.

Workplace Find View

A new view called Find in Workplace was created in release 1.7. This view is very similar to the Find Terms view except it will search the Workplace view instead of the Navigate Terms view.

Find Terms: New feature called "Jump to Term in Tree"

A new feature called Jump to Term in Tree has been added to the Find Terms view. Users can now easily jump directly to a term in the Navigate Terms view from the Find Terms view.

Once a term is found in the Find Terms view the user can click on the term using the right mouse button to display the pop-up menu. Selecting "Jump to Term in Tree" from the pop-up menu will bring the Navigate Terms view into focus and the hierarchical tree will automatically open to the location of the term selected in the Find Terms view.

OpenEMPISupport

OpenEMPI is an open source Enterprise Master Patient Index (EMPI) which is developed and supported by another community. The i2b2 IM cell has been developed to allow communication with OpenEMPI for those sites that choose to use it as their patient repository.

For additional information on OpenEMPI please see their website by going to the following location: https://openempi.kenai.com/

PostgreSQL Database Support

The ability to use a PostgreSQL database as an i2b2 database has been added to release 1.7. Both the create and insert data database scripts for PostgreSQL are included in this release.

Data: New Tables created for the IM Cell

The following new tables were created as part of the new IM cell.

Table Name Description
IM_MPI_DEMOGRAPHICS Contains General demographic information for the patients.
IM_MPI_MAPPING Maps the patient"s i2b2 number and the local MRN.
IM_PROJECT_SITES Contains information about the different sites (Source Systems).
IM_PROJECT_PATIENTS Stores the patients that are part of a project(s).
IM_AUDIT Stores the audit details of patients accessed in the IM cell. This includes; the user, site, and project requesting the access as well as the date in which it was accessed.

Data: New Columns added to support IM cell

A new column called Project_ID has been added to both the PATIENT_MAPPING and ENCOUNTER_MAPPING tables in the crc. The PROJECT_ID was added to support the IM cell. It will allow sites to track which project a patient is part of.

Data: Improved Patient Mapping Data

The PATIENT_MAPPING table in the CRC has been updated to include the following:

  • Mappings of existing patients to multiple site MRNs.
  • Project IDs added to patients.

Demo data has been added to all of the new IM tables except the AUDIT table. This IM data was added to provide examples for using the new IM cell.

Important
The mapping information added to the CRC and IM tables is strictly for demonstration purposes and does NOT contain real patient information.

New PostgreSQL Database Scripts

The i2b2 database scripts have been updated to include the table creation and data insert scripts for a PostgreSQL database.


Licensing

The i2b2 source code is licensed under the i2b2 Software License 2.1. This includes but is not limited to all code in the edu.harvard.i2b2.* package namespace.

Trademarks

Microsoft, Windows, Windows 7, Windows Server 2003 and 2008 are either registered trademarks or trademarks of Microsoft Corporation in the United States and / or other countries.

Mac OS is a registered trademark of Apple Inc.

Eclipse Galileo is a registered trademark of the Eclipse Foundation, Inc.

All other trademarks are the property of their respective owners.

 

 

 



 

  • No labels