Web Services for Corepoint Integration Engine

Create health data interoperability using modern communication standards

The Web Services feature in Corepoint Integration Engine is important for health organizations looking to meet the Meaningful Use requirement of successfully exchanging patient data with an unaffiliated external organization. The Corepoint Health Web Services feature allows users to participate in or create the most common health information exchange scenarios, such as enterprise HIEs, including those utilized in Accountable Care Organizations.

Web Services is the ideal communication standard for HIE creation and participation because organizations can exchange large amounts of data over the Internet and intuitively integrate received data into their application environment, all without the need for scripting. Because Web Services allows data transmission regardless of the vendor or workflow, it is the ideal communication method for connecting remote providers and applications across an HIE network.

Corepoint Integration Engine uses XML messages that follow the RESTful or SOAP standard for secure communications, the most common Web Services standards used in healthcare.

Secured Web Services updates data in real time based on trigger events, or action points in Corepoint Integration Engine. Once a patient's data is updated by a provider and the trigger is set, that patient record is published to one or more HIE.

 

Web Services Call

A Web Service Call feature is available as an Action List operator in Corepoint Integration Engine, giving users the ability to call any REST- or SOAP-based Web Service to request data. Because this feature is available in an Action List, the call is made to the external organization simultaneously, without the need for other software or a CareAgent. The only requirement is that the receiving application have Web Services listening capabilities.

Web Services Call in Corepoint Integration Engine

 

Web Services Send

Sender functionality allows users to also deliver web service messages from a connection queue. More complex than a simple Web Service Call in that it separates HL7 mapping from the data transport, this function handles multiple connections with built-in error handling capabilities. Like Web Services Call, users benefit from robust logging capabilities native to Corepoint Integration Engine.

Web Services Send in Corepoint Integration Engine

 

Web Services Listener

Listener functionality allows organizations to create the data architecture needed to establish an enterprise HIE by monitoring and receiving messages from calling applications. Using the same powerful integration features available for internal applications, Web Services Listener seamlessly processes incoming messages in Action Lists and routes them to other destinations or calling organizations.

Web Services Listener in Corepoint Integration Engine

 

Data mapping

One common use for Web Services is to look up codes and/or patient names. Corepoint Integration Engine acts as a Web Client to query the eMPI for the correct patient identifier.

In this example, an order is received from the referring physician community. Once that order arrives at the hospital facility, the integration engine can extract demographic information about the patient and encode it into the XML body of a REST- or SOAP-based message being sent to the eMPI. The integration engine acts as a Web Client, or a Web Service Consumer.

The way in which the data is encoded and what specific demographics must be included are defined in the WSDL provided by the eMPI vendor. The eMPIs acts as a Web Service Producer, and returns the appropriate local patient identifier. The integration engine can then map the local patient identifier into the order message before it is forwarded on to the local lab (LIS).

Hospital Corepoint Integration Engine Graphic

 

Transporting documents

Another common use of Web Services is for the transport of CCD documents to a local HIE.

For example, it might be required to upload a CCD to the HIE every time a patient is discharged so other providers in the area can have access to the data to continue care.

To illustrate: a hospital EHR sends the document to Corepoint Integration Engine using traditional TCP/IP. The integration engine utilizes Web Services to transport the document outside of the facility without performing any mapping in the document— it simply acts as a Web Services Consumer that routes the document to the HIE.

More complex scenarios might require routing to multiple downstream entities. In that scenario, the integration engine could parse the CCD document to determine the intended recipients from the header, and then route the document to all required entities via Web Services.

 

Hosting a Web Service

Corepoint Integration Engine can act as a Web Services producer when CCD documents are stored in a hospital’s repository, rather than with an HIE. In this case, the HIE must query the hospital when it has a request from another HIE member for patient health information regarding a specific patient.

Corepoint Integration Engine acts as a Web Services producer and listens for HIE Web Clients to request documents for a given patient. The integration engine would then retrieve the document from the local HIS and forward it to the HIE that made the initial query.

Similar to the way an integration engine manages and simplifies connections among applications within the facility, an integration engine is extremely useful in managing and simplifying connections to outside partners.

 

Conclusion

Web Services is changing the way healthcare organizations share data. As patient healthcare data is shared between facilities, privacy and security are of upmost importance.

Web Service lends itself well to this type of sharing as a secure method of transport that is flexible enough, with its XML structure, to incorporate profiles aimed at consent, authentication, auditing, and all the other attributes important to healthcare IT.

Download PDF

 Print Friendly