Not every application you want to interface to will use the same transport protocol. Some use TCP, while others may use MLLP, SMTP, FTP, or even a different version of the protocol you have standardized on.

When partners that you have built application interfaces to update or change their transport protocol, your team will need to update the interface on your end.

Where this becomes an issue is managing all the various application interfaces that you connect to. In order to simplify the management of each of the possible application transport protocols that are used, CloudPrime does the conversion for you, allowing you to implement the protocol that your applications speak.

Take for example a trading partner that uses MLLP to stream HL7 messages to the connector interface for transport. The partner configures the interface, sets the correct port and IP address, and the stream connects. On the other side, you can use the configuration of your choice to receive the messages, e.g. simple file transfer or TCP. When the message arrives, CloudPrime will do the conversion, and deliver the messages to your application in the transport protocol specified.

Since CloudPrime is handling the conversion, trading partners will not be effected if one partner moves or upgrades to a newer standard. [See Figure 1] 

 

Figure 1 – Application interfaces using native transport protocols on the CloudPrime network.

CloudPrime currently supports over a dozen transport and message protocols, including TCP, MLLP, EDI, FTP, SFT, and more…

To learn more, contact us at