Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
799022f
publish GP IT post
veroje Apr 15, 2026
a08effb
add design history on GP IT
veroje Apr 15, 2026
9d56ed7
add link to decision to replace
veroje Apr 15, 2026
39f546e
Update app/breast-screening-pathway/2026/04/before-integrating-with-G…
veroje Apr 15, 2026
e1b30a2
Update app/breast-screening-pathway/2026/04/before-integrating-with-G…
veroje Apr 15, 2026
fc5c485
Update app/breast-screening-pathway/2026/04/before-integrating-with-G…
veroje Apr 15, 2026
c93214d
Update app/breast-screening-pathway/2026/04/before-integrating-with-G…
veroje Apr 15, 2026
27ab472
Update app/breast-screening-pathway/2026/04/before-integrating-with-G…
veroje Apr 15, 2026
b232e9c
Update app/breast-screening-pathway/2026/04/before-integrating-with-G…
veroje Apr 15, 2026
2e21944
Remove nhsuk-frontend from package.json and package-lock.json
veroje Apr 15, 2026
bbddd83
Revert "Remove nhsuk-frontend from package.json and package-lock.json"
veroje Apr 15, 2026
1a2d078
Remove nhsuk-frontend from package.json and package-lock.json
veroje Apr 15, 2026
b6e46c9
Revert "add design history on GP IT"
veroje Apr 15, 2026
eb20025
Merge branch 'pathway-prepare-gp-it' of https://github.com/NHSDigital…
veroje Apr 15, 2026
b5d01af
change title, change image
veroje Apr 16, 2026
441073a
add links to GP IT gateways
veroje Apr 16, 2026
9da3570
Address further feedback
veroje Apr 16, 2026
5997b31
Merge branch 'main' into pathway-prepare-gp-it
frankieroberto Apr 16, 2026
2b8dbce
Revert package-lock changes
frankieroberto Apr 16, 2026
395bfcf
iterate image
veroje Apr 16, 2026
835674f
Merge branch 'pathway-prepare-gp-it' of https://github.com/NHSDigital…
veroje Apr 16, 2026
cabb52c
Update index.md
veroje Apr 16, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1,89 @@
---
title: Before we can build an integration with GP patient records
Comment thread
veroje marked this conversation as resolved.
Outdated
description: We want to send breast screening results directly to GP patient records. Here's what we need to work through first.
date: 2026-04-16
tags:
- GP IT
- SNOMED CT
author:
- Veronika Jermolina
opengraphImage:
src: /breast-screening-pathway/2026/04/before-integrating-with-GP-IT/GP-IT-plan.png
alt: 4 steps to consider before integrating with GPs
---

