• Aboutelizabeth han
  • Best Ofthe greatest hits
  • Med 2.0what is it?
  • PresshS out and about

November 20, 2009
Posted by Elizabeth Han

Dreaming of a Health Information System Built on Google Wave

 

Update Jan 26th, 2010: Thanks to Dr. Ves (@DrVes) for suggesting this post on Clinical Cases and Images: CasesBlog!

Let’s face it. The last two weeks of gently fiddling with Google Wave (effy [dot] han [at] googlewave.com) really weren’t all that gentle. From painful slowness on Firefox to the most awkward reply structure ever (someone please explain this to me!) to extensions that would barely load let alone function – Wave was more of a rollercoaster than the idyllic sea that its name was probably meant to evocate. I’m still just as excited about Wave in health care as I was in July, but there is plenty more to consider now that many of us have gotten our hands wet. Is our ideal feasible?

A health information system built on Wave could take patient empowerment to the next level.

My take on the utility of Wave in health care grew out of a quote from The Possibilities for Patient-Centered Communication:

Doctors and patients are able to initiate communicate around a condition and all things related to the patient’s condition are captured within a wavelet (individual conversations/collaborations). Things like MRI’s and test results can be appended to a wave and doctors and specialists can collaborate through the wave. Since the communication is server-based, these conversations can be captured, secured, tagged, searched, etc.

In my mind, it looks something like this:

wave

The fishiness explained.

The Fishbone represents my (Liz’s) wave swimming along in a big happy ocean of health (…). The first level is an example sequence of actions (mostly from the health professional’s point of view) starting from the tail, when the patient’s problem starts.  The red terms are features that I believe should be accommodated within the wavelet. Some, like Maps and Calendar, can be readily pulled from existing Google services.

The order of the tasks/wavelets is not absolute, but I think that part of the genius of Wave is the ambition to allow an (invited) participant to join at any time and immediately understand the progression of events that has led to the current state of collaboration on the wave. Tag/group support and accurate timestamping is paramount.

At any branch, a patient can insert a reply (ugh, if they ever figure the current reply structure out, anyway), start a chat, go nuts with Playback. There should also be a gallery of useful interpretative extensions available, including live language translation, medical jargon lookup, hive mind experiences.

As DrV noted, if the physician doesn’t provide the information, the patient’s just going to go home and Google it. Even I feed many of my smaller irritations through an AskMetafilter search first because these people are fast and well-articulated.

Others have been even more productive.

And by more, I mean much, much more.

  1. Siamak Ashrafi at Ylabz recently put together an excellent video depicting how a doctor and nurse could communicate in real-time [Youtube] on a Wave-based system with support for Google Health. Most interestingly, he suggests that “a hospital could install Google Wave inside their firewall and obtain full compliance”.
  2. Quite appropriately, there’s a wave on this topic that is generating top-notch discussion. This is a text version, which naturally makes me wonder if public waves can be linked to (similar to the Google Reader’s public share page). The URL within Wave is here, if you’re interested.
  3. And don’t forget the always-excellent Cameron Neylon of Science in the Open, who has been hard at work spreading the Google Wave love. This video demos some research-helpful extensions [Viddler] such as Nature’s adorably-named Igor (search and insert citations).

Then again, maybe it’s premature: what [the wave] is and what never should be.

So that was the good news.

Unfortunately, or perhaps not–at this stage, we are all just playing around with our new toy—the reality could rapidly devolve into this:

  • Empty wavelets
  • Vandalism
  • Scary embedded media
  • Advertising
  • 100 000+ pairs of eyes glazing over

Next Wave post: I’d like to do a run-down of what I think are the most useful Wave extensions for health care. Stay tuned.

Related posts:

  • Google Wave for Medicine 2.0
  • The Search for Better Search in EMR

3 Comments

