HL7 Survival Guide - Chapter 8 – Test Scenarios and Test Systems

644 views
496 views

Published on

This guide is for healthcare integration analysts and their managers. In this chapter, learn about testing, which is conducted during different phases in the interface cycle: during configuration and development; during the formal validation phase and during maintenance.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
644
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
32
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

HL7 Survival Guide - Chapter 8 – Test Scenarios and Test Systems

  1. 1. HL7 SURVIVAL GUIDE CHAPTER 8 A publication of A supplement to the HL7 Survival Guide, available at http://caristix.com/blog/category/hl7-survival-guide/
  2. 2. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 Caristix software brings your whole interfacing process together in a single, powerful platform. 2 ABOUT CARISTIX VENDOR- AGNOSTIC Work with any interface engine. NO MORE TRIAL AND ERROR Scope it right. Manage requirements. CUT TIME-TO- GO-LIVE Up to 50%. CLEAR YOUR INTERFACING BACKLOG Simplify dramatically. Align teams. REQUEST A DEMO http://promo.caristix.com/demo/
  3. 3. WWW.CARISTIX.COM SHARE THE SLIDE DECK CHAPTER 8: Test Scenarios and Test Systems
  4. 4. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 It’s time for testing, which is conducted during different phases of the interface lifecycle 4 Why Test?
  5. 5. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 For the development phase of your interface: • Test to avoid introducing new problems. • Test your code to make sure you are not interjecting errors. • Make sure you interface makes sense and meets your requirements. For the validation phase: • Determine that the interface works well. • Make sure it meets of the requirement of clinical workflow. • Test performance, extreme data cases. • Check how well the interface supports large volumes of data. 5 Why Test?
  6. 6. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 During validation, automate your testing • Be able to connect to web services or a database, such as by calling a web service, and check in the database after sending a message. • Validate inbound and outbound messages. • Validate ack and nack. • Generate values and test messages from a profile or specification, and generate a large volume of data/messages if you’re conducting volume testing. • Repeat test plans/scenarios, and create reports. 6 What to Look for in a Test Tool
  7. 7. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 7 What to Test • Understand the clinical workflows being supported by the interface • Test to be sure that the interface engine behaves as expected for both standard as well as unexpected workflows. – With edge cases, consider more possibilities • Test to be sure you are not introducing errors. • Use sample messages and those that verify beyond the basic exchange of data. • Automate your testing. – Increase testing flexibility • If provided use vendors’ validation guides fill of test scenarios. – Makes sure those scenarios match your workflows
  8. 8. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 Make sure that your tests cover your interoperability requirements, and include the following: • 1. Workflow. Confirm the interface engine handles your standard workflows as expected. • 2. Edge cases: unexpected values. If you’re testing birth dates, include 1899 as well as 2017. Include dates with the month and day reversed. Try different abbreviations for the days of the week. Check all caps on names. Check accented names. Check hyphenated last names, and those with an apostrophe. • 3. Performance, load, and network testing. Though interface developers don’t normally test network infrastructure, you may want to do this during the validation phase to see how workflows and data are impacting overall infrastructure performance. A high-volume interface may need more load testing than a low-volume interface, depending on your interface engine and connectivity infrastructure. • 4. Individual systems. You should test each system on its own, kind of analogous to unit testing in software development. For instance, in addition to making sure the surgical and billing systems handle workflow end to end, make sure they work separately. 8 Test Types
  9. 9. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 After configuring a test plan and test scenarios, configure you interface in a test system, not a production system: – If you forget to cancel or delete all test transactions once you’re through with testing, you’ll end up with faulty transactions in your production system. – You run the risk of impacting ePHI or HIPAA-protected health data. – You don’t want phantom data turning up in a CMS audit. Your clinical systems contain data that constitute a legal record. Set up a test system with the same configuration as your production system, including the same rights and versions. Upload enough patient data, and be sure your tests cover your requirements. 9 Create a Test System
  10. 10. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 As part of the testing process, run reports. The reports should document the following: • Number of times the test was run, as well as test duration – if you’re sending messages, this helps you understand performance. • Test results, including positive validations and failures. • The messages that were used; note the data source (SQL queries pulling from a database, an HL7 message feed, a batch file). • Summary of test scenarios that were run. 10 Test Reports
  11. 11. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 • A basic listener/receiver allows you to play/test messages without implementing your interface engine in a production environment. • Download the free Caristix Message Player to send or receive messages. Read about how we use Message Player here. 11 Message Player for Basic Listening and Routing
  12. 12. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 • Iterate more accurately • Verify functionality immediately • Save time and ensure a better go-live • Enable traceability – Easily troubleshoot – Determine responsibility for issues as you work with vendors and HIE partners 12 Why You Need These Artifacts
  13. 13. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 • Chapter 9 in the HL7 Survival Guide • Message Samples and Test Messages – The right tools are helpful when testing your interface. Most important is having the right message samples and test messages. Learn more in Chapter 9. – Blog link: http://caristix.com/blog/2012/11/hl7-survival- guide-chapter-9/ – Slide deck on Slideshare: coming soon. 13 UP NEXT: CHAPTER 9
  14. 14. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 8 Is a recommendation unclear? Disagree with something we said? Let us know! We thrive on feedback. Contact Us support@caristix.com 1-877-872-0027 14 QUESTIONS? FEEDBACK? © Caristix 2013. All rights reserved.

×