Message-ID: <908298872.7902.1711649274981.JavaMail.confluence@ip-172-30-4-17.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7901_637916658.1711649274979" ------=_Part_7901_637916658.1711649274979 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html 1.7.08b Release Notes

1.7.08b Release Notes

=20 =20 =20 =20

i2b2 Release 1.7.08b

=20

Release Date: December 14, 2016

=20

1.7.08b Release Summary

=20

Release 1.7.08b fixes a bug in the CRC regarding when a query finishes r= unning the BATCH_MODE in the QT_QUERY_INSTANCE table says PROCESSING INSTEA= D OF FINISHED.

=20

Installation Notes

=20 =20 =20 =20

Upgrade Notes

=20

i2b2 Release 1.7.08b contains changes to the following software compone= nts:

=20 =20 =20

Change Summary - i2b2 Core Software - Release= 1.7.08b

=20

Bug Fixes

=20 =20
=20
=20

i2b2 Release 1.7.08a

=20

Release Date: November 23, 2016

=20

1.7.08a Release Summary

=20

Release 1.7.08a is primarily focused on fixing and improving the queuein= g process. The main issue addressed in this release is a fix for an issue t= hat 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 wa= s misleading to users as they were informed it generated an error an was th= erefore no longer running. A number of other issues were uncovered during t= he development and testing of this release. A complete list of each issue c= an be found in the section titled Change Summary - i2b2 Core Software

=20 =20 =20

Installation Notes

=20 =20

Upgrade Notes

=20

i2b2 Release 1.7.08a contains changes to the following software compone= nts:

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

Change Summary - i2b2 Core Software - Release= 1.7.08a

=20

Improvements

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

Bug Fixes

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

Change Summary - i2b2 Web Client Softwar= e - Release 1.7.08a

=20

Bug Fixes

=20
    =20
  • [WEBCLIENT-205] - Update date constr= aint warning message (patient_dimension)
  • =20
=20
=20
=20 =20

i2b2 Release 1.7.08

=20

Release Date: October 7, 2016

=20

1.7.08 Release Summary

=20

Release 1.7.08 contains a number of new features as well as bug fixes. B= elow are a few highlights of the changes included in this release. Informat= ion about the other changes can be found in the sections that follow this o= ne.

=20

JBoss Updated to WildFly

=20

In order to address some of the security vulnerabilities that exist in s= ome 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.<= /p>=20

=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"info" Note

The Third Party Software Changes sectio= n 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 existi= ng JBoss 7. In the section labeled i2b2 Property Settings for WildFly 10 and JBoss 7 we ha= ve 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 additiona= l information that you will need to be aware of before using 1.7.08 with yo= ur existing JBoss,
=20
=20

SQL Server: Option to Improve Query Per= formance

=20

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

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

=20

Additional information about this new feature can be found in the= Improvement / New F= eature Details section under the SQL Server: Option to Improve Query Performance<= /a> heading.

=20

Improvements to the Processing of Queueing= Queries

=20

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

=20
    =20
  • SMALL_QUEUE
  • =20
  • SMALL_QUEUE_RUNNING
  • =20
  • MEDIUM_QUEUE
  • =20
  • MEDIUM_QUEUE_RUNNING
  • =20
  • LARGE_QUEUE
  • =20
  • LARGE_QUEUE_RUNNING
  • =20
=20

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 qu= ery status can be seen in Previous Queries as well as in Show Que= ry Status.

=20

A complete list of all the statuses as well as additional informat= ion about this new feature can be found in the Improvement / New Feature Details section un= der the Impro= vements to the Processing of Queueing Queries heading.

=20

SHRINE Approval

=20

3D"ShrineSHRINE Release 1.21.2 has been tested w= ith i2b2 1.7.08 Release and has been approved by the SHRINE T= eam

=20

Installation Notes

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

Upgrade Notes

=20

i2b2 Release 1.7.08 contains changes to the following software componen= ts:

=20
    =20
  • Database Scripts
  • =20
  • i2b2 Server
  • =20
  • i2b2 Web Client
  • =20
=20 =20

Third Party Software Changes

=20

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

= =20
    =20
  1. Apache Ant has been upgraded to 1.9
  2. =20
  3. Apache Axis2 has been upgraded to 1.7.1
  4. =20
  5. Java JDK has been upgraded to 8.0
  6. =20
  7. JBoss has been upgraded to WildFly 10
  8. =20
=20

3rd Party Software Versions and Links<= /h3>=20

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

=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 = =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3rd Party SoftwareVersionDownload LinkVendor Documentationi2b2 Installation Guidei2b2 Notes
Apache Ant 1.9 Apache Ant 1.9 Softwar= e Ant's manual and API documentation is in= cluded in the binary distribution.
Apache Axis2 1.7.1Axi= s2 1.7.1 Software Installation Guide Apache Axis2 Download the WAR Distribution File
Java JDK 8.0 JDK 8 SoftwareJava JDK Reminder: Update your JAVA_HOME environm= ent variable to point to JDK 8.0
WildFly 10 WildFly 10 SoftwareGetting Started Guide
=20 =20

i2b2 Property Settings for WildFly 10 = and JBoss 7

