Message Transport - Sending HL7 Messages

You have determined that in your HL7 interface you will be needing to create HL7 messages and now it's time to plan for which transport mechanisms you are going to support which will allow you to deliver those messages to your trading partner(s). Remember that, for now, you don't need to think about HOW your interface will actually create the HL7 messagesOutbound Whiteboard, that's for later when you are considering HL7 Message Processing. The only thing that you have to know in order to work out your various modes of HL7 transport is: 

FileDropWhere is your outbound interface ENDPOINT going to be? As with Receiving HL7 Messages, the governing body of HL7 gives you a clue about what this endpoint should be. Remember that in order for your interface(s) to be officially considered "HL7 Compliant" your interface must be able to deliver a HL7 data file drop to your trading partner(s), which really just means that you can write HL7 data files into a folder on the file system and make that folder available (if possible and practicable) to your trading partner(s). Now, obviously, if the trading partner which needs to receive the HL7 messages is on a remote server you might not want to let them join your WAN and make a folder available to them. However, by using a data file drop as your interface endpoint you can easily all of the other Message Transport mechanisms. 

 Relevant HermeTech Products for Sending HL7 Messages



BlueLeftArrow32 Back To: Receiving HL7 Next Article: Message Processing BlueRightArrow32