A Healthcare Information Services Provider Business Model

Life as a Healthcare CIO (Jan 5 2011)

1. I've written previously about Healthcare Information Exchange Sustainability and the need for Healthcare Information Services Providers (HISPs) to serve as gateways connecting individual EHRs.How should HISPs be funded and how can we encourage HISP vendors to connect every little guy in the country?We've started to think about this in Massachusetts.There are numerous vendors promising HISP services -  Medicity (Aenta), Axolotl (Ingenix), Surescripts, Verizon, and Covisint. An HIE needs to include at least one common approach to data transport, a routing directory, and a certificate management process that creates a trust fabric.   Existing HISP vendors have heterogeneous approaches to each of these functions.    In the future,  the Direct Project may provide a single approach, but for now HISP vendors will need to be motivated to adhere to State HIE requirements.An idea that has been embraced by some State HIEs, such as New Hampshire, is to pay HISP vendors a modest fee (under 100K) to support State requirements.   This "connectivity" incentive results in interoperable HISPs, creating a statewide network of networks.Once a standardized HISP approach is supported by multiple vendors, then individual practices need to be connected.   Some practices will be aggregated into hubs by EHR software vendors as has been done in cities such as North Adams (Massachusetts), projects such as the New York City ... (Read Full Article)

   Bookmark or Share this article

Login to comment