=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"warning" Warning
As stated earlier, the i2b2 = team made the decision to upgrade to WildFly 10 and JDK 8 in order to addre= ss 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 n= ot want to upgrade your environment to use WildFly there are a few things y= ou need to be aware of.=20
    =20
  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. =20
  3. JDK 8 does not work with JBoss 7. If you are upgrading to JDK8 then you= have to upgrade to WildFly
  4. =20

If you are upgrading to WildFly and JDK 8 you need to do these up= grades before you upgrade your i2b2 server code.
=20
=20

The property settings delivered with i2b2 version 1.7.08 are pointing t= o WildFly. For those sites that are currently using JBoss 7 and are not rea= dy 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.

=20

WildFly Property Modifications

= =20
CRC Cell Property Changes
=20

File Name: crc_application_director= y.properties
Location: edu.harvard.i2b2.crc/etc/spring/

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: e= du.harvard.i2b2.crc.applicationdir=3D/opt/wildfly-10.0.0.Final/stand= alone/configuration/crcapp
JBoss 7 path: e= du.harvard.i2b2.crc.applicationdir=3D/opt/jboss-as-7.1.1.Final/stand= alone/configuration/crcapp
=20
=20

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

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: j= boss.home=3D/opt/wildfly-10.0.0.Final
JBoss 7 path: j= boss.home=3D/opt/jboss-as-7.1.1.Final
=20
=20
File Repository Cell Property Chang= es
=20

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

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: e= du.harvard.i2b2.fr.applicationdir=3D/opt/wildfly-10.0.0.Final/standa= lone/configuration/frapp
JBoss 7 path: e= du.harvard.i2b2.fr.applicationdir=3D/opt/jboss-as-7.1.1.Final/standa= lone/configuration/frapp
=20
=20

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

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: j= boss.home=3D/opt/wildfly-10.0.0.Final
JBoss 7 path: j= boss.home=3D/opt/jboss-as-7.1.1.Final
=20
=20
Identity Management (IM) Cell Prope= rty Changes
=20

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

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: e= du.harvard.i2b2.im.applicationdir=3D/opt/wildfly-10.0.0.Final/standa= lone/configuration/imapp
JBoss 7 path: e= du.harvard.i2b2.im.applicationdir=3D/opt/jboss-as-7.1.1.Final/standa= lone/configuration/imapp
=20
=20

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

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: j= boss.home=3D/opt/wildfly-10.0.0.Final
JBoss 7 path: j= boss.home=3D/opt/jboss-as-7.1.1.Final
=20
=20
Ontology Cell Property Changes=20

File Name: ontology_application_dir= ectory.properties
Location: edu.harvard.i2b2.ontology/etc/sprin= g/

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

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

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: j= boss.home=3D/opt/wildfly-10.0.0.Final
JBoss 7 path: j= boss.home=3D/opt/jboss-as-7.1.1.Final
=20
=20
PM Cell Property Changes
=20

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

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: j= boss.home=3D/opt/wildfly-10.0.0.Final
JBoss 7 path: j= boss.home=3D/opt/jboss-as-7.1.1.Final
=20
=20
Server-Common Changes=20

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

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: j= boss.home=3D/opt/wildfly-10.0.0.Final
JBoss 7 path: j= boss.home=3D/opt/jboss-as-7.1.1.Final
=20
=20
Workplace Cell Property Changes=20

File Name: workplace_application_di= rectory.properties
Location: edu.harvard.i2b2.workplace/etc/spr= ing/

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

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

=20
=20 =20 = =20 =20 =20 =20 =20 =20 =20
WildFly 10 path: j= boss.home=3D/opt/wildfly-10.0.0.Final
JBoss 7 path: j= boss.home=3D/opt/jboss-as-7.1.1.Final
=20 =20

Change Summary - i2b2 Core Software - Release = 1.7.08

=20

Improvements

=20 =20

New Features

=20 =20

Bug Fixes

=20 =20

Documentation

=20 =20 =20

Change Summary - i2b2 Web Client Software= - Release 1.7.08

=20

Improvements

=20 =20

New Features

=20 =20

Bug Fixes

=20 =20 =20

Change Summary - i2b2 Community Plugins - R= elease 1.7.08

=20

Bug Fixes

=20 =20 =20

Improvement / New Feature Details

= =20

View and Update the DB_LOOKUP = Tables

=20

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

=20

Release 1.7.08 added the ability to view current database connections d= efined 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 t= o 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. T= his page will display all the values in a table format.

=20

The following screen shot shows all the entries in the CRC_DB_LOOKUP ta= ble.

=20
=20

3D"DB

=20
=20

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. Th= e page will be updated to a form with fields to capture the information to = be stored in the DB_LOOKUP table.

=20
=20

3D"DB

=20
=20

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 fil= ed in the DB_LOOKUP table. Make any changes and click on Save to sav= e your edits.

=20
=20

3D"DB =

=20
=20 =20

Improvements to the Processing o= f Queueing Queries

=20

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

=20

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 cr= c.properties file.

=20
    =20
  1. Small Queue
  2. =20
  3. Medium Queue
  4. =20
  5. Large Queue
  6. =20
=20

In the Web Client, the status of a query can be seen in Previous Querie= s. 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_QUE= RY_INSTANCE table to see the queue information. The statuses and queue info= rmation were often ambiguous which would make it challenging to trouble sho= ot any issues.

