USER EXPERIENCE DESIGN
Making EMT communication more efficient
There is a lot of pressure on EMTs to do their job well. Despite this expectation, the current methods for communication and information exchange are not effective. The process begins with a call from the emergency operator. The operator gives the EMT team a brief overview of the accident, with perhaps a single-line summary of how it occurred. No patient status information is given. Arrival at the scene is the first chance EMTs have to figure out what happened. They have to analyze the situation, talk to bystanders, assess patients, begin treatment, and take photos and notes about the scene. All of this information and assessment has to be accurate. They have to complete it all in ten minutes or fewer, but can’t rush. Once a patient is in the ambulance, assessment and treatment continue.
With the current system, EMTs take scene photos with a phone camera. This often leads to a negative perception from bystanders, who see the phone and don’t realize the paramedics are still doing their jobs. EMTs take notes on-scene, either with their phone or on paper. In the ambulance, EMTs have a tablet computer they can use for notes. Note-taking and documentation, however, are not as important as patient care.
While ambulances include a lot of medical equipment, such as ECG monitors, defibrillators, ventilators, and ultrasound, much of the patient assessment is still visual. It is difficult for EMTs to determine if there are internal injuries. If the patient is unconscious, medical conditions and medications may be near-impossible to identify.
This is where Medicus comes in. Medicus is a system for EMTs that streamlines triage, diagnosis, and treatment. Its infrared camera uses artificial intelligence to quickly identify potential symptoms and injuries. The included tablet puts scene pictures, ambulance notes, and multiple patients’ information in one place. Medicus enables EMTs to do their jobs faster and more efficiently.
This project was completed virtually over ten weeks. I was the UX writer and assisted with user research and testing.
What is Lean UX?
The traditional UX process begins with research. We search the internet, do interviews and surveys, evaluate the competition, and affinitize it all to look for patterns. Those patterns are used to formulate guiding questions and direct concept ideation. In a SCAD UX class, this takes up the first five weeks of the ten-week quarter. The next five weeks, following the traditional process, would be concept development and user testing.
Lean UX is different. It focuses less on research and more on rapid prototyping. We did basic research to understand our target area, developed a hypothesis and design questions to test, and prototyped our first minimum viable product (MVP). This was all done in the first three weeks of the quarter.
The rest of the quarter was focus on improving the MVP. We began with testing the basic, essential features. We spent a few days refining the MVP based on user feedback, added a little more to the MVP, and tested again. This process was repeated several times over the next few weeks. The last week or two were dedicated to polishing the completed MVP and preparing our final deliverables.
App Walkthrough – Light Mode
App Walkthrough – Dark Mode
Jasmine Attanasio: Team Lead
Isha Ray: Product Designer
Kayla Haselein: Visual Design
Madeline Walz: UX Writing