CONNECT Roadmap Draft version as of February 4 th,

CONNECT Roadmap Roadmap Development and Modification How was this roadmap developed and modified? –Based off of the remaining items from the Roadmap –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 efforts and guidance (e.g., Direct, MU2) –Collected industry input from industry and S&I Framework initiatives –Received feedback through forums and tried to anticipate future needs of the overall CONNECT Community 1 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 –Work within the new Open Source Community framework and governance model –Ensure that the Federal Agency CONNECT code branch maintains the ability to meet all environmental requirements –Be ready to address and incorporate expected industry changes such as Provider Directories, etc. –Continue to modularize and refine CONNECT and remove dead code/technical debt from the product 3

Proposed New Features –Build system administration GUI or portal to aid in gateway administration and configuration (CONN-48) –Direct specification and functionality support (CONN-381) –Support for X12 messages Research needed on use cases, message types, and requirements Are there CORE requirement dependencies –Streamlined CONNECT deployment or Production in 24 Hours Concept Refine lightweight gateway and simple, providing additional modularity and flexibility Work with community to build “out of the box” ready adapters for major EHRs and other interoperability infrastructure 4 CONNECT Roadmap Draft New Feature List

Proposed New Features continued –Auditing Cleanup and compliance Bring auditing into IHE/ATNA specification compliance (needed as part of Healtheway certification) (CONN-27) Modify gateway to adapter APIs to pass the Role value for audit purposes (CONN-161 & 287) –Implement functionality needed to support provider directories (expected 2014 specification completion) –Implement common toolset for payload/content creation and validation (CCDA, Quality Reporting, Population Health) 5 CONNECT Roadmap Draft New Feature List

Ongoing Development Work –Remaining Code Improvements related to CONN-29 related to build/deploy, code cleanup, and component technology upgrades to make the code is easier to maintain and build –eHealth Exchange (participant/ product) and Meaningful Use certification testing implementing the enhancements and defect fixes required to pass certification (CONN-282) –General Bug Fixes and Improvements 6 CONNECT Roadmap Ongoing Development Work

Monitoring Industry Initiatives –Continue to position CONNECT as an interoperability platform supporting key health data exchange use cases Review applicability of RESTful interface Blue Button and additional integration or data exchange workflows –Review S&I Framework initiatives –Meaningful Use Stage 3 objectives and measures (determine where and how pull capabilities will be supported) –Implement functionality needed to support any patient matching requirements 7 CONNECT Roadmap Monitoring Industry Initiatives

CONNECT Roadmap Ongoing Activities Ongoing activities –Support CONNECT releases per the Service Level Agreement (SLA) –Actively participate in the various ONC, industry specification and certification bodies –Represent the Federal version of CONNECT at 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! 8

Questions/Comments 9