Open Health Tools UI Platform Approved for Public Release: XXXXX. Distribution Unlimited.
Agenda UI Problem Open Health Tool UI Platform Collaboration OHT UI Platform Architecture Enabling Innovation
UI Problem: Allowing Clinician Access to Full Patient Health Record Siloed Health Data Multiple data sources Email Fax Phone Handhelds One size fits all User Interface (UI) EHR(s) EHR UIs lack of usability in nonstandard EHR user interface design 1 EHR EHR Scanned Records Lack of Interoperability between EHRs Patient Components of Health IT stacks Cost to organizations Health IT Budget Significant % of annual IT budgets 2 1. John Halamaka : http://geekdoctor.blogspot.com/2012/10/a-timefor-boundless-energy-and-optimism.html?m=1 2. Open Health Tools Documentation
Open Health Tools UI Platform Enable an adaptable Health IT Infrastructure, through providing an adaptable user interface that is flexible enough to meet the needs of a range of Health IT users as part of a suite of Open Health Tools Provide an Open Source pilot of end to end capability that demonstrates how to lower the barriers to innovation 4
Open Health Tools (OHT) Overview OHT Mission Statement Open Health Tools (OHT) is dedicated to improving the world s health and well-being by unleashing health IT innovation. Open Source Healthcare Transform the healthcare industry through open, standard-based interoperable systems, with source innovative technology and solutions Solution can serve a range of users Low resource -> High Resource Page 5
OHT UI Platform Collaboration MITRE Healthcare Research medcafe.org Parson s Institute of Information mapping A Research, Development, and Professional Services facility leveraging Knowledge Visualization to solve real-world problems Experts in UI experience Developed HealthBoard An open source presentation layer and prototype for the Patient Centered Medical Home Researcher from Columbia University Providing evidence based research on effectiveness of this UI approach 6
Open Health Tools UI Platform Solution An adaptable framework that enables a user to build a personal view of a patient record, using a palette of widgets, each of which is separable and platform independent allowing for flexibility and system evolution through substitutability.
Palette Based User Interface
OHT UI Platform Principles Design to the 80% DO no(or minimal) harm in customization Integrated, adaptable and consistent across modality/ platform Portability of access. Has to across multiple data repositories/ EHRs / products Palette of reusable, easily extensible and complementary components 9
Palette of reusable, easily extensible and complementary components Many small, independent pieces that each run standalone Easy to deploy and add new capability through adding new widgets User decides which components to use depending upon patient Allows use of Best of Breed components Replacing/ upgrading components is easy
Integrated, adaptable and consistent across modality/ platform Javascript framework on top of HL7 Standard Enables widgets to run independent of Platform Consistent display Laptop / Desktop Browser Mobile Device Tablet Device Lowering Barriers to Innovation UI developers only need to have knowledge of Javascript Add new widgets through simple Javascript API
Portability of access Has to across multiple data repositories/ EHRs / products Normalize data to HL7 Standard hdata Currently moving to FHIR UI developers only worry about one data format Less time and resources on taking care of underlying data interoperability issues More time can be spent on creating better ways to display the information to enable better and safer patient care 12
User Defined Interface Speed Patient Data Re-Acquisition Use Pre configured Interfaces Components/ Template Template: predefined set of components arranged optimally Default templates are provided to align with common use cases Create/ add new templates as desired User/Clinician Defined Views Customize view for patients Align with patient use cases Per Patient Views Some patients do not fit the mold Modify a view for a specific patient and save record view Displays saved view on re-engagement with Patient Speeds re-engagement with a patient
So Why Do I Care? One Size Interface Palette (Apps) Based Interface 14
How Does All This Enable Innovation? How to get from here? To here?
Enable Innovation VistA RESTful Services hdata/ HL7 GreenCDA UI Presentation
Provide Consistent Access to Data Pieces VistA RESTful Services hdata/ HL7 GreenCDA JSON Patient Medications Careplan Conditions Observations Procedures http://localhost:8888/observation/search?subject=f001
UI Platform: Enable Innovation Web Server RESTful Services hdata/ HL7 GreenCDA HTML AJAX
User Perspective Rapidly build the view you need for each patient Organize health record in a way that makes sense Developer Perspective Allows for rapid innovation Get the right tools to the right people Administrator Perspective Build right-sized system Enables system evolution and Best of Breed
Questions? For more information Open Health Tools (OHT) http://www.openhealthtools.org/ medcafe Contact : Gail Hamilton : ghamilton@mitre.org http://medcafe.org Live demo http://medcafe.org/medcafe Login: guest1, Password: guest1 HealthBoard http://piim.newschool.edu/healthboard/ Source code (GIT) https://github.com/medcafe/medcafe OHT UI Platform Collaboration Site http://hingx.org/groupmanagement/viewprofile?groupid=46