Hey, Matt here. I’m going to save you some time, here are the links to the press release and the Redox AppExchange Listing. We’re really excited to launch a comprehensive set of packages aimed at helping provide Redox EHR integration across the Salesforce and Mulesoft ecosystem. Both of these partners are the world leaders in their respective categories, and we couldn’t be happier to be working with them to deliver these incredible solutions.
What this is means for healthcare providers.
Salesforce Health Cloud is one of the fastest-growing platforms in the provider toolkit. We are seeing tons of organizations leverage Salesforce for case management, population health initiatives, appointment follow-up and reminders, and more. All of these workflows are best when that Salesforce instance is communicating with your EHR. Historically, there wasn’t a really great way to do this, and most built custom integrations (at a high cost). We worked really closely with the Health Cloud product team to understand the most needed integration use cases and developed an out-of-the-box integration solution that requires no additional development, backed by Redox’s world-class implementation and support. From a provider perspective, this makes it faster and easier to turn on an integrated version of Health Cloud than ever before. Oh, and if you’ve already got Redox powering integration at your organization, this leverages much of your existing infrastructure.
What this means for enterprise organizations.
In parallel to our Salesforce discussions, we engaged with Mulesoft to deliver a fully managed EHR integration solution for their Anypoint Platform. The Anypoint Platform is a beast. It’s a true engine that can power thousands of downstream workflows by unifying and relating multiple APIs into singular workflows. The problem is that healthcare is stuck in 1998 and APIs are still a relatively new thing. Insert Redox. We’re consolidating any and all legacy interfaces (HL7, CDA, X12) as well as the FHIR and vendor-specific EHR APIs into a single API that can then be used across the Mulesoft platform. This replaces the need to manually manage an HL7/FHIR listener on each interface at each connection point. This integration package also includes full bi-directional capabilities. And yes – you can send data from Redox to Mulesoft and then to Salesforce and back in the opposite direction. We’re tentatively calling that the trifecta.
What does this mean for Redox?
As my colleague Devin said in our previous AWS partnership announcement, our driving motivation is to make healthcare data useful. We are not naive enough to think it’s something that we can do alone. Salesforce represents one of the most powerful developer communities on Earth. We are proud to help power their expansion into healthcare and enable world-class developers, systems integrators, architects, and admins to design solutions that make healthcare better.
We need health systems and providers to look at best-of-breed digital health and see efficiency, not friction. This partnership is all about maximizing the usability of data. When you have great data coursing through two great platforms, solutions are endless and simple to design and implement. And, as always, when you build with our reusable infrastructure, you make future projects even easier.
Questions? Thoughts on what to build next? Drop me a note any time: firstname.lastname@example.org.