Catalyzing the app store for EHRs

Dr. Lumpkin serves as director of the Robert Wood Johnson Foundation’s Health Group, where he is responsible for planning and program management. Prior to joining RWJ, Dr. Lumpkin led the Illinois Department of Public Health for 12 years. As  assistant vice president, Downs plays a leading role on the Foundation’s Pioneer Portfolio team. During his tenure at the Foundation he has created, developed,  or overseen the  Foundation’s investments  in such key initiatives as Project HealthDesign, InformationLinks, the Health e-Technologies Initiative, the Public Health Informatics Institute, Connecting for Health, and Common GroundHis writings may be found at Pioneering Ideas, where this post first appeared.

Iphone_health Recently, Steve posted about the idea, floated by Ken Mandl and Zak Kohane, that EHRs (or health IT more broadly) could move to a model of competitive, substitutable applications running off a platform that would provide secure medical record storage.  In other words, the iPhone app model, but, for example, you could have an e-prescribing app that runs over an EHR instead of the Yelp restaurant review app on your iPhone.  We’re thinking about the provider side of the market here, as Google Health and Microsoft HealthVault are already doing this on the consumer side.

It’s nice to ponder these “what ifs,” but we’re a bit more action-oriented here and we’ve turned our attention to asking what it would take to make this happen.  It seems that there are two things that are needed. First, we need the platform.  Some of the most notable platforms started out as proprietary that were then opened up.  The IBM PC comes to mind as an example. Some were designed from the beginning to be open platforms with limited functionality until the market started developing applications.  A recent example is the development of iGoogle and the tons of applications that are available for free.  Finally, there was the purely public domain development from the beginning to end that we’ve seen in the Linux world.  Or perhaps we don’t need a common platform and maybe what is needed is to stimulate the market for health IT products that have open application programming interfaces (APIs) that allow for third-party application development?  Several ideas come to mind.

A venture fund for platform providers.

Perhaps the key is to put more money behind companies that offer EHRs that allow 3rd party app development.  Will seeding a fund convince other investors to get in?  Are there startup ventures out there that could take advantage of the fund?
A venture fund for app developers.  Apple and Kleiner Perkins did this – they set up a $100 million fund to invest in companies that would develop applications for the iPhone.  Makes some sense, but there are some differences.  Apple already had the platform and a developer community was emerging.

A prizeBob Hughes has posted before on Pioneering Ideas about prize philanthropy, which is an intriguing approach to stimulating desired breakthroughs.Could a prize that awards a pot of money for development and ultimately use of a platform/app approach to health IT catalyze a competition among vendors?  Prizes tend to work well when companies believe that winning the prize will give them a leg up (through the innovations they developed to win the prize or the reputational capital earned by the publicity) on a new market.  The cash doesn’t hurt either, but it’s often not enough.  Would that be the case here?  What accomplishment should a prize reward in this case?  Apple made some headlines by announcing that a billion iPhone apps had been downloaded.  Could the prize target be a certain number of app downloads?  The intriguing idea is that a group of vendors could collaborate to share the prize by developing a common API (see OpenSocial as a model).  Would the publicity alone (assuming there was lots) stir up demand for this approach?

Other ideas.  We’d love to hear them. As you can see, we don’t have the answers here and need a lot of input.So if you have some thoughts on this, post a comment or contact us.  And if you know others that might care, please pass this on.

Livongo’s Post Ad Banner 728*90

Categories: Uncategorized

Tagged as: , , ,

Leave a Reply

13 Comment threads
0 Thread replies
Most reacted comment
Hottest comment thread
12 Comment authors
Eunicebest vacuum cleaners 2014Steve DownsKen Mandl and Zak KohaneMargalit Gur-Arie Recent comment authors
newest oldest most voted

Excellent blog post. I certainly appreciate this site.
Keep it up!

best vacuum cleaners 2014

A hoover is the very best of cleansing tools; it may also
be the more costly. You will find several different
sorts of vacuum with various characteristics.
Therefore before you buy a top-rated vacuum-cleaner be
sure you know what class of vacuum cleaner is
perfect for your demands.

Picking the best vacuum cleaner could be perplexing.
To simply help make things better you should be aware of what the various
sorts of hoover are, what the primary qualities you’ll be able to find on a
vacuum cleaner, and want you sort of flooring you’re going to
be using a vacuum-cleaner on.

Steve Downs

