|
| 1 | +--- |
| 2 | +title: 4 things to do before integrating breast screening with GP records |
| 3 | +description: We want to send breast screening results directly to GP patient records. Here's what we need to work through first. |
| 4 | +date: 2026-04-16 |
| 5 | +tags: |
| 6 | + - GP IT |
| 7 | + - SNOMED CT |
| 8 | +author: |
| 9 | + - Veronika Jermolina |
| 10 | +opengraphImage: |
| 11 | + src: /breast-screening-pathway/2026/04/before-integrating-with-GP-IT/GP-IT-plan.png |
| 12 | + alt: 4 steps to consider before integrating with GPs |
| 13 | +--- |
| 14 | + |
| 15 | +3 million paper result letters are sent by breast screening offices (BSOs) to GPs every year. 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/). Our task was to determine what it would take to automatically write breast screening results to the patient record, replacing paper with fast, modern, secure digital data transfer. |
| 16 | + |
| 17 | +The reality was more complex than we imagined. |
| 18 | + |
| 19 | +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. |
| 20 | + |
| 21 | +So even a medium-term solution would be unpredictable, costly and time-consuming. |
| 22 | + |
| 23 | +Our discovery exposed the limitations of NBSS and helped inform a [decision to replace](../../../../manage-breast-screening/2025/07/the-future-of-nbss/) it with a modern breast screening service. |
| 24 | + |
| 25 | + |
| 26 | + |
| 27 | +## New breast screening service pilot |
| 28 | + |
| 29 | +Since the discovery, team [Manage breast screening](../../../../manage-breast-screening/) have 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. |
| 30 | + |
| 31 | +This means we are no longer held back by getting data out of NBSS. We can move forward but some challenges remain. |
| 32 | + |
| 33 | +## Decide what outcomes to record and how to act on them |
| 34 | + |
| 35 | +We already know that we need to record the following outcomes, or screening results: |
| 36 | + |
| 37 | +- normal (routine recall): participant invited again in 3 years |
| 38 | +- did not attend: participant didn't attend and will be invited again |
| 39 | +- technical recall: mammogram not of sufficient quality, participant invited back |
| 40 | +- recall for assessment (abnormal result): further investigation needed |
| 41 | + |
| 42 | +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 when receiving the information. |
| 43 | + |
| 44 | +## Choose SNOMED CT codes |
| 45 | + |
| 46 | +To help GP systems decide how to process breast screening results, we'd need to tag them with machine-readable codes that GP IT systems can understand and act upon. For example: |
| 47 | + |
| 48 | +- a normal breast screening result can be automatically filed to the patient record |
| 49 | +- 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 |
| 50 | + |
| 51 | +There are already [SNOMED CT](https://digital.nhs.uk/services/terminology-and-classifications/snomed-ct) (Systematised Nomenclature of Medicine - Clinical Terms) codes to denote breast screening outcomes, the most used codes being: |
| 52 | + |
| 53 | +- 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) |
| 54 | +- 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) |
| 55 | + |
| 56 | +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: |
| 57 | + |
| 58 | +- 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) |
| 59 | + |
| 60 | +And that the results come from a test (now replaced by a FIT test): |
| 61 | + |
| 62 | +- 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) |
| 63 | + |
| 64 | +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. |
| 65 | + |
| 66 | +New SNOMED CT codes are [released twice a year](https://www.england.nhs.uk/long-read/clinical-coding-snomed-ct/#:~:text=The%20UK%20version%20of%20SNOMED,or%20more%20frequently%20when%20needed.), or more frequently when needed, and can take several months to approve. |
| 67 | + |
| 68 | +## Describe and sequence approval steps |
| 69 | + |
| 70 | +As this work relies on GP IT systems, there are various approval steps and gateways that we'll need to go through. When we last looked into this problem, some of these steps were: |
| 71 | + |
| 72 | +- [Digital services for integrated care]((https://digital.nhs.uk/services/digital-services-for-integrated-care)) (DSIC) front door |
| 73 | +- [Joint GP IT Committee](https://www.rcgp.org.uk/about/communities-groups/health-informatics) (JGPITC) |
| 74 | +- GP IT roadmap |
| 75 | + |
| 76 | +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. |
| 77 | + |
| 78 | +We are speaking to other teams who we can collaborate with and learn from. One of those is the [Patient data manager](https://digital.nhs.uk/services/patient-data-manager) (PDM) 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. |
| 79 | + |
| 80 | +## Understand policy implications |
| 81 | + |
| 82 | +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. |
| 83 | + |
| 84 | +## Conclusion |
| 85 | + |
| 86 | +Digital transformation is constrained by governance and approval processes as much as by software engineering - both need our attention. The 4 things we described are 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. |
| 87 | + |
| 88 | +Next, we will describe the detail of each of the 4 challenge areas. |
0 commit comments