This release note applies to you if you are upgrading to 1.7.07b from an earlier version of i2b2.
=20
If you are installing 1.7.07b 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
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
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
=20
=20
=20
Third Party Sof=
tware 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
[WEBCLIENT-178] - Error returned whe=
n reloading the i2b2 Web Client after it times out
=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
SHRINE 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
[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
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
[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
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
[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
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
[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
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
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
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
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 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
[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
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
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
=20
=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
Enter your current password.
=20
Enter a new password for your user.
=20
Retype your password.
=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
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
=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 S=
oftware 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.
[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 S=
oftware Changes
=20
In release 1.7 the i2b2 Server has been updated to use the follow=
ing versions of third party software.
=20
=20
JBoss has been upgraded to 7.1.1
=20
Apache Ant has been upgraded to 1.8.2
=20
Apache Axis2 has been upgraded to 1.6.2
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
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.
[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 =
li>=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
Change Temporal Constraint to Define sequence of Events.<=
/li>=20
Define Population in which events occur (optional step).
=20
Define Events
=20
Define order of events (temporal relationships)
=20
Run the query
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
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
=20
=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
=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
=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
=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
=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
Page 1: Define Population
=20
Page 2: Define Temporal Relationships
=20
Page 3: Review and Submit Query
=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
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
=20
=20
=20
Page 1: Define Pop=
ulation
=20
On this page you will define your population requirements.
=20
=20
=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
=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
=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
=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 () 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
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
=20
=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
Previous Query (name)
=20
Previous Query Result
=20
Patient
=20
=20
=20
=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() will retrieve the group of previous queries that occ=
ur prior to the date displayed in the date / time field.
=20
The Next button() 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.=
p>=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
New tables to store identifiers from different sites, and patients that=
are included in a project.
=20
Audit controls are implemented that are in compliance with the HIPAA pr=
ivacy rules.
=20
Services developed to set and validated an AES key for encrypting and d=
ecrypting patient MRNs in the IM cell.
=20
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.
=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
Set and / or validate that the project key is defined in the IM Cell.=
li>=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
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
=20
=20
=20
View the audit information.
=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.
The patient sets can be expanded to display a list of patients.
=20
=20
=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
=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
=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.=
p>=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
Table Name
=20
Description
=20
=20
=20
IM_MPI_DEMOGRAPHICS
=20
Contains General demographic information=
for the patients.
=20
=20
=20
IM_MPI_MAPPING
=20
Maps the patient"s i2b2 number an=
d the local MRN.
=20
=20
=20
IM_PROJECT_SITES
=20
Contains information about the different=
sites (Source Systems).
=20
=20
=20
IM_PROJECT_PATIENTS
=20
Stores the patients that are part of a p=
roject(s).
=20
=20
=20
IM_AUDIT
=20
Stores 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
=20
=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
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
=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.