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
=20 =20 =20 =20 =20
Release Date: November 13, 2014
=20i2b2 Release 1.7.04 contains changes to the following software componen= ts:
=20No changes to third party software are included in release 1.7.04
=20Release Date: August 28, 2014
=20i2b2 Release 1.7.03a contains changes to the following software compone= nts:
=20No changes to third party software are included in release 1.7.03a
= =20Release Date: August 20, 2014
=20i2b2 Release 1.7.03 contains changes to the following software componen= ts:
=20No changes to third party software are included in release 1.7.03
=20JIRA ISSUES: [CORE-135]=
=20In 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.
=20JIRA ISSUES: [CORE-141]=
=20In 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
=20Release Date: July 1, 2014
=20i2b2 Release 1.7.02 contains changes to the following software componen= ts:
=20No changes to third party software are included in release 1.7.02
=20JIRA ISSUES: [CORE-95] a= nd [WEBCLIENT-56]
=20In 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 | 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
In the i2b2 Web Client, a new option called Change Password now a= ppears in the Web Client's toolbar.
=20 =20Clicking on Change Password will open the i2b2 Change Password= window.
=20 =20In the i2b2 Workbench, a new button labeled Password has been add= ed to the i2b2 desktop title bar.
=20 =20Clicking on Password will open the Set Password window.
=20 =20The 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:
=20Once 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 | 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
Release Date: February 4, 2014
=20i2b2 Release 1.7.01 contains changes to the following software component= s:
=20No changes to third party software are included in release 1.7.01
=20Release Date: December 20, 2013
=20i2b2 Release 1.7 contains changes to the following software components:=
=20In release 1.7 the i2b2 Server has been updated to use the follow= ing versions of third party software.
=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. Server edu.harvard.i2b2.server-common= p> Client edu.harvard.i2b2.common | =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).
=20The first component to these queries is the list of events defined by th= e user.
=20The 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.
=20Users 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.
=20The 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.
=20The 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.
=20It 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.
=20The following two sections will describe how to run Temporal Queries in = the i2b2 Web Client and the i2b2 Workbench.
=20In the i2b2 Web Client there are five basic steps in defining a tempo= ral query in the Query Tool view.
=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
The first step is to change the Temporal Constraint to Define sequenc= e of Events.
=20 =20Once 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 =20The 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.
=20To define the events simply click on the Page selection box and s= elect Event 1 from the drop-down list.
=20 =20The 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.
=20Once 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.
=20If you need to add a third event you can click on the New Event butto= n located next to the Page selection box.
=20As 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.
=20The page will display as follows:
=20 =20In 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.
=20In the i2b2 Workbench there are three pages or steps in defining and run= ning a temporal query in the new Temporal Query Tool view.
=20Each page as well as defining constraints is further defined in the next= few sections.
=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
On this page you will define your population requirements.
=20 =20As stated earlier there are two components to a temporal query= ; (1) List of events and (2) the relationship between the events.
= =20The second page is where you will define both the events and their relat= ionship.
=20 =20On 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 =20There are some minor differences in terminology or layout that needs to = be noted in this release note.
=20In 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.
=20If 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 =20The 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.
=20In the existing Query Tool view ("Classic") the exclusion constra= int was defined by clicking on the button labeled Exclude.
=20 =20In the Temporal Query Tool view (New) the exclusion constraint wa= s rolled into the window for defining the Occurrence constraint.
=20 =20The 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 =20The above option is equivalent to the Exclude feature in the clas= sic Query Tool view.
=20New 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 | 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
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;
=20Users can now retrieve the next or previous grouping of previous queries= by the date in which the query was created.
=20 =20The Previous button () will retrieve the group of previous queries that occ= ur prior to the date displayed in the date / time field.
=20The Next button () will retrieve the group of previous queries that occur after= the date displayed in the date / time field.
=20A 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:
=20In 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.
=20The 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 | 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 | =20
Patient Sets View=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). The patient sets can be expanded to display a list of patients. Users can drag an entire patient set or a single patient to other views =
in the i2b2 Workbench. Users can also perform a search in which they can search by the name of =
the patient set or for a list of patient sets that contain a specific patie=
nt. 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. 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. 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
OpenEMPI is an open source Enterprise Master Patient Index (EMPI) which =
is developed and supported by another community. The i2b2 IM cell has been =
developed to allow communication with OpenEMPI for those sites that choose =
to use it as their patient repository. For additional information on OpenEMPI please see their website by going=
to the following location: https://openempi.kenai.com/ 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. The following new tables were created as part of the new IM cell. 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. The PATIENT_MAPPING table in the CRC has been updated to include =
the following: 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
The i2b2 database scripts have been updated to include the table creatio=
n and data insert scripts for a PostgreSQL database. 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. 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. Mac OS is a registered trademark of Apple Inc. Eclipse Galileo is a registered trademark of the Eclipse Foundation, Inc=
. All other trademarks are the property of their respective owners.Workplace Find View
=
=20
Find Terms: New feature call=
ed "Jump to Term in Tree"
=20
OpenEMPISupport
=20
PostgreSQL Database Support<=
/h3>=20
Data: New Tables created fo=
r the IM Cell
=20
=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
Data: New Columns added =
to support IM cell
=20
Data: Improved Patient Mappin=
g Data
=20
=20
=20
=20
=20
=20
=20
Important =20
The mapping information add=
ed to the CRC and IM tables is strictly for demonstration purposes and does=
NOT contain real patient information.New PostgreSQL Databa=
se Scripts
=20
Licensing
=20
Trademarks
=20