Download
1 / 53
E N D
2. NIST PIX/PDQ Pre-connectathon Test Tool: Overview I Supports Pre-Connectathon testing for:
3. NIST PIX/PDQ Pre-connectathon Test Tool: Overview II Options for meeting the 2010 V2 PIX/PDQ Pre-connectathon testing requirements:
Use the existing PIX/PDQ MESA tests
Use the NIST PIX/PDQ Pre-connectathon test tool
The NIST Tool is the preferred method for pre-connectathon testing (Steve and/or Lynn will provide a “Cookie”)
Options for meeting the 2010 V3 PIX/PDQ Pre-connectathon testing requirements:
Use the NIST PIX/PDQ Pre-connectathon test tool
December 1st is relaxed
NIST took on this role recently
Moving forward (2011?)
It is planned that this tool will replace the existing PIX/PDQ V2 mesa tests
Serve as a platform to support other IHE domain pre-connectathon testing
Serve as a platform to support ARRA meaningful use testing
Tool Benefits
Automated Testing
Centralized Testing
Low barrier to entry for tool use
Explicit test descriptions and test assertions
Raises the bar of conformance testing (will propagate to connectathon testing)
Has the capability to raise bar further
4. Acknowledgements NIST design and development team: Harold Affo, Roch Bertucat, Len Gebase, Sydney Henrard, Mary Laamanen, Andrew McCaffrey, Caroline Rosin, and Robert Snelick.
Eric Poiseau (INRIA/IRISA) provided the initial versions of IHE PIX/PDQ HL7 V2 conformance profiles.
The original MESA test cases for PIX HL7 V2 were developed by Steve Moore at the Mallinckrodt Institute of Radiology.
The original MESA test cases for PIX and PDQ HL7 V3 were developed by Rita Noumeir and Jean-Francois Pambrun at the University of Quebec.
Abby George of Booz-Allen-Hamilton made significant contributions to this tutorial and the user’s guide.
Beta Testers: George Cole, Laurie Flaherty (Allscripts), Umberto Cappellini, Susanne Hartenstein (TIANI SPIRIT), Fred Harmon, Anthony LaRocca (Sage), Vassil Peytchev, Justin Stauffer (Epic)
Wenzhi Li (Open Health Tools-OHT, MISYS) for making available an on-line PIX/PDQ Server that we could use for testing
5. NIST PIX/PDQ Test Tool: Access Tool Access—Open for business on November 12th, 2009
http://141.156.15.209:8080/NIST-PreConnectathonTests
Web-based application so downloads and installations are not necessary
User’s Guide is available at this site
Tool may be used in Anonymous Mode or Registered Mode
Anonymous: Does not require user registration and may be used to conduct ad-hoc system testing
Registered Mode:
Required to save pre-connectathon test results
Test reports are made available to the IHE project manager
Avenue for meeting pre-connectathon requirements to participate in the connectathon
IHE PIX/PDQ Google Group
Group to discuss testing issues and report tool bugs
http://groups.google.com/group/ihe_pix_pdq_testing
Go to site and request membership to the group
Preferred method of communication for discussing common issues
Vendor specific issues or bugs can be sent directly to rsnelick@nist.gov
6. Testing Environments
7. NIST PIX/PDQ Test Tool: Operational Process
8. NIST PIX/PDQ Test Tool: PIX Test Coverage
9. NIST PIX/PDQ Test Tool: PDQ Test Coverage
11. Test Case 10501 – PIX Query Case 1 and 2 – HL7 Version 2
12. Test Case 10501 – PIX Query Case 1 and 2
13. Test Case 10501 – PIX Query Case 1 and 2
14. Test Case 10501 – PIX Query Case 1 and 2
15. Test Case 10501 – PIX Query Case 1 and 2 (v2)
17. HL7 v2 Transactions Validation Process HL7 v2 Syntax Validation:
Ensure the message structure is valid with respect to the HL7 V2 message definition and the HL7 V2 conformance profile
Ensure that the conformance requirements such as usage, cardinality, data type usage, etc. are valid with respect to the standard and the HL7 V2 conformance profile that constrains the message in accordance with the IHE technical framework for a given transaction
Value Set Semantic Validation:
Ensure that elements that refer to a table are valid with respect to the value set it references. The value set is given by the HL7 V2 standard or as constrained by the IHE technical framework. An example includes confirming that the administrative sex element (PID.8) of the PID segment contains a value that is given in the HL7 V2 Administrative Sex table (HL70001).
Identify conformance violations of constraints implied by the IHE Integration Profile, these constraints are captured in a validation context file. An example of such a test includes an element that is fixed in the IHE integration profile (e.g., RCP.1 = I).
3. HL7 v2 MLLP Validation:
Ensure the message is valid with respect to the HL7 V2 MLLP specification for wrapping and unwrapping HL7 V2 messages. This is an implied test.
4. Test Case Specific Validation:
Verify element content against a validation context file that captures test values as defined in the pre-connectathon test cases.
18. Test Case 10501 – Test Case Specific Validation Checks
19. Validation Operational Process: Origin of Test Assertions
20. HL7 V2 Conformance Profile Example (ADT A04 Message)
21. HL7 V2 Table Library Example
22. HL7 v2 Validation Context Example
23. HL7 v2 Message Validation Report
24. Testing Validation Types
25. Conceptual View of HL7 v2 PIX Manager Test
26. Step 1 and 1a
27. Step 2 and 2a
28. Step 3 and 3a
29. Step 4 and 4a
30. Step 5 and 5a
32. NIST PIX/PDQ Test Tool: Steps for Test Execution Register/Log-in
Select Test Case
Client Type (PIX Source and Consumer, PDQ Consumer)
Server Type (PIX Manager, PDQ Supplier)
Configure Test
Run Test
View/Save/Submit Reports
33. Registration/Log-in To register, send the following information via email to rsnelick@nist.gov:
Name
Company Name
Email Address
Application Name (MSH 3.1) for V2 Only
Facility Name (MSH 4.1) for V2 Only
The IHE Actors that you plan on testing (e.g. V2 PIX Manager)
NIST Administrator will then send log-in credentials
Log-in is required to save test results, submit results to the IHE project manager, and gain credit for test completion
35. Review Overview
36. Select Test Case - Client
37. Select Test Case - Server
38. Configure – User Client
39. Configure – User Server
40. Run Test
41. View/Save/Submit Report
42. View Results – Validation and Summary Reports
43. View Results – Test Summary
45. HL7 V3 Validation Overview Check for correct Interaction ID (although no check on structure outside of correct root element name)
Implied communication message exchange test (i.e., SOAP—no WS-addressing)
Check against the validation context for the specific test case
Similar to v2
Not quite as robust and flexible as v2 testing yet
This will be improved in the coming weeks/months
Will incorporate our v3 External Validation Service (EVS)
47. Configuration Information V2 Applications sending ER7
IP Address: 141.156.15.209
Port Number: 9080
V2 Applications sending XML
IP Address: 141.156.15.209
Port Number: 9070
V3 Application
IP Address: 141.156.15.209
Port Number: 9090
V3 SOAP end-point
http://141.156.15.209:9090
48. Example PIX Source Vendor Configuration Information Configuration Information for sending V2 messages
Application Name: NIST_Swan_PIX_Manager_78 (varies)
Facility Name: NIST
IP Address:141.156.15.209
Port Number:9080 (ER7 Messages)
Port Number:9070 (XML Messages)
Configuration Information for sending V3 messages
Application Name: 2.16.840.1.113883.3.72.6.5.92 (varies)
Facility Name: 2.16.840.1.113883.3.72.6.1 (Optional)
IP Address: 141.156.15.209
Port Number: 9090 (V3 Messages)
49. Dynamic PIX/PDQ Server Application Name Allocation For each test case instance the name of the PIX Manager or PDQ Supplier is created dynamically
In order to interact with our PIX Manager or our PDQ Supplier Test Agent you will need to use the information provided in “Configuration Information” dialog
For example (V2):
Application Name: NIST_Swan_PIX_Manager_150
Facility Name: NIST
For example (V3):
Application Name: 2.16.840.1.113883.3.72.6.5.17
Facility Name: 2.16.840.1.113883.3.72.6.1 (Optional)
The life of this test agent exists only for the duration of the test
This ensures that each vendor test is isolated
If you send to an application name that no longer exists you will get the following response from our system:
Nothing from the user console—we’re still listening for messages
An acknowledge message with error is sent back to you over the network
50. Trouble-Shooting Site is unavailable
Typically means we are redeploying the application
This is a web application so we need to redeploy a .war file when we make changes
The downtime will be in the neighborhood of 15-20 minutes
We will not announce short term downtimes
DSL may be down
No response from console log
You may have sent to a destination that we could not process
i.e., An incorrect receiving name
In this case we will send back an acknowledge/error over the network
You need to check on your end
On our console log nothing will happen
If you determined that this was the problem you can resend a properly addressed message; we’ll still be listening up to the session timeout
Site appears to be down
Restart in a new browser window
Completed Report is missing
When we discover an error in the test case (i.e., the test case is wrong) we fixed it
Tests that passed using an incorrect test are no longer valid
This should not occur often
52. Summary New PIX/PDQ Pre-connectathon testing tool
Trial for the 2010 testing cycle
The tool is evolving…
So stick in there
We need your feedback
Serve as the platform for testing other IHE domains in future
Serve as the platform for ARRA meaningful certification testing as part of the NIST Healthcare Testing Infrastructure project
Components will be available in the NIST HIT Testing Infrastructure which will be enable integration into other tooling project (e.g., IHE Gazelle)
Current to-do list
Improve V3 validation
Improve test case descriptions
Bug tracking system
Development of test plans, cases, and documentation
Make software available
53. Support
54. Stick with us, things will only be muddy for a while…green grass is ahead
