Flashback to high school. Remember when someone from your class wouldn’t be there for a couple of days... and then a week, and then a couple of weeks. The rumors about what was up with that kid would begin to seep out of the air vents, reaching everyone and spreading around the school.
When I first began working in healthcare 14 years ago, it was using a DOS-based system on a terminal computer for admitting and registering patients at Elkhart General Hospital in northwest Indiana. I didn’t have my own cell phone yet and the idea of buying a laptop made me nervous because so many people had experienced catastrophic crashes with them. They just didn’t seem as stable as a desktop, you know?
In other words, I began working in the stone age.
At Redox, we have embarked on tackling a huge problem: interoperability. It’s not an atomic problem; it’s divisible into a number of more elementary, hard problems. We embarked on tackling interoperability because it’s challenging and so valuable to solve. Both aspects contribute to making Redox such an exciting place to work.
But what makes a problem hard? It’s common knowledge that interoperability is hard, but less common is a deep understanding of what makes it so. I submit that much of what makes interoperability and it’s divisible parts so hard is the plurality of necessary concerns in the space we work in. Some of those concerns are:
The end of September and the beginning of fall has brought with it some new features and welcomed updates to our core product offering. As they say, new season, new EHR integration platform (or something like that).