SlideShare a Scribd company logo
HL7 SURVIVAL
GUIDE
CHAPTER 6
A publication of
A supplement to the HL7 Survival Guide, available at
http://caristix.com/blog/category/hl7-survival-guide/
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
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/
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
CHAPTER 6: Interfacing Artifacts: HL7 Conformance Profiles or
Interface Specifications
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
The first 5 chapters have helped you thing strategically about
your interfacing project.
4
Dive into the nitty-gritty of what you need in
an interface specification and/or HL7 profile.
An interface specification should list:
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
1. Interface name
How do you refer to your interface in your integration environment? Devise a
naming system for easy name recognition and tracking.
2. Source or destination system name and version
System versions (and even product names) change over time. Make sure
you’ve got a way to track this in your spec.
3. Message types used in the interface
A message type is essentially a trigger event, such as patient admission, lab
request, lab results available, new appointment, etc. Focus on the ones you
need for your interface.
4. Message definitions including segments, fields, data types
You need a list of the segments, fields, and data types used in each message
type.
5. Segment and field attributes
These are optionality, repeatability, data type associated with a field, field
length, tables associated with field.
5
Interface Specification
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
6. Z-segments
Custom segments, if a vendor or your facility uses them.
7. Data types
Apart from a list of data types, you will also need attributes and
customizations.
8. HL7 tables
You need the real-world data or code sets that are actually implemented –
such as gender, race, and lab codes – not what the standard provides.
Keep track of the actual data and code sets used, along with where and
how they’re used, and the meaning of the information.
9. Specialized interoperability challenges
Without getting all necessary information upfront (i.e., what we outline in
this chapter), your challenges around interoperability become greater and
more insurmountable. In particular, read more addressing the challenges of
lab interoperability in this Clinical Innovation and Technology article: Lab
Interoperability Plays Catch Up.
6
Interface specification (cont)
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6 7
Spec = Interface Requirements
Combine the elements above with any necessary clinical or
workflow constraints. This becomes your specification or
profile.
• Make sure internal customers and vendors see this.
• Ask tough questions (including the ones we supplied in
chapters 4 and 5) as you review this spec.
• Pin down the right answers for your environment.
Leverage your interface specifications (and other interfacing
artifacts) to generate your interface code. In most cases, the
spec is delivered as a Word document so look for tools that will
help you connect the spec directly to your interface engine.
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
Regardless of how you develop a profile, you need to do it. We’ve
developed this HL7 profile template kit and made it available to you for
download.
• To build a profile, you have several options:
– Messaging Workbench available via HL7 International (look for a file name that
includes “MWB release”) is open-source software designed to build conformance
profiles. But keep in mind, with Messaging Workbench you’ll need to build out
individual profiles for each message type. If you define 10 message types for an
interface, you’ll be building 10 separate profiles. You’ll also have to read through
messages to get the information you need.
– Develop templates in Excel or Word and then populate them manually.
– Use Caristix software that automatically creates profiles from HL7 messages. In
our world, a profile corresponds to the spec for a source or destination system,
with however many message types you need.
8
How to Develop an HL7 Conformance Profile
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
• Gets analysts, developers, internal customers, vendors, and
consultants on the same page
• Helps identify risks before interface development
• Eliminates time spent determining requirements, testing,
and on trial and error during go-live
• Makes it possible to easily generate your HL7 interface
specification, gap analysis report, and test and validation
plan
9
Why You Need a Conformance Profile
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
Without an interface spec customized to your requirements,
– You’ll be stuck implementing a generic interface. The last thing you
can afford is to dedicate those resources to testing. But that’s what
you’ll find yourself doing if you go with a generic spec.
– After all, your interface will likely be buggy when it goes live because
your true requirements weren’t gathered up-front.
– As a result, you’ll find yourself bogged down with extensive
troubleshooting after go-live, especially when you run into issues with
clinical workflows because the interface doesn’t work as expected
and clinicians report a lack of data, orders, lab results, and/or
medication as a result.
10
The Dangers of a Missing Interface Specification
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
• HL7 conformance profiles (also known as profiles or interface
specifications). HL7 profiles should at a minimum provide a list of
messages, segments (including z-segments), fields, data types,
and typical code sets or data.
• Gap analysis between systems to connect. Gap analysis sets
the scope of the interfacing project. Read more about gap
analysis in this Caristix white paper.
• Test scenarios. Vendors typically provide you with a boilerplate
validation guide to ensure the interface works as expected.
ensure that your organization’s clinical workflows are covered.
Make sure the guide covers real-life and specific scenarios you
encounter in your environment.
11
Demand These Deliverables
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
Don’t take any chances – create those profiles. Get started
with our HL7 Profile Kit.
12
HL7 Profile Kit
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
• Chapter 7 in the HL7 Survival Guide
• Interfacing Artifacts:Gap Analysis
– Once you have profiles for your source and destination
systems, you’ll need to capture a list of all the gaps
between the two systems. The next chapters walk you
through that process. Learn more in Chapter 7.
– Blog link: http://caristix.com/blog/2012/11/hl7-survival-
guide-chapter-7/
– Slide deck on Slideshare: coming soon.
13
UP NEXT: CHAPTER 7
WWW.CARISTIX.COM SHARE THE SLIDE
DECK
HL7 SURVIVAL GUIDE CHAPTER 6
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.

