-
Notifications
You must be signed in to change notification settings - Fork 8
adds changes to plan post #336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mattlucht
wants to merge
9
commits into
NHSDigital:main
Choose a base branch
from
mattlucht:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+57
−0
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
e4c60f2
adds changes to plan post
mattlucht 68eac8c
Update app/screening-invite/2025/12/changes-to-the-digital-first-brea…
mattlucht ea1539f
Update app/screening-invite/2025/12/changes-to-the-digital-first-brea…
mattlucht a492200
resolves comments
mattlucht 7cdc51c
Fix header formatting
mattlucht 9b2651b
fixes punctuation
mattlucht 678cb5b
fixes url
mattlucht b7de19e
Revise digital breast screening communication plans
mattlucht 5e96cca
Add files via upload
mattlucht File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
57 changes: 57 additions & 0 deletions
57
...5/12/changes-to-the-digital-first-breast-screening-communication-plans/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,57 @@ | ||
| --- | ||
| title: Changes to the digital-first breast screening communications plan | ||
| description: This post outlines the changes to our plans for digital-first communications for breast screening | ||
| date: 2025-12-22 | ||
| author: Mari Wightman | ||
| tags: | ||
| - private beta | ||
| - screening | ||
| --- | ||
|
|
||
| The focus for [Team Invite](/screening-invite/) until recently was on rolling out digital communications in the routine breast screening pathway, using NHS Notify. We were in the private beta phase, working with a handful of breast screening offices (BSO) on how we could deliver invitations for the initial screening appointment. We were doing this by ingesting appointment data from National Breast Screening System (NBSS), via a MESH inbox, into the Manage Breast Screening component. However because we weren’t fully integrating with NBSS, we learnt that the level of service we could provide BSOs at this stage was limited, wouldn't fully meet their needs, and would be difficult to scale beyond a handful of BSOs. | ||
|
|
||
| Rather than trying to force a digital communication service alongside the legacy system, we have made the decision to pause the work on delivering digital comms in breast screening until it can be done in the right way, alongside the new end-to-end digital service replacing NBSS. Although it was a difficult decision to make because of the hard work that has gone into it so far, it is the right one given the renewed focus on replacing legacy breast screening systems, rather than further deepening our reliance on them. | ||
|
|
||
| Here is what we would have done next after delivering invitations in private beta. A summary of the private beta user research activities [can be found in this post](/screening-invite/2025/12/invite-breast-screening-private-beta-user-research/). We hope these will help future teams looking at participant engagement in breast screening understand some of the challenges and complexities. | ||
|
|
||
|  | ||
|
|
||
| ## Communication types | ||
|
|
||
| There were some obvious next steps that we would have looked to tackle had we continued with the roll-out. Launching with only invitations for the initial screening appointment meant that there were communications relating to the appointment phase of the participant journey that would not be delivered in a consistent way. | ||
|
|
||
| ### Reminders | ||
|
|
||
| Text reminders are already prevalent in the service, with the majority of BSOs sending a couple of reminders ahead of the appointment, but at a variety of time intervals. Had we continued, we would have done a short piece of research to understand the most effective timing for reminders, and tested our assumptions that sending only digital reminders was appropriate. | ||
|
|
||
| ### Non-attenders of first appointment | ||
|
|
||
| Participants who don’t attend their first appointment are sent a follow-up appointment invitation. The majority of BSOs send timed appointments as instructed in the service specification. While we were looking at delivering comms to support the current service on NBSS, our initial plan had been to take a similar approach to what’s done today and send a second timed appointment digitally. Now that comms will be delivered alongside the new service, it would be worth looking into what the reasons are for people not attending the first appointment, and whether there is a more effective way of boosting uptake with non-attenders. | ||
|
|
||
| ### Rescheduled appointments | ||
|
|
||
| A challenge we had while integrating with NBSS was that we couldn’t easily or accurately identify when an appointment that we were receiving was newly booked or rescheduled, and if the latter, whether it was driven by the participant or the BSO. From research in private beta we found out that these distinctions are important: firstly in terms of it being clear which was the relevant appointment time, given the participant may have received multiple invitations. Secondly, the context within the message of who had rescheduled the appointment and why was important, especially if it was BSO-led due to issues such as staff shortages. For teams looking at these scenarios in the new service, it would be worth exploring how this can be better supported, so the messaging is clear, and participants know exactly which timing is relevant after rescheduling. | ||
|
|
||
| ### Results | ||
|
|
||
| A significant part of the participant journey that we hadn’t delved into in depth was how results should be communicated. Other screening programmes have led the way in understanding the most appropriate channels for communicating both normal and abnormal results. However this would need to be looked at specifically in the context of breast screening, given the sensitivity of the messages and different service context and demographic group. Equally, learning from how we approached private beta, time should be spent on understanding the current process of how BSOs process and send out the results, so that it can inform the solution in the new service. For example, how much can or should the sending of results be automated? Do BSOs want a level of control over when results are sent so it can be coordinated with other activities they carry out? | ||
|
|
||
| ## Beyond specific comms types | ||
|
|
||
| Working with BSOs highlighted some areas that we were not specifically looking at for private beta that we would need to consider for wider roll-out, that spanned the participant experience rather than being specific to a comms type. For example how we could support underserved communities and what information would be useful to capture from a participant before an appointment. | ||
|
|
||
| ### Participant actions driven from comms | ||
|
|
||
| Much of the excitement we were getting from BSOs when talking about digital comms wasn’t necessarily about the comms themselves, but the participant actions that could be driven from them that could help BSOs. Some ideas we wanted to explore were: | ||
|
|
||
| * participants being able to confirm if they were attending an appointment or not | ||
| * collecting personal information about a participant ahead of the appointment | ||
| * whether they had potential for improving clinic management and appointment outcomes. | ||
|
|
||
| ### Supporting underserved communities | ||
|
|
||
| Specifically, if we should be providing comms in alternative languages and formats. We found that there isn’t currently a consistent approach to how these groups are supported nationally in breast screening, and while integrating with NBSS, we would struggle to get the information about participant’s needs to drive engagement more tailored to their needs. Research was done to understand the landscape and potential options, but no conclusion was reached on which approach should be taken. Going forwards, this should be thought of at a pathway level, rather than specifically just on how it’s managed through comms, as arguably the approach should be consistent across all participant touchpoints. It’s also worth considering which data informing participants’ needs should be used given there are currently inconsistencies between locally held information (in NBSS) and centralised data (in PDS). | ||
|
|
||
| ### Working with BSOs | ||
|
|
||
| A significant area of focus beyond Private Beta would have been the change management aspects of how we onboard a large number of BSOs, all with slightly different operational processes, internal governance and supplier arrangements. In Private Beta we were hoping to work with 4-5 BSOs that varied in these ways, to understand what support they needed, so that we could develop an onboarding process that would require as little direct input from the Digital Screening team as possible, given the ambitious product roadmap we wanted to focus on. |
Binary file added
BIN
+189 KB
...ital-first-breast-screening-communication-plans/sms-breast-screening-invite.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like there may be a space within this path?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing the parent folder name includes a space when it shouldn't.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, the page renders at https://dsps-design-main-gcmurwfiskrgd.herokuapp.com/screening-invite/2025/12/changes-to-the-digital-first-breast-screening-communication-plans%20/ - a space at the end!