Thanks all for the helpful comments. Among other things, they give me a sense of how a metaphor can be a double-edged sword – it can give people an image that can help to translate a concept but at the same time, the details of that image can distract from the basic point. While the image of iPhone and its apps evokes the innovation that can be unleashed when developers have a popular distribution channel and a well-defined programming interface, the same image can seem a bit too simple, too glossy and too glib for the EHR discussion. The part… Read more »

Margalit Gur-Arie

Dr. Mandl & Dr. Kohane, I think you are correct regarding the lack of ability to integrate new products with existing EHRs. This was probably done by design partially in order to reduce the risk for the EHR vendor and partially because of the obvious limitations of client/server architectures. It seems to me that the proper recourse would be to demand (enforce?) open standards of interoperability and integration. I am not at all convinced that fragmentation of the EHR functionality package is beneficial to physicians, both from a usability point of view and mainly from a cost perspective. I also… Read more »

Ken Mandl and Zak Kohane

Interesting comments. We should be so lucky that current healthcare applications should be so substitutable and therefore removable as applications are on most operating systems. Instead, if you buy an EHR, you are buying into a very monolithic solution and cannot easily integrate with new products in the marketplace. We hope that a platform will address this and help create a market for innovative offerings. Without really wanting to defend the iPhone as a product, we do recognize that even its early incarnation, applications share access to contact lists and phone services with more interoperation to come.

Margalit Gur-Arie

I have to admit that the analogy to the “open iPhone platform” escapes me at every level. First of all the iPhone is hardware; the “platform” is really the OS, which is not at all open – it can only be used on Apple iPhones. The fact that people can write apps for the iPhone may be innovative in the mobile phone world, but it is how things have been working all along in the computer world. Anybody can write an app for Windows, package it and sell it, or make it available for free download. So what is different… Read more »

Ashland Dentist

While it’s true that this is a good idea – to use records with immediacy when needed, we must also weigh the cost of privacy and especially the loss of data through theft and mishandling. I don’t think I want any of my family members’ information floating out there to be misused due to a hacker or a sorkers incompetence.

Francois Andry

There are already some open source platforms that try to address HealthCare components integration issues.
(e.g. openeHealth.org)
As MarkS pointed-out, one of the most critical part is context management: how aggregate components/services efficiently and share user/patient contextes while keeping high level of security and privacy? CCOW tried to solve this at the application level, but is too cumbersome for components (e.g. widgets/portlets). We need a something lighter.

Sherry Reynolds

Great conversation starter. I assume that everyone is aware that we already have an open source software that links to National Health Information Network? http://www.connectopensource.org/display/Gateway/CONNECT+Community+Portal “Connect is an open source software gateway that connects the organizations health IT systems to the Nationwide Health Information Network (NHIN). Built through the collaboration of more then 20 federal agencies, the CONNECT Gateway can reap the benefits of health information exchange with other health institutions around the country.” The VA already also has more patients and providers on their open source system (VA Vista) then live in most European countries and the largest private… Read more »

Jay Parkinson

I think you’ll see this sooner than later. It’s really a no brainer. Luckily, we’re in an industry 10 years behind everyone else so all we have to do is observe what happened 10 years ago and emulate the best of breed.
But don’t worry, it’s close. I promise.


Science today has changed, I hope you used the right way, because there are medications such as vicodin, oxycodone, Lortab, etc, are anxiolytic and although much help to soothe the pain, can be double-edged weapon to control pain, so indicate in http://www.findrxonline.com to be confident that this discovery is beneficial to all.

Tom Leith
Tom Leith

There is nothing “obscure” about the protocols most EHR and PM type systems use, but MarkS is right — the protocols are the platform: HL7, DICOM, NCPDP, X12.n, ASTM, and CCR/CCD family of “stuff” I think is probably most useful to practitioners and patients in cross-organizational use cases. We have these already. For one of them in particular (HL7) the greatest current problem is what I call “minimal implementation”. Especially with Version 3, it will be much harder for vendors (and hospital CIOs) to get away with minimal implementation in the future, one hopes the NEAR future. The HL7 Reference… Read more »


You don’t need a ‘platform’. An interoperability specification is the platform and it needs to be open to ensure wide adoption and innovation. EHRs now are closed systems with limited data import and export over largely proprietary and/or obscure protocols. This keeps the customer captive but stifles the kind of innovation you are trying to foster. In order for this to work, you will need to have open interoperability specifications. You need to have a way that an eRx application can talk to the patient index to get patient demographic information and also talk to the EHR to get allergy… Read more »