September 2021 12
Understanding HL7 Segment Grammar Notation
By convention, a standard segment grammar notation is defined to provide a convenient way to indicate the segments that can be included in a particular type of HL7 message.
Many vendors use this segment grammar notation to specify what segments may be included with each type of HL7 message that they send.
Webinar Series | Part 2: Interface Development: Solutions & Workflows
We're extremely proud to have hosted part one of our four-part Iguana 'Did You Know?' webinar series. In yesterday's webinar, we explored some of Iguana's hidden tools and features that play a crucial role in optimizing the development, administration, and workflow design processes.
Understanding HL7 Delimiter Redefinitions
The HL7 Delimiter Characters shown in the table below lists the default delimiter characters that are normally used in HL7 messages.
An HL7 message can choose to employ HL7 delimiter redefinitions.
If the standard characters are not convenient to use, the HL7 message can use different delimiter characters.
How to replace an interface engine
“The only thing constant in life is change.” – Francoise de la Rochefoucauld 1613 – 1680 Traditionally, upgrading or replacing an interface engine employs the “Test, Switch, Pray” methodology. This means running the new interface engine through a battery of tests to attempt to cover all of the possible use and test cases it may […]
Understanding HL7 Messages: HL7 Composites
Each segment of an HL7 message consists of one or more composites (also known as fields). By default, the | (pipe) character is used to separate one composite from another.
A composite can be a primitive data type (such as a character string or a number), or can contain other composites.
If a composite contains other composites, these sub-composites (or sub-fields) are normally separated by ^ characters.
HL7 Standard: The ACKnowledgment Protocol
An important part of the HL7 standard is the ACKnowledgment protocol.
Every time an application accepts a message and consumes the message data, it is expected to send an ACKnowledgment message back to the sending application.
The sending application is expected to keep on sending a message until it has received an ACK message.
If you do not follow this rule, data may be lost in transmission.
Is High Availability For Your Integration Platform Worth It?
Learn why implementing a High Availability solution is essential to your healthcare integration projects.
Disaster Recovery vs. High Availability vs. Fault Tolerance: What are the Differences?
While these terms are related to one another, it is worthwhile to know the differences between them and understand the role that they play in keeping your systems online.
Why HL7 Message Throughput Is a Critical Metric for Interface Engines [White Paper]
The Iguana HL7 interface engine demonstrates high throughput far exceeding the most demanding integration applications.
Iguana® provides you with the necessary tools to develop, test, deploy and monitor your interfaces to integrate your EMR, EHR, HIS, PACS or any other healthcare information systems.
Why You Need A Modern Integration Engine Now More than Ever Before
An integration engine (and seriously, let’s stop calling it an interface engine. it does so much more) is an essential piece of healthcare’s technology infrastructure.
Today, during this unprecedented global pandemic we need a highly reliable solution to integrate our data seamlessly.
Enjoying this blog?
Sign up to receive healthcare integration news, just like this, from iNTERFACEWARE Inc.
iNTERFACEWARE needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Privacy Policy.