Posted Under Uncategorized

  • http://WebsiteURL Colin

    Hey congrats on your domain and hosting. Did you use the coupon I sent you? Also smart of you to RFD it up and use Dave’s Network. ;)

    The reply structure of Wave makes perfect sense to me. It’s the same threaded reply system used in newsgroups and old-school message boards. Modern message boards now use a flat structure that makes it easier to see new posts (they’re right at the end). But this new structure means you’re replying to a topic rather than a post. The system used in Google Wave lets you reply to individual posts rather than tag a reply at the end. This structure is much more intuitive to a new reader browsing the topic for the first time. In the flat message board system, the only way to reply to a post is to quote them in your post. This is not ideal. The replying post could be many pages away from the post being replied to, so the reader needs to keep track of a dozen different conversations going on at once while reading the topic. You mentioned the usefulness of this reply system in your post when you said that the patient could reply to any branch in the fish rather than at the end.

    Anyway, I think what fundamentally separates Wave from a typical wiki/forum setup is the live editing and playback functionality. Most of the other stuff can be implemented into a wiki or forum through hacks and addons. I’m wondering how these features in particular are useful for medical purposes. Is real time communication practical in most situations? Or would it be more efficient for a doctor to wait for the patient to enter all possible data before responding?

  • Elizabeth Han

    Re: reply structure — perhaps “structure” was the wrong word to use. I think the threading of course makes perfect sense. I was just getting irritated with the difficulty of adding replies where I wanted them to go. That plus lag and empty blips opening up randomly was killing the reply experience. I’m sure the team is working on optimizing.

    Re: the relevance of real-time — I’m seeing the applications as “compartmentalized”. It should be obvious what is editable and not editable in real time based on the function of the wavelet. Like if it’s supposed to be a live feedback session on test results, then you enable everything and chat away. If you’re filling in a form, then the doc doesn’t have to watch you do it, but playback might be important to see when you submitted in order to provide context for a later discussion.

  • Pingback: Health Information System Built on Google Wave « WK Learning

  • About Elizabeth

      I'm a medical student and biomedical engineer at the University of Toronto. I write about medicine in the age of social. [More...]

    • Latest Posts
     

    Medical Pinterests?

     

    We’re back!

     

    Research Recruitment Redux: Add Quora?

    • Tweets (@effyhan)

    5 Alternatives to Pinterest: Juxtapost, We Heart It & Image Spark : Shiny Shiny http://t.co/mlKSElXw

    follow me on
    twitter

    Categories

    • Canada
      • Toronto
    • Design & Usability
    • Doctor-Patient Relationship
    • Electronic Medical Records
    • Ethics & Professionalism
    • Google
    • Health Care Reform & Politics
    • Primary Care
    • Research & Science
    • Social Media
    • Stories
    • Telemedicine
    • Twitter
    • Uncategorized
    • US Health Care
  • Archives

    • 2012
      • January
    • 2011
      • February
      • March
      • April
      • June
    • 2010
      • January
      • February
      • March
      • April
      • May
      • June
      • July
      • September
      • October
      • December
    • 2009
      • June
      • July
      • October
      • November
      • December
    • 2008
      • March
  • Friends Who Blog

    • Alex Heeney
    • Elliott Sales de Andrade
    • Kelvin Lui
    • Paul Kishimoto
    • Tim Chen
    • Ting Zhu
  • Med2 Blogroll

    • 33charts by DrV
    • Better Health
    • Canadian Medicine News (Canadian)
    • Dr. Dialogue by Dr. Juliet Mavromatis
    • Dr. Edwin Leap
    • Dr. Fullerton (Canadian)
    • Dr. Greiver's EMR (Canadian)
    • Dr. Gunther Eysenbach (Canadian)
    • Dr. Jay Parkinson
    • Dr. Wes
    • Kevin, MD
    • MobiHealthNews by Brian Dolan
    • Musings of a Distractible Mind by Dr. Rob
    • Nick Dawson
    • Science in the Open by Cameron Neylon
    • Scienceroll by Bertalan Mesko
    • See First by Evan Falchuk

All text (c) 2011 by Elizabeth Han.
This site is using an adaptation of the Handgloves Theme

Subscribe via RSS