The following is a guest blog by Brandt Welker, CTO at MedicaSoft. This is the second blog in a three-part sponsored blog post series focused on new HIT for integration. Each month, a different MedicaSoft expert will share insights on new and innovative technology and its applications in healthcare.
What are some of the common complaints doctors and nurses have about their EHRs?
“I have to click too much.” “Information is buried.” “It doesn’t follow my workflow.” “It’s slow.”
“I feel like a data entry clerk.” “*insert your favorite gripe here*” There is no shortage of commentary on the issues irking clinicians when it comes to technology. What there is a shortage of are ideas to fix it.
Better technology is out there serving other industries … and it can be applied in healthcare. Technology should ease administrative loads and put clinicians back in front of patients! I’ve talked about some of this previously and how we keep clinicians involved in our design process. When it came to building an entirely new EHR, the driving force behind our team researching and adopting new technologies was to imagine a clean slate.
Most of our team came from backgrounds with the Department of Veterans’ Affairs (VA’s) world of VistA. We learned a lot about legacy systems over the years – both beloved and maligned – and asked ourselves what a system would look like if it was unencumbered by the past. How would that system look? What could that system be? What technology choices should we make to simplify things? How could it play nicely with other systems and encourage true interoperability? How could it support users’ clinical workflow?
From the beginning, we decided that the most important thing was to get the platform right. Build the platform and build it right and things will work together. Build it to play nicely with other technology and interoperate. Make it fast. Make it easy. Make it open. Make it affordable. All of these needs were a part of our system “wish list.”
So, how’d we do it? We researched technology working in other fields and also elected to use HL7® FHIR® to its fullest extent. By now, you’ve probably heard a lot about the HL7® FHIR® standard. Many companies are using HL7® FHIR® to build APIs that are doing amazing things across the industry. We decided to use the HL7® FHIR® document data model as the basis of our platform – it simplifies implementation without sacrificing information integrity. We coupled it with a very powerful database and search engine – Couchbase & Elasticsearch. These are two high-performance tools used across industries. When you need a whole lot of data to move fast, you use Couchbase and Elasticsearch.
Couchbase is our NoSQL database. Couchbase is open-source and optimized for interactive applications. It provides low-latency data management (read: lots of data very quickly) for large-scale applications (like an EHR!). It lets us store records as documents and it’s really good at data replication. You might recognize Couchbase — many other industry giants such as ebay, LinkedIn, and Verizon use it. It is an open-source database optimized for interactive applications. We selected Elasticsearch as our search engine. Some of your favorite sites and services use Elasticsearch – Netflix, Facebook, LinkedIn, and Wal-Mart, to name a few.
On top of Couchbase and Elasticsearch are FHIR APIs. These interactions are managed by type. We also use a Parser/Assembler Service that lets us combine, rearrange, and augment documents. Data is placed in the proper JSON format to be sent through the FHIR API into Couchbase. Our Community Health Record sits on top of this and everything described here is a part of our open platform – the one we built from scratch and architected to be interoperable and easy. Pretty neat, huh?
Once you have the platform, you can build all kinds of things to sit on top of it. The sky is the limit! In our case, we have a Personal Health Record and an Electronic Health Record, but we built it this way so you can use a wide range of technologies with the platform – things like Alerts or Analytics or Population Health or Third Party Applications, even custom built items that folks may have developed in-house will work with the platform. Essentially, using the platform means we can integrate with whatever you already have in place. Maybe you have an EHR with some issues, but you don’t have the time or budget allotted for another huge EHR implementation. No problem – we can help you view your data with a modern interface – without having to buy a whole other EHR. Revolutionary!
There are several other technology choices we made along the way, too – Node.js, NGINX, Angular.js are a few more. Angular.js allows us to be speedy in our development process. We can develop and build features quickly and get changes in front of clinicians for their feedback, which results in less time between product builds and releases. It means folks don’t have to wait months and months for changes they want. Angular is also web-based, which means user interfaces are modern and just like the interfaces everybody uses in their day-to-day lives. Angular.js was created by Google and there are many large companies you’ll recognize who use it to develop – PayPal, Netflix, LEGO, YouTube, to name a few.
I believe healthcare is lagging in adopting new technologies and there are a lot of excuses around why user interfaces in healthcare are generally horrible – they range from the software being written before Web 2.0 to users accepting that it is how it is and finding a way to work around their technology. The latter is probably the saddest thing I see happening in hospitals and clinics. Tech is there to make work easier, not more complicated.
There was a great quote from Dale Sanders, Executive Vice President of Product Development at Health Catalyst in MedCity News last week:
“Every C-level in healthcare has to be a bit of a technologist right now,” he said. “They need to understand this world. If you’re not aware of technology, it puts you … at a strategic disadvantage.”
I can’t emphasize how true this statement is. If you’re not paying attention to where technology is going, you’re not paying attention to where healthcare is going and you’re going to get left behind.
About Brandt Welker
Brandt is a HIT architecture and software expert. He calls Reading, Pennsylvania home. He has architected software systems and managed large IT and innovations programs at the U.S. Department of Veterans Affairs (VA) and the National Aeronautics and Space Administration (NASA). He’s also trained astronauts at the Neutral Buoyancy Lab. He’s currently the Chief Technology Officer at MedicaSoft. Brandt can be found on LinkedIn.
MedicaSoft designs, develops, delivers, and maintains EHR, PHR, and UHR software solutions and HISP services for healthcare providers and patients around the world. For more information, visit www.medicasoft.us or connect with us on Twitter @MedicaSoftLLC, Facebook, or LinkedIn.