More Related Content

PPTX
Building bridges devdays 2017- powerpoint template
PPTX
Furore devdays 2017 - workflow
PPTX
Furore devdays2017 general-introtofhir
PPTX
Furore devdays2017 tdd-1-intro
PPTX
Furore devdays2017 tdd-2-advanced
PPTX
Advanced .net api (ewout)
PPTX
Whats new (grahame)
PPTX
Validation in net and java (ewout james)
Building bridges devdays 2017- powerpoint template
Furore devdays 2017 - workflow
Furore devdays2017 general-introtofhir
Furore devdays2017 tdd-1-intro
Furore devdays2017 tdd-2-advanced
Advanced .net api (ewout)
Whats new (grahame)
Validation in net and java (ewout james)

What's hot (8)

PDF
Integrating with the epic platform fhir dev days 17
PPTX
20171116 rene spronk_profiling_governance
PPTX
2017 11-ccda-on-fhir
PPTX
OData, External objects & Lightning Connect
PPTX
Design patterns fast track
PDF
Building on cerner with smart on fhir fhir dev days 2017
PPTX
Furore devdays 2017- continua implementing fhir
PPTX
Dev days 2017 referrals (brian postlethwaite)
Integrating with the epic platform fhir dev days 17
20171116 rene spronk_profiling_governance
2017 11-ccda-on-fhir
OData, External objects & Lightning Connect
Design patterns fast track
Building on cerner with smart on fhir fhir dev days 2017
Furore devdays 2017- continua implementing fhir
Dev days 2017 referrals (brian postlethwaite)
Ad

Viewers also liked (17)

PPTX
HL7 Survival Guide - Chapter 3 - The Heart of the Matter: Data Formats, Workf...
PPTX
: HL7 Survival Guide - Chapter 7 – Gap Analysis
PPTX
HL7 Survival Guide - Chapter 11 – Maintenance, Troubleshooting, and Monitoring
PPTX
HL7 Survival Guide - Chapter 4 – Your EHR Strategy and Working with Vendors
PPTX
Introduction to hl7 v3
PPTX
HIE technical infrastructure
PPTX
HL7 Health level 7
PPTX
CICS Transaction Gateway V9.1 Overview
DOCX
IBM Websphere concepts
PDF
IBM WebSphere application server
DOC
Websphere interview Questions
PPTX
Hl7 V3 Reference Models 20091123
DOCX
Ibm web sphere application server interview questions
PPTX
Websphere Application Server V8.5
PPTX
Payment systems
PPT
Trade And Settlement Process
PPTX
Payment and Settlement Systems(SWIFT,NEFT and Securities Cycle)
HL7 Survival Guide - Chapter 3 - The Heart of the Matter: Data Formats, Workf...
: HL7 Survival Guide - Chapter 7 – Gap Analysis
HL7 Survival Guide - Chapter 11 – Maintenance, Troubleshooting, and Monitoring
HL7 Survival Guide - Chapter 4 – Your EHR Strategy and Working with Vendors
Introduction to hl7 v3
HIE technical infrastructure
HL7 Health level 7
CICS Transaction Gateway V9.1 Overview
IBM Websphere concepts
IBM WebSphere application server
Websphere interview Questions
Hl7 V3 Reference Models 20091123
Ibm web sphere application server interview questions
Websphere Application Server V8.5
Payment systems
Trade And Settlement Process
Payment and Settlement Systems(SWIFT,NEFT and Securities Cycle)
Ad

Similar to HL7 Survival Guide - Chapter 6 – Interfacing Artifacts: HL7 Conformance Profiles and Interface Specifications (20)

