Message Transport - Receiving HL7 Messages

You have determined that in your HL7 interface you will be needing to consume HL7 messages and now it's time to plan for which transport mechanisms you are going to support which will allow your trading partner(s) to get those messages to you. Remember that, for now, you don't need to think about HOW your interface will actually consume the HL7 messagesInbound 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 entry point going to be? That is to say, where is the "front door" to your HL7 interface? The governing body of HL7 gives you a pretty straightforward clue about what this should be. In our earlier article about HL7 Message Transport we told you that in order for your interface(s) to be officially considered "HL7 Compliant" you must be able to accept a HL7 data file drop which we strongly recommend as well. By using a data file drop as your interface entry point which really means just that your interface can import HL7 data files from a folder on the file-system, you can easily implement every other possible type of HL7 Message Transport. Your HL7 interface doesn't know (or care) HOW the HL7 data files get into the folder, it just reacts to their presence and consumes them.

 Relevant HermeTech Products for Receiving HL7 Messages

  

BlueLeftArrow32 Back To: Message Transport Next Article: Sending HL7 Messages BlueRightArrow32