Blog

Rhapsody Health Solutions Team

Blogs

How Interoperability Can Unlock the Potential of Telehealth

Telehealth workflows require data exchange across several institutions’ systems to exchange patient scheduling messages and patient summary documents.

Blogs

DaVinci Aims to Boost Payer-Provider Interoperability

There are a number of Use Cases (and Implementation Guides) that are part of the overall Da Vinci project. Initially 12 were identified — of which two were chosen to start with, and three more are in the active phases of development...

Blogs

Continuous 24/7 Support During Crises

With attention on the COVID-19 (Coronavirus) pandemic, we continue to closely monitor the dynamic developments to ensure the ongoing health and safety of our employees and customers.

Blogs

Converting Data Feeds to FHIR

Mapping language offers a vendor-agnostic approach to the tricky issue of conversion between FHIR and other message standards.

Blogs

Corepoint 7.3 is now available

First Product Update Under New Brand Demonstrates Continued Focus on Enhancing Product lines and Listening to Customers; New Features Include FHIR V4 R4 Support, Automated Debugging Functionality, and User Experience Enhancements

Blogs

Survey Addresses the State of Patient Matching in the U.S.

The findings are based on a national survey of healthcare provider and HIE leaders in 2020 to capture a candid and comprehensive picture of the current patient matching landscape.

using_rhapsody_as_FHIR_facade_part_1_image2

Blogs

Using Rhapsody as a FHIR® Façade (Part One)

There are many issues to address when doing when working with clinical data, including technical and security concerns. We cover a RESTful FHIR® interface.

Blogs

Rhapsody Releases First Update to Flagship Interoperability Platform

Rhapsody 6.5 Signifies New Company’s Commitment to Customers and Partners with Enhanced Features for Collaboration, Shared Workflows, User Experience, APIs and DICOM Update

Blogs

What is Corepoint Health Doing to Support FHIR?

What is Corepoint doing to support FHIR? And how critical is it that engine vendors, such as Corepoint, support the creation of the specification?