Thank you for joining. This presentation will begin shortly. May 22, 2018

Welcome to the OSEHRA Innovation Webinar Open API and Open Architecture  Work Group (OA2)  Purpose, Goals and Scope Andrea Hopkins Director – Senior Solution Architect CGI Federal Thomas Pole Executive Architect Healthcare Technology Unisys Federal Opening slide

Agenda The Opportunity Why Open Architecture Why now? Why Open Architecture How is that different from Open API? Specific OA2 WG Work Products What are our tangible goals? Near Term OA2 WG Events and Projects Planning, out reach, analysis & design, pilots Discussion The overall OA2 WG goals are defined but the plans to achieve those goals are TBD by all of us Your input is where we’d like to focus today

The Open API & Open Architecture Opportunity The current state of Healthcare IT needs and capabilities HIT modernizations are very popular, very difficult, and rarely succeed From Standish Research Chaos Reports Success = On time, on budget, functionally complete Challenged = Significantly deficient on time, budget and/or functionality Failed = Not delivered or delivered with less than minimum functionality All IT modernizations have this issue, but HIT is especially challenged Special circumstances, HIT market is very dynamic lately: The Federal Gov. movement from GOTS to “COTS” The state of interoperability versus the needs and hopes for interoperability The movement toward Open API’s (aka pull mode) replacing Healthcare IT’s publish and subscribe interoperability protocols (aka push) model Explosion in interest in mobile in general, patient facing app’s especially Security issues, is HIT the new #1 favorite target for bad actors? The Open Architecture Opportunity

The Open API & Open Architecture Opportunity Can more attention to HIT Architecture better support the needs of HIT consumers? Not just the technical architecture (i.e. structure) but also the operational architecture (i.e. user work flows and physical environment) Greater focus on operational architecture will both improve technical architecture, and could greatly improve organizational change management efforts The Open Architecture Opportunity

Why Open Architecture How is Open Architecture different from Open API’s Architecture includes the systems Components (i.e. parts and pieces) Integration points (i.e. Where components connect) The operational context of the system (e.g. user work flows, physical environment, governance/regulation, etc.) API’s are the most common form of integration points or system interfaces API’s are intrinsically part of the Architecture Open API’s are a critical requirement for an Open Architecture Our goal is to: Leverage the work already being performed in other WG’s Enable collaboration among many groups, not only within OSEHRA Why Open Architecture

Specific OA2 WG Work Products Conceptual Open Architecture (COA) for EHR and related systems The work product that is not TBD, it captures the goals of the OA2 WG Including both technical and operational dimensions of the COA Open Architecture Community Library Enable OA2 related cross-organizational discussion Collect Open API and Open Architecture information in an online community library Enable and enhance collaboration across WG’s Pilots/Proofs of concept of specific aspects of the Conceptual Open HIT Architecture Validate the COA by designing and implementing systems that use it Develop design patterns that derive application architecture from the COA’ which is really an enterprise architecture Potential Open Architecture Work Products

Pilots & PoC’s: Focus on What has Changed Focus on the changes, which are mostly driven by changes in our operational environment New work flows Patients as end users: portals, PHR’s, mobile health apps, home car HIT services New governance Movement from HIE to Open API Renaming certification from MU to Interoperability New systems in the US Gov context diagram SaaS from Cerner Amazon, Apple and others HIT services and applications Focus on the effects of operational architecture changes on the technical architecture Potential Open Architecture Work Products

OA2 WG Events and Projects Bi-weekly meetings starting July 11 or 25? Week before or following the OSEHRA Summit July 18-20 OSEHRA Summit presentation/WG meeting Projects (examples to start discussion) Common components: e.g. Patient ID, protocol translator, Import/Export function for complete patient records Support and infrastructure features: security, survivability, performance, access New applications (leverage common components) e.g. Data migration, Personal Health Record, Med Device management interfaces Events and Projects

Discussion Questions Suggestions Decisions Starting date for bi-weekly calls, suggestion: July 11th to plan for OA2-WG meeting at summit July 25th to start on our agenda Forming sub-committees on specific topics/tasks Open Architecture Questions and Discussion

Thank you! Questions? andrea.hopkins@cgifederal.com thomas.pole@unisys.com Opening slide

OSEHRA Summit: Register Now! Opening slide