In a previous post titled “3 Questions to ask your healthcare API vendor”, I  touched on why we don’t use an off-the-shelf interface engine for Redox. In this post, I want to dig deeper into why I’m so passionate about this. 

On the way back from my recent overseas adventures, I was lucky enough to binge watch the entire first season of Mr. Robot. The show is amazing and I highly recommend it!

On Wednesdays we come together as a full team for our weekly meeting. We're geographically distributed, so the majority of us appear as a tiny box on a TV at the end of the conference room table. After the normal banter and AV woes are ironed out, the first thing on the agenda is silence—we sit and meditate together. This lasts about three minutes and is followed by a lap around the group to share your personal wellness intention for the coming week and assess how last week's intention went.

One of the most amazing parts of building a network of health systems and digital health applications that can easily share data through our platform is all the incredibly talented people we get to work with on a daily basis. From brilliant app developers building solutions that will drastically improve patient care to the interface analysts and IT teams who valiantly keep all of these systems running and evolving- we get to interact and partner with really awesome people!

The thing that healthcare IT and ancient China have most in common? Most people in the United States have no idea about how either work. The second? There is a lot more nuance than even scholars of both fields know.

With all the EHRs that our engine interacts with, it's kind of hard to keep track of what all the connection types and data formats we support are. As always, I try to help clarify things.

 Just wanted to share a quick demo video from Health 2.0 Winter Tech back on January 13th, 2016 in San Francisco as part of JPM.

Thanks to Gauss Surgical for letting me use them as an example!

Half of the Redox team is remote. This month, I'm extremely remote -barely working from China. In this post I'd like to meditate on what tools you need to be a successful remote worker.

If you're reading this, you likely have a need to integrate your application with EHRs across the country (maybe even the world!). There are a handful of API companies out there, with us at Redox pushing the pack. As you review available solutions, it is important to ask the right questions and get past the marketing. This post overviews some really tough decisions we have had to make in designing our product, and why we made the choices we did.

I use the word incentives a lot, partly because I'm married to an economics professor, and partly because it's been a key part of my motivation for most of my life.