The Open Library of HIE Presented by: Alesha R. Adamson John Bozada

 What is OLHIE  History of OLHIE  Stakeholders ◦ Open Health Tools (OHT) and Pronoia Health  OLHIE the Library Paradigm and Framework  Governance and policy  Project plan  Getting involved

Let Us Inform One Another

 The Open Library of HIE (OLHIE) is an online ecosystem that will allow “Authors” of HIE-related assets to share their work and provide “Readers” with real-world resources to inform their work. ◦ Interfaces: requirements, work-flow, templates, datasets, technical and user documentation ◦ Policies, tool-kits, and forms ◦ Model RFP and Contract language to encourage/require federal/state funded assets be contributed to the library ◦ Other source code for connecting EHRs, labs, pharmacies, and public health agencies

 Promote reuse, cooperation, and learning in order to reduce the cost of building and operating HIE.  Create a web application that allows readers to search, categorize, “like”, review, and create their own bookshelves that can be shared with other readers and inform authors.  Streamlined workflow for authors to publish, version, make private, and remove assets.

Where was OLHIE born?

Stephen says: “the HIE side of things will largely be bridged in the near and even mid term by developing interfaces… LOTS of interfaces… lots of CUSTOM interfaces… lots of EXPENSIVE custom interfaces.” Stephen Palmer Director, Office of eHealth Coordination, Texas

Accelerate connections between Health Information Exchanges (HIE). Facilitate the reuse of HIE interfaces, and other assets, especially those developed with federal or state funding. Reduce cost of interoperability Increase the potential for interoperability Promote community learning

 Community Engagement ◦ HIEs ◦ Vendor Community  Library Development  Workflow and Vetting

Who is interested in OLHIE?

 Delaware: Mark Jacobs  Georgia: Kelly Gonzalez  Texas: Stephen Palmer  Vermont: Terry Bequette

 Arizona  California  Colorado  Delaware  Georgia  Texas  Vermont  Hawaii  Illinois  Maryland  Nebraska  North Dakota  Wyoming

 Cerner  General Dynamics, Information Technology (GDIT)  Mirth Corp  Orion Health  College of Health Information and Management Executives (CHIME)  National eHealth Collaborative (NeHC)

 Name change (ILP OLHIE)  Asset repository, not just an interface repository  Tools and services for the future  Robust community  “Dollars for Deltas”  Availability of real-world assets to academia

 California eHealth Quality ◦ Requirements gathering session April 25 ◦ Committed to contributing code and non-code assets  HIE Ready Toolkit  Public Health Interfaces, and others ◦ Working with Redwood MedNet, Inland Empire HIE, Santa Cruz HIE and other State agencies

 Holding a joint requirements gathering session with VT and DE  Planning requirements gathering session in TX ◦ Local HIEs will be included  Scheduling a mid-phase “sanity check” with GA in June

What is OLHIE’s heritage?

501(c)(6) Non-profit Organization Provides facilitation, resources and governance to Open Source projects Improving the world's health and well-being by unleashing health IT innovation

Robert Kolodner, MD Chief Health Informatics Officer Dr. Brian Barry Chief Technology Officer Skip McGaughey Executive Director Chairman of the Board

Government Agencies Canada Health Infoway (CA) Indian Health Services (US) National Health Service (UK) National eHealth Transition Authority (AU) Veterans Health Administration (US) Academic Institutions Australian Health Research Centre (AU) Cardiff University (UK) Linkoping University (SE) Mohawk College (CA) Georgia Tech (US) Oregon State University (US) Florida International University (US) Healthcare Systems (US) Mayo Clinic Hartford Healthcare System Southeast Texas Health System Standards Organizations and Open Source Foundations Eclipse Foundation, Inc. HL7 IHTSDO Object Management Group (OMG) Open Health Data Other Non-Profit Organizations AHIMA Foundation Global Patient Identifiers, Inc. Internet2 MITRE Corp.

Vendors 5AM AEGIS Andago Apelon Bedarra Research Black Duck Cambio Healthcare Cognitive Medicine CollabNet Collaborative Software Initiative DSS, Inc. Discovery Machine FEI Firestar Software GDIT Global Patient Identifiers, Inc. Harris Corporation Hewlett Packard IBM Inpriva ITG Health Jembi Health Systems JP Systems Lamprey Networks, Inc. Medsphere NetGen Software NexJ Nitor Group Ocean Informatics OpenMRS Oracle Palamida Phast PHII Pronoia Health Red Hat Sage Shoulders Corporation SETHS TBS Tolven

