Add Breast Screening Reporting section (#198)

gjackson296 · web-flow · commit d09f03495008 · 2025-08-13T17:09:49.000+01:00
* Add Breast Screening Reporting section And a first post on Data Product Design Principles. * Conform BSR content to how to guide https://design-history.prevention-services.nhs.uk/guide/how-to-add-a-new-service/ * Make 'Breast screening reporting' name consistent Some occurrences had the 'team' suffix. * Make BSR entry alphabetical in project.njk * Make 'Data product design...' page sentence case * Replace table image with markdown table * Add exact node tool version Using 22 alone didn't work: ``` $ asdf install Trying to update node-build... ok node-build: definition not found: 22 failed to run install callback: exit status 2 ``` * Fix globbing bug This was stopping the pages being picked up. Thank you to edwardhorsford for the fix! * Fix year typo * Revert asdf exact pinning * Add back design principles learnings * Fix png display typo and folder structure
diff --git a/app/_layouts/product.njk b/app/_layouts/product.njk
@@ -37,6 +37,7 @@
     {% set sections = [
       { title: "Screening", services: [
         "Bowel screening",
+        "Breast screening reporting",
         "Cohort manager",
         "Explore team",
         "Manage breast screening",
diff --git a/app/images/breast-screening-reporting/2025/02/data-product-design-principles/data-product-design-principles.png b/app/images/breast-screening-reporting/2025/02/data-product-design-principles/data-product-design-principles.png
diff --git a/app/posts/breast-screening-reporting.md b/app/posts/breast-screening-reporting.md
@@ -0,0 +1,13 @@
+---
+layout: collection
+title: Breast screening reporting
+description: >
+  Breast Screening Reporting is a data team, formed in July 2025.
+  It focuses on the performance and reporting of screening services.
+  It continues some of the work of Team Analyse.
+pagination:
+  data: collections.breast-screening-reporting
+  reverse: true
+  size: 50
+permalink: "breast-screening-reporting/{% if pagination.pageNumber > 0 %}page/{{ pagination.pageNumber + 1 }}{% endif %}/"
+---
diff --git a/app/posts/breast-screening-reporting/2025/02/2025-02-01-data-product-design-principles.md b/app/posts/breast-screening-reporting/2025/02/2025-02-01-data-product-design-principles.md
@@ -0,0 +1,54 @@
+---
+  title: Data product design principles
+  description: Ensuring data is usable and useful
+  date: 2025-02-01
+  tags:
+    - data
+    - reporting
+    - user needs
+---
+
+
+**Note: this work was completed by Team Analyse. It will be carried forward by Breast Screening Reporting.**
+
+There can be a perception that data is somehow independent of its users and if they just see some numbers that’s enough. Our research into data needs showed us that not all users can use what they are given, and therefore that rolling out a product or platform is not the same as adoption among users.
+
+## What we found
+
+In Breast Screening Offices (BSOs) we saw that some data was:
+
+- difficult to access due to problematic logins, for example
+- not specific enough to them to be useful
+- difficult to use due to the complexity of the tool
+- communicated using language and concepts users didn’t always understand
+- did not contain all the data needed to answer their questions
+
+In a busy work context these can act as big barriers to valuable data.
+
+In addition to data in tools and platforms there are issues with accessing data in their own system, the National Breast Screening System (NBSS) such as:
+
+- specialised skills are needed to get data out using a second system
+- often when data is extracted, BSO admin staff users spend time manually ‘wrangling’ data before it is usable
+
+## What we did
+
+This evidence suggested we need some design principles to ‘keep us honest’ into the future and ensure that we are always meeting the needs of users, not just supplying the right numbers. Users must be able to easily access, understand and act on the data they need.
+
+The draft of design principles below was inspired by NHS design principles and adapted for data users in breast screening.
+
+![1. Be relevant and useful
+Understand what data I need to answer my question
+2. Keep it simple
+Don’t overload me with options and possibilities in a tool I may be unfamiliar with; I am busy. Help me focus on what’s relevant to my question
+3. Make it easy to access
+Logins and permissions can be a barrier in busy environments. I may only need data infrequently logins can expire.
+4.  Make it easy to understand
+I may not be expert in understanding data or statistics. I should not need special training. Avoid jargon.
+5. Don’t make me do work for the data I need
+Data should work hard for me
+6. Add value and insight
+Highlight where I need to pay attention; help me find patterns; join data sets for me that help me answer a question](data-product-design-principles.png)
+
+## What’s next
+
+As we continue our work we will refer to these principles to ensure the NHS gets the full value from the data we make available.
diff --git a/app/posts/breast-screening-reporting/breast-screening-reporting.json b/app/posts/breast-screening-reporting/breast-screening-reporting.json
@@ -0,0 +1,5 @@
+{
+  "eleventyNavigation": {
+    "parent": "Breast screening reporting"
+  }
+}
diff --git a/eleventy.config.js b/eleventy.config.js
@@ -73,6 +73,10 @@ module.exports = function (eleventyConfig) {
     return collection.getFilteredByGlob("app/posts/bowel-screening/**/*.md")
   })
 
+  eleventyConfig.addCollection('breast-screening-reporting', collection => {
+    return collection.getFilteredByGlob('app/posts/breast-screening-reporting/**/*.md')
+  })
+
   eleventyConfig.addCollection("cohort-manager", (collection) => {
     return collection.getFilteredByGlob("app/posts/cohort-manager/**/*.md")
   })

-Original file line number
+Diff line change
@@ @@ -0,0 +1,5 @@ @@
 +{
 +  "eleventyNavigation": {
 +    "parent": "Breast screening reporting"
 +  }
 +}