=20

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

=20
    QUEUED ERROR COMPLETED PROCESSING SMALL_QUEUE MEDIUM_QUEUE LARGE_QUEUE MED= IUM_QUEUE_RUNNING LARGE_QUEUE_RUNNING RUNNING=20
=20

In addition to updating the status of queries, an additional feature wa= s added to the Web Client that makes these statuses visible to users. The q= uery status can be seen in Previous Queries as well as in Show Qu= ery Status.

=20 =20

SQL Server: Option to Improve= Query Performance

=20

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

= =20

Large data warehouses that contain broad and deep ontologies run the ri= sk of CRC queries having a slow response time. In this release (1.7.08) a n= ew parameter has been added to the crc.properties file. This new par= ameter 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 t= he query to run more efficiently and process the request faster.

=20

Parameter Name: edu.harvard.i2b2.crc.setfinderquery.constraintlo= gic
Located in: crc.properties file
Behavior:

= =20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
ValueBehavior
TEMP or TEMPTABLESTemp tables will be used when building q= ueries.
WITHCurrent query logic is used
=20

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

=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20
3D"" Important
This change only affects SQ= L Server databases. Both PostgreSQL and Oracle do not have the capabilities= of using temp tables. They will continue to use the WITH clause.
=20
=20 =20

Date Constraint Improvem= ents

=20

JIRA ISSUES: [WEBCLIEN= T-133] - Restrict ability to add Date Constraint if a panel contains an= y age concepts.

=20

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

= =20

General i2b2 users do not know whether or not an age has a start date a= nd 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 larg= er network in which some sites may store it in the PATIENT_DIMENSION and ot= hers in the OBSERVATION_FACT. This scenario will definitely result in misle= ading results and the user will be unaware of the discrepancy.

=20

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 f= ollowing message will appear when attempting to set a date constraint on a = panel with an age concept: Date constraints are not allowed for age rel= ated concepts. This panel contains at least one age related concepts, there= fore a date constraint can not be set for this panel."

=20 =20

Web Client Configurations=20

JIRA ISSUES: [ WEBCLIE= NT-198] - Parameters/Configurations for Web Client

=20

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 t= he login screens, default user id and password values, as well as how obfus= cated results display in the i2b2 Web Client.

=20

       File Name: i2b2_ui_config.j= s        File Location: /webclient/js= -i2b2/

=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
ParameterDescriptionDefault Value
titleLogoSrcLogo that appears in toolbar when logged= into the i2b2 Web Client."assets/images/title.gif"
loginHeaderTextText in the header bar of the login box<= /td>=20 "i2b2 Login"
loginUsernameTextText for the username input of the login= box."Username:"
loginDefaultUsernameDefault text inside the username input.<= /td>=20 "demo"
loginPasswordTextText for the password input of the login= box."Password:"
loginDefaultPasswordDefault text inside the password input.<= /td>=20 "demouser"
loginHostTextText for the PM cell dropdown of the log= in box."i2b2 Host:"
obfuscatedDisplayNumberThe number to display after the plus/min= us for obfuscated results.
Please see the important note at end of t= his table.
3
useFloorThresholdIf true, any result below floorTh= resholdNumber shows as '{floorThresholdText} {floorThresholdNumber}'
If= false, floor threshold will not be used when displaying values in t= he i2b2 Web Client.
false
floorThresholdNumberThreshold for the low number of results<= /td>=20 10
floorThresholdTextText that is prefixed before {floorThres= holdNumber} (include trailing space)"Less Than "
=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20
3D"" Important
The calculation for the rea= l obfuscation value continues to be controlled by the server and is based o= n the value defined in the CRC properties file. The obfuscatedDisplayNum= ber parameter in the i2b2_ui_config.js simply defines what numbe= r to display to the user when viewing the query results.
=20
=20 =20

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

=20

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

=20

Prior to release 1.7.08, parameters are sent in as Unicode (nvarchar) i= nstead of varchar. SQL Server then has to explicitly convert the nvarchar t= o 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).

=20

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

=20

Connection Parameter: connection-property name=3D"sendStringPara= metersAsUnicode"
Added To: datasource definition
Behavi= or:

=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
ValueBehavior
falseString based variable will be sent as va= rchar
trueCurrent logic is used; String based vari= able will be sent in Unicode (nvarchar)
=20

Example:        <connect= ion-property name=3D"sendStringParametersAsUnicode" >false</connectio= n-property>

=20 =20

Updated JDBC Drivers=20

JIRA ISSUES: [CORE-229]= - Provide updated JDBC drivers used by Oracle, PostgreSQL, and SQL Server<= /p>=20

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

=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20
3D"" Important
Sites that choose to upgrad= e their JDBC drivers will be required to also updated the datasource files = for all of their cells.
=20
=20

Information on Upd= ating Drivers

=20

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

=20
Location of JDBC J= ar files
=20

Your current JDBC jar files reside in the following directories:

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

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

=20
    =20
  1. Oracle =3D ojdbc7.jar
  2. =20
  3. PostgreSQL =3D postgresql-9.4-1209.jar
  4. =20
  5. SQL Server =3D sqljdbc42.jar
  6. =20
=20
Update Existin= g i2b2 Instance
=20

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

