|
| 1 | +--- |
| 2 | + title: Defining appointment status labels |
| 3 | + description: Reviewing how to classify appointments so users can see and understand the status of each one. |
| 4 | + date: 2025-02-03 |
| 5 | + |
| 6 | +--- |
| 7 | + |
| 8 | +## Why status labels are needed |
| 9 | + |
| 10 | +Without actively noticing it, you probably encounter digital and physical status labels multiple times a day. |
| 11 | + |
| 12 | +While browsing Rightmove you’ll see tags such as New, Reduced, No Chain, Under Offer and Sold STC. At an airport you’ll see a departure board with flight statuses including Go to Gate, Gate Closing, Boarding, Delayed or Cancelled. |
| 13 | + |
| 14 | +Labels are used by system designers to instinctively help people quickly see if something is relevant to them and understand the possible actions they need to take. |
| 15 | + |
| 16 | +In the Manage breast screening service, we had applied a selection of appointment statuses in the prototype: |
| 17 | + |
| 18 | +- Scheduled |
| 19 | +- Checked in |
| 20 | +- Attended |
| 21 | +- Attended not screened |
| 22 | +- Did not attend |
| 23 | + |
| 24 | +These tags appear on a clinic list, on the first page of the appointment workflow, and in a participant’s screening history. They may also be provided in future iterations as filters allowing users to refine the list of visible appointments. |
| 25 | + |
| 26 | +They tested relatively well in initial user research sessions. However, further content design work was required to ensure that: |
| 27 | + |
| 28 | +- each tag covers an absolute scenario (as each appointment can have only one status) |
| 29 | +- user actions can trigger the appropriate status changes |
| 30 | +- there is a logical linguistic flow between them |
| 31 | +- the colours used for each label make sense |
| 32 | + |
| 33 | +## Working through the scenarios |
| 34 | + |
| 35 | +There were a lot of potential outcomes not covered in our initial tags. |
| 36 | + |
| 37 | +For each status, we outlined the situation for when it would be seen, then wrote some words or phrases to be considered. There are no specific character restrictions for labels in the prototype but keeping them succinct was a primary consideration. |
| 38 | + |
| 39 | +The preferred options for each scenario are marked in bold below. |
| 40 | + |
| 41 | +### Scenario – participant invited to an appointment, but they’ve not confirmed |
| 42 | + |
| 43 | +- **Invited** |
| 44 | +- Invite sent |
| 45 | + |
| 46 | +A straightforward status that we can label clearly and concisely. |
| 47 | + |
| 48 | +### Scenario – participant indicated they will attend but has not yet arrived |
| 49 | + |
| 50 | +They may also have physically arrived but not yet been checked in. |
| 51 | + |
| 52 | +- **Confirmed** |
| 53 | +- Scheduled |
| 54 | +- Due |
| 55 | +- Booked |
| 56 | +- Invite accepted |
| 57 | +- Expected |
| 58 | + |
| 59 | +Users have indicated it’s useful to know if participants are likely to show up. We’ve included the ‘Invited’ and ‘Confirmed’ statuses, but this will rely on technical work within the appointment scheduling service to allow this data to be passed through effectively. |
| 60 | + |
| 61 | +While this functionality is explored further, ‘Scheduled’ will be used as a suitable backup to cover both scenarios. |
| 62 | + |
| 63 | +### Scenario – participant has arrived at the clinic |
| 64 | + |
| 65 | +Confirmation of this could be through a self-service kiosk, or they could be checked in by one of the clinic team. |
| 66 | + |
| 67 | +- **Checked in** |
| 68 | +- Arrived |
| 69 | +- Ready |
| 70 | +- Ready for radiographer |
| 71 | + |
| 72 | +This was deemed the clearest way to indicate the participant’s physical presence is confirmed. |
| 73 | + |
| 74 | +### Scenario - mammographer has successfully taken the required images |
| 75 | + |
| 76 | +- **Screened** |
| 77 | +- Fully screened |
| 78 | +- Attended |
| 79 | +- Completed |
| 80 | +- Imaging completed |
| 81 | +- Finished |
| 82 | + |
| 83 | +We went with the most succinct option that could not be confused with another scenario. |
| 84 | + |
| 85 | +The ‘Completed’ status was a strong option, although it could be applied to various situations (an appointment where the participant does not get screened is theoretially ‘complete’). |
| 86 | + |
| 87 | +### Scenario - mammographer began taking images but could not complete the process |
| 88 | + |
| 89 | +This could be for a technical reason, because the participant asked them to stop, or for several other reasons. |
| 90 | + |
| 91 | +- **Partially screened** |
| 92 | +- Partial screening |
| 93 | +- Incomplete |
| 94 | +- Screening incomplete |
| 95 | + |
| 96 | +While the first two options are both accurate, we selected one to match the past-tense verb style used in other labels. The others are correct but could feasibly be applied to other appointment scenarios (such as a participant withdrawing consent before screening starts). |
| 97 | + |
| 98 | +### Scenario - participant attended their appointment but screening did not begin |
| 99 | + |
| 100 | +This could be because they failed their ID check, because they withdrew consent, or for several other reasons. |
| 101 | + |
| 102 | +- **Attended not screened** |
| 103 | +- No screening performed |
| 104 | +- Not screened |
| 105 | + |
| 106 | +At 21 characters this is a bit lengthy for a label but is the most effective way of getting across the necessary information. It’s also the label used in the current service, so it’s something users will recognise and understand. |
| 107 | + |
| 108 | +### Scenario - participant did not turn up and did not contact the clinic |
| 109 | + |
| 110 | +- **Did not attend** |
| 111 | +- Missed appointment |
| 112 | +- Appointment missed |
| 113 | +- Absent |
| 114 | +- No show |
| 115 | + |
| 116 | +‘Did not attend’ (or DNA) is a commonly used term across the NHS so is the obvious choice. |
| 117 | + |
| 118 | +### Scenario - appointment is not going ahead |
| 119 | + |
| 120 | +This is either because the clinic has determined that it can’t run (maybe due to staff illness or a technical reason), or because the participant has informed the clinic that they can’t make it. |
| 121 | + |
| 122 | +- **Cancelled** |
| 123 | +- Cancelled by participant |
| 124 | +- Cancelled by clinic |
| 125 | +- Postponed |
| 126 | +- To be rescheduled |
| 127 | + |
| 128 | +For the purposes of where this status will be seen, a simple ‘Cancelled’ message will suffice. Users do not need to see by whom or what needs to be done next. |
| 129 | + |
| 130 | +## The final selection |
| 131 | + |
| 132 | +- Invited |
| 133 | +- Confirmed |
| 134 | +- Checked in |
| 135 | +- Screened |
| 136 | +- Partially screened |
| 137 | +- Attended not screened |
| 138 | +- Did not attend |
| 139 | +- Cancelled |
| 140 | + |
| 141 | +### Using colour |
| 142 | + |
| 143 | +To prevent visual styles from swaying user feedback on the words used for each status, we’re planning to test labels using neutral colours. |
| 144 | + |
| 145 | +The following options have been identified from the [colours that can be applied to tags](https://service-manual.nhs.uk/design-system/components/tag#additional-colours) from NHS design system which have been added to the prototype. |
| 146 | + |
| 147 | + |
| 148 | + |
| 149 | +We are proposing an ‘active’ blue for the checked in status as it stands out among the other statuses. In a live clinic environment, these are the most important participants for staff to be aware of. |
| 150 | + |
| 151 | +The ‘Special appointment’ tag is sometimes applied when the participant has needs that require additional support from radiographers (such as a physical impairment). |
| 152 | + |
| 153 | +As this is not part of the appointment status flow, it was not included as part of this review and will be considered separately. We do need to consider it within the colour selection though to ensure it does not conflict or overlap with anything being used elsewhere. |
| 154 | + |
| 155 | +## Evolving the status quo |
| 156 | + |
| 157 | +These labels are being actively tested in research. |
| 158 | + |
| 159 | +To help the next stage of development we are looking to understand: |
| 160 | + |
| 161 | +- Is there any difference in behaviour or understanding between admin teams and radiologists regarding status labels? |
| 162 | +- Do users need to actively filter by appointment status? If so, why? |
| 163 | +- What are the other scenarios that we’ve yet to consider or encounter? |
| 164 | +- How this flows into the next stage in the process – other statuses such as ‘Reviewed’, ‘Checked’, ‘Cleared’ or ‘Recalled’ may be required once images have been looked at by a radiographer. |
| 165 | + |
| 166 | +There are also plans to test some of the alternative options through a survey so we can check our preferences against those of our users. This will likely be done alongside other questions on the prototype that require quantitative feedback. |
0 commit comments