Medication Administration Program

A concept project to explore a digital solution for the MAP protocol.

0 - Project Overview

Map and Me

One of my most rewarding jobs was working in a group home for older adults who had special needs. Every night and morning, one of the staffers would administer medication to the four clients.

In order to do this, we had to get MAP-certified and follow an exact protocol every time we administered meds. This protocol would ensure patient-safety and client dignity.

When I had the opportunity to tackle a project for my General Assembly pre-work, I remembered my time passing meds and opted to create a digital solution for MAP.

Problem Statement

MAP is time-consuming and subject to human error. The documentation is currently done through pen and paper.

Solution Statement

I designed a MAP-compliant mobile app for direct care staffers to use when administering medication.

1 - Research

Reviewing MAP

I started my project by reviewing the MAP protocol. My first task was to see if there was a digital solution already out there. Once I determined that there was no existing digital solution, I reviewed the MAP guidelines and regulations.

The best research tool for me was this demonstration video of a med pass.

User Research

After reviewing MAP, I interviewed two current MAP users. I asked them about their experiences with MAP and what they would like to see in a digital version. I then took their feedback and created an affinity map.

The affinity map.

Feature Prioritization

After reviewing the user feedback, I thought about what features might address their concerns. I then created a feature prioritization matrix to figure out my priorities.

Based on my user research and the subsequent analysis, I decided to focus on three primary issues:
1. security and patient safety
2. users getting distracted during the med pass
3. ease of use for a wide range of staffers

The feature prioritization matrix.

2 - Sketching

Translating MAP into an App

Since MAP is a protocol, I was trying to very literally interpret those steps into digital ones. But within those screens, I was also trying to address the aforementioned user concers.

Here's how I thought about and interpreted the primary three concerns.

1. Security

When I initially thought about app security, I had a few rules.
1. Keep things easy. No complicated passwords, no hard to type symbols.
2. Any secondary code must be easy to receive and be read on any device.
3. Each session must require a new passcode.

In order to address this, I added a two-factor authentication solution. The user selects her name and she receives a 5-digit number code on her phone. She enters it in and she's ready to start the med pass.

A friendly two-factor authentication screen.

2. Keep Users Engaged

To keep users engaged, I created multiple ways of answering the same question. I would keep the number of patterns low, so that users can be comfortable with what they're doing but not overly automated.

Here the user taps to select the right answers. It's familiar and forgiving.
Instead of repeating the first pattern, the next check uses a drag and drop activity.

3. Keeping the Client First

One of the most important aspects of MAP is that it keeps the client front-and-center. Not only does this reduce potential errors, but it helps to preserve the client's dignity.

In order to do this, I put the client face and name on the screen in front of the user. I wanted users to remember not only who they were passing meds to, but why it was so important they pay attention.

For certain screens, the user are not allowed this "hint", which is why the user name and image is not on the screens for the main checks.

Staffers must select a client before doing anything else.
With a high staff turnover rate, images can help reinforce client dignity.
The client's image and name stays in the corner, with the exception of the check screens.

3 - The Prototype

Skipping Ahead

As this was a one week project focused on decision-making, I went from sketching to high-fidelity wire frames using Sketch. I then turned these wireframes into a prototype using InVision.

I recently went back and cleaned up the screens a bit, but this is it.

4 - Next Steps

User Research

First, I would employ more user research . For example, I was very guided by my own experience in this process. In the future, I'd want to explore other situations in which MAP is used. For example, what about day programs where dozens of clients might be receiving medication? Also, how would the MAP App handle liquid medication? Injections?

User Testing

After more user research and more iterations, I could begin proper user testing. I would probably go back to a paper prototype and start putting it in front of users. Then I could iterate just on sketches, until I felt I could move onto wireframes.

Talk to Stakeholders

And of course for a project like this, I would have to work with the stakeholders - aka the Massachusetts departments of Mental Health, Children and Family Services, and Developmental Services. So there would be a substantial amount of work before further pursuing this on a professional level. Still, I enjoyed getting to explore this issue in an academic setting and hopefully I'll be able to work on it at a higher level further down the road.