Changes between Version 19 and Version 20 of i2b2 AUG 2013

Timestamp:

06/25/13 11:00:54 (11 years ago)

Author:

Richard Bramley

Comment:

--

i2b2 AUG 2013

@@ -23 +23 @@
 1. [#AUG8 Extending i2b2 with the R Statistical Platform]
 1. [#AUG9 Integrated Data Repository Toolkit (IDRT) and ETL Tools] ''(Sebastian Mate - Erlangen; Christian Bauer - Goettingen)''
+1. [#AUG10 Other Comments and Things Learnt]
 
 === i2b2 SHRINE Conference ===
@@ -327 +328 @@
 Presentation of the ETL tools using the Talend ETL framework.
 
+=== [=#AUG10 Other Comments and Things Learnt] ===
+
+==== Ontology Item Sub Queries ====
+
+Ontology items can be defined as a sub query.  This can be used for things such as:
+1. Date Caluculations
+1. Aggregate Values
+
+==== CRC Plugins ====
+
+There was mention made of CRC plugins.  I will need to investigate these further.
+
 == i2b2 SHRINE Conference ==
 
-
-
 === [=#SHRINE1 SHRINE Clinical Trials (CT) Functionality and Roadmap] ===
+
+SHRINE allows a query to be run across multiple i2b2 instances.  It is implemented as an i2b2 cell called the SHRINE adapter.  This adapter maps concept codes from their local value to the standard values used on the SHRINE network.
+
+==== SHRINE CT ====
+
+This project uses the i2b2 CT changes that allow individual patient details to be viewed in projects.  It extends the idea to allow the projects to span multiple sites.
+
+===== Workflow =====
+
+1. User creates a query using SHRINE to create a patient set.
+1. This patient set is dragged into the new Authorization Request Module in the we client.
+1. Project is created using the patients when the authorisation has been received.
+1. Specified user with the correct permissions can then view a limited set of data for these patients and run queries based on this patient set.
+1. Users from the patient's originating site with the correct permission can also view the patient PII data using SMART apps.
+
+===== Clinical Trial SMART app =====
+
+This SMART app allows the user to enter criteria for entering a clinical trial.  The app then tells the user whether the patient is eligible or if not why not.
+
+===== Release Stages =====
+
+The release of the changes will be staged as follows:
+
+1. All managers at each site to view queries run from the SHRINE on their i2b2 instance, including the patient sets returned.
+1. Improved web client UI.
+1. Allow patients sets to be assigned to multi-site projects, which make visible a limited data set.
+1. Allow selection of individual patients into user generated patient set.
+1. Enable patient-centric SMART apps showing PII to be enabled for multi-site projects.
+
 === [=#SHRINE2 SHRINE National Pilot Lessons Learned] ===
+
+A couple of presentations and a panel to discuss the problems encountered from running the SHRINE national pilot.  These included:
+
+* Authentication problems.  Running queries across multiple sites highlighted potential problems with user authentication:
+ * How can we be sure that the request has come from the correct organisation?  For this each node in the SHRINE had to install an SSL certificate for each other node.
+ * How can we be sure that the user making the request is authenticated?  Have to trust client's authentication.  Could use Shibboleth or OAuth.
+* Connectivity.  Network problems meant that quite often one or more of the nodes required for a query was unavailable, causing the query to fail silently.  These issues will be addressed in the SHRINE source code.
+* Ontology / Mapping / Semantic Issues.  See later.
+* Peer-to-peer issues.  Each node connects directly to each other node.  Thus making the administration effort rise exponentially with the number of nodes.
+ 
 === [=#SHRINE3 SHRINE Ontology Panel] ===
 === [=#SHRINE4 University of California Research Exchange (UC ReX)] ===