The other day, I had the opportunity to interview Mark Scheppe, a developer at CODE responsible for integrating their application at customer sites running EHRs like GE Centricity and NextGen. In our talk, he explains the challenges associated with integration, as well as provides some insights for developers at the beginning of the journey.
The combined power of HIPAA-compliant Backend as a Service and pre-built EHR integrations reduces mobile app time-to-market by 80 percent or more.
Boston (PR Web)—August 11, 2016 - Kinvey, the leading HIPAA-compliant mobile Backend as a Service (mBaaS) and Redox, the leading Electronic Healthcare Record (EHR) API integration provider, today launched an end-to-end solution designed to accelerate the delivery of digital health innovations by solving the hard problems related to bridging EHR data into mobile, web and smart device applications. The on-demand cloud-based platform accelerates app delivery by 80 percent or more.
I've spent a lot of valuable time reading and learning how to become a rockstar developer from people like Fred Brooks and Jeff Atwood, but no one has really written a guide about how to be a rockstar healthcare developer.
This post will be my quick hits on what is different about developing in the healthcare space and what Redox can help with.
Nettie woke me up at 5am on Saturday, "My water broke, and you should see this sunrise!" She was a silhouette of orange and pink sky standing above a towel. We were six days past the due date and expecting labor to start. I struggled out of bed and prepped the hospital bag, made breakfast, tried not to freak out. It wasn't until noon when contractions started. Over the next few hours, they grew in intensity and progressed to around five minutes apart. They say not to go to the hospital until you hit around three minutes. I called our doula who came right over to begin her work. By nightfall, contractions had intensified but the frequency was still around five minutes. We decided to go to the hospital anyway.
When I worked at Epic, I was asked to do many challenging and exciting things. The most challenging and least exciting thing, though, was being a project manager for integration projects. Since this role exists at Redox as the Customer Success (CustoSucc) team, I feel privileged to be working with people who are excelling in ways I never could.
In this post, I'll explain what an integration project is, why it's a project, and why Redox has a recipe for success.
Oh, hi. I’m Nick John.
I joined Redox at the beginning of June as a Solutions Engineer. In reality, though, my relationship with Redox began a very long time ago: when I worked at Epic as the Director of Interface Implementation, I found myself on a number of projects with the founders of Redox, as well as several of the developers and Customer Success staff now working here, too. We each left Epic, one by one, to spread our wings and find new ways to help the world. I set sail for Portland to live the city life and climb its glorious mountains, while my friends set their minds to solving interoperability in healthcare.
MADISON, WI—(Marketwired - June 21, 2016) - Redox, an integration platform that enables applications to easily and securely share data with electronic health records (EHRs), announced the integration of five cloud-based software applications which address some of the biggest challenges in the healthcare industry. Since closing their Series A investment in October of 2015, Redox has been scaling its ability to help cloud applications integrate with various legacy EHR vendors used at health systems. Today, hundreds of developers use the Redox platform to provide healthcare systems with innovative applications that improve patient care. Among these are: