Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • B2B Data Exchange 10.2.2
  • All Products

Table of Contents

Search

  1. Preface
  2. Informatica Managed File Transfer Welcome Overview
  3. Dashboard
  4. Resources
  5. Workflows
  6. Task Reference
  7. Services Overview
  8. Users
  9. Logs and Reports
  10. Encryption
  11. System
  12. Appendix
  13. Glossary Terms

User Guide

User Guide

Back Next

HL7 Message Handling

HL7 Message Handling

When an MLLP client sends a message to the Informatica Managed File Transfer MLLP service, it is required to wait for an HL7 Acknowledgement before sending the next message. The content of the acknowledgement must be examined to determine the specific type of the acknowledgement before the next message can be transmitted.
HL7 Messages are used to transfer electronic data between disparate healthcare systems. Each HL7 message sends information about a particular event such as a patient admission. There are two types of Acknowledgement messages (ACKs) used in healthcare data exchange communications: HL7 ACKs include original mode acknowledgements and enhanced mode acknowledgements, and non-HL7 ACKs, also known as static string acknowledgements.
An HL7 ACK is created with information from the HL7 message, and is in the following HL7 formats.
  • Original Mode Acknowledgement: This acknowledgement is a "Receive" ACK. It indicates that a message has been received but not necessarily processed yet.
  • Enhanced Mode Acknowledgement: This acknowledgement is an "Application" ACK that is a resultant status return rather than a communication response, such as an order response.
Original Mode Acknowledgements include the following HL7 acknowledgements:
  • Application Accept (AA) acknowledgement. The message was accepted without error.
  • Application Error (AE) acknowledgement. The message had an error and was rejected.
  • Application Reject (AR) acknowledgement. The message was rejected because of an error.
Enhanced Mode Acknowledgement include the following HL7 acknowledgements:
  • Application Accept (AA) acknowledgement. The message was accepted without error.
  • Application Error (AE) acknowledgement. The message had an error and was rejected.
  • Application Reject (AR) acknowledgement. The message was rejected because of an error.
  • Commit Accept (CA) acknowledgement. The message was accepted by the backend system.
  • Commit Error (CE) acknowledgement. The message had an error and was rejected by the backend system.
  • Commit Reject (CR) acknowledgement. The message was rejected in the backend system because of an error.
The MLLP service will send an acknowledgement once it receives the message from client. If the message was accepted without error, it will send AA acknowledgement to the client and save the message in the
userdata/MLLP/ListenerName
 folder. The saved message name will be in the format
msg_(Client)IP_(Client)Port_Timestamp
 . It will create the service event "
MLLP Message received successfully
 ".
If the message had validation error and was rejected, it will send an AE acknowledgement to the client and save the message in the
userdata/MLLP/<ListenerName>
folder. The saved message name will be in the format
err_msg_(Client)IP_(Client)Port_Timestamp
 . It will create an "
MLLP Message received failed
 " service event.
If the message was rejected because of an error such not having write permission to the
userdata/MLLP/ListenerName
 directory, it will send AR acknowledgement to the client. It will create an "
MLLP Message received failed
 " service event.
0 COMMENTS
We’d like to hear from you!