HL7 Specifications Defined
October 31st, 2006 by Sonal Patel
(9 votes, average: 4.78 out of 5)
Loading ...Posted in HL7 Messaging, HL7 Standard, HL7 Integration
When embarking into an HL7 integration project, specifications can be a great resource of information. HL7 specifications for an interface project to exchange clinical data is no different.
An interface implies two sides, each side being a clinical application that should be able to provide HL7 specifications for the project.
The specifications will detail important information regarding the interface including the following:
- Communication protocol
- HL7 standard version
- HL7 message(s) to be sent or received
- Message format or segment layout for each message
- Field list for all segments including Z segments
- Other details (e.g., use requirements, field content, optionality, etc.)
If you are able to obtain good specifications detailing all the needed information, you should be ready to begin the gap analysis phase.
However, specifications or useful specifications may not be provided. In these cases, you can try to request sample messages from the application. With the right tools, you can probably determine the HL7 messaging format to be used.
With or without specifications, asking for sample messages is always a good idea. Often times, don’t be surprised to find that the sample messages do not match the specifications. You can simply add these items to the gap analysis.
Good luck in your HL7 integration project!
Last 5 posts by Sonal Patel
- The Benefits of Improving Your Healthcare Billing Operations - January 8th, 2008
- HL7 Messages in Healthcare Billing Environments - January 4th, 2008
- Radiology Workflow - Integrated - December 20th, 2007
- Placer Order Number vs. Filler Order Number - September 28th, 2007
- HL7 Separator Characters - September 24th, 2007
[…] The HL7 2.X standard varies greatly in how it is implemented by each medical device or application vendor, causing nonconformance between message formats. Determining and understanding nonconformance between provider or vendor message formats involves reviewing the their message specifications and sample messages. […]
[…] These problems can be avoided upfront if the implementation team has a solid understanding of how ACKs will work between the systems. It is important to review the HL7 specifications of any application that you will be interfacing with to gain a thorough understanding of how their system sends and receives HL7 acknowledgment messages. […]
[…] A phone call or face-to-face meeting where HL7 specifications are reviewed or exchanged. During this HL7 conference, there is a “meeting of the minds” with respect to the data elements and work flows that will be supported by the HL7 interface. […]
[…] HL7 Specifications - Each vendor should be able to supply an inbound and outbound HL7 specification for their application. The quality of these documents will vary greatly from vendor to vendor. These documents will allow you to do a gap analysis (see below) between the two systems. […]
[…] HL7 messaging, the exact field contents can be negotiated based on interface specifications between the sending and receiving […]
[…] Drafting and/or evaluating HL7 specifications […]