You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: app/manage-your-appointments/2025/10/pharmacy-visits-what-we-learnt-part-1/index.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,18 +7,16 @@ We recently visited 10 pharmacies in London to see how they were using MYA just
7
7
8
8
We did this research for two main reasons:
9
9
10
-
## 1. To help us better understand the feedback we were receiving
10
+
###1. To help us better understand the feedback we were receiving
11
11
We’ve been getting lots of feedback through our feedback survey, in the Q&A during training webinars and via the service desk. This feedback is great for learning what users want and where they’re running into problems, but it’s usually it’s missing the detail required to fully understanding the underlying need.
12
12
13
-
## 2. To hear from users unlikely to take part in remote research
13
+
###2. To hear from users unlikely to take part in remote research
14
14
Up to this point, most of the research on MYA has been remote. This means the sample has skewed towards the kind of users who can easily join a pre-scheduled Teams call. As a result, we’ve heard from lots of back office staff for large pharmacy chains, and people in admin roles for Trusts and PCNs. But, we haven’t heard from as many pharmacists or dispensers as we should have, especially given pharmacies account for roughly 95% of MYA’s users.
15
15
16
-
# What we learnt
17
-
18
16
## Different approaches to running seasonal vaccinations
19
17
This research helped us get a clearer picture of how pharmacies run their seasonal vaccination services and how, in turn, they set up appointment availability in MYA. Broadly, the pharmacies I visited took one of two approaches.
20
18
21
-
## A flexible approach
19
+
###A flexible approach
22
20
The most common approach pharmacies took was to allow bookings at any time and set up their appointment availability to mirror their opening hours. That meant going into MYA, creating a weekly repeating session for Monday – Friday, adding all the vaccination services they offer, and then setting the start and finish times to match opening hours. More often than not the start and ed dates for this covered the whole campaign.
23
21
24
22
[image of typical availability]
@@ -27,7 +25,7 @@ Pharmacies taking this approach typically had lower demand for both seasonal vac
27
25
28
26
This also meant they had a relaxed attitude to walk-ins and patients ringing to book an appointment, which they would often just note down in a paper diary. As one pharmacist put it “it’s not go manage your appointments, it’s go with the flow”.
29
27
30
-
## Less room for manoeuvre
28
+
###Less room for manoeuvre
31
29
At the other end of the spectrum there was a smaller group of pharmacies who found it more difficult to juggle seasonal vaccinations alongside everything else. These pharmacies typically had a single pharmacist on site, coupled with high demand for other services, like dispensing. This meant they were more worried about falling behind, or becoming overwhelmed, and they were trying to set up MYA in a way that kept things manageable.
32
30
33
31
Across these sites I saw 3 approaches to this:
@@ -40,15 +38,15 @@ These approaches worked okay, but still felt like ‘workarounds’ with trade-o
40
38
## Assumptions challenged
41
39
In addition to helping us understand how pharmacies run their services, this research challenged a few unspoken assumptions I think we’d been making.
42
40
43
-
### Assumption 1: Professionals are more confident with technology
41
+
### 1. Professionals are more confident with technology
44
42
We assumed that because our users are professionals, with higher level qualifications, they’ll be “tech savvy” and comfortable with more technical language than we might include in a public facing service. In reality, that wasn’t the case. In general, as long as the task was straightforward they were okay, but when things got a little more tricky it caused problems. For example, many pharmacies really struggled to track down the service welcome email using by searching their inbox.
45
43
46
-
### Assumption 2: They'll read guidance or attend training first
44
+
### 2. They'll read guidance or attend training first
47
45
We’d assumed staff would attend training or read guidance before using the service. We also thought they’d approach creating availability carefully and methodically, with a mindset more like doing a tax return, than doing online shopping.
48
46
49
47
In reality pharmacy staff simply don’t have the time for guidance or training beforehand, or to carefully double check everything. Plus, finding time without distractions to do an admin task like this is hard. That means when they get to it, the mindset is to get their appointment availability set up quickly before they get interrupted.
50
48
51
-
### Assumption 3: Pharmacies run services to the minute
49
+
### 3. Pharmacies run services to the minute
52
50
We assumed pharmacies deliver most vaccinations at pre-booked time slots, sticking closely to scheduled appointments. At the pharmacies we visited in this research, we found walk-ins were equally, if not more common. My impression was that pharmacies are less concerned with strict timings and more focused on providing a good service overall. If someone turns up early, they may be seen early; if they’re late, it’s usually not a problem.
53
51
54
52
When you take a step back, none of this is especially surprising. But, without regular research with end users, it’s easy to slip back into self-referential design.
0 commit comments