GR2 - Design Document
Table of Contents
Scenario
- Mr. Z, a 55 year old male, is at work in Building 66 when he notices a sudden pain in his chest and left arm.
- He calls 911 and waits in his office until the local paramedics arrive.
- When the paramedics arrive, they record:
- his name,
- age,
- ECG,
- and medical history.
- The paramedics bring Mr. Z to the hospital at fast as they can and deliver him to the local triage nurse, to whom they transfer the patient information and the electrocardiogram (ECG) results.
- The nurses perform an ECG of their own on Mr. Z.
- The nurses determine that he is having a heart attack.
- The nurses quickly ask for a few details about:
- the history of the pain,
- the symptoms,
- any allergies they should be aware of.
- They note down only the most important things, like allergies or current treatments that might interfere with treatment.
- They will record the other information on his medical history once they have the time.
- As Mr. Z is was not allergic to aspirin; the nurses quickly administer a dose,.
- The Doctor reads the nurses notes and sends Mr. Z into the coronarography room to have a balloon catheter inserted into his blocked artery (percutaneous coronary intervention, aka angioplasty).
- The Doctor prescribes Heparin to prevent blood clotting.
- Over the next few days after the angioplasty Mr. Z. is also monitored, but less closely.
- The nurses come by to:
- dispense medications,
- note his medical status,
- take samples ordered by the doctors,
- record ECG data to assess his heart function,
- monitor blood pressure,
- and perform blood tests to check for infection.
- The nurses note other kinds of information important to taking care of the patient
- E.g. his shellfish allergy.
- Two different doctors stop by visit Mr. Z everyday day:
- one in the morning,
- and one at the end of the afternoon.
- The doctors read through any pertinent notes left by the other doctor, and the nurses.
- The doctors then examine the patient and make adjustments to the orders.
- At the end of the stay (typically a few days for a heart attack), a doctor reviews Mr. Z's information to ensure that no other problems are present.
- The Doctor decides that Mr. Z is well enough to leave the ICU.
- When Mr. Z leaves, the doctor reviews the medications prescribed and procedures performed by the hospital to send an accurate bill to his insurance provider.
Design Sketches
Click any of the images to enlarge, or open the image independently for a full-size view.
Design Sketches by Mohammad Ghassemi
Design 1:
Sketch |
Description |
---|---|
|
This design utilizes a common two-pane display to allow for the taxonomy hierarchy structuring the data to be conveyed. By making fields editable in-place, the design promotes quick and accurate updating of patient records. The design also provides all of the information needed on a single screen, without any switching of contexts required. |
Design 2:
Sketch |
Description |
---|---|
|
This design provides different views of the application for the three main user classes. Paramedics, nurses, and doctors each have a view tailored to their needs when using the application. Data is structured intuitively and fields are editable to, again, promote quick and accurate updating of patient records. |
Extreme Design 1: Ultra-efficient
Sketch |
Description |
---|---|
|
This non-computer interface uses a tool that the users are likely already familiar with: a whiteboard. By wirelessly syncing information from a smart-board to a centralized system, nurses and doctors can interact with the application in a mode that is very familiar to them. Networked medical equipment can feed data directly into the application, and identifying pens help tie inputed data to its authoring nurse or doctor. |
Design Sketches by Franck Dernoncourt
Design 3:
Sketch |
Description |
---|---|
|
This design focuses on textual information, and information density. In order to make decisions, the medical staff need to have access very quickly to a lot of data. To avoid overwhelming the users by information, the default view presents a synopsis for every element of the patient's folder. If the medical staff need more information, they can simply click on "more details." |
Design 4:
Sketch |
Description |
---|---|
|
In opposition to the previous design, this sketch focuses on visual information. Currently, the whiteboards the medical staff are using do not allow easy display of visual information with precision. However precision can be key to detect anomalies in the patient, and thus the existing solutions are inadequate. |
Extreme Design 2: Hands-free Interface
Sketch |
Description |
---|---|
|
This last design handles a common issue with medical staff: they don't have the time to type everything and/or their hands are already busy. Using voice recognition to navigate through the application using voice commands and to input text could be extremely useful for them.
|
Design Sketches by Kamran Khan
Design 5:
Sketch |
Description |
---|---|
|
This design allows for nurses and doctors to see all of the data that they need in one screen. It provides an overview of all of the patients managed, and allows for quick diving into each of the patient's records. Important demographic and historical information about each patient is accessible in a consistently placed sidebar, and nurses and doctors can add notes and other information to each patient's record. Rich media is embedded into the interface, allowing doctors to review test results and images directly in the interface. Medicine distribution information is also clearly presented, as are real-time patient vitals and potential alerts. |
Design 6:
Sketch |
Description |
---|---|
|
This design takes a different approach, using different screens for different views of the data. The screens are split functionally, but due to the definitions of our user classes, this partitioning also matches well with our partitioning of users. The screen shown at the top left is for initializing a patient record, and is most suited for paramedics on the field. It allows for quick entry of patient data, including demographic information, field notes, and medical history. The screen at the bottom left is an overview screen which provides the status of every patient managed---this screen is targeted towards the nurse user class. Nurses can quickly see which patients need tending to (for administration of medication, etc.) and they can monitor vitals and other status metrics. Doctors may also use this screen for oversight over the ICU. The screen on the right shows the detail view of a specific patient, and will be used by both nurses and, especially, doctors. |
Extreme Design 3: Non-computer, Location-based Interface
Sketch |
Description |
---|---|
|
This "extreme" design breaks outside of the bounds of the computer and uses specialized hardware and sensors to collect data about patients, doctors, nurses, and paramedics. |
Design Sketches by Robin Deits
Design 7:
Sketch |
Description |
---|---|
|
This design is centered around fast entry of textual information and the display of relevant information to all the hospital staff. Primary information about the patient is presented at the top of the display at all times, and below that is a list of notes from hospital staff. Each note is tagged with the date and the name of the person who provided the information, and can be expanded to show additional detail. A checkbox on the right side of each note will automatically include that note's title in the central "whiteboard" display, so that doctors and nurses can easily see a record of treatments and medications for all patients. |
Design 8:
Sketch |
Description |
---|---|
|
This design is focused on consistency with the timeline metaphor. When viewing a single patient's record, each piece of information is presented along a vertical timeline. Previous interactions, drugs, etc. are presented along the left side of the timeline and orders for future treatments are presented on the right. Alternate views of the patient information maintain consistency with the timeline:
|
Extreme Design 4: Non-Computer Interface
Sketch |
Description |
---|---|
|
This design is meant to solve many of the problems presented in hospital information-tracking without requiring any form of computer interface. It consists of self-duplicating stickers with unique, easily human-readable codes to identify all the pieces of information belonging to a patient. More information about this interface is included in the Storyboard Design 2. |
Storyboard Designs
Be sure to click through to the individual pages for the storyboards below, which include diagrams and descriptions of each of the proposed designs.
Proposed Design 1
Storyboard
Analysis
Learnability: Good |
Learnability: Bad |
---|---|
|
|
Efficiency: Good |
Efficiency: Bad |
|
|
Safety: Good |
Safety: Bad |
|
|
Proposed Design 2
Storyboard
Analysis
Learnability: Good |
Learnability: Bad |
---|---|
|
|
Efficiency: Good |
Efficiency: Bad |
|
|
Safety: Good |
Safety: Bad |
|
|
Proposed Design 3
Storyboard
Analysis
Learnability: Good |
Learnability: Bad |
---|---|
|
|
Efficiency: Good |
Efficiency: Bad |
|
|
Safety: Good |
Safety: Bad |
|
|
1 Comment
Unknown User (jks@mit.edu)
Excellent job overall, exploring designs and organizing your ideas about visualizing patient information. Since you're all contending with organizing and presenting all of a patient's information, there is almost no consideration about how to efficiently input specific kinds of information (other than the voice recognition sketch and handwriting in the non-computer interface). For example, how does a doctor or nurse input medication type, dosage and timing? How do EKGs get into the system? In other cases, where the user just has to type, are there opportunities for autocomplete to increase efficiency? Narrowing your scope will allow you to focus on issues like this, which are a huge part of the usability of your system.