From 96ff8fa16d1970d20d49d957bf7b222e956c51ce Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Tue, 30 Jul 2024 15:53:28 +0000 Subject: [PATCH 01/12] Create page for AI ethics template copy --- docs/our_work/ai-ethics.md | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 docs/our_work/ai-ethics.md diff --git a/docs/our_work/ai-ethics.md b/docs/our_work/ai-ethics.md new file mode 100644 index 00000000..b18f0173 --- /dev/null +++ b/docs/our_work/ai-ethics.md @@ -0,0 +1,35 @@ +--- +title: 'Operationalising AI Ethics in NHS England' +summary: 'ONE LINE SUMMARY GOES HERE' +origin: 'NHS England' +tags: ['AI', 'ETHICS', 'TRANSPARENCY', 'DOCUMENTATION', 'RESEARCH', 'GUIDANCE', 'BEST PRACTICE'] +--- +[comment]: <> When making your tags, it might be handy to see a list of the tags that have already been defined. Run `python utils/list-tags.py` from the terminal to print the existing tags (assuming you are in the root directory - update the path if not). You can also run it from VS Code by opening the file and clicking the "Run" button in the top right (but you'll need to have the Python extension installed to do it this way). + +[comment]: <> The metadata block above is used to make the title, the tags, and the first block of "quote text" just beneath the title + +[comment]: <> Make a nice visual abstract for your project, or show some key result, which makes the impact of your work clear - imagine your audience is an educated observer from the health system +[![Alt text for the image](../images/)]() + +[comment]: <> Add some description about your project - keep it punchy, focussing on the benefits, anything new, and only the most important parts of the methods, particularly anything which might interest people. + +People often have this problem - we used data science to make the solution. We worked with patient groups / clinicians / senior decision makers to come up with a solution which use AI, etc., we were able to automate this task. + +## Results + +[comment]: <> Add some description of the key results - again keep them punchy, and in real units that people can understand if possible. This is where we get across the impact. It might be that the image describes this, in which case reference that. +by automating the problem area described above, we were able to save £xxx / so many hours of doctor / patient / staff time. The diagram above shows how impactful this was. + +Output|Link + +[comment]: <> below you can put any relevant links through to outputs, and published code, published papers, live tools, websites, blog articles, anything which is relevant to the project. +---|--- +Open Source Code & Documentation|[Github](#add URL) +Case Study| +Technical report|[e.g. biorxiv.org]() +Algorithmic Impact Assessment|e.g. N/A + +When you finish creating your project page, make sure you add it into the appropriate navigation sections in the [mkdocs.yml](https://github.com/nhsengland/datascience/blob/main/mkdocs.yml) for website navigation purposes! + +[comment]: <> (The below header stops the title from being rendered (as mkdocs adds it to the page from the "title" attribute) - this way we can add it in the main.html, along with the summary.) +# From 685fefc3814a7328a455c421e586be567993cbd6 Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Fri, 9 Aug 2024 10:52:06 +0000 Subject: [PATCH 02/12] tags --- docs/our_work/ai-ethics.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/our_work/ai-ethics.md b/docs/our_work/ai-ethics.md index b18f0173..1a3d8bfa 100644 --- a/docs/our_work/ai-ethics.md +++ b/docs/our_work/ai-ethics.md @@ -2,12 +2,10 @@ title: 'Operationalising AI Ethics in NHS England' summary: 'ONE LINE SUMMARY GOES HERE' origin: 'NHS England' -tags: ['AI', 'ETHICS', 'TRANSPARENCY', 'DOCUMENTATION', 'RESEARCH', 'GUIDANCE', 'BEST PRACTICE'] +tags: ['AI', 'ETHICS', 'TRANSPARENCY', 'QUALITY', 'DOCUMENTATION', 'RESEARCH', 'GUIDANCE', 'BEST PRACTICE'] --- [comment]: <> When making your tags, it might be handy to see a list of the tags that have already been defined. Run `python utils/list-tags.py` from the terminal to print the existing tags (assuming you are in the root directory - update the path if not). You can also run it from VS Code by opening the file and clicking the "Run" button in the top right (but you'll need to have the Python extension installed to do it this way). -[comment]: <> The metadata block above is used to make the title, the tags, and the first block of "quote text" just beneath the title - [comment]: <> Make a nice visual abstract for your project, or show some key result, which makes the impact of your work clear - imagine your audience is an educated observer from the health system [![Alt text for the image](../images/)]() From 33f5d59217ec524f031ac39eda390f0295e8e339 Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Fri, 9 Aug 2024 10:58:57 +0000 Subject: [PATCH 03/12] Remove redundant content --- docs/our_work/ai-ethics.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/docs/our_work/ai-ethics.md b/docs/our_work/ai-ethics.md index 1a3d8bfa..bd878800 100644 --- a/docs/our_work/ai-ethics.md +++ b/docs/our_work/ai-ethics.md @@ -4,15 +4,14 @@ summary: 'ONE LINE SUMMARY GOES HERE' origin: 'NHS England' tags: ['AI', 'ETHICS', 'TRANSPARENCY', 'QUALITY', 'DOCUMENTATION', 'RESEARCH', 'GUIDANCE', 'BEST PRACTICE'] --- -[comment]: <> When making your tags, it might be handy to see a list of the tags that have already been defined. Run `python utils/list-tags.py` from the terminal to print the existing tags (assuming you are in the root directory - update the path if not). You can also run it from VS Code by opening the file and clicking the "Run" button in the top right (but you'll need to have the Python extension installed to do it this way). + +Under construction. [comment]: <> Make a nice visual abstract for your project, or show some key result, which makes the impact of your work clear - imagine your audience is an educated observer from the health system [![Alt text for the image](../images/)]() [comment]: <> Add some description about your project - keep it punchy, focussing on the benefits, anything new, and only the most important parts of the methods, particularly anything which might interest people. -People often have this problem - we used data science to make the solution. We worked with patient groups / clinicians / senior decision makers to come up with a solution which use AI, etc., we were able to automate this task. - ## Results [comment]: <> Add some description of the key results - again keep them punchy, and in real units that people can understand if possible. This is where we get across the impact. It might be that the image describes this, in which case reference that. @@ -27,7 +26,5 @@ Case Study| Technical report|[e.g. biorxiv.org]() Algorithmic Impact Assessment|e.g. N/A -When you finish creating your project page, make sure you add it into the appropriate navigation sections in the [mkdocs.yml](https://github.com/nhsengland/datascience/blob/main/mkdocs.yml) for website navigation purposes! - [comment]: <> (The below header stops the title from being rendered (as mkdocs adds it to the page from the "title" attribute) - this way we can add it in the main.html, along with the summary.) # From 1eb0977521111b129293bd4f3453b14a18c5240c Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Wed, 28 Aug 2024 16:45:30 +0000 Subject: [PATCH 04/12] Update with latest info from white pape --- docs/our_work/ai-ethics.md | 32 +++++++++++++++----------------- 1 file changed, 15 insertions(+), 17 deletions(-) diff --git a/docs/our_work/ai-ethics.md b/docs/our_work/ai-ethics.md index bd878800..5126ad0b 100644 --- a/docs/our_work/ai-ethics.md +++ b/docs/our_work/ai-ethics.md @@ -1,30 +1,28 @@ --- -title: 'Operationalising AI Ethics in NHS England' -summary: 'ONE LINE SUMMARY GOES HERE' +title: 'AI Ethics in Practice at NHS England' +summary: 'Defining ethical AI development best practice for data practitioners in the NHS' origin: 'NHS England' tags: ['AI', 'ETHICS', 'TRANSPARENCY', 'QUALITY', 'DOCUMENTATION', 'RESEARCH', 'GUIDANCE', 'BEST PRACTICE'] --- +_This project is currently live, and as such the following is subject to change._ -Under construction. +AI presents transformative opportunities in healthcare, but the technology brings with it risks to people, the natural environment and society at large. NHS England has a responsibility to effectively harness AI to support the provision of better care to all patients. -[comment]: <> Make a nice visual abstract for your project, or show some key result, which makes the impact of your work clear - imagine your audience is an educated observer from the health system -[![Alt text for the image](../images/)]() +To do this, data scientists (among others) need to ensure ethical considerations are embedded in the development, evaluation and implementation of AI and data science projects more generally. -[comment]: <> Add some description about your project - keep it punchy, focussing on the benefits, anything new, and only the most important parts of the methods, particularly anything which might interest people. +However, there are few practical examples of what ethical AI in health looks like for those involved in its design and implementation. This is despite the proliferation of guidance from research institutions and other organisations. -## Results +## Ongoing work -[comment]: <> Add some description of the key results - again keep them punchy, and in real units that people can understand if possible. This is where we get across the impact. It might be that the image describes this, in which case reference that. -by automating the problem area described above, we were able to save £xxx / so many hours of doctor / patient / staff time. The diagram above shows how impactful this was. +We have written a White Paper in which we identify the characteristics of ethical AI that data scientists should be concerned with at the NHS. This takes into account other actors in AI development at the NHS, including cybersecurity, assurance and governance colleagues. -Output|Link +This paper proposes that data scientists specifically focus on trying to ensure four characteristics of AI: fair, transparent, value-adding and reliable. -[comment]: <> below you can put any relevant links through to outputs, and published code, published papers, live tools, websites, blog articles, anything which is relevant to the project. ----|--- -Open Source Code & Documentation|[Github](#add URL) -Case Study| -Technical report|[e.g. biorxiv.org]() -Algorithmic Impact Assessment|e.g. N/A +Our practical suggestions of how we can work towards embedding these characteristics in working practices include: + +* trialling tools and frameworks on live and emerging projects and to share learnings with the wider community. This will eventually constitute a portfolio of real examples that can inform future projects. +* coordinating a series of interactive workshops to build awareness of ethical risks, and to create and sustain a shared vocabulary to document and help mitigate these risks effectively along each project’s lifecycle. Initially this will be based on the [Data Hazards project](https://datahazards.com/). +* developing standardised resources that can be flexible to different types of data science projects, but ensure a minimum level of consideration and proportionate action. This includes a [Model Card](https://github.com/nhsengland/model-card). +* mapping the development processes and involved actors of AI at the NHS and growing a platform to share knowledge and experiences. -[comment]: <> (The below header stops the title from being rendered (as mkdocs adds it to the page from the "title" attribute) - this way we can add it in the main.html, along with the summary.) # From c560de74c4e0275b1061c00d233bdb5fd8e08dbe Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Wed, 28 Aug 2024 16:48:56 +0000 Subject: [PATCH 05/12] add links to steps --- docs/our_work/ai-ethics.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/our_work/ai-ethics.md b/docs/our_work/ai-ethics.md index 5126ad0b..cdfe7214 100644 --- a/docs/our_work/ai-ethics.md +++ b/docs/our_work/ai-ethics.md @@ -20,9 +20,9 @@ This paper proposes that data scientists specifically focus on trying to ensure Our practical suggestions of how we can work towards embedding these characteristics in working practices include: -* trialling tools and frameworks on live and emerging projects and to share learnings with the wider community. This will eventually constitute a portfolio of real examples that can inform future projects. +* trialling tools and frameworks on live and emerging projects and to share learnings with the wider community. This will eventually constitute a portfolio of real examples that can inform future projects, similar to the use cases features in the [OECD's Catalogue of Tools & Metrics for Trustworthy AI](https://oecd.ai/en/catalogue/tool-use-cases). * coordinating a series of interactive workshops to build awareness of ethical risks, and to create and sustain a shared vocabulary to document and help mitigate these risks effectively along each project’s lifecycle. Initially this will be based on the [Data Hazards project](https://datahazards.com/). * developing standardised resources that can be flexible to different types of data science projects, but ensure a minimum level of consideration and proportionate action. This includes a [Model Card](https://github.com/nhsengland/model-card). -* mapping the development processes and involved actors of AI at the NHS and growing a platform to share knowledge and experiences. +* mapping the development processes and involved actors of AI at the NHS and growing a platform to share knowledge and experiences. This will help us to identify how to incorporate ethical considerations into the data science lifecycle. # From 1710c8c9130e98d6d3706ea05a33ab5a8e0aeda3 Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Thu, 29 Aug 2024 12:35:42 +0000 Subject: [PATCH 06/12] Include outputs and in progress sections --- docs/our_work/ai-ethics.md | 28 ++++++++++++++++++++++++---- 1 file changed, 24 insertions(+), 4 deletions(-) diff --git a/docs/our_work/ai-ethics.md b/docs/our_work/ai-ethics.md index cdfe7214..c48008a7 100644 --- a/docs/our_work/ai-ethics.md +++ b/docs/our_work/ai-ethics.md @@ -4,7 +4,11 @@ summary: 'Defining ethical AI development best practice for data practitioners i origin: 'NHS England' tags: ['AI', 'ETHICS', 'TRANSPARENCY', 'QUALITY', 'DOCUMENTATION', 'RESEARCH', 'GUIDANCE', 'BEST PRACTICE'] --- -_This project is currently live, and as such the following is subject to change._ +!!! warning + + This project is currently in development, and as such the following is subject to change. + +## Background AI presents transformative opportunities in healthcare, but the technology brings with it risks to people, the natural environment and society at large. NHS England has a responsibility to effectively harness AI to support the provision of better care to all patients. @@ -12,7 +16,7 @@ To do this, data scientists (among others) need to ensure ethical considerations However, there are few practical examples of what ethical AI in health looks like for those involved in its design and implementation. This is despite the proliferation of guidance from research institutions and other organisations. -## Ongoing work +## Aim We have written a White Paper in which we identify the characteristics of ethical AI that data scientists should be concerned with at the NHS. This takes into account other actors in AI development at the NHS, including cybersecurity, assurance and governance colleagues. @@ -21,8 +25,24 @@ This paper proposes that data scientists specifically focus on trying to ensure Our practical suggestions of how we can work towards embedding these characteristics in working practices include: * trialling tools and frameworks on live and emerging projects and to share learnings with the wider community. This will eventually constitute a portfolio of real examples that can inform future projects, similar to the use cases features in the [OECD's Catalogue of Tools & Metrics for Trustworthy AI](https://oecd.ai/en/catalogue/tool-use-cases). -* coordinating a series of interactive workshops to build awareness of ethical risks, and to create and sustain a shared vocabulary to document and help mitigate these risks effectively along each project’s lifecycle. Initially this will be based on the [Data Hazards project](https://datahazards.com/). -* developing standardised resources that can be flexible to different types of data science projects, but ensure a minimum level of consideration and proportionate action. This includes a [Model Card](https://github.com/nhsengland/model-card). +* coordinating a series of interactive workshops to build awareness of ethical risks, and to create and sustain a shared vocabulary to document and help mitigate these risks effectively along each project’s lifecycle. +* developing standardised resources that can be flexible to different types of data science projects, but ensure a minimum level of consideration and proportionate action. * mapping the development processes and involved actors of AI at the NHS and growing a platform to share knowledge and experiences. This will help us to identify how to incorporate ethical considerations into the data science lifecycle. +## Outputs + +We have: + +* developed a [Model Card Template](https://github.com/nhsengland/model-card). +* coordinated the publication of a record for the [Automatic Moderation of Ratings & Reviews project](./ratings-and-reviews.md) on the government's [Algorithmic Transparency Recording Standard](https://www.gov.uk/algorithmic-transparency-records/nhs-england-nhs-dot-uk-reviews-automoderation-tool). +* written a (currently internal) White Paper defining the scope of operationalising AI Ethics in NHS England. + +## In progress + +We are currently exploring: + +* how we can use the [Data Hazards project](https://datahazards.com/) to communicate potential harms of our work +* the development of a generic statement detailing how projects have taken ethical considerations into account +* supporting our information governance teams on whether additional instruments (such as model cards) can help inform a Data Protection Impact Assessment for AI use cases + # From ed9ab04af610a4a0ca60d93719fc8763dc681039 Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Thu, 29 Aug 2024 12:40:33 +0000 Subject: [PATCH 07/12] correct asses to assess --- docs/our_work/p14_mcr.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/our_work/p14_mcr.md b/docs/our_work/p14_mcr.md index 6d1bd05a..0f77d092 100644 --- a/docs/our_work/p14_mcr.md +++ b/docs/our_work/p14_mcr.md @@ -2,7 +2,7 @@ layout: base title: Using Model Class Reliance to Understand the Impact of Commerical Data on Predictions permalink: p14_mcr.html -summary: How to asses the value that commercial sales data of over-the-counter prescriptions has on respiratory death predictions +summary: How to assess the value that commercial sales data of over-the-counter prescriptions has on respiratory death predictions tags: ['MCR', 'PYTHON', 'MORTALITY', 'RESPIRATORY'] --- From 5e50e0ef5fcce72759b8753e6cbfc802b92e5fe2 Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Thu, 29 Aug 2024 12:41:52 +0000 Subject: [PATCH 08/12] add ethics --- mkdocs.yml | 32 +++++++++++++++++--------------- 1 file changed, 17 insertions(+), 15 deletions(-) diff --git a/mkdocs.yml b/mkdocs.yml index b81ab0dc..c6d7ec29 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -10,7 +10,7 @@ plugins: blog_dir: ./articles authors_file: "{blog}/.authors.yml" - tags: - tags_file: our_work/tags.md + tags_file: our_work/tags.md - exclude-search: exclude: - our_work/template-project.md @@ -19,21 +19,22 @@ plugins: nav: - Home: index.md - About the team: about.md - - Projects: + - Projects: - Our Work: our_work/index.md - Project Tags: our_work/tags.md - Past/Current Projects: - Current Projects: - AI Dictionary: our_work/ai-dictionary.md + - AI Ethics in Practice: our_work/ai-ethics.md - Data Linkage Hub: our_work/data-linkage-hub/ - NHS.UK Automatic Moderation of Ratings & Reviews: our_work/ratings-and-reviews.md - Reproducible Analytical Pipelines Squad: our_work/ds218_rap_community_of_practice.md - - Tool to Asses Privacy Risk of Text Data - Extended: our_work/ds255_privacyfp.md + - Tool to Assess Privacy Risk of Text Data - Extended: our_work/ds255_privacyfp.md - A&E Forecasting Tool: our_work/a_and_e_forecasting_tool.md - Reusable Data Validation Process: our_work/sde_data_validation.md - RAG: our_work/ds251_RAG.md - Primary Care Data Generator: our_work/swpclab.md - - Past Projects: + - Past Projects: - 2023: - AI Models for Shortlisting Interview Candidates: our_work/casestudy-recruitment-shortlisting.md - AI Skunkworks Team: our_work/ai-skunkworks.md @@ -41,7 +42,7 @@ nav: - Enriching Clinical Coding for Neurology Pathways using MedCAT: our_work/p43_medcat.md - Including Mortality in our Implementation of Hypergraphs: our_work/p42_hypergraphs2.md - Parkinson's Disease Pathology Prediction: our_work/parkinsons-detection.md - - Tool to Asses Privacy Risk of Text Data: our_work/c399_privfinger.md + - Tool to Assess Privacy Risk of Text Data: our_work/c399_privfinger.md - 2022: - Adding a Clinical Focus to Evaluating MM Data Representations: our_work/p31_txtrayalign2.md - Ambulance Handover Delay Predictor: our_work/ambulance-delay-predictor.md @@ -57,11 +58,11 @@ nav: - Synthetic Data From Real Data: our_work/casestudy-synthetic-data-pipeline.md - Synthetic Data Generation Pipeline: our_work/synthetic-data-pipeline.md - Understanding the Impact of Co-Morbidities: our_work/p34_hypergraphs.md - - 2021: + - 2021: - AI Deep Dive Workshops: our_work/ai-deep-dive.md - CT Alignment & Lesion Detection: our_work/ct-alignment.md - Creating a Generic Adversarial Attack for Synthetic Data: our_work/c339_sas.md - - Developing SynthVAE: our_work/p21_synthvae.md + - Developing SynthVAE: our_work/p21_synthvae.md - Differential Privacy in a VAE for Synthetic Data Generation: our_work/p12_synthvae.md - Impact of Commercial Data on Predictions: our_work/p14_mcr.md - Length of Hospital Day Prediction: our_work/long-stay.md @@ -71,7 +72,7 @@ nav: - SynPath Simulator on Diabetes Pathway: our_work/p11_synpathdiabetes.md - Text Analysis using Structural Topic Modelling: our_work/p23_stm.md - TxtRayAlign: our_work/p22_txtrayalign.md - - 2020: + - 2020: - Data Lens: our_work/data-lens.md - Main Work Areas: - Predictive Analytics Products: @@ -85,7 +86,7 @@ nav: - Renal Health Prediction: our_work/renal-health-prediction.md - A&E Forecasting Tool: our_work/a_and_e_forecasting_tool.md - Data Science for Linked/Longitudinal Data: - - Data Linkage Hub: + - Data Linkage Hub: - our_work/data-linkage-hub/index.md # - ... | flat | our_work/data-linkage-hub/*.md - ... | flat | our_work/data-linkage-hub/linkage-projects/*.md @@ -94,11 +95,12 @@ nav: - AI Models for Shortlisting Interview Candidates: our_work/casestudy-recruitment-shortlisting.md - Data Lens: our_work/data-lens.md - NHS.UK Automatic Moderation of Ratings & Reviews: our_work/ratings-and-reviews.md - - Tool to Asses Privacy Risk of Text Data: our_work/c399_privfinger.md - - Tool to Asses Privacy Risk of Text Data - Extended: our_work/ds255_privacyfp.md + - Tool to Assess Privacy Risk of Text Data: our_work/c399_privfinger.md + - Tool to Assess Privacy Risk of Text Data - Extended: our_work/ds255_privacyfp.md - Data Science Capability: - AI Deep Dive Workshops: our_work/ai-deep-dive.md - AI Dictionary: our_work/ai-dictionary.md + - AI Ethics in Practice: our_work/ai-ethics.md - AI Skunkworks Team: our_work/ai-skunkworks.md - NHS @Home Programme: our_work/open-safely.md - Reproducible Analytical Pipelines Squad: our_work/ds218_rap_community_of_practice.md @@ -120,7 +122,7 @@ nav: - Understanding the Impact of Co-Morbidities: our_work/p34_hypergraphs.md - Synthetic Data: - Creating a Generic Adversarial Attack for Synthetic Data: our_work/c339_sas.md - - Developing SynthVAE: our_work/p21_synthvae.md + - Developing SynthVAE: our_work/p21_synthvae.md - Differential Privacy in a VAE for Synthetic Data Generation: our_work/p12_synthvae.md - Generic Patient Simulator: our_work/c245_synpath.md - Primary Care Data Generator: our_work/swpclab.md @@ -131,12 +133,12 @@ nav: - SDE Service Data Wranglers: - Reusable Data Validation Process: our_work/sde_data_validation.md - Our Team's Publications: our_work/Publications.md - # This allows any projects that get added to appear in the main page of the navigation, makes it easy to spot when people have forgotten to categorize them. + # This allows any projects that get added to appear in the main page of the navigation, makes it easy to spot when people have forgotten to categorize them. - ... | flat | regex=our_work/(?!template-project\.md).*\.md - # - Tools: + # - Tools: # - ... | flat | tools/*.md - PHDInterns: PhDInterns.md - - Articles: + - Articles: - ... | flat | articles/*.md - Playbooks: playbooks.md # - Codebases: codebases.md From 3931a1acadca879bbcf1ea39a6bf759b3d150af1 Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Thu, 29 Aug 2024 12:43:20 +0000 Subject: [PATCH 09/12] format and remove redundant reference --- README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index ff6a5582..377f2d95 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,11 @@ # [NHS England Data Science](https://nhsengland.github.io/datascience/) + ![CI](https://github.com/nhsengland/datascience/actions/workflows/pages-build-deployment.yml/badge.svg "CI badge indicating passing or failing status") [![Release Version](https://img.shields.io/github/v/release/nhsengland/datascience "Release version")](https://github.com/nhsengland/datascience/releases) [![MkDocs Material](https://img.shields.io/badge/style-MkDocs%20Material-darkblue "Markdown Style: MkDocs")](https://squidfunk.github.io/mkdocs-material/reference/) [![licence: MIT](https://img.shields.io/badge/Licence-MIT-yellow.svg)](https://opensource.org/licenses/MIT "MIT License") [![licence: OGL3](https://img.shields.io/badge/Licence-OGL3-darkgrey "licence: Open Government Licence 3")](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/) - > **This material is maintained by the [NHS England Data Science team](mailto:datascience@nhs.net)**. > > See our other work here: [NHS Digital Analytical Services](https://github.com/NHSDigital/data-analytics-services). @@ -18,12 +18,10 @@ Visit our [website](https://nhsengland.github.io/datascience/) for more informat [ 
 Data Science team website 
 ](https://nhsengland.github.io/datascience/) - ## Licence -Unless stated otherwise, the codebase is released under the [MIT Licence][2]. This covers both the codebase and any sample code in the documentation. +Unless stated otherwise, the codebase is released under the [MIT Licence][1]. This covers both the codebase and any sample code in the documentation. HTML and Markdown documentation is © Crown copyright and available under the terms of the [Open Government 3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/) licence. -[1]: ./CONTRIBUTE.md -[2]: ./LICENCE +[1]: ./LICENCE From 1866723ae592de300689b47293f183247799d328 Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Thu, 29 Aug 2024 12:46:40 +0000 Subject: [PATCH 10/12] correct numeration --- CONTRIBUTE.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTE.md b/CONTRIBUTE.md index be2480e7..a8db6829 100644 --- a/CONTRIBUTE.md +++ b/CONTRIBUTE.md @@ -16,7 +16,7 @@ If you want to contribute to our resources: 4. Make your change 5. Check how your change looks on our website by hosting the website locally (follow [the steps below](#contribute-to-nhs-england-data-science-website) on how to do this) 6. Content Review (follow the [instructions](#content-review)) -6. Push to your fork and [submit a pull request][pr] +7. Push to your fork and [submit a pull request][pr] Your pull request will then be reviewed. You may receive some feedback and suggested changes before it can be approved and your pull request merged. @@ -58,7 +58,8 @@ The website currently uses the [Material for MkDocs](https://squidfunk.github.io Here is a good [cheat sheet](https://yakworks.github.io/docmark/cheat-sheet/) for what features can be used in MkDocs and also interesting features in [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/reference/). ### Content Review -Prior to making a pull request, ensure that, if the changes involve a change or addition of content (rather than technical or spelling changes) to the site, you have gone through a content review as outlined [here](https://nhsd-confluence.digital.nhs.uk/display/DAT/Website+Gateway). This is to ensure that no sensitive or policy content goes into your PR, as whilst PRs aren't live on the website they are still public (as the repo is public). + +Prior to making a pull request, ensure that, if the changes involve a change or addition of content (rather than technical or spelling changes) to the site, you have gone through a content review as outlined [here](https://nhsd-confluence.digital.nhs.uk/display/DAT/Website+Gateway). This is to ensure that no sensitive or policy content goes into your PR, as whilst PRs aren't live on the website they are still public (as the repo is public). #### Blog / Article From e36aaddce9f212b3d098abe15503737f1602d9b5 Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Thu, 29 Aug 2024 13:17:38 +0000 Subject: [PATCH 11/12] correct website gateway link --- CONTRIBUTE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTE.md b/CONTRIBUTE.md index a8db6829..5cff8798 100644 --- a/CONTRIBUTE.md +++ b/CONTRIBUTE.md @@ -59,7 +59,7 @@ Here is a good [cheat sheet](https://yakworks.github.io/docmark/cheat-sheet/) fo ### Content Review -Prior to making a pull request, ensure that, if the changes involve a change or addition of content (rather than technical or spelling changes) to the site, you have gone through a content review as outlined [here](https://nhsd-confluence.digital.nhs.uk/display/DAT/Website+Gateway). This is to ensure that no sensitive or policy content goes into your PR, as whilst PRs aren't live on the website they are still public (as the repo is public). +Prior to making a pull request, ensure that, if the changes involve a change or addition of content (rather than technical or spelling changes) to the site, you have gone through a content review as outlined [here](https://nhsd-confluence.digital.nhs.uk/display/DAT/C&M:+Website+Gateway). This is to ensure that no sensitive or policy content goes into your PR, as whilst PRs aren't live on the website they are still public (as the repo is public). #### Blog / Article From 2978790c610d1df81b16a1f9dbaf30d710834d0e Mon Sep 17 00:00:00 2001 From: Harriet Sands Date: Mon, 2 Sep 2024 15:47:38 +0000 Subject: [PATCH 12/12] Capitalising bullet point entries --- docs/our_work/ai-ethics.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/our_work/ai-ethics.md b/docs/our_work/ai-ethics.md index c48008a7..0cb7efcb 100644 --- a/docs/our_work/ai-ethics.md +++ b/docs/our_work/ai-ethics.md @@ -24,25 +24,25 @@ This paper proposes that data scientists specifically focus on trying to ensure Our practical suggestions of how we can work towards embedding these characteristics in working practices include: -* trialling tools and frameworks on live and emerging projects and to share learnings with the wider community. This will eventually constitute a portfolio of real examples that can inform future projects, similar to the use cases features in the [OECD's Catalogue of Tools & Metrics for Trustworthy AI](https://oecd.ai/en/catalogue/tool-use-cases). -* coordinating a series of interactive workshops to build awareness of ethical risks, and to create and sustain a shared vocabulary to document and help mitigate these risks effectively along each project’s lifecycle. -* developing standardised resources that can be flexible to different types of data science projects, but ensure a minimum level of consideration and proportionate action. -* mapping the development processes and involved actors of AI at the NHS and growing a platform to share knowledge and experiences. This will help us to identify how to incorporate ethical considerations into the data science lifecycle. +* Trialling tools and frameworks on live and emerging projects and to share learnings with the wider community. This will eventually constitute a portfolio of real examples that can inform future projects, similar to the use cases features in the [OECD's Catalogue of Tools & Metrics for Trustworthy AI](https://oecd.ai/en/catalogue/tool-use-cases). +* Coordinating a series of interactive workshops to build awareness of ethical risks, and to create and sustain a shared vocabulary to document and help mitigate these risks effectively along each project’s lifecycle. +* Developing standardised resources that can be flexible to different types of data science projects, but ensure a minimum level of consideration and proportionate action. +* Mapping the development processes and involved actors of AI at the NHS and growing a platform to share knowledge and experiences. This will help us to identify how to incorporate ethical considerations into the data science lifecycle. ## Outputs We have: -* developed a [Model Card Template](https://github.com/nhsengland/model-card). -* coordinated the publication of a record for the [Automatic Moderation of Ratings & Reviews project](./ratings-and-reviews.md) on the government's [Algorithmic Transparency Recording Standard](https://www.gov.uk/algorithmic-transparency-records/nhs-england-nhs-dot-uk-reviews-automoderation-tool). -* written a (currently internal) White Paper defining the scope of operationalising AI Ethics in NHS England. +* Developed a [Model Card Template](https://github.com/nhsengland/model-card). +* Coordinated the publication of a record for the [Automatic Moderation of Ratings & Reviews project](./ratings-and-reviews.md) on the government's [Algorithmic Transparency Recording Standard](https://www.gov.uk/algorithmic-transparency-records/nhs-england-nhs-dot-uk-reviews-automoderation-tool). +* Written a (currently internal) White Paper defining the scope of operationalising AI Ethics in NHS England. ## In progress We are currently exploring: -* how we can use the [Data Hazards project](https://datahazards.com/) to communicate potential harms of our work -* the development of a generic statement detailing how projects have taken ethical considerations into account -* supporting our information governance teams on whether additional instruments (such as model cards) can help inform a Data Protection Impact Assessment for AI use cases +* Using the [Data Hazards project](https://datahazards.com/) to communicate potential harms of our work. +* Developing a generic statement detailing how projects have taken ethical considerations into account. +* Supporting our information governance teams on whether additional instruments (such as model cards) can help inform a Data Protection Impact Assessment for AI use cases. #