Rhapsody Health Solutions Team

Using Web Services in Corepoint Integration Engine

January 16, 2012


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.

Meaningful Use Stage 2 states that qualifying organizations must exchange summary of care records electronically. Web Services is a highly interoperable communication method that allows for real-time health data communication.

Web Services is a method of communication between electronic devices that can be securely exposed over the Internet. The Web Services feature makes it easier to communicate health data between disparate organizations, regardless of the operating system or software in use.

Through Corepoint Integration Engine Web Services, 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.

The Corepoint Health Web Services feature empowers users to participate in or create the most common health information exchange scenarios, such as private HIEs, including those utilized in Accountable Care Organizations (ACOs).

Key Features and Advantages

  • Secure, RESTful, and SOAP-based Web Services feature gives users the ability to act as either a Web Service Consumer or a Web Service Provider, all within Corepoint Integration Engine.
  • Corepoint Web Service Consumer feature includes “call” and “send” abilities with logging and error handling capabilities. Deploy data to multiple endpoints utilizing current engine and server configuration.
  • Web Service feature allows users to establish the destination hub, free of scripting, that receives inbound requests from external calling applications equipped with Web Services capabilities. A Web Service using Corepoint Integration Engine creates an intuitive health data information exchange architecture powered by the most trusted integration engine in healthcare.
  • Supports secure messaging, reliable messaging, secure transport, client certificates, SOAP 1.1, SOAP 1.2, and WS* standards

Powering health information exchange

Web Services Description Language (WSDL) is an XML-based language that provides the framework to send messages electronically over the Internet.

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

Because Web Services allows data transmission regardless of the vendor or workflow, it has been proven to be the ideal communication method for connecting remote providers and applications across an HIE network.

Secured Web Services is extremely interoperable because the data is updated in real-time based on trigger events, or action points in Corepoint Integration Engine.

Once a patient’s health data is updated by a provider and the trigger is set, that patient record is published to one or more HIEs using industry-standard methods, such as IHE profiles.

The exchanged CCD is wrapped with metadata that is stored in the HIE document registry, and the document itself typically is stored in the HIE document repository.

Using Web Services in Corepoint

Web client: call and sender

Web Service Call  A Web Service Call feature is available as an Action List operator in Corepoint Integration Engine, giving users the ability to call any RESTful- 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 synchronously, and the response can be processed within the Action List logic. The only requirement is that the receiving application has Web Services listening capabilities.

The following diagram illustrates how the Web Service Call feature operates in the Corepoint Integration Engine:


Web Services Sender  Sender functionality allows users to also deliver web service messages from a connection queue.

This feature is more complex than a simple Web Service Call in that it separates HL7 mapping from the data transport, handles multiple connections, and has built-in error handling capabilities.

And, like Web Services Call, users benefit from the robust logging capabilities native to Corepoint Integration Engine.

The following diagram illustrates how the Web Service Send feature operates in Corepoint Integration Engine:


Web Services: listener

The Web Service Listener feature in the Corepoint engine helps healthcare organizations create the data architecture needed to establish a health information exchange. This feature in the engine gives organizations the ability to monitor and receive messages from calling applications.

Using the same powerful integration features available for internal applications, the Web Services Listener feature seamlessly processes incoming messages in Action Lists and routes them to other destinations or calling organizations.

The following diagram illustrates how Corepoint Integration Engine provides the architecture necessary for successfully establishing an HIE:


To learn more about Corepoint Integration Engine and what it can do for you, click here!

Related Blogs

Shelley Wehmeyer

Manage versions and workflows with improved visibility and usability in Rhapsody Semantic 15.3

Learn about the latest enhancements of Rhapsody Semantic including namespace versioning and FHIR code system version support.

Read more

Rhapsody Health Solutions Team

Glossary: Healthcare Interoperability Terms and Definitions

Find definitions of commonly used healthcare interoperability terms in this glossary.

Read more

Jesse Eichhorn

Introducing EMPI innovations to better support health equity, workflow efficiency, and patient empowerment

Learn more about how Rhapsody EMPI 11.3 introduces new capabilities that support health equity, efficiency, and empowerment.

Read more