HIE Certified Network Pilot Testing w CONNECT May 02, 2013

Purpose and Goals for FHA CONNECT program pilot testing participation Better understanding of test procedures and tools -> Help with execution during the final certification testing program. Provide feedback to CCHIT regarding the test tools/test cases -> Help improve the overall testing process for the community. Validate the core functionality of CONNECT with regards to PD, QD, RD, MP/AF(MA) NwHIN specifications and identify gaps or missing functionality if any -> Help identify any non-compliant issues sooner, no surprises later Understanding the level of effort for test case execution -> Help in planning and effort estimation for final certification 2

Purpose and Goals for FHA CONNECT program pilot testing participation (Continued) Provide feedback and guidance to federal partners and other adopters using CONNECT who are looking to certify their CONNECT HIE implementations in the future -> Support community members looking to certify their CONNECT implementations 3

Important Notes Participation in pilot does not result in certification of vendor product. –CONNECT participation in the pilot does not guarantee that CONNECT will be certified. Program team needs to better understand how can CONNECT as a product be certified. –Is CONNECT required to have fully functional adapters for certification of HIE Network? –Is there a modular approach or other options being discussed i.e. gateway only option and what does that entail? 4

Resource Pages Link to questionnaire and test cases for CONNECT: – ONNECT_Questionnaire_with_Test_Cases-Wave_1.xlsxhttps://developer.connectopensource.org/download/attachments/ /C ONNECT_Questionnaire_with_Test_Cases-Wave_1.xlsx Test case detail and status page – –Table smoke test cases + 20 test cases that team was asked to focus on first. ( –Table 2 - All applicable test cases – 128 test cases

Test cases team needs to focus on first(Table 1) 1) Smoke test Service Set (Initiator and Responder) –Test cases confirms connectivity with DIL by requiring CONNECT to initiate and respond to a simple sequence of PD/QD/RD requests. (CONN-317) –6 test cases 2) Patient Discovery(Initiator) –Subset of PD test cases initiating PD requests related to certificate revocation and expired certificate. –2 test cases 3) Query for Documents (Responder) –Subset of QD test cases focused on handling error cases as the responder –16 test cases 4) Retrieve Documents (Responder) –Subset of RD test cases related to retrieving one document and handling invalid request –2 test cases 6

All applicable test cases for CONNECT (Table 2) 5) Patient Discovery (Initiator and Responder) –Test cases initiating and responding to PD requests including handling error scenarios –23 test cases (includes 5 MA test cases) 6) Query for Documents (Initiator and Responder) –Test cases initiating and responding to QD requests including handling error cases –95 test cases (includes 71 MA test cases) 7) Retrieve Documents (Initiator and Responder) –RD test cases focused on validating retrieving a single or multiple documents successfully and handling error scenarios –10 test cases 7

Questions and Discussion 8