Redox

Redox FHIR® API

Every connection in FHIR®

A FHIR®-conformant API designed to allow us to support 100% of our customer’s integration needs with a modern development experience, even if the systems on the other end aren’t so modern.

  • Simplified, strictly defined FHIR R4 API
  • Standardization of HL7v2, CDA documents, custom EHR APIs, and EHR FHIR profiles with one API
  • Adherence to ONC requirements
  • Sandbox environment with clinical and operational test data

THE FHIR STANDARD

With the release of the final rule for the Cures Act, the healthcare industry is looking forward to FHIR® as the future of integration.

However, the deadline for EHRs to make FHIR® APIs available isn’t until December 2022. While some vendors are ahead of the curve, we’re at the very beginning of a long transition process.

THE PATH TO FHIR
WHAT TO EXPECT

For the next several years, most providers are going to be stuck in a complex world of support for different standards without a clear incentive to move from legacy standards to FHIR®.

Healthcare developers should expect:

  • Variances in implemented FHIR® versions
  • Incomplete support of full integration workflows
  • Limited support for FHIR®-based event notifications
  • Minimal support for write-back via FHIR®

THE GRAY PERIOD OF TRANSITION

Across the more than the 1000 integrations Redox supports, only 8% would be able to power their integration using only the mandated APIs. An additional 58% of our integrations would be partially supported.

FHIR® is a registered trademark of Health Level Seven International (HL7) and are used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.