=20
=20
=20 =20 =20 =20
Linux Command
   &nbs= p;  ant copy_new_jdbc_jar
=20
=20
=20
=20 =20 =20 =20
Windows Command
   &n= bsp;  %ANT_HOME%\bin\ant.bat copy_new_jdbc_jar
=20
=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20
3D"" Warning
If you choose to install the = new JDBC jar files you also need to update your datasource files wit= h the new driver information. This needs to be done for each cell in the i2= b2 hive.
=20
=20
=20

i2b2 Release 1.7.07c

=20

Release Date: June 7, 2016

=20

Installation Notes

=20 =20

SHRINE Approval

=20 =20

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

=20

Upgrade Notes

=20

i2b2 Release 1.7.07c contains changes to the following software compone= nts:

=20 =20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"important" Important
The Admin changes can be f= ound 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 include= d in this file. If you are upgrading from 1.7.07 then you do not need to up= date 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.=
=20
=20

Third Party S= oftware Changes

=20

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

= =20

Change Summary - i2b2 Web Client Softwar= e - Release 1.7.07c

=20

Bug Fixes

=20 =20
=20

i2b2 Release 1.7.07b

=20

Release Date: March 1, 2016

=20

Installation Notes

=20 =20

SHRINE Approval

=20 =20

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

=20

Upgrade Notes

=20

i2b2 Release 1.7.07b contains changes to the following software compone= nts:

=20
    =20
  • i2b2 Web Client
  • =20
  • i2b2 Server - Admin code only
  • =20
=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"important" Important
The Admin changes can be f= ound 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 include= d in this file. If you are upgrading from 1.7.07 then you do not need to up= date 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.=
=20
=20

Third Party S= oftware Changes

=20

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

= =20

Change Summary - i2b2 Web Client Softwar= e - Release 1.7.07b

=20

Bug Fixes

=20
    =20
  • [WEBCLIENT-177] - PHP Proxy Update <= /li>=20
  • [WEBCLIENT-178] - Error returned whe= n reloading the i2b2 Web Client after it times out
  • =20
=20
=20

i2b2 Release 1.7.07

=20

Release Date: January 15, 2016

=20

Installation Notes

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

SHRINE Approval

=20

3D"ShrineSHRINE Release 1.20.1 has been tested = with i2b2 1.7.07 Release and has been approved by the SHRINE = Team

=20

Upgrade Notes

=20

i2b2 Release 1.7.07 contains changes to the following software componen= ts:

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

Third Party S= oftware Changes

=20

No changes to third party software are included in release 1.7.07

=20

Change Summary - i2b2 Core Software - Release = 1.7.07

=20

Improvements

=20
    =20
  • [CORE-118] - Increase number of queries th= at can be run in the "lifetime" of the database
  • =20
  • [CORE-187] - Split the observation_fact_de= mo_insert_data script into smaller scripts
  • =20
  • [CORE-194] - Split the icd10_icd9_diagnose= s_insert_data script into smaller scripts
  • =20
  • [CORE-201] - Update i2b2 demo data scripts= to support Microsoft SQL Server 2012
  • =20
=20

Bug Fixes

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

Change Summary - i2b2 Web Client Software= - Release 1.7.07

=20

Improvements

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

New Features

=20 =20

Bug Fixes

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

Change Summary - i2b2 Community Plugins - R= elease 1.7.07

=20

Improvements

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

New Features

=20
    =20
  • [PLUGINS-15] - Set up production reposit= ories for all plugins
  • =20
=20

Bug Fixes

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

i2b2 Release 1.7.06

=20

Release Date: August 12, 2015

=20

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

Upgrade Notes

=20

i2b2 Release 1.7.06 contains changes to the following software componen= ts:

=20
    =20
  • i2b2 Server
  • =20
  • i2b2 Web Client
  • =20
  • i2b2 Workbench
  • =20
=20

Third Party S= oftware Changes

=20

No changes to third party software are included in release 1.7.06

=20

Change Summary - i2b2 Core Software - Release = 1.7.06

=20

Bug Fixes

=20
    =20
  • [CORE-149] - JDBC calls to interrupted thr= eads throw sqlexceptions - Queries do not leave medium queue
  • =20
  • [CORE-165] - Timeline filter not working i= f database is SQL Server
  • =20
  • [CORE-180] - SHRINE queries will not run o= nce i2b2 is updated to 1.7.05
  • =20
=20

Documentation Update= s

=20
    =20
  • [CORE-179] - Difference between documentat= ion and table concept_dimension
  • =20
=20

Change Summary - i2b2 Web Client Software= - Release 1.7.06

=20

Bug Fixes

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

i2b2 Release 1.7.05

=20

Release Date: May 6, 2015

=20

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

Upgrade Notes

=20

i2b2 Release 1.7.05 contains changes to the following software componen= ts:

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

Third Party S= oftware Changes

=20

No changes to third party software are included in release 1.7.05

=20

Change Summary - i2b2 Core Software - Release = 1.7.05

=20

Bug Fixes

