With Redox, you can connect to over 100 different EHR systems and over 80 additional systems. This means you can seamlessly integrate with any system your connection might use.
Use Network Explorer to see which systems we’ve already built system adapters for. If you find the system you need to integrate with and your partner is ready to kick off, request a connection to start implementation work.
Can’t find the system your connection uses in the existing Redox network? Don’t worry, we’re always ready to tackle the next opportunity and add a new system adapter.
Our philosophy is simple: If a system can support a workflow through its APIs, Redox can enable that integration for you. We thrive on expanding our network and ensuring you have the connectivity you need, regardless of the system.
Be proactive and let us know when there’s a system you potentially want to integrate with. This helps us to get ahead of timelines.
If you’re ready to integrate with a new EHR or other system, the process is straightforward.
- Reach out: Contact your Redox account representative and let them know which EHR or other system(s) you want to connect with.
- Share what you have: If you have access to technical specs, API documentation, or any relevant resources, share them with us.
- No specs? No problem: If you don’t have any resources to share, don’t worry. We have a dedicated engineering team that specializes in investigating, scoping, and developing adapters for new systems. We’ll take the lead on reviewing available specs and will reach out to the EHR or other system’s company if we need extra support.
We’re committed to never being the barrier to your integration needs. Once we have the necessary information, our team quickly gets to work, focusing on impact over process.
- Initial review: Our standard review process typically takes 1 to 2 weeks. During this time, we analyze the documentation to estimate the development effort and timeline.
- Development timelines: Timelines can vary depending on complexity, but new system adapters are relatively quick. We often see a turnaround time of 4 to 6 weeks.
- Implementation: Our implementation team works closely with our API developers to test and validate development with your partner connection.
We believe in building a reusable network that benefits everyone. Because of that, we don’t consider building a new system adapter to be the same as custom development work.
There’s often no cost for building a new system adapter. However, there’s a cost for custom development work. Let’s break down the difference:
- New system adapter: A new system adapter means adding any API, format, or new connectivity method your connection prefers we use. Our goal is to make it as easy as possible for you to integrate with your connections.
- Custom development work: This refers to non-standard, custom development unique to you. For example, if you’d prefer we code up to your proprietary API rather than use ours.