Each year 3 million paper result letters are sent from breast screening offices (BSOs) to general practices (GPs) to update patient records. About a year ago we ran a discovery to [understand if we could solve this problem nationally](https://design-history.prevention-services.nhs.uk/explore-team/2025/06/insights-and-opportunities-for-sharing-breast-screening-results-with-gp-surgeries/).
Comment thread
veroje marked this conversation as resolved.
Outdated
Comment thread
veroje marked this conversation as resolved.
Outdated

The reality was more complex than we imagined.

The legacy NBSS system runs in 75 local instances - we'd need to implement a solution in every BSO. The patient record is managed by 2 dominant GP IT providers – who would need to make changes, adding a dependency on their delivery roadmaps.

So even a medium-term solution would be unpredictable, costly and time-consuming.

Our discovery exposed the limitations of NBSS and helped inform a decision to replace it with a modern breast screening service.

![4 steps to consider before integrating with GPs](GP-IT-plan.png)

## New breast screening service pilot

Almost a year since then, team [Manage breast screening](../../../../manage-breast-screening/) launched a live pilot of the first slice of the new breast service in Humberside - our pilot partners. We are months away from being able to generate results in the new breast screening service.
Comment thread
veroje marked this conversation as resolved.
Outdated

This means we are no longer held back by getting data out of NBSS and in theory, can move forward. However, before integration work can start, we need to work through some challenges.

## Decide what outcomes to record

We already know that we need to record the following outcomes, or screening results:

- normal (routine recall): participant invited again in 3 years
- did not attend: participant didn't attend and will be invited again
- technical recall: mammogram not of sufficient quality, participant invited back
- recall for assessment (abnormal result): further investigation needed

We still need to consider whether new outcomes, like [partial mammography](../../../../manage-breast-screening/2026/02/improving-the-partial-mammogram-process/), are needed and agree the full list with the delivery teams. We should also consider what action, if any, should GPs take on receiving them.
Comment thread
veroje marked this conversation as resolved.
Outdated

## Describe and sequence approval steps

As this work relies on GP IT systems, there are various approval steps and gateways that we'll need to go through. Last time we looked into this problem, some of these steps were:

- Digital services for integrated care (DSIC) front door
- Joint GP IT Liaison (JGPITL)
- Joint GP IT Committee (JGPITC)
- GP IT roadmap
Comment thread
veroje marked this conversation as resolved.
Outdated

We need to confirm if these are still the right steps and the order in which we should go through them, and if there are any dependencies.

We are speaking to other teams who we can collaborate with and learn from. One of those is the PDM (Patient data manager) team, who are simplifying integration with GP IT systems. Another is the [Health check online team](../../../../nhs-health-check-online/), who are piloting a solution with [PDM](https://digital.nhs.uk/services/patient-data-manager).
Comment thread
veroje marked this conversation as resolved.
Outdated

## Choose SNOMED CT codes

If we wanted to automate the processing of breast screening results, we'd need to tag them with machine-readable codes that GP IT systems can understand and act upon. For example:

- a normal breast screening result can be automatically filed to the patient record
- an abnormal result can be flagged to GPs, who can decide what action to take - such as offering the person support while they go through the assessment
Comment thread
veroje marked this conversation as resolved.
Outdated

There are already SNOMED CT (Systematised Nomenclature of Medicine - Clinical Terms) codes to denote breast screening outcomes, the most used codes being:
Comment thread
veroje marked this conversation as resolved.
Outdated

- Mammography normal (finding) [`168749009`](https://termbrowser.nhs.uk/?perspective=full&conceptId1=168749009&edition=uk-edition&release=v20260311&server=https://termbrowser.nhs.uk/sct-browser-api/snomed&langRefset=999001261000000100,999000691000001104)
- Breast neoplasm screening normal (finding) [`171175005`](https://termbrowser.nhs.uk/?perspective=full&conceptId1=171175005&edition=uk-edition&release=v20260311&server=https://termbrowser.nhs.uk/sct-browser-api/snomed&langRefset=999001261000000100,999000691000001104)

We also know that other programmes, like [Bowel cancer screening](../../../../bowel-screening/), clearly signal through their codes that these are results of a national screening programme:

- Bowel cancer screening programme faecal occult blood test normal (finding) [`375211000000108`](https://termbrowser.nhs.uk/?perspective=full&conceptId1=375211000000108&edition=uk-edition&release=v20260311&server=https://termbrowser.nhs.uk/sct-browser-api/snomed&langRefset=999001261000000100,999000691000001104)

And that the results come from a test (now replaced by a FIT test):

- Bowel cancer screening programme: faecal occult blood result (observable entity) [`368481000000103`](https://termbrowser.nhs.uk/?perspective=full&conceptId1=368481000000103&edition=uk-edition&release=v20260311&server=https://termbrowser.nhs.uk/sct-browser-api/snomed&langRefset=999001261000000100,999000691000001104)

We may decide to use one of the existing SNOMED CT codes or apply for new ones. Applying for new SNOMED CT codes depends on deciding what results we will need to record.

New SNOMED CT codes are released twice a year – in April and October and can take several months to approve.

## Understand policy implications

Importantly, we need to understand the legal basis for processing and exchanging this data and consider whether these changes will have any policy implications. If they do, we need to allow time to build the necessary consensus.

## Conclusion

Each of these 4 steps is complex and dependent on others. Our choices will be driven by getting a solution to a small number of BSO partners and GP administrators as safely and as quickly as possible, so we can start learning from their feedback.

We will share an update on each of the 4 challenge areas as we progress.
23 changes: 6 additions & 17 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

3 changes: 2 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,8 @@
"dependencies": {
"@11ty/eleventy": "^3.1.5",
"@x-govuk/nhsuk-eleventy-plugin": "^1.2.0",
"http-server": "^14.1.1"
"http-server": "^14.1.1",
"nhsuk-frontend": "^10.4.2"
Comment thread
frankieroberto marked this conversation as resolved.
Outdated
},
"devDependencies": {
"@x-govuk/eslint-config": "^0.0.2",
Expand Down
Loading