Blog

Rhapsody Health Solutions Team

Blogs

Azure API for FHIR Expands Possibilities for FHIR Workflows

With the release of Azure API for FHIR, Corepoint Integration Engine has more opportunity to help users solve complex integration problems.

Blogs

Ticket Validation through Corepoint Integration Engine

When an issue arises in the world of healthcare IT that affects the exchange of clinical data, it is crucial to act fast. If not, it could result in a domino effect throughout a healthcare organizatio

DocuTAP workflow with Corepoint Integration Engine

Blogs

Enhancing IT Support at Children’s of Alabama

The world of healthcare IT rarely sleeps. Critical data is exchanged around the clock so patients can receive the timely, urgent care they need. And if something halts or delays this process, an organ

Blogs

10 Years as the #1 Ranked Integration Engine in KLAS®

For the tenth consecutive year, Corepoint Integration Engine is named the top integration engine by KLAS Research, earning a score of 96.6

Blogs

HL7 FHIR Release 4

Blogs

Migrating From On-Premises to the Cloud in Four Steps

Migrating from any on-premise integration engine or interoperability platform to a cloud-based platform is now easier than ever. In fact, the migration process can be summarized in four easy steps.

Blogs

Security and the Cloud? A Decade Old Question and Answer

Today, as more and more organizations move their day-to-day infrastructure to the cloud, people are becoming more comfortable with the technology and the question has morphed into: “How secure is it, and what is in place to ease my concerns around security?”

Blogs

Security and Privacy – Rhapsody as a Service

How Rhapsody's Security and Privacy aspects factored into the University of Louisville Hospital's decision

White papers

Migrating from a Legacy Integration Engine

To leverage cloud and mobile technologies, healthcare organisations should consider replacing their older integration platforms. By doing this, they can avoid relying on developers with knowledge of specialised algorithmic programming languages (e.g., Monk) and eliminate the need to support platforms that have been discontinued, are no longer supported, or don’t support contemporary integration requirements.