1. Connectathon 2009 Gazelle: HL7 V2 EVS, PIX Tests Agents, Automated Testing Project plans for Connectathon 2009 (February 23 rd -27 th 2009 ) November 14 th, 2008 (Update: December 9 th, 2008) National Institute of Standards and Technology (NIST) Robert Snelick

2. Testing Activities I HL7 V2 EVS  NIST and INRIA HL7 V2 EVSs to be used in post processing of messages captured during connectathon  This type of testing was conducted at the 2008 European Connectathon  Messages validated against HL7 conformance profiles, HL7 default tables, and local tables (connectathon tables  we need)  EVS Web Service follows new Gazelle design (including the proposed common file formats)  Can the results be seen immediately in Kudu? That is, are there plans to develop this?

3. Connectathon HL7 EVS Testing Proxy (Mirth) NIST HL7 V2 Validation Web Service Network INRIA Test Harness (Kudu) Vendor Application A NIST Resource Repository Web Service Results displayed in Kudu Vendor Application B Vendor Application C Vendor Application D Message Database Value Set Table File (XML) Results Report Files (XML) Profiles (XML) INRIA HL7 V2 Validation Web Service Profiles (XML)

4. Testing Activities II HL7 V2 EVS with validation context  Adds validation with context testing for the PIX transactions  Need to associate profiles, tables, messages, and validation context (assertion list) files  Maybe PDQ transactions (if we have time to build)

5. Connectathon HL7 V2 EVS Testing with Validation Context Proxy (Mirth) NIST HL7 V2 Validation Web Service Network INRIA Test Harness (Kudu) Vendor Application A NIST Resource Repository Web Service Results displayed in Kudu Vendor Application B Vendor Application C Vendor Application D Message Database Validation Context Files (XML) Value Set Table File (XML) Results Report Files (XML) Profiles (XML) INRIA HL7 V2 Validation Web Service PIX Test Scenarios Profiles (XML)

6. Testing Activities III NIST Test Agents as a “Vendor” Application  The Test Agents can be used as another Vendor Application  Tests conducted with the NIST Test Agents don’t count towards connectathon results  Vendors can use the Test Agents as a debugging tool at connectathon  Help NIST gather requirements and debug Test Agents (perform research experiments)  Test Agents (PIX Manager, PIX Source, PIX Consumer)  Need to configure Kudu with NIST Test Agents???

7. Connectathon HL7 V2 EVS Testing with Validation Context (NIST as Vendor) Proxy (Mirth) NIST HL7 V2 Validation Web Service Network INRIA Test Harness (Kudu) Vendor Application A NIST Resource Repository Web Service Results displayed in Kudu NIST PIX Source Application (Test Agent) NIST PIX Manager Application (Test Agent) NIST PIX Consumer Application (Test Agent) Message Database Validation Context Files (XML) Value Set Table File (XML) Results Report Files (XML) Profiles (XML) INRIA HL7 V2 Validation Web Service PIX Test Scenarios Profiles (XML)

8. Testing Activities IV PIX Source, PIX Manager, PIX Consumer Test Agents via Web Services  Access via client code (Future: Kudu, Gazelle Test Engine)  Not for Connectathon this year?

9. PIX Test Agents Web Service INRIA HL7 V2 Validation Web Service Network Vendor Client Code (Future: Kudu, Gazelle Test Engine) NIST IHE HL7 V2 PIX Source Test Agent WS NIST HL7 V2 Message Generation Web Service NIST Resource Repository Web Service PIX Test Scenarios Vendor Application NIST IHE HL7 V2 PIX Manager Test Agent WS NIST IHE HL7 V2 PIX Consumer Test Agent WS Validation Context Files (XML) Generation Context Files (XML) Value Set Table File (XML) PIX Test Scenario Results Report Files (XML) Profiles (XML) NIST HL7 V2 Validation Web Service

10. Testing Activities V PIX Source, PIX Manager, PIX Consumer Test Agents via browser interface (to framework/agent)  Provides a browser interface to conduct pre-connectathon and connectathon tests  Could be used by connectathon participates for pre- connectathon testing and connectathon testing  Tests conducted with the NIST Test Agents don’t count towards connectathon results  Vendors can use the Test Agents as a debugging tool  Future: Could handle Mesa tests  “Simulates” features that will be included on the Gazelle Test Engine  Could be incorporated into Kudu?

11. Test Agents Web Client Interface INRIA HL7 V2 Validation Web Service Network NIST Web Client (Browser) NIST HL7 V2 Test Framework NIST HL7 V2 Message Generation Web Service NIST Resource Repository Web Service PIX Test Scenarios Vendor Application Validation Context Files (XML) Generation Context Files (XML) Value Set Table File (XML) Pre-canned IHE PIX Test Scenarios Profiles (XML) NIST HL7 V2 Validation Web Service PIX Client Test PIX Feed Test Formatted Report Results Report Files (XML) Message Validation Logging Configure messages configure NIST IHE HL7 V2 Test Agent Message Generation Messages

12. Next Steps Develop example test case  PIX Scenario used at June meeting  PIX Manager is Software Partners  Need generation and validation context files  Need user table (2009 connectathon data) Test Client Browser Interface  Test Case Scenario Script  Configuration  Results Reporting (NIST and INRIA) Message Validation Service Message Generation Service Registry/Repository Compare Validation results with MWB, INRIA, NIST

13. IHE PIX Client Test Case Actors (PIX Source, PIX Manager, PIX Consumer)  PIX Source: NIST PIX Source Test Agent  PIX Manager: Vendor Application  PIX Consumer: NIST PIX Consumer Test Agent Test Case Description  A patient Farnsworth is loaded in the PIX Manager. This record of Farnsworth contains a global ID.  Using a local ID for patient Farnsworth, query the PIX manager to obtain the global ID for Farnsworth. Test Case Steps  PIX Source sends patient Farnsworth record containing the global ID to PIX Manager (ADT A04 message)  PIX Manager acknowledges receipt of ADT A04 message  PIX Consumer generates query (QBP K23) message with local ID for patient Farnsworth  PIX Manager generates response (RSP K23) message with global ID for patient Farnsworth

14. IHE PIX Client Test Case Processing PIX Source sends patient Farnsworth record with the global ID for Farnsworth to PIX Manager (ADT A04 message)  NIST Test Harness generates ADT A04 message and sends to PIX Source Test Agent  PIX Source Test Agent sends message to Vendor PIX Manager Application PIX Manager acknowledges receipt of ADT A04 message  PIX Manager processes message and generates/sends acknowledgement message to PIX Source Test Agent  PIX Source sends acknowledgement message to NIST Test Harness  NIST Test Harness validates the acknowledgement message using the EVS PIX Consumer generates query (QBP K23) message with local ID for patient Farnsworth  NIST Test Harness generates QBP K23 message and sends to the PIX Consumer Test Agent  PIX Consumer sends query message to Vendor PIX Manager Application PIX Manager generates response (RSP K23) message with global ID for patient Farnsworth  PIX Manager processes the message and generates a RSP K23 message  PIX Manager sends the message to the PIX Consumer  PIX Consumer receives the message and sends message to the NIST Harness  NIST Test Harness evaluates the response message using the EVS

15. Web Client Test Harness Provides a utility to conduct pre-connectathon testing No need for other vendors Web Client (Test harness) automates test script normally provided by the monitor  For example, PIX Feed Test:  Monitor inspects vendor database and checks message logs of sender and receiver  Automated testing will query receiving vendor for relevant data sent in PIX feed; apply validation