1. Developers Integration Lab (DIL) Nationwide Health Information Network Interoperability Presented By Mario Hyland, AEGIS.net, Inc. Federal Health Architect 1

2. Agenda »NHIN Testing Background »History Nationwide Health Information Network Validation (On-Boarding) NwHIN Interoperability Test Platform »Developers Integration Lab Benefits Architecture Plan for Phase 1 and Phase 2 »Discussion 2

3. NHIN Testing Background »To date the following Testing Approaches have been utilized by ONC: CONNECT Development Contractor would provide system level testing, mostly SoapUI Tests NwHIN Testing Workgroup (define test cases and test scenarios) NwHIN Validation (On-Boarding) Team would NwHIN Participants S&I Framework Test and Infrastructure Team currently maintains both a manual NwHIN Conformance Test Lab and an automated Interoperability Test Lab 3

4. 4

5. NwHIN Validation (On-Boarding) »The S&I Test and Infrastructure Team has collected empirical evidence over the past year which shows that numerous NwHIN Participants arrive to conduct Conformance Testing never having tested Gateway-to- Gateway communication. »This represents a significant risk to the Validation Team as they manage their schedule and develop approaches to scale their processes. »The next wave of Participants will potentially have less Exchange experience 5

6. NwHIN Interoperability Test Platform 6

7. 7

8. Objectives »Provide an environment for Participants to experience Gateway-to- Gateway communication earlier in the Development / Implementation phase of the Candidates HIT projects. »Provide an independent Testing Environment for emerging NwHIN Specifications (and their implementation) for the CONNECT platform or other Commercial Gateway Products (Axolotl). »Provide an independent Testing Environment for future CONNECT Releases. »Provide an Integration Environment to support code contribution from the Open Source Community, including Federal Partners. 8

9. Benefits »Aid with improving the NwHIN Validation (On-Boarding) Process, by ensuring Candidates poses the requisite knowledge before being scheduled for Conformance Testing. »Provide a Platform for non-CONNECT gateway products to test NwHIN Conformance and Interoperability with the NwHIN Specification – example Axolotl »Provide a Community approach to Open Source Development contribution and Integration which poses little to no impact the CONNECT Development Team »Provide for independent and enhanced testing capabilities 9

10. DIL Architecture 10

11. DIL Architecture 11

12. DIL Plan for Phase 1 12 »Standup the DIL (25 Nodes) »Standup the DIL Root Certificate Authority (CA) – Self Service »Standup the DIL UDDI – Self Service »Standup the DIL GUI / Profile Management »Performance Testing Round 1 (25 Nodes) (CONNECT 3.2 Plan) »Deferred (A-Sync) Testing (CONNECT 3.2 Plan)

13. DIL Plan for Phase 2 13 »Standup the DIL (200 Additional Nodes) »Upgrade the DIL GUI, including NwHIN Conformance & Interop Tests »Publish a Integration Lab Governance Plan »Continuous Integration Build Server / Lab Environment »Implement the Regression Testing Suite »Implement the Performance Testing Suite »Performance Testing Round 2 (200+ Nodes) (CONNECT 3.2 Plan) »Host CONNECT Experimental version w/SAML 2.0 (Metro 2.1)

14. Governance Model 14

15. Integration Lab Service 15

16. Discussion 16