PPTX
HL7 Survival Guide - Chapter 10 – Process and Workflow
PDF
Software Engineering - chp2- requirements specification
PDF
Rumos-MDD-Step Into Power Platform Presentation
DOCX
Tony Reid Resume
PDF
ArcSight Actor Model Import Connector for Microsoft Active Directory release ...
PPTX
Reasons Why Health Data is Poorly Integrated Today and What We Can Do About It
PPTX
HL7 Survival Guide - Chapter 12 – Definitions
PDF
Cascading concurrent yahoo lunch_nlearn
PDF
The IBM Data Engine for NoSQL on IBM Power Systems™
DOCX
1 SDEV 460 – Homework 4 Input Validation and Busine
PPT
Fuse overview
PDF
Dairy management system project report..pdf
PPTX
1 extreme performance - part i
PDF
Realtime Embedded Multithreading Using Threadx And Mips Edward L Lamie Auth
PPTX
Critical Preflight Checks for Your EPM Applications
PPT
Project seminar
PDF
Omni-Path Status, Upstreaming and Ongoing Work
DOC
Database project
PDF
Create Your Own Software | Build 100% Unique Product Packages
PDF
Guidelines data cite_denmark_ver2
HL7 Survival Guide - Chapter 10 – Process and Workflow
Software Engineering - chp2- requirements specification
Rumos-MDD-Step Into Power Platform Presentation
Tony Reid Resume
ArcSight Actor Model Import Connector for Microsoft Active Directory release ...
Reasons Why Health Data is Poorly Integrated Today and What We Can Do About It
HL7 Survival Guide - Chapter 12 – Definitions
Cascading concurrent yahoo lunch_nlearn
The IBM Data Engine for NoSQL on IBM Power Systems™
1 SDEV 460 – Homework 4 Input Validation and Busine
Fuse overview
Dairy management system project report..pdf
1 extreme performance - part i
Realtime Embedded Multithreading Using Threadx And Mips Edward L Lamie Auth
Critical Preflight Checks for Your EPM Applications
Project seminar
Omni-Path Status, Upstreaming and Ongoing Work
Database project
Create Your Own Software | Build 100% Unique Product Packages
Guidelines data cite_denmark_ver2

Recently uploaded (20)

PDF
Agricultural_Statistics_at_a_Glance_2022_0.pdf
PDF
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
PPTX
Understanding_Digital_Forensics_Presentation.pptx
PPTX
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
PDF
Approach and Philosophy of On baking technology
PDF
KodekX | Application Modernization Development
PDF
Modernizing your data center with Dell and AMD
PDF
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
PDF
NewMind AI Weekly Chronicles - August'25 Week I
PPTX
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
PDF
cuic standard and advanced reporting.pdf
PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
PDF
Network Security Unit 5.pdf for BCA BBA.
PDF
Building Integrated photovoltaic BIPV_UPV.pdf
PDF
Per capita expenditure prediction using model stacking based on satellite ima...
PDF
Encapsulation theory and applications.pdf
PPTX
Cloud computing and distributed systems.
PPTX
A Presentation on Artificial Intelligence
PPTX
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
PPT
Teaching material agriculture food technology
Agricultural_Statistics_at_a_Glance_2022_0.pdf
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
Understanding_Digital_Forensics_Presentation.pptx
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
Approach and Philosophy of On baking technology
KodekX | Application Modernization Development
Modernizing your data center with Dell and AMD
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
NewMind AI Weekly Chronicles - August'25 Week I
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
cuic standard and advanced reporting.pdf
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
Network Security Unit 5.pdf for BCA BBA.
Building Integrated photovoltaic BIPV_UPV.pdf
Per capita expenditure prediction using model stacking based on satellite ima...
Encapsulation theory and applications.pdf
Cloud computing and distributed systems.
A Presentation on Artificial Intelligence
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
Teaching material agriculture food technology

