: This guide is for healthcare integration analysts and their managers. In this chapter, learn about choosing the right message sample and test messages. You need messages samples and test messages that reflect your environment.

1. HL7 SURVIVAL
GUIDE
CHAPTER 9
A publication of
A supplement to the HL7 Survival Guide, available at
http://caristix.com/blog/category/hl7-survival-guide/

2. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9
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. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
CHAPTER 9: Message Samples and Test Messages

4. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9
Now that you know what is needed to test your interface, you
need to feed the right message samples and test messages.
4
What makes messages right?

5. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9
Sample messages and test messages that reflect your
environment:
• Your ADT message flow
• Your specific lab codes and text messages
• Your case mix
For testing:
• Sample messages give you custom formats, structure and
data values.
• Look at the issues highlighted during gap analysis.
• Make sure your messages cover your use cases.
5
What Makes Messages Right?

6. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9
You need production data.
• Once you have the right message samples and test
messages.
• Make sure you have a sufficient volume of quality test data.
• Make sure your productions data reflects the data you work
with day in and day out.
– Both data type and format as well as volume
• The result:
– Accurately test for load and performance.
– Avoid message workflow problems that can bring down interfaces.
6
Go with Production Data

7. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9 7
It All Starts with De-identification
• You can’t use real production data
• Remove protected health information (PHI)
• Use de-identification
– Keep the clinical workflow in the messages
– Remove the patient identifiers
– Replace them with fake values
– Use off-the-wall fake values for edge cases
– Makes sure those scenarios match your workflows
• Employer information can contain PHI
– Remove employer name or insert replacement names
– Easy to re-identify data through information source
For more on de-identification, check out these blog posts.

8. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9
Here’s what to keep in mind when you de-identify your production data:
• Satisfy HIPAA. Remove the 18 identifiers designated by HIPAA as protected
health information (PHI).
• Maintain message flow. If “John Doe” in your production data becomes “Michael
Smith” in your test log, ensure that Michael Smith in your A01 admission
message is the same Michael Smith upon discharge.
• De-identify data in z-segments. PHI can hide in z-segments.
• Log volume. Aim for at least a week’s worth of messages and ideally a few
months’ worth.
• Traceability. Record which data was de-identified and which fields and data
types were transformed.
8
De-identification of Production Data

9. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9
• Without the right message samples and test messages, you
can run into issues with the lack of updated vocabulary and
potential for downtime if messages contain unexpected
values.
• Confirm that you are not introducing errors.
Caristix Cloak software removes protected patient information in HL7
messages. Cloak produces auditable reports of de-identification. Generate
clinically valid data for interface development, testing and analytics.
9
Avoid Problems with Updated Vocabulary

10. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9
If your new to interfacing, you might think about just hitting Google
for some sample messages. If you do, some basic structure like
pipes and carets might be right. But:
• You won’t have information about the interface you are trying to
build:
– The message types it uses
– The segments and fields
– Positions
– Optionality
• Developers need the information in messages in order to build a
solid set of requirements for the actual interface.
• To develop a viable interface, work with realistic messages.
• In addition, whatever you find on the internet will be practically
used due to security measures.
10
Don’t Fall into the Beginner’s Trap

11. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9
• Chapter 10 in the HL7 Survival Guide
• Process and Workflow
– Map out your processes and workflows to understand
how your interface can support them. Learn more in
Chapter 10.
– Blog link: http://caristix.com/blog/2012/11/hl7-survival-
guide-chapter-10/
– Slide deck on Slideshare: coming soon.
11
UP NEXT: CHAPTER 10

12. WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 9
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
12
QUESTIONS? FEEDBACK?
© Caristix 2013. All rights reserved.