Integrating Your Telemedicine Solution With Redox

Posted March 30, 2017
By Redox

Whether increasing access to clinical services for remote patients, improving health outcomes by enabling faster diagnosis and treatment from specialists, or reducing healthcare costs, telemedicine is emerging in the healthcare industry as an essential service and tool.

Telemedicine applications rely on highly efficient workflows, and due to this, having the right information arrive via the right system at the appropriate time is critical. Health systems’ workflows, databases, integration data standards, and communication protocols can be difficult to navigate, but working with Redox minimizes these complexities for your application—we know the ins and outs of the technical and legal work required to integrate from decades of hands-on experience. We know what data your application needs, where and how that data exists, and how to get it securely to and from the EHR.

Often, telemedicine solutions are hindered by the technical variance among EHRs, and with EHR configurations differing from health system to health system, how your application receives something as simple as an admission message can vary drastically. Scaling and deploying rapidly becomes challenging when your application needs to redevelop your product for each new integration, and since these point-to-point connections require a significant amount of time to develop, they divert time away from enhancing and developing your application.

Finding an integration solution that is quick to implement—and easily updated as you expand to new sites—will enable your application scale successfully.

One of the main benefits of choosing an integration partner is the added value in terms of scalability. With Redox, our network enables your application to deploy to multiple health systems without ever having to increase your IT team or infrastructure.

How Redox Helps

Telemedicine solutions have truly revolutionized patient care—a simple dermatology visit used to involve physically going to a physician’s office, but now, patients can take pictures using a smartphone and submit them directly to a physician for review. While effortless for the patient, these applications require building custom interfaces that file data back to the EHR. That means for every new integration, your team would need to reconfigure your application to meet the requirements of each unique health system.

That is, until now. Redox is the “build once, go anywhere” partner for telemedicine applications. Our team of EHR integration experts has successfully integrated customers with EHRs both large and small, powering telemedicine solutions to provide care, improve patient outcomes, and reduce cost. Here’s how we do it.

       1.  Our modern API exposes a single connection and standard for your application to build against. Instead of changing how you send in documentation for visits into Cerner, Epic, Greenway, or any other EHR, you will always structure your results  and send your messages in the same format via a single HTTPS connection. This eliminates having to reconfigure your product for every new deployment, growing your scaling potential and freeing up months of time.

       2. Instead of establishing and supporting the connections to your customer’s on-premise EHRs, we handle all connectivity and maintenance to the health system. With no VPNs, SFTP, or other nasty acronyms to worry about, you don’t have to expand or dedicate staff to becoming a network security team—it’s all handled by our fully managed services.

       3. We are integration experts, not just in the technical sense, but also when it comes to the business side of the project, too. Our expertise has helped close sales and expedite projects because we understand that framing is crucial—presenting the project in a way that highlights the value of the product to both the patient and health system makes it nearly impossible for an IT team to object. An average point-to-point interface project can take between 40-60 hours of health system IT resources, while an average Redox integration project requires, on average, only 10.

       4. Lastly, unlike any other integration solution, Redox’s industry leading platform can accommodate the inevitable changes that will occur in the healthcare space, be it an EHR update, change of system, or adoption of a new data standard like FHIR. Our hub-and-spoke model allows us to quickly make changes on an engine level that will ripple out and affect your application’s workflow, and our SaaS model means you are always covered with long term support and flexibility.

A Telemedicine Integration Workflow

Remote Appointments

  1. Your application receives information that a telemedicine appointment has been scheduled via subscription to the Redox Scheduling data model.


2. During the visit, the provider delivers care to the patient, including clinical documentation like assigning a diagnosis, adding allergies to the patient’s chart, and ordering medications or labs.

3. The provider documents the care delivered.


1. Your application receives an admission message from Redox via the Patient Admin data model.

    • Depending on your workflow, these messages can be filtered down to certain departments or types of patients.

2. The clinical care team delivers and documents the care received by the patient.

    • If the care is documented in the application, the data can be sent to the EHR for long-term storing in the patient’s medical chart. This data would likely be sent into the EHR using Redox’s Media or Notes data models. For discrete documentation, like vital signs or assessments, we would leverage Flowsheets or Results.
    • To push additional information such as allergies, medications, or problems (diagnoses), your application would utilize the Clinical Summary data model.

The Next Steps

We’ve executed these workflows at health systems across the country and would love to help your organization achieve its strategic goals. To learn more about how Redox accelerates the telemedicine workflow and positions your solution to scale rapidly, contact our Solutions Team. We’ll discuss your specific use case and outline what your project would look like.

For technical clarification on how you would use our platform to integrate with any EHR, check out more information on our most commonly used data models for this use case.