I2B2 Users Group

1
I2B2 Users Group

• https//www.google.com/a/i2b2aug.org
• There are many institutions beginning to
  collaborate on this google group U. Mass,
  UTMC-H, UCSF, U. Wash
• Please remember to click on Site Map in upper
  left corner after logging in

2
UCSF Field Report

• i2b2 Related Activities

3
Platform Selection

• i2b2 on Sybase IQ
• i2b2 Sybase VM Now Available (we would like to
  distribute that)
• Initial Datasets are from UCSF Med Center UCare
  (with some Flowcast), PICIS
• We have initial an data dump and are now
  designing the ETL environment based on that.

4
Initial Customers

• We have identified 2 early adopter researchers
  to help drive our initial requirements.
• Quality Engineering (Join of our initial core
  i2b2 with 7 Health Provider DBs)
• Pediatrics (with some addition clinical data)

5
Current Status

• Building production subnet
• Building ETL Environment
• PHI/Disambiguation
• BAA negotiation with medical center
• i2b2 Environment
• Security Infrastructure

6
Four Technical Initiatives

1. Use of Column Oriented Databases in support of
   translational biomedical science
2. Ontology Mapper
3. MPI/PHI/Disambiguation
4. Alternate UI Layers for i2b2

7
Column Oriented Databases

• Optimized for Read (which matches the high level
  requirements of a typical IDR)
• This has ramifications regarding the support of
  alternate user interfaces (such as for Quality
  Process Improvement)
• Acts as a native data cube
• This can dramatically shorten the data request
  lifecycle for researchers using SAS, STATA and
  other similar environments

8
Ontology Mapper(UCSF, U.Rochester, UCD, UPenn,
U.Washington)

• Trades high cost up-front data governance for
  the mapping of data on request.
• Rules based system (Protégé) which translates
  data between terminologies as a background task).
• Scalable and Inexpensive Approach
• (rules are re-usable, requires only BA skill
  level to handle requests, promotes self service
  architectures, dramatically lowers cost of
  deployment and system maintenance)
• The OntoMapper network protocol has been
  included in HL7 CTS II for next ballot (in 1
  month)

9
OntoMapper Status

• High level design of system is now completed
• Seeking grant funding
• Currently involved in detailed resource and
  project management planning and scheduling
• Currently establishing necessary infrastructure
  for the eventual software development that will
  soon follow
• Establishing initial OntoMapper User Group to
  assist us in prioritizing features during
  implementation cycle and for recruitment of
  collaborators on four derivative research papers.

10
PHI/Disambiguation

• Have completed some initial design work
• Imports from multiple medical centers
• HIPAA Honest Broker functionality as it relates
  to access to multiple med center specific PHI
  Databases
• Locating PHI databases within medical center
  walls while still supporting system-wide (across
  multiple medical centers) disambiguation. (A
  federated MPI)

11
Alternate UI Development

• Work on layered UIs that talk to i2b2 web
  services interface
• Integration of i2b2 with Microsoft Business
  Catalog Server and SharePoint
• Integration of security models between portal
  environments (like SharePoint) and i2b2