A couple of summers ago I was asked to prototype an Integrated Health Education / Registration-Visit Information Intake Tool for a couple of local community health clinics. My undergraduate ninjas at the time, Allen Luo & Jakkree Janchoi, helped flush out the design, with Allen finalizing and mocking it up. Basically, an incoming patient will receive a smart tablet and be able to watch health related videos. In the back, the data on videos seen can be communicated to the doctor, or the doctor can recommend videos for the patient to see. In user story terms:

• Doctor observes patient’s interests in health education
  • User Interface gathers statistics on media consumed (Figure 1)
  • Statistics on media consumed may alert the doctor to address a particular topic (Figure 2)
• Patient receives recommended health education
  • Doctors may examen medical records to recommend topics (Figure 3)
  • Artificial Intelligence may examen medical records to recommend topics (Figure 4)

It was a good idea. Unfortunately, the proposal died as that: a proposal. As usual, when dealing with public and non-profit entities the “no money” card always flies up. (Well, it was more complicated than that…) This blog post is basically documentation of the work that we did, particularly Allen’s great implementation of my chicken scratch designs.

This was pre-iPad. This would probably look different with iOS specific UI. After all, iPad would be the way to go for something like this. A question I would have these days: would the video recommended to you, or data on the videos you watched fall under HIPAA?

Figure 1: A mockup of the media selection library.

Figure 2: A mockup of a recommendation resulting from a patient’s media consumption log

Figure 3: Doctor can recommend a particular video “prescription”

Figure 4: A mockup of a recommendation resulting from a patient’s EMR

Figure 5: “Patient” watching a video :)