Skip to content

Commit 3e1f1fb

Browse files
authored
Cohort Manager search feature (#317)
1 parent 235ab7e commit 3e1f1fb

File tree

4 files changed

+80
-0
lines changed

4 files changed

+80
-0
lines changed
56.5 KB
Loading
Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
---
2+
title: Designing a search feature for Cohort Manager
3+
description: Adding a search feature so that users can quickly find all data exceptions and reports linked to a particular NHS number
4+
date: 2025-12-16
5+
author: Arpana Ghagre
6+
tags:
7+
- beta
8+
- live
9+
- breast screening
10+
---
11+
## Introduction
12+
13+
Cohort Manager is a product designed to improve data quality in screening programmes by identifying, correcting, and managing demographic details, so the right people are selected for invitation. When records enter the screening pathway, ‘validation rules’ detect issues such as missing or incorrectly formatted information. These are flagged as data exceptions: some are resolved automatically, while others require manual intervention through the user interface (UI), where they can be “raised” with the right teams for resolution.
14+
15+
We recently updated Cohort Manager’s UI to include a search feature so that users can quickly find all data exceptions and reports linked to a particular NHS number.
16+
17+
This addition builds on the foundations introduced in [our earlier post](/select/), which explained how the UI surfaces exceptions in participant data for resolution. The search feature was requested by a new user group with a slightly different need, and this post will explore how it was designed to meet that requirement.
18+
19+
### Cohort Manager user groups
20+
21+
Cohort Manager now serves three main user groups:
22+
- **National Service Desk (NSD)**: Pick up data exceptions and raise them with the National Back Office (NBO), Cohorting as a Service (CaaS), and Breast Screening (BS) Select teams to be resolved.
23+
- **BS Select Second Line Support Team**: Investigate complex participant data issues, such as possible confused or duplicate participant records. They require full historical visibility of reports and exceptions to track changes and resolve cases.
24+
- **Service Management Team (SMT)**: Handle customer queries from Breast Screening Offices (BSOs) and support incident investigation and reporting.
25+
26+
## Why the search is needed (the problem)
27+
28+
The initial request for the search feature came from the Service Management Team (SMT). SMT users often need to resolve complex issues linked to a participant's record. This involves looking into the detailed history of issues to spot recurring activity and work out exactly what the problem is. 
29+
30+
Cohort Manager's user interface wasn't designed with this use case in mind. It only displays current data exceptions and can't sort exceptions by NHS number. This forces SMT users to manually navigate through multiple records, slowing down investigations, increasing the risk of duplication, and making it harder to align information across systems like ServiceNow. 
31+
32+
## The solution
33+
34+
We introduced a search bar in the Cohort Manager UI header that is accessible from any screen. The search feature was designed to meet these needs through simplicity and inclusivity. This global approach supports all three user groups, whilst ensuring that the feature is scalable and maintainable as the system develops. 
35+
36+
![Screenshot from the Cohort Manager. It contains a search box in the header](global-search.png "A view of Cohort Manager's interface showing where the search box is located (in the header)")
37+
38+
## Search by NHS number only
39+
40+
SMT users confirmed they would need to search by NHS number alone, so we limited the search criteria to this. As a unique identifier for a participant, this helps limit results and enables accurate searches with direct matches.
41+
42+
## Displaying historic information 
43+
44+
Crucially for SMT users, search results include historic exceptions and reports, not just current activity. This gives users the full history they need to investigate issues effectively. 
45+
46+
## How results are presented
47+
48+
Search results appear in a table showing the most recent items first for faster triage. The table includes key details to aid investigation: demographics, exception details such as **local reference, exception status** and **brief description**, **ServiceNow case IDs**, and **report types**. Users can click on individual results to view full details of exceptions or reports.
49+
50+
![Screenshot from the Cohort Manager. Showing how the search results are shown for exceptions and the reports](search-results.png "A view of Cohort Manager's interface showing the search results for exceptions and reports")
51+
52+
## Search error scenarios
53+
54+
When using the search feature, we considered the following common error cases:
55+
- **empty input**: the search box is left blank
56+
- **invalid format**: the NHS number entered does not match the required format
57+
58+
For all these scenarios, the system shows the ‘No results’ page :
59+
60+
![Screenshot from the Cohort Manager. Showing no results for empty inpout and/or invalid format](no-result.png "A view of Cohort Manager's interface showing no results")
61+
62+
## Challenges building the ‘no results’ page
63+
64+
This page was built without a ready‑made NHS design component. To replicate the look and feel, the HTML and CSS code had to be copied directly from the Chrome Developer Tool.
65+
66+
This highlights a gap: NHS should provide a dedicated design component for search and related pages. Having a reusable component would make development faster, ensure consistency across services, and reduce reliance on manual workarounds.
67+
68+
## How it tested
69+
70+
Prototype testing confirmed that the search met user expectations in terms of:
71+
- **the ability to view full details of each result**
72+
Testing confirmed that users could click into search results and see the complete information behind each exception or report. This was important because investigations often require more than just a summary — users need access to the full demographic details, exception history, and linked ServiceNow case IDs to understand the context and resolve issues accurately.
73+
- **clarity of information presented**
74+
The prototype was checked to ensure that the search results table displayed information in a clear, structured way. Key fields such as NHS number, demographics, exception status, and report type were easy to read and logically organised. This clarity reduced confusion, helped users quickly identify the right record, and avoided mistakes during investigations.
75+
- **alignment with real-world workflows**
76+
The search feature was tested against actual scenarios faced by Service Management Team (SMT) and other user groups. For example, SMT users often need to trace the history of a participant’s record across multiple exceptions and reports. Testing showed that the search results supported this workflow by presenting historic data in newest‑to‑oldest order, making triage faster and investigations more consistent with how teams work in practice.
77+
78+
## Our future expectation
79+
80+
We hope the search feature will continue to make investigations faster and easier, giving users greater confidence when resolving participant data issues and simplifying workflows across ServiceNow and Cohort Manager.
216 KB
Loading
268 KB
Loading

0 commit comments

Comments
 (0)