=20
    =20
  • [CORE-149] - JDBC calls to interrupted thr= eads throw sqlexceptions
  • =20
  • [CORE-156] - PM may not send the correct c= ell information when multiple projects and cells defined
  • =20
  • [CORE-158] - JBoss server log contains pas= sword information when debug is turned on
  • =20
  • [CORE-159] - Inconsistency in JBoss711Fina= l and Install documentation
  • =20
  • [CORE-166] - Hard coded references to I2B2= DEMODATA in CRC install files
  • =20
  • [CORE-167] - Metadata data install error <= /li>=20
  • [CORE-169] - SHRINE Previous Queries: Path= displays in Query Tool instead of item name
  • =20
  • [CORE-174] - concept_dimension.concept_cd = is nullable in postgresql implementation
  • =20
  • [CORE-177] - Workbench may be using the wr= ong cell data when multiple projects and cells defined
  • =20
=20

Change Summary - i2b2 Web Client Software= - Release 1.7.05

=20

New Features

=20
    =20
  • [WEBCLIENT-78] - Ability to refresh = in PQ and workplace
  • =20
  • [WEBCLIENT-80] - New view: Find Prev= ious Queries
  • =20
  • [WEBCLIENT-89] - New Graph Results v= iew to display patient breakdowns in a graph
  • =20
=20

Improvements

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

Bug Fixes

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

i2b2 Release 1.7.04

=20

Release Date: November 13, 2014

=20

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

Upgrade Notes

=20

i2b2 Release 1.7.04 contains changes to the following software componen= ts:

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

Third Party S= oftware Changes

=20

No changes to third party software are included in release 1.7.04

=20

Change Summary - i2b2 Core Software - Release = 1.7.04

=20

Improvements

=20
    =20
  • [CORE-134] - Improve appearance of tooltip= s in Ontology Views
  • =20
  • [CORE-136] - Jump to terms does not displa= y modifiers
  • =20
  • [CORE-142] - Add ability to add metadataxm= l to a modifier from within Edit Terms view
  • =20
  • [CORE-144] - Add ability to expand inactiv= e folders to view its children
  • =20
=20

Bug Fixes

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

Change Summary - i2b2 Web Client Software= - Release 1.7.04

=20

Improvements

=20
    =20
  • [WEBCLIENT-67] - Add ability to expa= nd inactive items to view its dependents / children
  • =20
=20

Bug Fixes

=20
    =20
  • [WEBCLIENT-13] - Data & admin ro= les specified in Project Request plug-in are listed 'undefined' in admin de= tail view
  • =20
  • [WEBCLIENT-50] - New Events for temp= oral queries are mislabled after using 'Clear'
  • =20
  • [WEBCLIENT-64] - Can't drop previous= temporal query into query tool if span of time defined in query
  • =20
  • [WEBCLIENT-65] - Date constraint not= available for Groups over Group3
  • =20
  • [WEBCLIENT-72] - Synonyms issue in 1= .7.04 release
  • =20
=20
=20

i2b2 Release 1.7.03a

=20

Release Date: August 28, 2014

=20

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

Upgrade Notes

=20

i2b2 Release 1.7.03a contains changes to the following software compone= nts:

=20
    =20
  • i2b2 Web Client
  • =20
=20

Third Party S= oftware Changes

=20

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

= =20

Change Summary - i2b2 Web Client Softwar= e - Release 1.7.03a

=20

Bug Fixes

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

i2b2 Release 1.7.03

=20

Release Date: August 20, 2014

=20

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

Upgrade Notes

=20

i2b2 Release 1.7.03 contains changes to the following software componen= ts:

=20
    =20
  • i2b2 Server
  • =20
  • i2b2 Web Client
  • =20
=20

Third Party S= oftware Changes

=20

No changes to third party software are included in release 1.7.03

=20

Change Summary - i2b2 Core Software - Version = 1.7.03

=20

Bug Fixes

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

Improvements

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

Change Summary - i2b2 Web Client Software= - Release 1.7.03

=20

Bug Fixes

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

Improvement / New Feature Details

= =20

Edit tool to = file C_PATH and C_SYMBOL when adding new item

=20

JIRA ISSUES: [CORE-135]=

=20

In the i2b2 metadata table there are two columns (C_PATH and C_SYMBOL) t= hat 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 n= ow be populated with the appropriate data when creating a new container, fo= lder, term, or modifier from within the Edit Terms view.

=20

Edit Tool vi= ew: Line feeds removed from Metadataxml

=20

JIRA ISSUES: [CORE-141]=

=20

In the Edit Terms view users can create terms that have values associate= d to them. These values are stored in the C_METADATAXML column in the custo= m 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 wi= th carriage returns / line feeds. This change improves the way the metadata= xml if filed into the table by removing all line feeds from the data before= filing it into the C_METADATAXML column

=20
=20

i2b2 Release 1.7.02

=20

Release Date: July 1, 2014

=20

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

Upgrade Notes

=20

i2b2 Release 1.7.02 contains changes to the following software componen= ts:

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

Third Party S= oftware Changes

=20

No changes to third party software are included in release 1.7.02

=20

Change Summary - i2b2 Core Software - Version = 1.7.02

=20

Improvements

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

Bug Fixes

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

Change Summary - i2b2 Web Client Software= - Release 1.7.02

=20

Improvements

=20 =20

Bug Fixes

