This past week, Google had its annual developers conference, Google I/O. One of the more provocative talks, called “The End of Search as We Know It,” was by Amit Singhal, who is in charge of search for Google.
The vision, as described by Amit, is that instead of typing words into a box on a website or mobile app, we will have conversations with Google, enabling a much more personalized, refined experience. The holy grail, of course, is that Google analytics become both predictive and prescriptive, serving you content that is just right for you and anticipates your needs.
It seems there is a race on now to achieve this vision. One could argue that Amazon, Apple, Facebook, Pandora and others are all in the same mode. Best I can tell, the promise these companies are floating to advertisers is that their ads will be served up to that focused slice of the population that will find their product relevant in the moment.
If you apply this thinking to healthcare, several controversies/topics come to the fore.
Is Google competing with IBM’s Watson? Undoubtedly yes. On the other hand, I’m guessing Google is disenchanted with the consumer health space after the demise of its personal health record (PHR). And IBM seems to be focused on clinician decision support. So early in the game, with respect to healthcare anyway, maybe there is not much competition. The path for clinician decision support is clear and the market obvious, whereas the path and market for consumer health decision support are blurry.
This is my new office. I signed the lease for this property yesterday – another big step in the process of getting my new practice off the ground. I should feel good about this, shouldn’t I? I’ve had people comment that I’ve gotten a whole lot accomplished in the 4 weeks since I’ve been off, but the whole thing is still quite daunting. Yes, there are days I feel good about my productivity, and there are moments when I feel an evangelical zeal toward what I am doing, but there are plenty more moments where I stare this whole thing in the face and wonder what I am doing.
I walked through the office today with a builder to discuss what I want done with the inside; it quickly became obvious that there was a problem: I don’t know what I want done, and nobody can tell me what I should do. Yes, I need a waiting area, at least one exam room, an office for me, a lab area, bathrooms, and place for my nurse, but since I don’t really know which of my ideas about the practice will work, I don’t know what my needs will truly be. How much of my day will be spent with patients, how much will be doing online communication, and how much will be spent with my nurse? I want a space for group education, but how many resources should I put toward that? I also want a place to record patient education videos, but some of my “good ideas” just end up being wasted time, and I don’t know if this is one of them.
I come across the same problem when I am trying to choose computer systems. I know that I want to do that differently: I want the central record to be the patient record, not what I record in the EMR. I want patients to communicate with me via secure messaging and video chat, and I want to be able to put any information I think would be useful into their PHR. So do I build a “lite” EMR product centered around the PHR, or do I use a standard EMR to feed the PHR product? Do I use an EMR company’s “patient portal” product, or do I have a stand-alone PHR which is fed by the EMR? I have lots of thoughts and ideas on this, but I don’t really know what will work until I start using it.
[youtube width=”475″ height=”300″]http://www.youtube.com/watch?v=5ESWiBYdiN0[/youtube]
TED Fellow Salvatore Iaconesi released this video along with his digital medical records – everything from CT and MRI scans to lab notes. He posted the health files to invite the online world to participate in the process of treating his brain cancer. As he wrote on his website:
This is my OPEN SOURCE CURE. This is an open invitation to take part in the CURE. CURE, in different cultures, means different things. There are cures for the body, for spirit, for communication.
Grab the information about my disease, if you want, and give me a CURE: create a video, an artwork, a map, a text, a poem, a game, or try to find a solution for my health problem. Artists, designers, hackers, scientists, doctors, photographers, videomakers, musicians, writers. Anyone can give me a CURE.
Create your CURE using the content which you find in the DATI/DATA section here on this site… All CURES will be displayed here.
Electronic health records (EHRs) offer many valuable benefits for patient safety, but it becomes apparent that the effective application of healthcare informatics creates problems and unintended consequences. As many turn their attention to solving the seemingly intractable problems of healthcare IT, one element remains particularly challenging–integration–healthcare’s “killer app.” Painfully missing are low-cost, easy to implement, plug-and-play, nonintrusive integration solutions. But why is this?
First, we must stop confusing application
integration with information
integration. Our goal must be to communicate data (ie, integrate information), not to integrate application functionality via complex and expensive application program interfaces (APIs). Communicating data simply requires a loosely coupled flow of data, as occurs today via email. In contrast, integration is a CIOs nightmare. Integrating applications, when we just wanted a bit of information, is akin to killing a gnat with a brick.
Even worse, like a bad version of Groundhog Day, the healthcare IT industry keeps repeating the same mistakes, and we keep working with these mistakes. Consultants and vendors from whom we request simple data communication solutions offer their sleight of hand, which usually recasts our problem into a profitable application integration project that simply costs us more money. This misdirection takes us down a maze of tightly coupled integrations that are costly, fragile and brittle, and not really based on loosely-coupled data exchanges, a simpler approach that allows the Internet to perform so well.
The key to unlocking the potential of EHRs lies in securely communicating (a.k.a. exchanging) data between EHR silos. If we simply begin by streaming data from EHR systems onto a common backbone, using a common currency like XML (eXtensible Markup Language), we will have solved healthcare integration in a way that works the way much of the Internet works. And this is good. When this happens, we know interoperability will work, robustly.Continue reading…
Who owns a patient’s health information?
·The patient to whom it refers?
·The health provider that created it?
·The IT specialist who has the greatest control over it?
The notion of ownership is inadequate for health information. For instance, no one has an absolute right to destroy health information. But we all understand what it means to own an automobile: You can drive the car you own into a tree or into the ocean if you want to. No one has the legal right to do things like that to a “master copy” of health information.
All of the groups above have a complex series of rights and responsibilities relating to health information that should never be trivialized into ownership.
Raising the question of ownership at all is a hash argument. What is a hash argument? Here’s how Julian Sanchez describes it: