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

1.7.04 Release Notes

=20 =20 =20 =20 =20

i2b2 Release 1.7.04

=20

Release Date: November 13, 2014

=20

Installation Notes

= =20 =20

Upgrade Notes

=20

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

=20 =20

Third Party Soft= ware 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

Bug Fixes

=20 =20

Change Summary - i2b2 Web Client Software= - Release 1.7.04

=20

Improvements

=20 =20

Bug Fixes

=20 =20

i2b2 Release 1.7.03a

=20

Release Date: August 28, 2014

=20

Installation Notes=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 So= ftware 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

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 So= ftware 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

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 So= ftware 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

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 So= ftware 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

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 So= ftware 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 Cli= ent: 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: Cha= nge Temporal Constraint
=20

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

=20
=20

3D"Temp=

=20
=20
S= tep 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=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

i2b= 2 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

i= 2b2 Workbench: New Temporal Query Tool View

=20

Define Date Constraints and Exclusions in Temporal Query To= ol View

=20
Defining the Da= te 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 Popu= lation
=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 S= ubmit
=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 Quer= y 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 Manage= ment 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

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

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_7413_792814177.1711615884774--