=20
    =20
  • [WEBCLIENT-27] - Wrong icon appears = when dragging folder to Workplace View
  • =20
  • [WEBCLIENT-43] - ontology cell conce= pt navigation "Show Synonymous Terms" checkbox inconsistency
  • =20
  • [WEBCLIENT-46] - Renaming shared fol= ders doesn't work in the webclient
  • =20
  • [WEBCLIENT-47] - "Delete Concept" in= I2B2 web app deletes the first occurrence of the concept, not the one sele= cted
  • =20
  • [WEBCLIENT-51] - Only 1 temporal rel= ationship sent in xml even though multiple are defined
  • =20
  • [WEBCLIENT-52] - Modifier folders/co= ntainers don't work with i2b2 v1.7 and PostgreSQL
  • =20
  • [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
  • =20
  • [WEBCLIENT-55] - With error in data = source the client runs on forever
  • =20
  • [WEBCLIENT-58] - Operators do not de= fault correctly when adding a temporal relationship
  • =20
  • [WEBCLIENT-59] - Print Query not wor= king in Chrome browser
  • =20
=20

Tasks

=20
    =20
  • [WEBCLIENT-61] - Disable changing pa= sswords on the demo site
  • =20
=20

Improvement / New Feature Details

= =20

Password Management

=20

JIRA ISSUES: [CORE-95] a= nd [WEBCLIENT-56]

=20

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, user= s 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 i2b= 2 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.

=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"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 wi= ll need to contact their site administrator and follow the protocols establ= ished at their institution.

This feature is only available f= or those users that log in with the standard i2b2 Authentication method.
=20
=20

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

=20
=20

=20
=20

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

=20
=20

=20
=20

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

=20
=20

=20
=20

Clicking on Password will open the Set Password window.=20

=20

=20
=20

The functionality to change your password is the same regardless of whet= her you access the change password window from within the i2b2 Web Client o= r the workbench. There are basically three steps:

=20
    =20
  1. Enter your current password.
  2. =20
  3. Enter a new password for your user.
  4. =20
  5. Retype your password.
  6. =20
=20

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.

=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"info" Note
Once you change your password y= ou will need to log out of the Web Client or Workbench and log back in usin= g your new password.
=20
=20
=20

i2b2 Release 1.7.01

=20

Release Date: February 4, 2014

=20

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

Upgrade Notes

=20

i2b2 Release 1.7.01 contains changes to the following software component= s:

=20
    =20
  • Database Scripts
  • =20
  • i2b2 Server
  • =20
  • i2b2 Web Client
  • =20
=20

Third Party = Software Changes

=20

No changes to third party software are included in release 1.7.01

=20

Change Summary - i2b2 Core Software - Version = 1.7.01

=20

Improvements

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

Bug Fixes

=20
    =20
  • [CORE-83] - Trying to build and compile i2b= 2 Server on Fedora Core 20 with Wildfly 8.0.0
  • =20
  • [CORE-85] - Fresh install fails on PM Modul= e and admin screen
  • =20
  • [CORE-87] - Installation process needs to p= ut database drivers in i2b2.war/WEB-INF/lib
  • =20
  • Data Install: The stored procedures for PostgreSQL for the CRC Loader w= as enhanced and optimized.
  • =20
  • 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.
  • =20
  • 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.
  • =20
=20

Documentation

=20
    =20
  • [CORE-58] - Workbench 1.6 and default insta= ll
  • =20
  • [CORE-77] - I2B2 installation Guide fixes <= /li>=20
  • [CORE-90] - Install Documentation: Wrong sc= hema configurations documented for a PostgreSQL database
  • =20
=20

Change Summary - i2b2 Web Client Software= - Release 1.7.01

=20

Bug Fixes

=20
    =20
  • [WEBCLIENT-48] - Web client gets int= o non-functional state
  • =20
  • Clicking on the Clear button does not return the Query Tool to the defa= ult settings. When a temporal query is created, and a user clicks on the cl= ear button to start a new query, the Temporal Constraint is changed to "Def= ine sequence of events" and it should default to "Treat all groups independ= ently.
  • =20
  • 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.
  • =20
=20
=20

i2b2 Release 1.7

=20

Release Date: December 20, 2013

=20

Installation Notes=20
    =20
  • This release note applies to you if you are upgrading to 1.7 fr= om an earlier version of i2b2.
  • =20
  • 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.
  • =20
  • If you are installing a new instance of i2b2 we recommend you refer to= the installation documentation found on the i2b2 community wiki. This docu= mentation will guide you through the entire installation process.
  • =20
=20

Upgrade Notes

=20

i2b2 Release 1.7 contains changes to the following software components:=

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

Third Party = Software Changes

=20

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

=20
    =20
  1. JBoss has been upgraded to 7.1.1
  2. =20
  3. Apache Ant has been upgraded to 1.8.2
  4. =20
  5. Apache Axis2 has been upgraded to 1.6.2
  6. =20
=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"warning" Warning
Only the i2b2 Server was upg= raded to use the above versions of JBoss, Ant, and Axis2. The i2b2 Workbenc= h 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 co= mmons.

Server edu.harvard.i2b2.server-common

Client edu.harvard.i2b2.common

=20
=20

Change Summary - i2b2 Core Software - Release = 1.7

=20

Improvements

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

New Features

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

Bug Fixes

=20
    =20
  • [CORE-5] - CRC build from source deposits i2= b2Common-core.jar in wrong directory
  • =20
  • [CORE-70] - I2b2 compilation of CRC Cell fa= ils
  • =20
  • [CORE-74] - Typo in i2b2_config_data.js of = admin interface
  • =20
  • [CORE-81] - No PATIENT_NUM in OBSERVATION_F= ACT_PK (conflict with documentation)
  • =20
=20

Documentation

=20
    =20
  • Architecture, design and messaging documents for the new Identity Manag= ement (IM) Cell.
  • =20
  • Design documentation for the new Temporal Query Tool plug-in.
  • =20
  • User guide for the new Temporal Query view.
  • =20
  • Documentation for the new views (Patient Set, Patient Mapping, Managers= Tool, and Find in Workplace).
  • =20
  • [CORE-8] - Suggestions for improvements to i= nstallation documents
  • =20
  • [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 x= x
  • =20
  • [CORE-78] - Errors in I2B2 Hive Installatio= n Guide v 1.7.0
  • =20
=20

Tasks

=20
    =20
  • [CORE-45] - Establish CRCLoader project (ec= lipse) from exiting ant build file failed
  • =20
=20

Change Summary - i2b2 Web Client Software= - Release 1.7

=20

New Features

=20
    =20
  • Temporal Queries (Modification made to existing Query Tool)
  • =20
=20

Documentation

=20
    =20
  • [WEBCLIENT-40] - Webclient: document= ation should state that php and curl are prerequisites for the webclient =20
=20

Improvement / New Feature Details

= =20

Temporal Queries

=20

The temporal query is a new type of query introduced in re= lease 1.7. There are two components to these queries that make them a littl= e more complex than the type of queries available prior to 1.7 (classic i2b= 2 queries).

=20

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

=20

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

=20

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

=20

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 e= xisting Query Tool view has been modified to accommodate Temporal Queries w= hile a new view called Temporal Query Tool view has been created for the i2= b2 Workbench.

=20

The new Temporal Query Tool view and the modifications to the existing Q= uery Tool view extend the query functionalities provided by the classic Que= ry Tool view.

=20

It is important to note that while the manner in which users setup a tem= poral query is different in each of the clients the overall functionality i= s the same.

=20

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

=20

i2b2 Web Cl= ient: Temporal Queries

=20

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

=20
    =20
  1. Change Temporal Constraint to Define sequence of Events.<= /li>=20
  2. Define Population in which events occur (optional step).
  3. =20
  4. Define Events
  5. =20
  6. Define order of events (temporal relationships)
  7. =20
  8. Run the query
  9. =20
=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"info" Note
For detailed information about = creating Temporal Queries please see the Temporal Query help file located o= n-line from within the i2b2 Web Client.
=20
=20
Step 1: Ch= ange Temporal Constraint
=20

The first step is to change the Temporal Constraint to Define sequenc= e of Events.

=20
=20

3D"Temp=

=20
=20
= Step 2: Define Population in which events occur
=20

Once you have changed the Temporal constraint to be Define sequence o= f 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= .

=20
=20

3D"Temp=

=20
=20
Step 3: Define Events<= /h6>=20

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

=20

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

=20
=20

3D"Temp=

=20
=20

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

=20

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

=20

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

=20
Step 4: Define Order of Events (Temporal Relationship)
=20

As stated earlier the second component of a temporal query is the relati= onship between the events (temporal relationship). In the i2b2 Web Client t= his 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.

=20

The page will display as follows:

=20
=20

3D"Temp=

=20
=20
Step 5: Run Query
=20

In the Web Client running a query works the same regardless of whether o= r 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.

=20

i2= b2 Workbench: New Temporal Query Tool View

=20

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

    =20
  1. Page 1: Define Population
  2. =20
  3. Page 2: Define Temporal Relationships
  4. =20
  5. Page 3: Review and Submit Query
  6. =20
=20

= i2b2 Workbench: New Temporal Query Tool View

=20

Define Date Constraints and Exclusions in Temporal Query T= ool View

=20
Defining the D= ate Constraints
=20
Exclude Panel
=20

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

=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"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.
=20
=20
Page 1: Define Pop= ulation
=20

On this page you will define your population requirements.

=20
=20

3D"Temp=

=20
=20
Page 2:= Define Temporal Relationships
=20

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

= =20

The second page is where you will define both the events and their relat= ionship.

=20
=20

3D"Temp=

=20
=20
Page 3: Review and = Submit
=20

On this page the name of the query will default and if you wish to renam= e 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.

=20
=20

3D"Temp=

=20
=20
Defining Date Constraints and Exclusions in Temporal Que= ry Tool View
=20

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

=20

Defining the= Date Constraints

=20

In the classic Query Tool view you can only define date constraints on t= he group / panel level. In the new Temporal Query TOol view you can now def= ine 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 gr= oups and the date constraint on the panel level will not be available for s= election.

=20

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.

=20
=20

=20
=20
Exclude Panel
=20

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

=20

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

=20
=20

=20
=20

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

=20
=20

=20
=20

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

=20
=20

=3D"Temporal

=20
=20

The above option is equivalent to the Exclude feature in the clas= sic Query Tool view.

=20

Previous Query: Filter lis= t by user

=20

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 (3D"Options) window there is a new field ca= lled 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 disp= lay the drop-down list. Once you select the user and click on OK, th= e Previous Queries view will refresh and display only those previous querie= s created by the selected user.

=20
=20

=20
=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
3D"important" Important
In i2b2 only managers are = allowed to view queries for another user, therefore this feature is only av= ailable 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 i= nactive and unavailable for selection.
=20
=20

Previous Query: Search Previou= s Queries View

=20

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 Term= s view. Users can search any of the three levels;

=20
    =20
  1. Previous Query (name)
  2. =20
  3. Previous Query Result
  4. =20
  5. Patient
  6. =20
=20
=20

3D"Previo=

=20
=20

Previous Query: Page through p= revious queries by date

=20

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

=20
=20

=20
=20

The Previous button (3D"Previous) will retrieve the group of previous queries that occ= ur prior to the date displayed in the date / time field.

=20

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

=20

Identity Manag= ement Cell (IM)

=20

A new cell called the Identity Management (IM) Cell was developed in rel= ease 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.=20

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

=20
    =20
  1. New tables to store identifiers from different sites, and patients that= are included in a project.
  2. =20
  3. Audit controls are implemented that are in compliance with the HIPAA pr= ivacy rules.
  4. =20
  5. Services developed to set and validated an AES key for encrypting and d= ecrypting patient MRNs in the IM cell.
  6. =20
  7. Unencrypted patient identifiers sent in the PDO can be processed throug= h the IM cell to retrieve all site IDs for the patient and project.
  8. =20
=20

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

=20

Managers Tool View

=20

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

=20
    =20
  1. Set and / or validate that the project key is defined in the IM Cell.=20
      =20
    • The project key is used by the IM cell to decrypte the patient id"s tha= t are encrypted.
    • =20
    • The Set Key is used to define the key in the IM cell.
    • =20
    • The Validate Key is used to verify the key is set.
    • =20
    =20
    =20
    =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
    3D"important" Important
    If you are using the IM ce= ll and your patient identifiers are encyrpted the you need to set the Proje= ct key in the IM cell. It is important to note that if you restart your i2b= 2 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 th= e i2b2 demo project is: i2b2demodatakey1

    In the VM image yo= u need to log into the i2b2 Workbench as the i2b2 Admin user.

    User ID: i2b2
    Password: demouser

    =20
    =20
  2. View the audit information.
  3. =20
      =20
    • As part of the IM cell an audit table was created to track when a patie= nt in the IM cell was accessed. This new view allows Project Managers or Ad= ministrators 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 pro= ject you are logged into.
    • =20
    =20
=20

=20

In release 1.7 a new view called Patient Sets was created. This n= ew 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 d= isplays the patient sets and not the previous query or other result sets (i= .e. Encounter sets, Number of patients, etc).

=20
=20

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

=20
=20

3D"Patien=

=20
=20

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

=20

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 patie= nt.

=20
=20

3D"Patien=

=20
=20

Workplace Find View

= =20

A new view called Find in Workplace was created in release 1.7. T= his view is very similar to the Find Terms view except it will searc= h the Workplace view instead of the Navigate Terms view.

= =20
=20

3D"Workpl=

=20
=20

Find Terms: New feature call= ed "Jump to Term in Tree"

=20

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

=20

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. S= electing "Jump to Term in Tree" from the pop-up menu will bring the Navi= gate Terms view into focus and the hierarchical tree will automatically= open to the location of the term selected in the Find Terms view.=20

OpenEMPISupport

=20

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.

=20

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

=20

PostgreSQL Database Support<= /h3>=20

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

=20

Data: New Tables created fo= r the IM Cell

=20

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

=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
Table NameDescription
IM_MPI_DEMOGRAPHICSContains General demographic information= for the patients.
IM_MPI_MAPPINGMaps the patient"s i2b2 number an= d the local MRN.
IM_PROJECT_SITESContains information about the different= sites (Source Systems).
IM_PROJECT_PATIENTSStores the patients that are part of a p= roject(s).
IM_AUDITStores the audit details of patients acc= essed in the IM cell. This includes; the user, site, and project requesting= the access as well as the date in which it was accessed.
=20

Data: New Columns added = to support IM cell

=20

A new column called Project_ID has been added to both the PATI= ENT_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 pr= oject a patient is part of.

=20

Data: Improved Patient Mappin= g Data

=20

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

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

Demo data has been added to all of the new IM tables except the AUDIT ta= ble. This IM data was added to provide examples for using the new IM cell.<= /p>=20

=20
=20 =20 =20 =20 =20 =20 =20 =20 =20
3D"" Important
The mapping information add= ed to the CRC and IM tables is strictly for demonstration purposes and does= NOT contain real patient information.
=20
=20

New PostgreSQL Databa= se Scripts

=20

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

=20
=20

Licensing

=20

The i2b2 source code is licensed under the i2b2 Software License 2.1. Th= is includes but is not limited to all code in the edu.harvard.i2b2.* packag= e namespace.

=20

Trademarks

=20

Microsoft, Windows, Windows 7, Windows Server 2003 and 2008 are either r= egistered trademarks or trademarks of Microsoft Corporation in the United S= tates and / or other countries.

=20

Mac OS is a registered trademark of Apple Inc.

=20

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

=20

All other trademarks are the property of their respective owners.

=20

------=_Part_7901_637916658.1711649274979--