HL7 Survival Guide - Chapter 6 – Interfacing Artifacts: HL7 Conformance Profiles and Interface Specifications

  • 1. HL7 SURVIVAL GUIDE CHAPTER 6 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 6 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 6: Interfacing Artifacts: HL7 Conformance Profiles or Interface Specifications
  • 4. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 The first 5 chapters have helped you thing strategically about your interfacing project. 4 Dive into the nitty-gritty of what you need in an interface specification and/or HL7 profile. An interface specification should list:
  • 5. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 1. Interface name How do you refer to your interface in your integration environment? Devise a naming system for easy name recognition and tracking. 2. Source or destination system name and version System versions (and even product names) change over time. Make sure you’ve got a way to track this in your spec. 3. Message types used in the interface A message type is essentially a trigger event, such as patient admission, lab request, lab results available, new appointment, etc. Focus on the ones you need for your interface. 4. Message definitions including segments, fields, data types You need a list of the segments, fields, and data types used in each message type. 5. Segment and field attributes These are optionality, repeatability, data type associated with a field, field length, tables associated with field. 5 Interface Specification
  • 6. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 6. Z-segments Custom segments, if a vendor or your facility uses them. 7. Data types Apart from a list of data types, you will also need attributes and customizations. 8. HL7 tables You need the real-world data or code sets that are actually implemented – such as gender, race, and lab codes – not what the standard provides. Keep track of the actual data and code sets used, along with where and how they’re used, and the meaning of the information. 9. Specialized interoperability challenges Without getting all necessary information upfront (i.e., what we outline in this chapter), your challenges around interoperability become greater and more insurmountable. In particular, read more addressing the challenges of lab interoperability in this Clinical Innovation and Technology article: Lab Interoperability Plays Catch Up. 6 Interface specification (cont)
  • 7. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 7 Spec = Interface Requirements Combine the elements above with any necessary clinical or workflow constraints. This becomes your specification or profile. • Make sure internal customers and vendors see this. • Ask tough questions (including the ones we supplied in chapters 4 and 5) as you review this spec. • Pin down the right answers for your environment. Leverage your interface specifications (and other interfacing artifacts) to generate your interface code. In most cases, the spec is delivered as a Word document so look for tools that will help you connect the spec directly to your interface engine.
  • 8. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 Regardless of how you develop a profile, you need to do it. We’ve developed this HL7 profile template kit and made it available to you for download. • To build a profile, you have several options: – Messaging Workbench available via HL7 International (look for a file name that includes “MWB release”) is open-source software designed to build conformance profiles. But keep in mind, with Messaging Workbench you’ll need to build out individual profiles for each message type. If you define 10 message types for an interface, you’ll be building 10 separate profiles. You’ll also have to read through messages to get the information you need. – Develop templates in Excel or Word and then populate them manually. – Use Caristix software that automatically creates profiles from HL7 messages. In our world, a profile corresponds to the spec for a source or destination system, with however many message types you need. 8 How to Develop an HL7 Conformance Profile
  • 9. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 • Gets analysts, developers, internal customers, vendors, and consultants on the same page • Helps identify risks before interface development • Eliminates time spent determining requirements, testing, and on trial and error during go-live • Makes it possible to easily generate your HL7 interface specification, gap analysis report, and test and validation plan 9 Why You Need a Conformance Profile
  • 10. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 Without an interface spec customized to your requirements, – You’ll be stuck implementing a generic interface. The last thing you can afford is to dedicate those resources to testing. But that’s what you’ll find yourself doing if you go with a generic spec. – After all, your interface will likely be buggy when it goes live because your true requirements weren’t gathered up-front. – As a result, you’ll find yourself bogged down with extensive troubleshooting after go-live, especially when you run into issues with clinical workflows because the interface doesn’t work as expected and clinicians report a lack of data, orders, lab results, and/or medication as a result. 10 The Dangers of a Missing Interface Specification
  • 11. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 • HL7 conformance profiles (also known as profiles or interface specifications). HL7 profiles should at a minimum provide a list of messages, segments (including z-segments), fields, data types, and typical code sets or data. • Gap analysis between systems to connect. Gap analysis sets the scope of the interfacing project. Read more about gap analysis in this Caristix white paper. • Test scenarios. Vendors typically provide you with a boilerplate validation guide to ensure the interface works as expected. ensure that your organization’s clinical workflows are covered. Make sure the guide covers real-life and specific scenarios you encounter in your environment. 11 Demand These Deliverables
  • 12. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 Don’t take any chances – create those profiles. Get started with our HL7 Profile Kit. 12 HL7 Profile Kit
  • 13. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 • Chapter 7 in the HL7 Survival Guide • Interfacing Artifacts:Gap Analysis – Once you have profiles for your source and destination systems, you’ll need to capture a list of all the gaps between the two systems. The next chapters walk you through that process. Learn more in Chapter 7. – Blog link: http://caristix.com/blog/2012/11/hl7-survival- guide-chapter-7/ – Slide deck on Slideshare: coming soon. 13 UP NEXT: CHAPTER 7
  • 14. WWW.CARISTIX.COM SHARE THE SLIDE DECK HL7 SURVIVAL GUIDE CHAPTER 6 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.