CONNECT Roadmap Updated version after June 27 th, 2013 Requirements and Prioritization Meeting 1

CONNECT Roadmap Roadmap development and modification How was this roadmap developed and modified? –Held CONNECT JAD on September 19, 2012 –Synthesized feedback received in various venues from the core federal partners (HHS/ONC, VA, DoD, SSA, CMS) –Listened to needs of other federal agencies (e.g., IHS) –Incorporated applicable ONC initiatives (e.g., Direct, MU2) –Collected industry input at Code-A-Thons and User Group Mtg. –Received feedback through forums and tried to anticipate future needs of the overall CONNECT Community 1 –Socialized with and received feedback from the DE&I Work Group in December 2012 and January 2012 –Updated requirement and prioritization meetings May 23 rd & June 13 th 1 CONNECT Community includes the federal funding partners and other organizations that have adopted or that are interested in adopting CONNECT 2

CONNECT Roadmap Continually Evolving Based on Needs What are the guiding principles we followed to build this roadmap? –Roadmap is not “set in stone” – we continue to update and refine this as a “living artifact” through the interaction with partners and CONNECT community –AGILE! Build targeted functionality to reduce delivery risk and deliver value at regular intervals – i.e., avoid “big bang” releases –Deliver one CONNECT release roughly every 3-4 months –Increase automation by maturing release testing suites –Continue to modularize CONNECT and remove dead code/technical debt from the product –Leverage contributions from the broader CONNECT Community 3

Agreed upon revised scope for 4.1 (Delivered April 11th) –CONNECT 4.1 Scope Added JBoss (open source version) support (CONN-303) Implemented Continuous Integration (CI) improvements Optimized code and build logic, reducing build time from 25 to 10 min Upgraded Apache CXF to Resolved 15 CONNECT 4.0 tickets reported by the Community –Removed lower priority HIEM + WS Addressing features (MB 3/26/13) Originally planned as part of 4.1 in the OY2 Road Map –Was released as a “silent” release 4 CONNECT Roadmap Work Package #1 Current Status

Additional agreed upon release –CONNECT 4.2 (Avaiable July 31 st ) Implement support for JAVA 6, required by WebSphere 7 (CMS/SSA) and WebLogic 11g (VA/CMS) (CONN-350) Multi-Specification DQ version identification (CONN-15 & 46) –Initiating and responding –Included in 4.2 in addition to the retrofit into 3.4 Higher priority community support tickets (TBD) 5 CONNECT Roadmap Work Package #1 Current Status

Additional agreed upon scope through June –eHealth Exchange HIE Certified Network Program Pilot Participation (CONN-312 & 317) Actual Certification for CONNECT (3.X or 4.X) is still TBD Estimated Completion date of May 31 st, 2013 –May 21 st, 2013 CONNECT User Group Meeting (CONN-33) –Continue ad hoc CONNECT Community Support, subject to resource availability 6 CONNECT Roadmap Work Package #1 Current Status

CONNECT Roadmap Work Package #1 Remaining items Work Package # 1 –Complete development of a robust CI and automated test environment to mature the overall product Complete initiatives to increase code quality, build and deploy ease and product stabilization (Numerous tickets in the backlog [such as 75,86,358,360] main feature ticket is CONN-29) 06/13/13: Important but partners would like to see this worked through the open source community as much as possible, Work will continue to address these tickets as bandwidth permits –CONNECT 3.4 (A 4.3 versus 3.4 Managing Board decision needed by 7/16) Multi-Specification DQ version identification (CONN- 15 & 46) –Responding and Initiating Will need partnership with DOD resources to jointly test 3.4 Tentative delivery in fall of 2013 (September/ October) 7

Next Proposed Release 4.3 (TBD in Fall 2013) –Implement the enhancements and defect fixes required to certify CONNECT 4.x under the new eHealth Exchange product certification process (CONN-282) Well begin testing with 4.2, certified version will be 4.3 Known issue with auditing specification compliance Expect additional issues will need to be addressed –Update Direct functionality to current phase of RI (CONN-381) CONNECT needs to support Quality of Service and Trust Bundles implemented in latest version of specifications Needed to support MU2 requirements Not originally in WP #1 but is a critical production need –Higher priority community support tickets (TBD as time and resources permit) 8 CONNECT Roadmap Work Package #1 Remaining items

CONNECT Roadmap Post 4.3 Feature List (Prioritized 6/27) Top priorities will be considered for inclusion in Release 4.4 6/27/13: Feature List –Build system administration and event viewer GUI to aid in gateway administration and configuration (CONN-48) Gathered some high level requirements during June 13 th meeting –Address findings for the Fortify security scan performed on Release 4.1 (CONN-488) –Refine lightweight gateway and simple API and interfacing adapters providing additional modularity and implementation flexibility (CONN-447) Further tighten APIs among CONNECT components to allow adopters to better incorporate new implementations and more “ready adapters for interfacing with existing systems and EHRs –Implementing support for Provider Directories per industry specifications (Estimated spec ready fall of 2013) (CONN-447) 9

CONNECT Roadmap Post 4.3 Feature List (Prioritized 6/27) 6/27/13: Feature List (Continued) –Implement common toolset for payload/content creation and validation (CCDA, Quality Reporting, Population Health) Discussed but goals and deliverables still to be determined –Remove required use of a database for audit/transaction/event logging (SSA/CMS) (CONN-219 & 335) –Build “CONNECT in 24 Hours”-type artifacts to lower barrier for new adopters (SSA) (CONN-445) –Build support for secure and unsecure inbound traffic, to better allow CONNECT to integrate with XML appliances (CMS) (CONN-283) –Modify gateway to adapter APIs to pass the Role value for audit purposes (VA) (CONN-161 & 287) 10

CONNECT Roadmap Post 4.3 Feature List (Prioritized 6/27) 6/27/13: Feature List (Continued) –Implement future Direct phases, as needed, to remain in sync with other Direct implementers –Implement asynchronous routing mechanism for DS to be more seamless (CONN-236) –Build FIPS install instructions for WebSphere 7 and WebLogic 11g (CONN-30 & 341) –Certify CONNECT 3.3 under the eHealth Exchange product certification program (SSA) (CONN-388) –Implement WSA Message ID enhancement based on Spec Factory guidance (CONN-28) –Complete HIEM tasks deferred from CONNECT 4.0 (CONN-26 & 34-36) 11

CONNECT Roadmap Ongoing Activities Ongoing activities –Support CONNECT releases per the Service Level Agreement (SLA) –Actively participate in the various ONC and industry specification and certification bodies –Hold community events, such as User Group Meetings and Code-A-Thons –Work with the eHealth Exchange and other exchanges, as appropriate, to ensure CONNECT remains aligned with industry needs –Will continue to refine this roadmap as requirements and priorities become clearer! 12

Questions/Comments 13