
By now many of us know about Google Wave and have watched the truly epic introductory video. I won’t try to summarize the OMG!PONIES effect – you’ve got to see it to believe it.
What I will say is this: Wave has been framed as the technology that could kill email, IM, photo/music/video sharing, and more; and it has also been getting quite a bit of attention for its potential to become the quintessential collaborative tool in science and medicine.
Cameron Neylon who writes the blog Science in the Open summarized the (tentative) excitement superbly:
Those of us interested in web-based and electronic recording and communication of science have spent a lot of the last few years trying to describe how we need to glue the existing tools together, mailing lists, wikis, blogs, documents, databases, papers. The framework was never right so a lot of attention was focused on moving things backwards and forwards, how to connect one thing to another. That problem, as far as I can see has now ceased to exist. The challenge now is in building the right plugins and making sure the architecture is compatible with existing tools. But fundamentally the framework seems to be there. It seems like it’s time to build.
Med 2.0 Inundation and Other Disasters
I think that quote really hits the nail on the head. The volume of medicine 2.0 tools is growing faster than ever, but that growth is also kind of digging itself into a hole.
For example, it’s been discussed that if Nature could only combine all its great Science 2.0 tools, including Connotea, Precedings, Second Nature (the Nature island in Second Life!), Nature Blogs, Nature Podcasts, etc., into a one-stop resource, then there would be no question that every scientist on the planet would use it. As it stands, the dispersion seems like a safe way for Nature to experiment with a lot of ideas and see what sticks. The stickies thrive in semi-obscurity; the un-stickies disappear into the web 2.0 deadpool (as popularized by TechCrunch).
But I guess we can’t really blame Nature for being cautious…the one-stop resource is truly a daunting feat. Take Facebook, for example. Facebook has been (in my opinion, unsuccessfully) trying to do this via the Applications feature. Maybe some people can’t live without their photos, SuperWall, iLike profile (seriously, where would iLike be without Facebook?), and What Pirate Are You? results on the same site, but to me the addends are just overcomplicated and distracting. Science 2.0 has to overcome that and set standards – Wave might be just what we need.
How About These Neat Applications?
With my pre-adulation out of the way, here are links to Science in the Open’s and HealthySpacesRx’s excellent follow-up posts, which throw out a few possible applications of Wave in medicine.
Paper-writing flow with Wave:
- Write collaboratively using the inline commenting feature. Wave updates everything in real-time and tracks the whole history of changes. History is playback-able.
- Add citations with a Citations Bot
- Spellcheck, check terminology, translate with a Language Bot
- Add charts and graphs with a Data Bot that links up to spreadsheets and other programs
- Get peer-reviewed by adding reviewers as participants. Comment dialogue proceeds write on the Wave in real-time.
- Submit to journal by adding a Submit Bot. Maybe each Journal will have its own Bot?
Electronic Medical Records (EMR) flow with Wave:
- Every patient gets his own Wave.
- As they come in, doctors add test results to the Wave. Other health care professionals can then access. The results can include photos, videos, text, x-rays, consent forms…
- Patient adds his own progress to the Wave. For example, by adding journal entries logging incidences of chronic pain, frequency of exercise, smoking.
- Caretakers and family members add important notes.
- Health care professionals discuss and decide on treatment right on the Wave. Get quick second opinions from professionals around the world.
What’s next?
So, as I see it, the first major issue to watch as we integrate Wave with medicine will be the task of developing these mysterious Wave participants that I’ve been calling Bots. As a related example, consider that most physicians are more keen to adopt the iPhone than EMR simply because existing EMR systems are poorly designed, and because EMR vendors haven’t opened up their APIs to facilitate the kind of application-developing that drives the Apple AppStore. Similarly, the success of Wave in medicine will depend on a strong community consisting of developers who will make these peer-review, language translation, video support “participants” possible.
With the tools in place, we must also carefully consider the implications of Wave and its imitators on existing controversies relating to privacy and accessibility. Who will be allowed to participate in the Wave? How will Wave participants be authenticated? How much access should patients have to their own Wave? Do patients even own the data? These are discussions that are not only important for Wave, but also for the notion of EHR in general.
Finally, what about the human touch – does Wave pose a threat? Are we, as patients, ready to become patients 2.0 to such an extent? What kind of proof-of-principle and education will get us there? Surely it will take much more than an hour-and-a-half-long video?
Stay tuned for more updates.