Open Library of HIE (formerly ILP) Platform Implementation Project Academic Outreach HL7 Tooling Common Terminology Services (CTS2) Conformance Services Privacy, Access and Security Services Model Driven Health Tools (MDHT) Medical Devices Interoperability Platform SNOMED CT Project Supply Chain Tooling Project IHE Profiles Project Canadian HER OpenCDS OpenExchange OHT Toolkit Application Integration Platform

 Proven governance framework  Provide an environment conducive for collaborative development  Can achieve synergistic benefits

The Library Paradigm

Only 1 of 4 requirements gathering sessions have occurred at the time of this presentation.

 Atomic unit for all assets is “Book”  A Book may have different Chapters ◦ Table of Contents, keywords, category ◦ Interface code, requirements specifications, diagrams ◦ Links to outside resources  A Book may be downloaded in part or in its entirety  Books can be rated and reviewed by members ◦ Peer promotion ◦ Search engine weights

 Revisions will be maintained  Level set of Categories provided by OLHIE: ◦ Interfaces, Policy, Forms, Contract/RFP Language  Additional categorization is managed by the members ◦ HL7, North Dakota, Minors, Interstate  Interfaces are a special kind of Book  Source and destination systems  Engine vendor  Message type

 Enable search engine indexing ◦ Google, Yahoo, Bing  Search by Category ◦ I’m new to this, where do I get started ◦ I want to see all the affinity domain documents ◦ I want to see everything from Hawaii  Hover-over review of content and authorship  Open a Book  Put Book on your Bookshelf

 Must sign contributor agreement ◦ Author attests that they own the IP or that they have authority to share the content ◦ Agreement will be counter-signed  Control their content ◦ Create, update, delete ◦ Approve Co-authors ◦ Promote contributors to Co-authors ◦ Approve content from Contributors ◦ Publish, keep private  View all Books contributed ◦ Author’s Bookshelf  Be alerted when reviewed or rated  Choose to allow messages from Readers ◦ With or without exposing their contact information

 Readers have created accounts, but may still be anonymous (IamElvis)  Search and retrieve Books  Promote and review Books  My Bookshelf, My Favorites  Can request to be a Contributor  Can request to be an Author or Co-author  Send messages to Authors

 Anyone may access the Library from a tablet or PC  Do not have a personal bookshelf  Are not able to leave ratings or reviews  Are not able to publish or suggest content  May create a Reader account

Suzallo Library at UW

 Collections of Books as a Book ◦ “California – The Book” or “I’m In – The Book of Authorization Forms” or “JohnBob’s Book of Lab Interfaces”  Free and subscription content  “Publishers” that manage many authors  Protected content  Link walking to outside resources  Reading clubs  Informing search criteria/weights with Reader ratings  Establish content affinities ◦ If you liked *that* you’ll love *this*  Subscribe to someone else’s bookshelf …What else you can think of?

Client Technology: Runs in a modern browser Built with Google Web Toolkit gwtBootstrap gwt-dnd Database: ? MySQL v 5.2 ? OrientDB ( Build tools: Maven v3 Development process management: LeanKit Server Platform: JBoss AS 7.11 ? OpenShift Content Management Repository (CMR): ? HingX ? ModeShape Code Repsoitory: GitHub ( h/olhie) h/olhie User Story Development: FreeMind IDE: Eclipse Java EE IDE for Web Developers - Juno Service Release 1 Optional: JBoss Tools

How is OLHIE governed?

 Governed by a set of bylaws that provide for: 1.Membership in OLHIE 2.An Executive Steering Committee (ESC) 3.Project Director 4.Committees

 Includes US states and/or territories, HIEs, vendors, other parties that wish to contribute  ESC will determine if prioritization is necessary  Members must ◦ Complete a membership application ◦ Be approved by a majority vote of the ESC ◦ Execute a membership agreement.

 Manages business and technical affairs  Members will include: ◦ Project Director ◦ At least three State Health IT Coordinators ◦ Representatives of HIEs, vendors and other interested parties ◦ Other appointments will be made by the ESC before adopting bylaws

 Responsible for day-to-day management of OLHIE

 Architecture and Technology Committee (ATC)  Change Control Committee (CCC)  Legal and Policy Committee (LPC)

Make recommendations to the ESC about the technology platform, development methodology, operations methodology and other technical issues.

Responsible for managing the content contained within the OLHIE repository. Responsible for establishing standards for data quality and completeness, and reviewing and approving data contributions.

Responsible for reviewing and taking appropriate actions about the intellectual property (IP), contractual and other legal policies

 OLHIE will be available to anyone, including: ◦ Discovery of interface assets ◦ Viewing and downloading assets distributed under open source or creative commons licensing  Ongoing discussion regarding commercially licensed assets

 Sustainability Plan  Committee Development  IP Policy  Other policies and procedures  RFP and contract language

When will OLHIE be ready?

How can I contribute?