I’ve always enjoyed reading HISTalk, and today was no exception. This time, I came across a piece by a vendor-affiliated physician arguing that it’s time for providers to shift from isolated EMRs to broader, componentized health IT platforms. The piece, by Excelicare chief medical officer Toby Samo, MD, clearly serves his employer’s interests, but I still found the points he made to be worth discussing.
In his column, he notes that broad technical platforms, like those managed by Uber and Airbnb, have played a unique role in the industries they serve. And he contends that healthcare players would benefit from this approach. He envisions a kind of exchange allowing the use of multiple components by varied healthcare organizations, which could bring new relationships and possibilities.
“A platform is not just a technology,” he writes, “but also ‘a new business model that uses technology to connect people, organizations and resources in an interactive ecosystem.’”
He offers a long list of characteristics such a platform might have, including that it:
* Relies on apps and modules which can be reused to support varied projects and workflows
* Allows users to access workflows on smartphones and tablets as well as traditional PCs
* Presents the results of big data analytics processes in an accessible manner
* Includes an engine which allows clients to change workflows easily
* Lets users with proper security authorization to change templates and workflows on the fly
* Helps users identify, prioritize and address tasks
* Offers access to high-end clinical decision support tools, including artificial intelligence
* Provides a clean, easy-to-use interface validated by user experience experts
Now, the idea of shared, component-friendly platforms is not new. One example comes from the Healthcare Services Platform Consortium, which as of last August was working on a services-oriented architecture platform which will support a marketplace for interoperable healthcare applications. The HSPC offering will allow multiple providers to deliver different parts of a solution set rather than each having to develop their own complete solution. This is just one of what seem like scores of similar initiatives.
Excelicare, for its part, offers a cloud-based platform housing a clinical data repository. The company says its platform lets providers construct a patient-specific longitudinal health record on the fly by mining existing EHRs claims repositories and other data. This certainly seems like an interesting idea.
In all candor, my instinct is that these platforms need to be created by a neutral third party – such as travel information network SABRE – rather than connecting providers via a proprietary platform created by companies like Excelicare. Admittedly, I don’t have a deep understanding of Excelicare’s technology works, or how open its platform is, but I doubt it would be viable financially if it didn’t attempt to lock providers into its proprietary technology.
On the other hand, with no one interoperability approach having gained an unbeatable lead, one never knows what’s possible. Kudos to Samo and his colleagues for making an effort to advance the conversation around data sharing and collaboration.