How to Establish a Health Information Exchange with CloudPrime

Bookmark this on Hatena Bookmark
Hatena Bookmark - How to Establish a Health Information Exchange with CloudPrime
Bookmark this on Yahoo Bookmark
Bookmark this on Livedoor Clip
Share on FriendFeed
How to Establish a Health Information Exchange with CloudPrimeCloudPrime Blog

In this article I wanted to review how one could create a Health Information Exchange using CloudPrime. What this means in the most simple terms is that the CloudPrime application messaging network enables you to connect health care application endpoints to a central hub for the purpose of creating an electronic data interchange. This information exchange can send data back to all the constituents as well as connect out to another network outside the system.

Exhibit A below represents the network topography of CloudPrime when implemented in a hub-and-spoke configuration. As you can see, there is a centralized EHR that connects out to various hospitals, physician groups, clinical labs, and pharmacies. Each one of these endpoints communicates in a two-way message exchange back to the central EHR (or HIE, Head Quarters, etc.), encrypting all traffic over the network.

Exhibit A

BlogDiagram resized 600

 

This is achieved by installing what is called a “CP Connector” at each end-point that interfaces to the application that will be sending data. These Connectors are capable of picking up HL7, EDI X12, and Flat Files (to see a full list of Protocols Supported, please visit https://cloudprime.net) and passing them along to the destination connectors via the Cloud. What is important to note is how the messages travel over the network.

  1. The messages are picked up and encrypted behind the endpoint’s firewall, ensuring all messages are sent securely,
  2. Messages are sent over multiple paths to guarantee the arrival of each message, something we call Multi-Pathing,
  3. Store and forward: A copy of each message is stored in the online data stores (in the Cloud) and persist until the message is delivered. Online storage is rules based, so CIOs and IT Managers can keep messages encrypted in the Cloud for as long as they want,
  4. The first message that arrives at the destination will be decrypted and delivered to the appropriate file system directory or application interface. The connector automatically de-duplicates each message and destroys any message that arrives after the first.
  5. All message transactions can be viewed in the CloudPrime portal for reporting and non-repudiation.

Deploy A Health Information Exchange Quickly

It can take as little as a month to deploy a CloudPrime Health Information Exchange, and once your network is established, adding new endpoints can be done in a matter of minutes.*

Below is a diagram of the simple steps required for downloading and installing a Connector at a new application endpoint.

Elapsed Time of Connector Installation

elapsedTimeInstallation

Once a Connector is installed, the user simply creates a connection (called Channels) interfacing to the source application and specifies the destination address on the CloudPrime network. Once this is done, the user can start sending messages back and forth to their trading partners on the network.

CloudPrime Channel Configuration Screen

CloudPrimeAdminPortal

CloudPrime makes it easy to create a secure, scalable and cost-effective health information exchange, connecting all the necessary dots on your network to achieve interoperability and compliance. To learn more about how you can begin using CloudPrime today to establish a Health Information Exchange on your network, contact us by emailing sales @ cloudprime dot net or calling .

* This is based on previous customer implementations. Experiences may vary depending on the requirements.

Leave a Reply