├── .babelrc ├── app ├── views │ ├── robots.txt │ ├── manifest.njk │ ├── pages │ │ ├── 404.njk │ │ ├── our-policies │ │ │ ├── privacy-policy.njk │ │ │ ├── index.njk │ │ │ ├── accessibility.njk │ │ │ ├── cookie-confirmation.njk │ │ │ ├── cookies-policy.njk │ │ │ ├── cookie-declaration.njk │ │ │ └── terms-and-conditions.njk │ │ ├── who-we-are.njk │ │ ├── get-involved.njk │ │ ├── key-information-and-tools │ │ │ ├── tech-plan-for-health-and-care.njk │ │ │ ├── index.njk │ │ │ ├── information-governance-guidance │ │ │ │ ├── index.njk │ │ │ │ ├── ig-professionals.njk │ │ │ │ ├── social-care-sector.njk │ │ │ │ ├── health-care-professionals.njk │ │ │ │ ├── COPI-notice-FAQs.njk │ │ │ │ ├── use-of-mobile-devices-by-patients.njk │ │ │ │ └── how-data-is-supporting-covid19.njk │ │ │ ├── designing-and-building-products-and-services.njk │ │ │ ├── apps-and-tools.njk │ │ │ └── data-driven-health-and-care-technology.njk │ │ ├── sitemap.njk │ │ ├── what-we-do.njk │ │ └── how-we-work.njk │ ├── includes │ │ ├── footer.njk │ │ ├── layout.njk │ │ └── header.njk │ ├── sitemap.xml │ └── index.njk ├── assets │ ├── open-graph.png │ ├── NHSX_AI_report.pdf │ ├── favicons │ │ ├── favicon.ico │ │ ├── favicon.png │ │ ├── apple-touch-icon.png │ │ ├── favicon-192x192.png │ │ ├── smalltile-70x70.png │ │ ├── widetile-310x150.png │ │ ├── largetile-310x310.png │ │ ├── mediumtile-144x144.png │ │ ├── mediumtile-150x150.png │ │ ├── apple-touch-icon-180x180.png │ │ └── favicon.svg │ ├── NHSx_Case_Studies_EMRAD.pdf │ ├── Final_General_COPI_Notice.pdf │ ├── NHSx_Case_Studies_Cogstack.pdf │ ├── NHSx_Case_Studies_Kortical.pdf │ ├── NHSx_Case_Studies_Precision.pdf │ ├── Covid19_Example_Privacy_Notice.pdf │ ├── S_0419_NHSX_header_F0241829-crop.png │ ├── NHS_Digital_Health_Technology_Standard_draft.pdf │ └── Digital_Innovation_in_Healthcare_Report_Web_Accessible.pdf ├── styles │ ├── main.scss │ ├── nhsx │ │ ├── core │ │ │ ├── _colours.scss │ │ │ └── _page.scss │ │ ├── components │ │ │ ├── _promo.scss │ │ │ ├── _hero.scss │ │ │ ├── _video.scss │ │ │ ├── _footer.scss │ │ │ ├── _tables.scss │ │ │ └── _header.scss │ │ └── _utilities.scss │ └── _nhsx.scss ├── locals.js ├── scripts │ └── main.js ├── config.js └── routes.js ├── .eslintrc.js ├── .editorconfig ├── .gitignore ├── webpack.config.js ├── azure-pipelines.yml ├── .github └── PULL_REQUEST_TEMPLATE.md ├── LICENSE ├── app.js ├── package.json ├── README.md ├── .sass-lint.yml ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md └── CHANGELOG.md /.babelrc: -------------------------------------------------------------------------------- 1 | { 2 | "presets": [ 3 | ["@babel/env"] 4 | ] 5 | } -------------------------------------------------------------------------------- /app/views/robots.txt: -------------------------------------------------------------------------------- 1 | User-agent: * 2 | Allow: / 3 | Sitemap: https://www.nhsx.nhs.uk/sitemap.xml 4 | -------------------------------------------------------------------------------- /app/assets/open-graph.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/open-graph.png -------------------------------------------------------------------------------- /.eslintrc.js: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | "extends": "nhsuk", 3 | "env": { 4 | "browser": true, 5 | } 6 | }; 7 | -------------------------------------------------------------------------------- /app/assets/NHSX_AI_report.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/NHSX_AI_report.pdf -------------------------------------------------------------------------------- /app/assets/favicons/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/favicon.ico -------------------------------------------------------------------------------- /app/assets/favicons/favicon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/favicon.png -------------------------------------------------------------------------------- /app/assets/NHSx_Case_Studies_EMRAD.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/NHSx_Case_Studies_EMRAD.pdf -------------------------------------------------------------------------------- /app/assets/Final_General_COPI_Notice.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/Final_General_COPI_Notice.pdf -------------------------------------------------------------------------------- /app/assets/favicons/apple-touch-icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/apple-touch-icon.png -------------------------------------------------------------------------------- /app/assets/favicons/favicon-192x192.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/favicon-192x192.png -------------------------------------------------------------------------------- /app/assets/favicons/smalltile-70x70.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/smalltile-70x70.png -------------------------------------------------------------------------------- /app/assets/favicons/widetile-310x150.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/widetile-310x150.png -------------------------------------------------------------------------------- /app/assets/NHSx_Case_Studies_Cogstack.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/NHSx_Case_Studies_Cogstack.pdf -------------------------------------------------------------------------------- /app/assets/NHSx_Case_Studies_Kortical.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/NHSx_Case_Studies_Kortical.pdf -------------------------------------------------------------------------------- /app/assets/NHSx_Case_Studies_Precision.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/NHSx_Case_Studies_Precision.pdf -------------------------------------------------------------------------------- /app/assets/favicons/largetile-310x310.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/largetile-310x310.png -------------------------------------------------------------------------------- /app/assets/favicons/mediumtile-144x144.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/mediumtile-144x144.png -------------------------------------------------------------------------------- /app/assets/favicons/mediumtile-150x150.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/mediumtile-150x150.png -------------------------------------------------------------------------------- /app/assets/Covid19_Example_Privacy_Notice.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/Covid19_Example_Privacy_Notice.pdf -------------------------------------------------------------------------------- /app/assets/S_0419_NHSX_header_F0241829-crop.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/S_0419_NHSX_header_F0241829-crop.png -------------------------------------------------------------------------------- /app/assets/favicons/apple-touch-icon-180x180.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/favicons/apple-touch-icon-180x180.png -------------------------------------------------------------------------------- /app/styles/main.scss: -------------------------------------------------------------------------------- 1 | // NHS.UK frontend 2 | @import 'node_modules/nhsuk-frontend/packages/nhsuk'; 3 | 4 | // NHSX website styles 5 | @import 'nhsx'; 6 | -------------------------------------------------------------------------------- /app/assets/NHS_Digital_Health_Technology_Standard_draft.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/NHS_Digital_Health_Technology_Standard_draft.pdf -------------------------------------------------------------------------------- /app/assets/Digital_Innovation_in_Healthcare_Report_Web_Accessible.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nhsx/old-nhsx-website/HEAD/app/assets/Digital_Innovation_in_Healthcare_Report_Web_Accessible.pdf -------------------------------------------------------------------------------- /app/locals.js: -------------------------------------------------------------------------------- 1 | module.exports = config => (req, res, next) => { 2 | res.locals.COOKIE_CONSENT_URL = config.cookies.scriptURL; 3 | res.locals.BASE_URL = config.baseURL; 4 | 5 | next(); 6 | }; 7 | -------------------------------------------------------------------------------- /.editorconfig: -------------------------------------------------------------------------------- 1 | # editorconfig.org 2 | root = true 3 | 4 | [*] 5 | charset = utf-8 6 | indent_size = 2 7 | indent_style = space 8 | trim_trailing_whitespace = true 9 | insert_final_newline = true 10 | end_of_line = lf 11 | 12 | [*.md] 13 | trim_trailing_whitespace = false 14 | -------------------------------------------------------------------------------- /app/styles/nhsx/core/_colours.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | #COLOURS 3 | ========================================================================== */ 4 | 5 | // sass-lint:disable no-color-hex 6 | 7 | $color_nhsx-blue: #003087; 8 | -------------------------------------------------------------------------------- /app/scripts/main.js: -------------------------------------------------------------------------------- 1 | // NHS.UK frontend 2 | import Header from '../../node_modules/nhsuk-frontend/packages/components/header/header'; 3 | import SkipLink from '../../node_modules/nhsuk-frontend/packages/components/skip-link/skip-link'; 4 | 5 | // Initialise components 6 | Header(); 7 | SkipLink(); 8 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | lib-cov 2 | *.seed 3 | *.log 4 | *.csv 5 | *.dat 6 | *.out 7 | *.pid 8 | *.gz 9 | *.swp 10 | 11 | pids 12 | logs 13 | results 14 | tmp 15 | coverage 16 | 17 | # API keys 18 | .env 19 | 20 | # Dependency directory 21 | node_modules 22 | bower_components 23 | 24 | # Editors 25 | .idea 26 | *.iml 27 | 28 | # OS metadata 29 | .DS_Store 30 | Thumbs.db 31 | 32 | # Compiled files 33 | public/ 34 | -------------------------------------------------------------------------------- /app/styles/nhsx/core/_page.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | #PAGE 3 | ========================================================================== */ 4 | 5 | .nhsx-section { 6 | padding-bottom: 32px; 7 | padding-top: 32px; 8 | 9 | @include mq($from: tablet) { 10 | padding-bottom: 60px; 11 | padding-top: 60px; 12 | } 13 | } 14 | 15 | .nhsx-section--white { 16 | background-color: $color_nhsuk-white; 17 | } 18 | -------------------------------------------------------------------------------- /app/config.js: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | // Service name 3 | serviceName: 'NHSX', 4 | 5 | // Environment 6 | env: process.env.NODE_ENV || 'development', 7 | 8 | // Base URL 9 | baseURL: process.env.BASE_URL || 'https://www.nhsx.nhs.uk', 10 | 11 | // Port to run local development server on 12 | port: process.env.PORT || 3000, 13 | 14 | // Cookie consent banner 15 | cookies: { 16 | scriptURL: process.env.COOKIE_CONSENT_URL || '/js/cookies.min.js', 17 | }, 18 | }; 19 | -------------------------------------------------------------------------------- /app/styles/nhsx/components/_promo.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | #PROMO 3 | ========================================================================== */ 4 | 5 | .nhsx-promo--grey, 6 | .nhsx-content--grey { 7 | background-color: $color_nhsuk-grey-5; 8 | } 9 | 10 | .nhsx-promo--white, 11 | .nhsx-content--white { 12 | background-color: $color_nhsuk-white; 13 | } 14 | 15 | .nhsx-promo--homepage-video { 16 | @include mq($from: desktop) { 17 | margin-bottom: 0; 18 | } 19 | } 20 | -------------------------------------------------------------------------------- /app/styles/nhsx/components/_hero.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | #HERO 3 | ========================================================================== */ 4 | 5 | .nhsuk-hero--nhsx { 6 | background-color: $color_nhsx-blue; 7 | 8 | .nhsuk-hero-content--nhsx { 9 | background-color: $color_nhsx-blue; 10 | width: 100%; 11 | 12 | .nhsuk-hero__arrow--nhsx { 13 | &:before, 14 | &:after { 15 | border: solid 32px $color_nhsx-blue; 16 | } 17 | } 18 | 19 | } 20 | } 21 | -------------------------------------------------------------------------------- /app/views/manifest.njk: -------------------------------------------------------------------------------- 1 | { 2 | "lang": "en", 3 | "name": "NHSX Website", 4 | "short_name": "NHSX", 5 | "description": "{% if pageDescription %}{{pageDescription}}{% else %}NHSX - a new unit driving forward the digital transformation of health and care.{% endif %}", 6 | "theme_color": "#003087", 7 | "background_color": "#003087", 8 | "start_url": "/", 9 | "display": "standalone", 10 | "orientation": "portrait", 11 | "icons": [ 12 | { 13 | "src": "/assets/favicons/favicon.png", 14 | "sizes": "192x192", 15 | "type": "image/png" 16 | } 17 | ] 18 | } 19 | -------------------------------------------------------------------------------- /webpack.config.js: -------------------------------------------------------------------------------- 1 | const path = require('path'); 2 | 3 | module.exports = { 4 | entry: { 5 | cookies: './app/scripts/cookie-consent.js', 6 | main: './app/scripts/main.js', 7 | }, 8 | mode: 'production', 9 | module: { 10 | rules: [{ 11 | test: /\.js$/, 12 | use: { 13 | loader: 'babel-loader', 14 | options: { 15 | presets: ['@babel/preset-env'], 16 | }, 17 | }, 18 | }], 19 | }, 20 | output: { 21 | filename: '[name].min.js', 22 | path: path.resolve(__dirname, 'public/js/'), 23 | }, 24 | watchOptions: { 25 | ignored: /node_modules/, 26 | }, 27 | }; 28 | -------------------------------------------------------------------------------- /app/styles/nhsx/components/_video.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | #VIDEO 3 | ========================================================================== */ 4 | 5 | .nhsx-embed-container { 6 | height: 0; 7 | max-width: 100%; 8 | overflow: hidden; 9 | padding-bottom: 56.25%; 10 | position: relative; 11 | } 12 | 13 | .nhsx-embed-container iframe { 14 | border: 0; 15 | } 16 | 17 | .nhsx-embed-container iframe, 18 | .nhsx-embed-container object, 19 | .nhsx-embed-container embed { 20 | height: 100%; 21 | left: 0; 22 | position: absolute; 23 | top: 0; 24 | width: 100%; 25 | } 26 | -------------------------------------------------------------------------------- /app/styles/nhsx/components/_footer.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | #FOOTER 3 | ========================================================================== */ 4 | 5 | .nhsuk-footer--nhsx { 6 | @include nhsuk-responsive-padding(4, bottom); 7 | 8 | border-top: 4px solid $color_nhsx-blue; 9 | } 10 | 11 | .nhsx-footer-ogl { 12 | background-color: $color_nhsuk-grey-4; 13 | } 14 | 15 | .nhsx-footer-ogl__text { 16 | @include nhsuk-font(16); 17 | color: $color_nhsuk-grey-1; 18 | margin-bottom: 0; 19 | padding-bottom: nhsuk-spacing(4); 20 | 21 | svg { 22 | margin-right: nhsuk-spacing(2); 23 | position: relative; 24 | top: 2px; 25 | } 26 | } 27 | -------------------------------------------------------------------------------- /azure-pipelines.yml: -------------------------------------------------------------------------------- 1 | trigger: 2 | branches: 3 | include: 4 | - master 5 | - refs/tags/v* 6 | paths: 7 | exclude: 8 | - CHANGELOG.md 9 | - README.md 10 | 11 | pool: 12 | vmImage: 'ubuntu-latest' 13 | 14 | steps: 15 | 16 | - script: npm ci 17 | displayName: 'Install' 18 | 19 | - script: npm run build 20 | displayName: 'Build' 21 | 22 | - script: npm test 23 | displayName: 'Test' 24 | 25 | - task: ArchiveFiles@2 26 | inputs: 27 | rootFolderOrFile: '$(System.DefaultWorkingDirectory)' 28 | includeRootFolder: false 29 | displayName: 'Create file archive to publish' 30 | 31 | - task: PublishBuildArtifacts@1 32 | displayName: 'Publish files to Azure Pipelines' 33 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | ## Description 2 | 3 | 4 | ### Related issue 5 | 6 | 7 | ## Checklist 8 | 9 | 10 | - [ ] Tested against the [NHS.UK frontend testing policy](https://github.com/nhsuk/nhsuk-frontend/blob/master/docs/contributing/testing.md) (Resolution, Browser & Accessibility) 11 | - [ ] Code follows the [NHS.UK frontend coding standards](https://github.com/nhsuk/nhsuk-frontend/blob/master/docs/contributing/coding-standards.md) 12 | - [ ] Version number increase (using [SEMVER](https://semver.org/)) 13 | - [ ] Documentation 14 | - [ ] CHANGELOG entry 15 | -------------------------------------------------------------------------------- /app/styles/_nhsx.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | NHSX website styles 3 | ========================================================================== */ 4 | 5 | /** 6 | * NHSX uses some custom styles in addition to the 7 | * NHS.UK frontend library. 8 | * 9 | * This also includes some hotfixes utilities for issues 10 | * found in the NHS.UK frontend library. 11 | */ 12 | 13 | // Core 14 | @import './nhsx/core/colours'; 15 | @import './nhsx/core/page'; 16 | 17 | // Components 18 | @import './nhsx/components/footer'; 19 | @import './nhsx/components/header'; 20 | @import './nhsx/components/hero'; 21 | @import './nhsx/components/promo'; 22 | @import './nhsx/components/tables'; 23 | @import './nhsx/components/video'; 24 | 25 | // Utilities 26 | @import './nhsx/utilities'; 27 | -------------------------------------------------------------------------------- /app/styles/nhsx/components/_tables.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | #TABLES 3 | ========================================================================== */ 4 | 5 | @include mq($until: tablet) { 6 | .nhsx-table-responsive--nhsx { 7 | thead { 8 | border: 0; 9 | clip: rect(0 0 0 0); 10 | height: 1px; 11 | margin: -1px; 12 | overflow: hidden; 13 | padding: 0; 14 | position: absolute; 15 | width: 1px; 16 | } 17 | tr { 18 | border-bottom: solid 2px $color_nhsuk-grey-4; 19 | display: block; 20 | 21 | &:last-child { 22 | border-bottom: 0; 23 | } 24 | } 25 | td { 26 | border-bottom: 1px dotted $color_nhsuk-grey-4; 27 | display: block; 28 | text-align: left; 29 | 30 | &:last-child { 31 | border-bottom: 0; 32 | } 33 | 34 | &::before { 35 | content: attr(data-label); 36 | display: block; 37 | font-weight: bold; 38 | padding-right: 20px; 39 | } 40 | } 41 | } 42 | } 43 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2019 NHSX 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /app/views/pages/404.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Page not found" %} 2 | 3 | {% extends 'includes/layout.njk' %} 4 | 5 | {% block outerBody %} 6 | 14 | {% endblock %} 15 | 16 | {% block body %} 17 |
18 |
19 | 20 |

Page not found

21 |

If you entered a web address, please check it was correct.

22 |

If you came across the broken link from another page, please email us at feedback@nhsx.nhs.uk or let us know on the @NHSX Twitter account.

23 | 24 |

Return to the NHSX homepage.

25 |
26 |
27 | {% endblock %} 28 | -------------------------------------------------------------------------------- /app/styles/nhsx/components/_header.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | #HEADER 3 | ========================================================================== */ 4 | 5 | .nhsuk-header--nhsx { 6 | background-color: $color_nhsx-blue; 7 | } 8 | 9 | @include mq($from: large-desktop) { 10 | .nhsuk-header__navigation--nhsx { 11 | background-color: $color_nhsx-blue; 12 | } 13 | } 14 | 15 | .nhsuk-header__link--nhsx, 16 | .nhsuk-header__logo--nhsx .nhsuk-logo--nhsx { 17 | width: 120px; 18 | } 19 | 20 | .nhsuk-header__menu-toggle--nhsx { 21 | &:hover, 22 | &:active, 23 | .is-active { 24 | background-color: $color_nhsuk-black; 25 | color: $color_nhsuk-grey-5; 26 | } 27 | } 28 | 29 | /* ========================================================================== 30 | #NAVIGATION 31 | ========================================================================== */ 32 | 33 | .nhsuk-header__navigation-link--nhsx { 34 | &:hover { 35 | background-color: $color_nhsx-blue; 36 | 37 | @include mq($from: large-desktop) { 38 | background-color: $color_nhsuk-black; 39 | } 40 | 41 | } 42 | 43 | &:active { 44 | background-color: $color_nhsuk-black; 45 | color: $color_nhsuk-grey-5; 46 | } 47 | } 48 | -------------------------------------------------------------------------------- /app/assets/favicons/favicon.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /app/views/pages/our-policies/privacy-policy.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Privacy policy" %} 2 | {% set pageDescription = "This privacy policy tells you what information we collect when you use the NHSX website." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 16 | {% endblock %} 17 | 18 | {% block body %} 19 |
20 |
21 | 22 |

Privacy policy

23 |

NHS England and NHS Improvement and the Department of Health and Social Care are delivering NHSX together.

24 |

These 2 privacy notices apply:

25 | 29 | 30 |
31 |
32 | {% endblock %} 33 | -------------------------------------------------------------------------------- /app/views/pages/our-policies/index.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Our policies" %} 2 | {% set pageDescription = "Our website policies cover accessibility, cookies, how we handle the data we collect and our terms of use." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 15 | {% endblock %} 16 | 17 | {% block body %} 18 |
19 |
20 | 21 |

Our policies

22 | 23 | 36 | 37 |
38 |
39 | {% endblock %} 40 | -------------------------------------------------------------------------------- /app/styles/nhsx/_utilities.scss: -------------------------------------------------------------------------------- 1 | /* ========================================================================== 2 | #UTILITIES 3 | ========================================================================== */ 4 | 5 | // sass-lint:disable no-important 6 | 7 | /** 8 | * Border on the right hand page navigation 9 | */ 10 | 11 | .nhsx-u-border-top { 12 | border-top: 2px solid $color_nhsx-blue; 13 | margin-top: nhsuk-spacing(5); 14 | 15 | @include mq($from: desktop) { 16 | margin-top: nhsuk-spacing(2); 17 | } 18 | } 19 | 20 | .nhsx-u-border-top h2 { 21 | margin-bottom: nhsuk-spacing(3); 22 | margin-top: nhsuk-spacing(3); 23 | } 24 | 25 | .nhsx-u-border-top ul { 26 | list-style: none; 27 | padding-left: 0; 28 | } 29 | 30 | /** 31 | * Hotfix for an issue with nested list spacing in 32 | * the NHS.UK frontend library 33 | * 34 | * https://github.com/nhsuk/nhsuk-frontend/issues/430 35 | */ 36 | 37 | .nhsx-u-nested-list { 38 | margin-bottom: 0; 39 | } 40 | 41 | .nhsx-u-nested-list > li { 42 | @include nhsuk-responsive-margin(2, 'top'); 43 | } 44 | 45 | /** 46 | * Hotfix for an issue with hero spacing in 47 | * the NHS.UK frontend library 48 | * 49 | * https://github.com/nhsuk/nhsuk-frontend/issues/431 50 | */ 51 | 52 | .nhsx-u-hero-spacing { 53 | padding-bottom: 20px; 54 | padding-top: 88px; 55 | 56 | @include mq($from: 340px) { 57 | padding-top: 32px; 58 | } 59 | 60 | @include mq($from: tablet) { 61 | padding-bottom: 36px; 62 | padding-top: 96px; 63 | } 64 | } 65 | -------------------------------------------------------------------------------- /app/views/pages/our-policies/accessibility.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Accessibility statement" %} 2 | {% set pageDescription = "We aim to make the NHSX website as accessible and easy to use as possible." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 16 | {% endblock %} 17 | 18 | {% block body %} 19 |
20 |
21 | 22 |

Accessibility statement

23 |

We aim to make the NHSX website as accessible and easy to use as possible. We've designed our pages to meet the Web Content Accessibility Guidelines to level AA and we've tested them with users with access needs. Some external site links may not be to WCAG level AA. Should you require that information in a different format please email us at feedback@nhsx.nhs.uk

24 | 25 |

How to contact us

26 |

If you have any questions about accessibility, please email us at feedback@nhsx.nhs.uk. We will respond within 5 working days.

27 | 28 |
29 |
30 | {% endblock %} 31 | -------------------------------------------------------------------------------- /app.js: -------------------------------------------------------------------------------- 1 | // Core dependencies 2 | const path = require('path'); 3 | 4 | // External dependencies 5 | const browserSync = require('browser-sync'); 6 | const compression = require('compression'); 7 | const express = require('express'); 8 | const nunjucks = require('nunjucks'); 9 | 10 | // Local dependencies 11 | const config = require('./app/config'); 12 | const locals = require('./app/locals'); 13 | const routes = require('./app/routes'); 14 | 15 | // Initialise application 16 | const app = express(); 17 | 18 | // Middleware to serve static assets 19 | app.use(express.static(path.join(__dirname, 'public/'))); 20 | app.use('/nhsuk-frontend', express.static(path.join(__dirname, '/node_modules/nhsuk-frontend/packages'))); 21 | 22 | // View engine (Nunjucks) 23 | app.set('view engine', 'njk'); 24 | 25 | // Use local variables 26 | app.use(locals(config)); 27 | 28 | // Use gzip compression to decrease the size of 29 | // the response body and increase the speed of web app 30 | app.use(compression()); 31 | 32 | // Nunjucks configuration 33 | const appViews = [ 34 | path.join(__dirname, '/app/views/'), 35 | ]; 36 | 37 | nunjucks.configure(appViews, { 38 | autoescape: true, 39 | express: app, 40 | noCache: true, 41 | watch: true, 42 | }); 43 | 44 | // Custom routes 45 | app.use('/', routes); 46 | 47 | // Run application on configured port 48 | if (config.env === 'development') { 49 | app.listen(config.port - 50, () => { 50 | browserSync({ 51 | files: ['app/views/**/*.*', 'public/**/*.*'], 52 | notify: true, 53 | open: false, 54 | port: config.port, 55 | proxy: `localhost:${config.port - 50}`, 56 | ui: false, 57 | }); 58 | }); 59 | } else { 60 | app.listen(config.port); 61 | } 62 | 63 | module.exports = app; 64 | -------------------------------------------------------------------------------- /app/views/pages/our-policies/cookie-confirmation.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Your cookie settings have been saved" %} 2 | {% set pageDescription = "Your cookie settings have been saved. We'll save your settings for a year." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 17 | {% endblock %} 18 | 19 | {% block body %} 20 |
21 |
22 | 23 |
24 | 25 |

{{ pageTitle }}

26 |

We'll save your settings for a year.

27 |

We'll ask you if you're still OK with us using cookies when either:

28 |
    29 |
  • it's been a year since you last saved your settings
  • 30 |
  • we add any new cookies or change the cookies we use
  • 31 |
32 |

You can also choose which cookies we use at any time.

33 | 34 |
35 | 36 |
37 |

Updated: January 2020

38 |
39 | 40 |
41 |
42 | {% endblock %} 43 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "nhsx-website", 3 | "version": "2.10.0", 4 | "description": "The NHSX website", 5 | "main": "app.js", 6 | "scripts": { 7 | "babel": "babel --presets es2015 app/scripts/main.js -o public/js/main.bundle.js", 8 | "build": "npm run build:css && npm run build:js && npm run build:assets", 9 | "build:css": "node-sass --output-style compressed app/styles/main.scss public/css/main.min.css", 10 | "build:js": "npm run webpack", 11 | "build:assets": "cpx 'app/assets/**/*' public/assets/", 12 | "clean": "touch public/tmp.txt && rm -rf public/*", 13 | "lint": "npm run lint:js && npm run lint:css", 14 | "lint:js": "eslint app/scripts/**", 15 | "lint:css": "sass-lint 'app/**/*.scss' -v -q", 16 | "nuke": "npm run clean && rm -rf node_modules/", 17 | "postinstall": "npm run build", 18 | "start": "node app", 19 | "test": "npm run lint", 20 | "watch": "concurrently \"npm run watch:scss\" \"npm run watch:js\" \"npm run watch:assets\" \"npm start\"", 21 | "watch:scss": "npm run build:css && npm run build:css -- -w", 22 | "watch:js": "webpack -w", 23 | "watch:assets": "cpx 'app/assets/**/*' public/assets/ --watch", 24 | "webpack": "webpack" 25 | }, 26 | "author": "https://github.com/nhsx", 27 | "repository": { 28 | "type": "git", 29 | "url": "https://github.com/nhsx/nhsx-website.git" 30 | }, 31 | "license": "MIT", 32 | "dependencies": { 33 | "compression": "^1.7.4", 34 | "express": "^4.17.1", 35 | "nunjucks": "^3.2.1", 36 | "path": "^0.12.7" 37 | }, 38 | "devDependencies": { 39 | "@babel/core": "^7.9.0", 40 | "@babel/preset-env": "^7.9.0", 41 | "babel-loader": "^8.1.0", 42 | "browser-sync": "^2.26.7", 43 | "concurrently": "^4.1.2", 44 | "cpx": "^1.5.0", 45 | "eslint": "^6.8.0", 46 | "eslint-config-airbnb-base": "^13.2.0", 47 | "eslint-config-nhsuk": "^0.16.0", 48 | "eslint-plugin-import": "^2.20.1", 49 | "minimist": "^1.2.5", 50 | "nhsuk-frontend": "^3.0.3", 51 | "node-sass": "^4.13.1", 52 | "sass-lint": "^1.13.1", 53 | "webpack": "^4.42.0", 54 | "webpack-cli": "^3.3.11" 55 | } 56 | } 57 | -------------------------------------------------------------------------------- /app/views/includes/footer.njk: -------------------------------------------------------------------------------- 1 | 26 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # NHSX website 2 | 3 | :warning: This repository has been deprecated and is now read only. This repository was for the first iteration of the NHSX website, which has now been redeveloped into a CMS. 4 | 5 | ## About the NHSX website 6 | 7 | From 1 July, NHSX will bring together teams from the Department of Health and Social Care, NHS England and NHS Improvement to drive digital transformation in health and care. 8 | 9 | The NHSX website contains information about what we do, who we are, how we work and also links to key information and tools. 10 | 11 | We have built the website using the [NHS.UK frontend library](https://github.com/nhsuk/nhsuk-frontend). 12 | 13 | ## Quick start 14 | 15 | ### Running the application 16 | 17 | Install the long-term support (LTS) version of Node.js, which also includes NPM. 18 | 19 | Clone the repository `git clone git@github.com:nhsx/nhsx-website.git nhsx-website`, then whilst in the project directory `cd nhsx-website`, install the required npm packages with: `npm install` 20 | 21 | Run the project in development mode `npm run watch` and visit http://localhost:3000. 22 | 23 | ## Contributing 24 | 25 | The code for the NHSX website is in the open and we encourage contributions. So if you come across a bug or a spelling mistake, feel free to open a pull request with your changes or you can open a GitHub issue to report it to us. 26 | 27 | Read our [contributing guidelines](CONTRIBUTING.md) for more information about contributing to the NHSX website. 28 | 29 | ## Environment variables 30 | 31 | Environment variables are expected to be managed by the environment in which 32 | the application is being run. 33 | 34 | | Variable | Description | Default | Required | 35 | | ------------- | ----------------- | -------------- | --------- | 36 | | `GOOGLE_UA` | Google analytics user account ID | | No 37 | | `COOKIE_CONSENT_URL` | The URL for the [NHS.UK in-house implementation of cookie consent](https://github.com/nhsuk/cookie-consent) | /js/cookies.min.js | 38 | | `BASE_URL` | Domain of the environment | https://www.nhsx.nhs.uk | 39 | | `NODE_ENV` | Node environment. Recommend environments: `production`, `staging` and `development` | development | 40 | | `PORT` | Server port | 3000 | 41 | 42 | ## License 43 | 44 | The codebase is released under the MIT License, unless stated otherwise. This covers both the codebase and any sample code in the documentation. 45 | -------------------------------------------------------------------------------- /.sass-lint.yml: -------------------------------------------------------------------------------- 1 | options: 2 | formatter: stylish 3 | files: 4 | include: 5 | - 'packages/**/*.scss' 6 | ignore: 7 | - 'node_modules/**/*' 8 | rules: 9 | # Rules explanations can be found: https://github.com/sasstools/sass-lint/tree/master/docs/rules 10 | # Disable a rule for the entire file: // sass-lint:disable border-zero 11 | # Disable a rule for a single line: // sass-lint:disable-line border-zero 12 | # Extends 13 | extends-before-mixins: 2 14 | extends-before-declarations: 2 15 | placeholder-in-extend: 0 16 | 17 | # Mixins 18 | mixins-before-declarations: 0 19 | 20 | # Line Spacing 21 | one-declaration-per-line: 2 22 | empty-line-between-blocks: 0 23 | single-line-per-selector: 2 24 | 25 | # Disallows 26 | no-attribute-selectors: 0 27 | no-color-hex: 2 28 | no-color-keywords: 2 29 | no-color-literals: 2 30 | no-combinators: 0 31 | no-css-comments: 0 32 | no-debug: 2 33 | no-disallowed-properties: 0 34 | no-duplicate-properties: 2 35 | no-empty-rulesets: 2 36 | no-extends: 0 37 | no-ids: 2 38 | no-important: 2 39 | no-invalid-hex: 2 40 | no-mergeable-selectors: 2 41 | no-misspelled-properties: 2 42 | no-qualifying-elements: 2 43 | no-trailing-whitespace: 2 44 | no-trailing-zero: 2 45 | no-transition-all: 2 46 | no-universal-selectors: 0 47 | no-url-domains: 0 48 | no-url-protocols: 0 49 | no-vendor-prefixes: 0 50 | no-warn: 2 51 | property-units: 0 52 | 53 | # Nesting 54 | declarations-before-nesting: 2 55 | force-attribute-nesting: 0 56 | force-element-nesting: 0 57 | force-pseudo-nesting: 0 58 | 59 | # Name Formats 60 | class-name-format: 0 # Revisit in the future 61 | function-name-format: 2 62 | id-name-format: 0 63 | mixin-name-format: 2 64 | placeholder-name-format: 2 65 | variable-name-format: 0 66 | 67 | # Style Guide 68 | attribute-quotes: 2 69 | bem-depth: 0 70 | border-zero: 2 71 | brace-style: 2 72 | clean-import-paths: 2 73 | empty-args: 0 74 | hex-length: 0 75 | hex-notation: 0 76 | indentation: 2 77 | leading-zero: 2 78 | max-line-length: 0 79 | max-file-line-count: 0 80 | nesting-depth: 0 81 | property-sort-order: 2 82 | pseudo-element: 0 83 | quotes: 2 84 | shorthand-values: 2 85 | url-quotes: 0 86 | variable-for-property: 2 87 | zero-unit: 2 88 | 89 | # Inner Spacing 90 | space-after-comma: 2 91 | space-before-colon: 2 92 | space-after-colon: 2 93 | space-before-brace: 2 94 | space-before-bang: 2 95 | space-after-bang: 2 96 | space-between-parens: 2 97 | space-around-operator: 2 98 | 99 | # Final Items 100 | trailing-semicolon: 2 101 | final-newline: 2 102 | -------------------------------------------------------------------------------- /app/views/pages/who-we-are.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Who we are" %} 2 | {% set pageDescription = "NHSX brings together teams from the Department of Health and Social Care, NHS England and NHS Improvement." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 15 | {% endblock %} 16 | 17 | {% block body %} 18 |
19 |
20 | 21 |

Who we are

22 |

NHSX brings teams from the Department of Health and Social Care, NHS England and NHS Improvement together into one unit to drive digital transformation and lead policy, implementation and change.

23 |

We are a diverse team with a range of skills and expertise, including clinicians, technologists, policy experts, developers, data scientists and project managers.

24 |

We report directly to the Secretary of State and the Chief Executive of NHS England and NHS Improvement. We are funded through existing budgets.

25 | 26 |

Leadership team

27 |

The leadership team of NHSX are: Matthew Gould (CEO), Simon Eccles, Tara Donnelly, Hadley Beeman, Kathy Hall, Iain O'Neil and Tim Donohoe.

28 | 29 |

Teams that have joined NHSX

30 |

Programme teams that have joined NHSX from NHS England and the Department of Health and Social Care include:

31 | 47 | 48 |

Find out more about the work of many of these teams on the NHS England digital transformation website.

49 | 50 |

Find out what we do

51 | 52 |
53 |
54 | {% endblock %} 55 | -------------------------------------------------------------------------------- /app/views/pages/get-involved.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Get involved" %} 2 | {% set pageDescription = "We want to hear from you. Contact us." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 15 | {% endblock %} 16 | 17 | {% block body %} 18 |
19 |
20 | 21 |

Get involved

22 |

Please get in touch.

23 |

We are keen to hear from everyone who is affected by the technology we use in health and care, from patients to technologists and innovators to carers to clinicians.

24 | 25 |

We are currently seeking views on an NHS Digital Health Technology Standard and our tech plan for health and care.

26 | 27 |

Engaging with digital health innovators

28 | 29 |

On 4 July 2019, NHSX held a listening event for innovators working in healthtech, in partnership with the Accelerated Access Collaborative, the Academic Health Science Network, the Office for Life Sciences and techUK. At the event, we asked the innovators what NHSX's priorities should be. This digital innovators summary report details the key themes that emerged and how we are responding to them.

30 | 31 |

We run monthly surgeries for digital innovators to meet with members of our Digital Innovation Team. These provide us with the opportunity to learn more about you and your product; and for you to ask us for advice on issues, such as scaling within the NHS. If you would like to register for a surgery, please fill in this innovator application form.

32 | 33 |

How to make a Freedom of Information request to NHSX

34 | 35 | 36 |

NHSX is a joint unit between NHS England and Improvement and the Department for Health and Social Care. All requests for information should be directed to NHS England and Improvement in the first instance.

37 |

If your request needs information from the Department of Health and Social Care we will forward on your request. This will not impact the Freedom of Information timeframe.

38 | 39 |

Got something to say? Contact us

40 | 44 | 45 |
46 |
47 | {% endblock %} 48 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # NHSX code of conduct 2 | 3 | ## Our pledge 4 | 5 | In order to create an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of: 6 | 7 | * age 8 | * body size 9 | * disability 10 | * ethnicity 11 | * gender identity and expression 12 | * level of experience 13 | * nationality 14 | * personal appearance 15 | * race 16 | * religion 17 | * sexual identity and orientation 18 | 19 | ## Our standards 20 | 21 | You can contribute to creating a positive environment in many ways. For example you can: 22 | 23 | * use welcoming and inclusive language 24 | * be respectful of differing viewpoints and experiences 25 | * accept constructive criticism gracefully 26 | * focus on what is best for the community 27 | * show empathy towards other community members 28 | 29 | You should not: 30 | 31 | * use sexualised language or imagery 32 | * make unwelcome sexual advances 33 | * troll, and make insulting or derogatory comments 34 | * make personal or political attacks 35 | * harass others, in public or private 36 | * publish others' private information, such as a physical or electronic address, without explicit permission 37 | * engage in any other conduct which could reasonably be considered inappropriate in a professional setting 38 | 39 | ## Our responsibilities 40 | 41 | As project maintainers, we are responsible for clarifying the standards of acceptable behaviour and we are expected to take appropriate and fair corrective action in response to any instances of unacceptable behaviour. 42 | 43 | We have the right and responsibility to remove, edit, or reject: 44 | 45 | * comments 46 | * commits 47 | * code 48 | * wiki edits 49 | * issues 50 | * other contributions that are not aligned to this code of conduct 51 | 52 | We also reserve the right to temporarily or permanently ban any contributor for other behaviours we deem inappropriate, threatening, offensive, or harmful. 53 | 54 | ## Scope 55 | 56 | This code of conduct applies whenever you are representing the project or community. For example you may be: 57 | 58 | * working in a project space online or in the public 59 | * using an official project email address 60 | * posting via an official social media account 61 | * participating in an online or offline event 62 | 63 | Project maintainers may further define and clarify representation of a project. 64 | 65 | ## Enforcement 66 | 67 | You should report any instances of abusive, harassing, or otherwise unacceptable behaviour to the project team at opensource@nhsx.nhs.uk. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain the anonymity of the reporter of an incident. We may post further details of specific enforcement policies separately. 68 | 69 | Project maintainers who do not follow or enforce this code of conduct in good faith may face temporary or permanent consequences. These will be determined by members of the project's leadership. 70 | 71 | ## Attribution 72 | 73 | This code of conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, available at [http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4/) 74 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/tech-plan-for-health-and-care.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Tech plan for health and care" %} 2 | {% set pageDescription = "Tech plan for health and care" %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 16 | {% endblock %} 17 | 18 | {% block body %} 19 |
20 |
21 | 22 |

Tech plan for health and care

23 | 24 |
25 |
26 | 27 |
28 |
29 | 30 |

NHSX is a joint unit bringing together teams from the Department of Health and Social Care and NHS England and NHS Improvement to drive the digital transformation of care.

31 | 32 |

Tech plan for health and care

33 | 34 |

NHSX will be engaging on a tech plan for health and care throughout Spring and Summer 2020.

35 |

Whether you’re an NHS CEO, a care professional, an administrator, a patient, a health charity worker or a developer; we want everyone to have their say on how technology is used to transform health and social care.

36 |

We’ll work openly with you to make sure all the essential building blocks, a clear division of labour and a plan are in place for tech-enabled care.

37 |

Over the next few months we’ll publish information iteratively and in phases as we develop the plan. We’re asking for your views to help shape each section as we go.

38 |

Join in the conversation or email techplan@nhsx.nhs.uk.

39 | 40 |

Policy and programme information

41 | 42 |

Information about pre-existing policy and programmes remains on NHS England's Digital transformation website and Gov.uk.

43 | 44 |
45 | 46 |
47 | 48 | 57 | 58 |
59 |
60 | {% endblock %} 61 | -------------------------------------------------------------------------------- /app/views/sitemap.xml: -------------------------------------------------------------------------------- 1 | 2 | 7 | 8 | https://www.nhsx.nhs.uk/ 9 | 2019-04-08T15:12:04+00:00 10 | 1.00 11 | 12 | 13 | https://www.nhsx.nhs.uk/who-we-are 14 | 2019-04-08T15:12:04+00:00 15 | 0.80 16 | 17 | 18 | https://www.nhsx.nhs.uk/what-we-do 19 | 2019-04-08T15:12:04+00:00 20 | 0.80 21 | 22 | 23 | https://www.nhsx.nhs.uk/how-we-work 24 | 2019-04-08T15:12:04+00:00 25 | 0.80 26 | 27 | 28 | https://www.nhsx.nhs.uk/key-information-and-tools 29 | 2019-04-08T15:12:04+00:00 30 | 0.80 31 | 32 | 33 | https://www.nhsx.nhs.uk/get-involved 34 | 2019-04-08T15:12:04+00:00 35 | 0.80 36 | 37 | 38 | https://www.nhsx.nhs.uk/key-information-and-tools/information-governance-guidance 39 | 2019-04-08T15:12:04+00:00 40 | 0.80 41 | 42 | 43 | https://www.nhsx.nhs.uk/our-policies/accessibility 44 | 2019-04-08T15:12:04+00:00 45 | 0.80 46 | 47 | 48 | https://www.nhsx.nhs.uk/our-policies/cookies-policy 49 | 2019-04-08T15:12:04+00:00 50 | 0.80 51 | 52 | 53 | https://www.nhsx.nhs.uk/our-policies/privacy-policy 54 | 2019-04-08T15:12:04+00:00 55 | 0.80 56 | 57 | 58 | https://www.nhsx.nhs.uk/sitemap 59 | 2019-04-08T15:12:04+00:00 60 | 0.80 61 | 62 | 63 | https://www.nhsx.nhs.uk/our-policies/terms-and-conditions 64 | 2019-04-08T15:12:04+00:00 65 | 0.80 66 | 67 | 68 | https://www.nhsx.nhs.uk/key-information-and-tools/tech-plan-for-health-and-care 69 | 2019-04-08T15:12:04+00:00 70 | 0.64 71 | 72 | 73 | https://www.nhsx.nhs.uk/key-information-and-tools/apps-and-tools 74 | 2019-04-08T15:12:04+00:00 75 | 0.64 76 | 77 | 78 | https://www.nhsx.nhs.uk/key-information-and-tools/data-driven-health-and-care-technology 79 | 2019-04-08T15:12:04+00:00 80 | 0.64 81 | 82 | 83 | https://www.nhsx.nhs.uk/key-information-and-tools/designing-and-building-products-and-services 84 | 2019-04-08T15:12:04+00:00 85 | 0.64 86 | 87 | 88 | https://www.nhsx.nhs.uk/our-policies 89 | 2019-04-08T15:12:04+00:00 90 | 0.64 91 | 92 | 93 | https://www.nhsx.nhs.uk/our-policies/cookie-declaration 94 | 2019-04-08T15:12:04+00:00 95 | 0.64 96 | 97 | 98 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to the NHSX website 2 | 3 | ## Contents 4 | - [About this application](#about-this-application) 5 | - [Running the application locally](#running-the-application-locally) 6 | - [Application structure](#application-structure) 7 | - [Versioning](#versioning) 8 | - [Releases & Deployments](#releases--deployments) 9 | 10 | ## About this application 11 | 12 | The website is a simple [express.js](https://expressjs.com/) application, which uses [nunjucks templating](https://mozilla.github.io/nunjucks/) for the HTML, [Sass](https://sass-lang.com/) for the CSS and JavaScript (with support for ES6) - all of which are compiled to plain HTML, CSS, JavaScript using [npm scripts](https://docs.npmjs.com/misc/scripts). We use various open source third party npm dependencies to achieve this, these are listed within the `package.json` file. 13 | 14 | The website is built using the [NHS.UK frontend library](https://github.com/nhsuk/nhsuk-frontend), so you can use any of the components within the [NHS digital service manual](https://beta.nhs.uk/service-manual/styles-components-patterns). 15 | 16 | ## Running the application locally 17 | 18 | To run the NHSX website locally you'll need to: 19 | 20 | * [set up git](https://help.github.com/articles/set-up-git/) 21 | * [install Node.js](https://nodejs.org/en/) 22 | 23 | We recommend to use the [long-term support (LTS) version of Nodejs](https://nodejs.org/en/download/), rather than the latest beta version. 24 | 25 | Clone the repository `git clone git@github.com:nhsx/nhsx-website.git nhsx-website`, then whilst in the project directory `cd nhsx-website`, install the required npm packages with: `npm install` 26 | 27 | Run the project in development mode `npm run watch` and visit http://localhost:3000. 28 | 29 | ## Application structure 30 | 31 | `.github/` 32 | 33 | GitHub specific files, such templates for pull requests and issues. 34 | 35 | `app/` 36 | 37 | This folder contains all the files you need for the website. 38 | 39 | `app/assets` 40 | 41 | Images, Documents etc 42 | 43 | `app/scripts` 44 | 45 | JavaScript 46 | 47 | `app/styles` 48 | 49 | CSS (Sass) 50 | 51 | `app/views` 52 | 53 | HTML (Nunjucks) 54 | 55 | `node_modules/` (Automatically generated) 56 | 57 | Node package manager modules for third party dependencies. This folder is automatically generated when running `npm install`. Don't manually edit files in this folder as they will be deleted. 58 | 59 | `public/` (Automatically generated) 60 | 61 | Automatically generated compiled files and build assets for the website. Don't manually edit files in this folder as they will be deleted. 62 | 63 | ## Versioning 64 | 65 | Versioning follows a [semver](https://semver.org/) approach, with the version number being in the `package.json` file and a `CHANGELOG.md` file documenting the changes between each release. For best practice, the version number should be bumped and a change log entry added for each release. 66 | 67 | ## Releases & Deployments 68 | 69 | Deployments to the staging environment [https://nhsx-website-stag-uks.azurewebsites.net/](https://nhsx-website-stag-uks.azurewebsites.net/) happen when changes are made to the `master` branch. Pull requests are required to make any changes to the `master` branch, which require at least 1 person to approve the pull request, usually a project maintainer. 70 | 71 | To release to the live environment [https://www.nhsx.nhs.uk/](https://www.nhsx.nhs.uk/), create a new tag and release under the [GitHub releases page](https://github.com/nhsx/nhsx-website/releases). The live environment sits behind a service called Akamai, a firewall and cache, the cache is set to 20 minutes so it will be around 20 minutes until you see the changes after releasing. 72 | -------------------------------------------------------------------------------- /app/views/pages/sitemap.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Sitemap" %} 2 | {% set pageDescription = "A list of pages on this website - with links." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 15 | {% endblock %} 16 | 17 | {% block body %} 18 |
19 |
20 | 21 |

Sitemap

22 | 23 | 67 | 68 |
69 |
70 | {% endblock %} 71 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/index.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Key information and tools" %} 2 | {% set pageDescription = "Links to standards, guidance and support for digital teams." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 15 | {% endblock %} 16 | 17 | {% block body %} 18 |
19 |
20 | 21 |

Key information and tools

22 |

Standards, guidance and support for digital teams.

23 | 24 |
25 |
26 | 27 |
28 |
29 | 30 |

NHSX will define strategy and set standards, for example, on:

31 | 37 |

This part of the website hosts NHSX-owned content and signposts to a range of information and tools on other organisations’ websites so that it’s easy to find all the information you need in one place.

38 | 39 |
40 |
41 | 42 |
43 |
44 | 51 |
52 |
53 | 60 |
61 |
62 |
63 |
64 | 71 |
72 |
73 | 80 |
81 |
82 | 83 |
84 |
85 | 86 |

Blogs and updates

87 | 88 |

Read more about NHSX's work on these 3 blogs.​

89 | 90 | 95 | 96 |

Get involved

97 | 98 |
99 |
100 | {% endblock %} 101 | -------------------------------------------------------------------------------- /app/views/includes/layout.njk: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | {% if pageTitle %}{{ pageTitle }} - NHSX{% else %}NHSX{% endif %} 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | Skip to main content 66 | 67 | {% include 'includes/header.njk' %} 68 | 69 | {% block outerBody %}{% endblock %} 70 | 71 | {% if pageLayout != 'Homepage' %} 72 |
73 |
74 | {% block body %}{% endblock %} 75 |
76 |
77 | {% endif %} 78 | 79 | {% include 'includes/footer.njk' %} 80 | 81 | {% block pageScripts %}{% endblock %} 82 | 83 | 84 | 85 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/information-governance-guidance/index.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Information Governance" %} 2 | {% set pageDescription = "data protection and corona virus advice" %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 16 | {% endblock %} 17 | 18 | {% block body %} 19 |
20 |
21 | 22 |

Information Governance

23 | 24 |
25 |
26 | 27 |
28 |
29 | 30 |

Information governance is all about how to manage and share information appropriately.

31 | 32 |

Covid-19 Information Governance Advice

33 | 34 | 39 | 40 |

Covid-19 Example Privacy Notice

41 |

NHSX continues to work closely with the National Data Guardian (NDG) and Information Commissioner's Office (ICO) to ensure a high level of transparency for patients during this period. This example supplementary privacy notice can be used by organisations to inform patients about the ways information is being used as a result of Covid-19.

42 | 43 |

How data is supporting the Covid-19 response

44 |

You can read current examples of how data is being used to support the Covid-19 response here.

45 | 46 |

The use of mobile devices by patients in hospitals

47 |

This guidance provides advice for patients using mobile devices such as phones, tablets and cameras in acute hospitals. This is particularly important at this time when patients may be isolated from loved ones.

48 | 49 |

COPI Notice - frequently asked questions

50 |

The Secretary of State for Health and Care has issued a range of Notices which require that data is shared for purposes of Covid-19. Read more about COPI Notices and what they mean here.

51 | 52 |

NHSX is building up information governance resources and information which we will make available here as soon as they are ready. In the meantime, if your Data Protection Officer or Caldicott Guardian is unsure of appropriate action to take, you can direct Information Governance questions to the NHSX IG team.

53 | 54 |
55 | 56 |
57 | 58 | 67 | 68 |
69 |
70 | {% endblock %} 71 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/designing-and-building-products-and-services.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Designing and building products and services" %} 2 | {% set pageDescription = "Resources for people developing services and technologies in health and social care." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 16 | {% endblock %} 17 | 18 | {% block body %} 19 |
20 |
21 | 22 |

Designing and building products and services

23 | 24 |
25 |
26 | 27 |
28 |
29 | 30 |

Resources for people developing services and technologies in health and social care.

31 | 32 |

NHS Digital Health Technology Standard consultation

33 |

To improve the way the NHS assesses technologies for use by patients and staff, NHSX is developing a Digital Health Technology Standard. This aims to help developers understand what’s expected of them, and speed up and streamline how health technologies are reviewed and commissioned for use in the NHS. Take a look at the draft standard, and then complete our short survey to ensure a robust, proportionate and attainable standard. The consultation runs until Wednesday 22 April 2020.

34 | 35 |

Data-driven health and care technology

36 |

NHSX wants to make the NHS a world leader in developing ethical and safe data-driven technologies. Find out more information on what AI is, why AI matters, what our AI lab will do and the tools and guidance we have developed to support innovators in this field.

37 | 38 |

Evidence standards framework for digital health technologies

39 |

The National Institute for Health and Care Excellence (NICE) has worked with partners to develop a standards framework to make sure new technologies are clinically effective and offer economic value.

40 | 41 |

NHS developer network

42 |

NHS Digital's NHS developer network includes technical information, software tools, source code and data for developers who are designing and building software for use in health and social care.

43 | 44 |

NHS digital service manual

45 |

The digital service manual helps NHS teams design and build consistent, usable digital services that put people first. It includes:

46 | 54 | 55 |
56 | 57 |
58 | 59 | 68 | 69 |
70 |
71 | {% endblock %} 72 | -------------------------------------------------------------------------------- /app/routes.js: -------------------------------------------------------------------------------- 1 | // External dependencies 2 | const express = require('express'); 3 | 4 | // Initialise router 5 | const router = express.Router(); 6 | 7 | router.get('/', (req, res) => { 8 | res.render('index'); 9 | }); 10 | 11 | router.get('/who-we-are', (req, res) => { 12 | res.render('pages/who-we-are'); 13 | }); 14 | 15 | router.get('/what-we-do', (req, res) => { 16 | res.render('pages/what-we-do'); 17 | }); 18 | 19 | router.get('/how-we-work', (req, res) => { 20 | res.render('pages/how-we-work'); 21 | }); 22 | 23 | router.get('/key-information-and-tools', (req, res) => { 24 | res.render('pages/key-information-and-tools/index'); 25 | }); 26 | 27 | router.get('/key-information-and-tools/apps-and-tools', (req, res) => { 28 | res.render('pages/key-information-and-tools/apps-and-tools'); 29 | }); 30 | 31 | router.get('/key-information-and-tools/designing-and-building-products-and-services', (req, res) => { 32 | res.render('pages/key-information-and-tools/designing-and-building-products-and-services'); 33 | }); 34 | 35 | router.get('/key-information-and-tools/policy-strategy-and-national-programmes', (req, res) => { 36 | res.render('pages/key-information-and-tools/tech-plan-for-health-and-care'); 37 | }); 38 | 39 | router.get('/key-information-and-tools/tech-plan-for-health-and-care', (req, res) => { 40 | res.render('pages/key-information-and-tools/tech-plan-for-health-and-care'); 41 | }); 42 | 43 | router.get('/key-information-and-tools/blogs-and-updates', (req, res) => { 44 | res.render('pages/key-information-and-tools'); 45 | }); 46 | 47 | router.get('/key-information-and-tools/information-governance-guidance', (req, res) => { 48 | res.render('pages/key-information-and-tools/information-governance-guidance/index'); 49 | }); 50 | 51 | router.get('/key-information-and-tools/information-governance-guidance/health-care-professionals', (req, res) => { 52 | res.render('pages/key-information-and-tools/information-governance-guidance/health-care-professionals'); 53 | }); 54 | 55 | router.get('/key-information-and-tools/information-governance-guidance/social-care-sector', (req, res) => { 56 | res.render('pages/key-information-and-tools/information-governance-guidance/social-care-sector'); 57 | }); 58 | 59 | router.get('/key-information-and-tools/information-governance-guidance/ig-professionals', (req, res) => { 60 | res.render('pages/key-information-and-tools/information-governance-guidance/ig-professionals'); 61 | }); 62 | 63 | router.get('/key-information-and-tools/information-governance-guidance/COPI-notice-FAQs', (req, res) => { 64 | res.render('pages/key-information-and-tools/information-governance-guidance/COPI-notice-FAQs'); 65 | }); 66 | 67 | router.get('/key-information-and-tools/information-governance-guidance/how-data-is-supporting-covid19', (req, res) => { 68 | res.render('pages/key-information-and-tools/information-governance-guidance/how-data-is-supporting-covid19'); 69 | }); 70 | 71 | router.get('/key-information-and-tools/information-governance-guidance/use-of-mobile-devices-by-patients', (req, res) => { 72 | res.render('pages/key-information-and-tools/information-governance-guidance/use-of-mobile-devices-by-patients'); 73 | }); 74 | 75 | router.get('/key-information-and-tools/data-driven-health-and-care-technology', (req, res) => { 76 | res.render('pages/key-information-and-tools/data-driven-health-and-care-technology'); 77 | }); 78 | 79 | router.get('/get-involved', (req, res) => { 80 | res.render('pages/get-involved'); 81 | }); 82 | 83 | router.get('/our-policies', (req, res) => { 84 | res.render('pages/our-policies/index'); 85 | }); 86 | 87 | router.get('/our-policies/cookies-policy', (req, res) => { 88 | res.render('pages/our-policies/cookies-policy'); 89 | }); 90 | 91 | router.get('/our-policies/cookie-declaration', (req, res) => { 92 | res.render('pages/our-policies/cookie-declaration'); 93 | }); 94 | 95 | router.get('/our-policies/cookie-confirmation', (req, res) => { 96 | res.render('pages/our-policies/cookie-confirmation'); 97 | }); 98 | 99 | router.get('/our-policies/terms-and-conditions', (req, res) => { 100 | res.render('pages/our-policies/terms-and-conditions'); 101 | }); 102 | 103 | router.get('/our-policies/privacy-policy', (req, res) => { 104 | res.render('pages/our-policies/privacy-policy'); 105 | }); 106 | 107 | router.get('/our-policies/accessibility', (req, res) => { 108 | res.render('pages/our-policies/accessibility'); 109 | }); 110 | 111 | router.get('/sitemap', (req, res) => { 112 | res.render('pages/sitemap'); 113 | }); 114 | 115 | router.get('/manifest.json', (req, res) => { 116 | res.set({ 'Content-Type': 'application/json' }); 117 | res.render('manifest'); 118 | }); 119 | 120 | router.get('/sitemap.xml', (req, res) => { 121 | res.set({ 'Content-Type': 'application/xml' }); 122 | res.render('sitemap.xml'); 123 | }); 124 | 125 | router.get('/robots.txt', (req, res) => { 126 | res.set('text/plain'); 127 | res.render('robots.txt'); 128 | }); 129 | 130 | router.use((req, res) => { 131 | res.statusCode = 404; 132 | res.render('pages/404'); 133 | }); 134 | 135 | module.exports = router; 136 | -------------------------------------------------------------------------------- /app/views/pages/our-policies/cookies-policy.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Cookies" %} 2 | {% set pageDescription = "We use 3 main types of cookie on our website. You can choose which cookies you're happy for us to use." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 16 | {% endblock %} 17 | 18 | {% block body %} 19 |
20 |
21 | 22 |
23 | 24 |

{{ pageTitle }}

25 | 26 |

What are cookies?

27 |

Cookies are files saved on your phone, tablet or computer when you visit a website.

28 |

They store information about how you use the website, such as the pages you visit.

29 |

Cookies are not viruses or computer programs. They are very small so do not take up much space.

30 | 31 |

How we use cookies

32 |

We use cookies to:

33 |
    34 |
  • make our website work, for example by keeping it secure and fast
  • 35 |
  • measure how you use our website, such as which pages you visit (anonymously)
  • 36 |
37 | 38 |
39 | 40 |
41 | 42 | 43 | List of cookies that make our website work 44 | 45 | 46 |
47 | 48 |
49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 |
Cookie names and purposes
Cookie namePurposeExpiry
ARRAffinityHelps our website work faster.When you close the browser
nhsuk-cookie-consentRemembers if you used our cookies bannerWhen you close the browser (if you do not use the banner) or 1 year (if you use the banner)
71 |
72 | 73 |
74 |
75 | 76 |
77 | 78 |

Change your cookie settings

79 |

Some cookies, like those used to measure how you use our website, are not needed for our website to work.

80 |

These cookies can help us make our website better, but we'll only use them if you say it's OK.

81 | 82 | 91 | 92 |

How we use the information we collect

93 |

To find out how we collect, store and use information about you or your visit, see our privacy policy.

94 | 95 |
96 | 97 |
98 |

Updated: January 2020

99 |
100 | 101 |
102 |
103 | {% endblock %} 104 | -------------------------------------------------------------------------------- /app/views/pages/what-we-do.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "What we do" %} 2 | {% set pageDescription = "NHSX has been created to give staff and citizens the technology they need." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 15 | {% endblock %} 16 | 17 | {% block body %} 18 |
19 |
20 | 21 |

What we do

22 |

NHSX is leading the largest digital health and social care transformation programme in the world. With investment of more than £1 billion pounds a year nationally and a significant additional spend locally, NHSX has been created to give staff and citizens the technology they need.

23 |

NHSX will deliver the Health Secretary’s Tech Vision, building on the NHS Long Term Plan. We will speed up the digital transformation of the NHS and social care. We have set ourselves five missions, which are focused on how we can make things better for patients and staff. These are:

24 | 31 | 32 |

Our responsibilities

33 | 34 |

Coordination and consistency

35 | 40 | 41 |

Setting standards

42 | 46 | 47 |

Driving implementation

48 | 54 | 55 |

Radical innovation

56 | 59 | 60 |

Common technologies and services

61 | 65 | 66 |

Reforming procurement

67 | 70 | 71 |

Cyber policy

72 | 75 | 76 |

Digital capability

77 | 80 | 81 |

Governance

82 | 86 | 87 |

Find out how we work

88 | 89 |
90 |
91 | {% endblock %} 92 | -------------------------------------------------------------------------------- /app/views/index.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Home" %} 2 | {% set pageDescription = "NHSX - a new unit driving forward the digital transformation of health and social care." %} 3 | {% set pageLayout = "Homepage" %} 4 | 5 | {% extends 'includes/layout.njk' %} 6 | 7 | {% block outerBody %} 8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |

Driving forward the digital transformation of health and social care

16 | 17 |
18 |
19 |
20 |
21 |
22 |
23 | 24 |
25 | 71 |
72 | 73 |
74 |
75 |
76 |
77 |

Video

78 |
79 |
80 |
81 |

Introducing NHSX

82 |

Matt Hancock explains how NHSX will transform the NHS.

83 |
84 |
85 |
86 | 87 |
88 |

Get involved

89 |

Please get in touch.

90 |

We are keen to hear from everyone who is affected by the technology we use in health and care, from patients to technologists to carers to clinicians.

91 | 95 | 96 | 106 | 107 |
108 |
109 |
110 |
111 |
112 | {% endblock %} 113 | -------------------------------------------------------------------------------- /app/views/includes/header.njk: -------------------------------------------------------------------------------- 1 | 80 | -------------------------------------------------------------------------------- /app/views/pages/our-policies/cookie-declaration.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Details about the cookies we use" %} 2 | {% set pageDescription = "This is a list of all the cookies we use on the NHSX website." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 17 | {% endblock %} 18 | 19 | {% block body %} 20 |
21 |
22 | 23 |
24 |

{{ pageTitle }}

25 |

Let us know which cookies we can use. We'll use a cookie to save your settings.

26 |
27 | 28 |
29 |

Cookies that measure website use

30 |

These cookies store anonymous information about how you use our website, such as what you click on.

31 |
32 | 33 |
34 | 35 | 36 | List of cookies that measure website use 37 | 38 | 39 |
40 | 41 |
42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 |
Cookie names and purposes
Cookie namePurposeExpiry
_gaUsed by Google Analytics. Tells us how you use our website.2 years
_gidUsed by Google Analytics. Sets a unique ID for your session to help tell us how you use our website.1 day
_gatUsed by Google Analytics. Helps stop Google Analytics web servers crashing when collecting information on how you use our website.1 min
69 |
70 | 71 |
72 |
73 | 74 |
75 | 76 | 92 | 93 | 94 | Save my cookie settings 95 | 96 | 97 |
98 | 99 |
100 |

Updated: January 2020

101 |
102 | 103 |
104 |
105 | {% endblock %} 106 | 107 | {% block pageScripts %} 108 | 125 | {% endblock %} 126 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/apps-and-tools.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Apps and tools for patient care" %} 2 | {% set pageDescription = "New digital apps and tools are empowering people to take control of their health and improving patient care." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 16 | {% endblock %} 17 | 18 | {% block body %} 19 |
20 |
21 | 22 |

Apps and tools for patient care

23 | 24 |
25 |
26 | 27 |
28 |
29 | 30 |

New digital apps and tools are empowering people to take control of their health and improving patient care.

31 | 32 |

Our roadmap

33 |

The Empower the Person roadmap sets out what's available now, along with delivery milestones for meeting our aim of giving people and patients the digital tools and information they need to better manage their health, wellbeing and care. (Links to an external website. Please see Accessibility Statement)

34 | 35 |

Where we are working

36 |

You can see where we are working on Empower the Person programmes, plotted on our interactive (beta) map.

37 | 38 |

Join our community

39 |

Join our Empower the Person community of interest to access presentations, latest updates and discussion forums. Log in using your nhs.net email. If you don’t have one, email england.digitalhealth@nhs.net for access.

40 | 41 |

Our digital services for patients at a glance

42 | 43 |

The NHS website

44 |

The NHS website (nhs.uk) gives the public information about conditions, treatments, medicines, NHS services and more.

45 | 46 |

NHS App

47 |

The NHS App is a simple and secure way for people to access a range of NHS services on their smartphone or tablet.

48 | 49 |

NHS login

50 |

The NHS login makes it easier and quicker for people to see their personal health information online. In future, they’ll use it to access other health and social care services online.

51 | 52 |

NHS Apps Library

53 |

The apps library on nhs.uk helps patients and the public find tools to help them manage and improve their health.

54 | 55 |

GP IT Futures

56 |

A new GP IT Futures framework will replace the contractual GP System of Choice framework, to supply IT systems and services to GP Practices in England.

57 | 58 |

Digital first and online consultations programme

59 |

Supporting the move towards a digital first approach, where patients can easily access the advice, support and treatment they need using digital and online tools, including online consultations.

60 | 61 |

NHS wifi

62 |

NHS WiFi is working to make sure everyone can access free, secure and consistent WiFi services at NHS sites across England.

63 | 64 |

Examples of how technology can improve patient care

65 | 66 |
67 |
68 |
69 |

MIRA rehab

70 |

A software platform that turns physiotherapy exercises into video games and helps with injury rehabilitation.

71 |
72 |
73 | 74 |
75 |
76 |
77 |

WaitLess app

78 |

An app that combines waiting times at urgent care centres with up-to-the-minute travel information to help patients decide where to go for faster treatment for minor injuries.

79 |
80 |
81 | 82 |
83 | 84 |
85 | 86 | 95 | 96 |
97 |
98 | {% endblock %} 99 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/information-governance-guidance/ig-professionals.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Information Governance advice for IG Professionals" %} 2 | {% set pageDescription = "data protection and corona virus advice" %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 17 | {% endblock %} 18 | 19 | {% block body %} 20 |
21 |
22 | 23 |

Covid-19 Information Governance advice for IG Professionals

24 | 25 |
26 |
27 | 28 |
29 |
30 | 31 |

Legal considerations

32 |

The legal framework has flexibility when it comes to the processing of information. Information relating to the Covid-19 outbreak should be shared as needed to support individual care and to help tackle the disease through research and planning during the Covid-19 situation. The focus should be to ensure the risk of damage, harm or distress being caused to individual patients and service users is kept to a minimum and that data is only processed where it is necessary to do so and in an appropriate manner.

33 | 34 |

Confidential Patient Information/Common law duty of confidentiality

35 |

The Secretary of State for Health and Social Care has directed NHS Digital to collect and analyse data from providers and other organisations involved in managing the Covid-19 response and then disseminate information to other bodies for the purpose of planning and managing the response. NHS England and NHS Improvement have been given legal notice to support the processing and sharing of information to help the Covid-19 response under Health Service Control of Patient Information Regulations 2002.

36 |

Individual healthcare organisations, Arms Length Bodies (except NHS Digital and NHS England and NHS Improvement which have been separately notified) and Local Authorities have now also been given legal notice under the same regulations to support the processing and sharing of information to help the Covid-19 response. The notice is available here.

37 |

This is to ensure that confidential patient information can be used and shared appropriately and lawfully for purposes related to the Covid-19 response.

38 |

These Notices will be reviewed on or before 30 September 2020 and may be extended by further notice in writing. If no further notice is sent they will expire on 30 September 2020.

39 |

Data controllers are still required to comply with relevant and appropriate data protection standards and to ensure within reason that they operate within statutory and regulatory boundaries.

40 | 41 |

General Data Protection Regulation (GDPR)

42 |

The GDPR allows information to be shared for individual care, planning and research. Where health and care information (which would be classed as special category data) is shared for either individual care or to help tackle the disease through research and planning then the relevant Article 6 conditions (official authority, compliance with a legal obligation, public interest and on occasion vital interests) and Article 9 conditions (substantial public interest, the delivery of health and care, vital interests or for public health purposes and scientific research) should be relied on as applicable to the situation.

43 |

The principles (Article 5 of GDPR) should continue to be followed. They form a framework of good information management with the key criteria enabling justification of actions taken. If you are not certain of an issue, such as a relevant retention time, then the law is flexible enough to allow you to revisit the issue once the answer becomes clearer.

44 |

If your organisation is going to process personal/confidential patient information in ways not covered by an existing Data Protection Impact Assessment (DPIA), e.g. using videoconferencing for consultations, then a short high level DPIA should be carried out. The DPIA should set out the activity being proposed; the data protection risks; whether the proposed activity is necessary and proportionate; the mitigating actions that can be put in place and a plan or confirmation that mitigation has been put in place. DPIAs are scalable, and in some instances this might not take more than a couple of pages. The ICO has produced guidance on carrying out DPIAs and a template that you can refer to. You should also update your privacy notice where data is being processed in new ways.

45 | 46 |

Further information

47 |

You can direct further Information Governance questions to the NHSX IG team.

48 | 49 |
50 | 51 |
52 | 53 | 61 | 62 |
63 |
64 | {% endblock %} 65 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/information-governance-guidance/social-care-sector.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Information Governance for the social care sector" %} 2 | {% set pageDescription = "data protection and corona virus advice" %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 17 | {% endblock %} 18 | 19 | {% block body %} 20 |
21 |
22 | 23 |

Covid-19 Information Governance advice for the social care sector

24 | 25 |
26 |
27 | 28 |
29 |
30 |

It is essential that during the Covid-19 outbreak carers, social care professionals, and clinicians are able to talk to each other and to the people they care for. You should be mindful of handling people’s information securely, but you need to make sure that you are using the communication available to you (phone, email etc) to clearly and quickly communicate with your local GPs, hospitals, community health services, local authorities, voluntary sector, pharmacists, and health services.

31 |

Under the Health and Social Care (Safety and Quality) Act 2015, it is legal to share information to support a person’s care. For Covid-19, carers, local authorities and social care providers, including care homes and domiciliary organisations, should be sharing information with the people they care for and their local GPs, community health services, hospitals, local authorities, voluntary sector, pharmacists, and health services.

32 |

Use your common sense to do the best thing for your service users and people in your care. The Information Commissioner has said that she can not envisage taking action against a health or care professional clearly trying to act to save lives.

33 |

The important thing, as always, is to consider what type of information you are sharing and with whom. As much as possible limit the use of people’s personal/confidential information.

34 | 35 |

How you can share information

36 | 37 |

Email and Data Security and Protection Toolkit (DSPT)

38 |

To help communication for Covid-19, Data Security and Protection Toolkit compliance requirements are being relaxed and NHSmail roll-out sped up. For all who have, or get, NHSMail accounts MS Teams access will be switched on.

39 |

NHSX, NHS England and NHS Digital are working to make the process for accrediting secure email services, easier and faster. It is important that social care is able to access secure email for Covid-19 as quickly as possible.

40 | 41 |

Mobile Messaging

42 |

It is absolutely fine to use mobile messaging to communicate with colleagues and people in your care as needed. It is also fine to use commercial, off-the-shelf applications such as WhatsApp and Telegram, where there is no practical alternative and the benefits outweigh the risk.

43 |

The important thing, as always, is to consider what type of information you are sharing and with whom. As much as possible limit the use of people’s personal/confidential information.

44 | 45 |

Videoconferencing

46 |

We encourage the use of videoconferencing to carry out consultations with people in your care, or meetings with colleagues across social care and health services. This could help to reduce the spread of Covid-19. It is fine to use video conferencing tools such as Skype, WhatsApp or Facetime as well as commercial products designed specifically for this purpose.

47 |

The consent of the person you care for may be implied by them accepting the invite and entering the consultation. But you should safeguard people’s personal/confidential information in the same way you would with any other consultation.

48 | 49 |

Homeworking

50 |

You may well need to work from home – for example, when self-isolating without symptoms. 51 |

If you are working from home and using your own equipment you should check that your internet access is secure (e.g. use a Virtual Private Network and/or if possible avoid public wi-fi) and that any security features are in use.

52 |

If you are taking any physical documents home with you that contain people’s personal/confidential information, you should also ensure the security of these documents at your home and when travelling.

53 | 54 |

Using Your Own Device

55 |

You can use your own devices to support video conferencing for consultations, mobile messaging and home working where there is no practical alternative.

56 |

Reasonable steps to ensure this is safe include: setting a strong password; using secure channels to communicate e.g. tools/apps that use encryption; and not storing people’s personal/confidential information on the device unless absolutely necessary and appropriate security is in place.

57 |

Information should be safely transferred to the appropriate health and care record as soon as it is practical to do so.

58 | 59 |

Further information

60 |

If your Data Protection Officer or Caldicott Guardian is unsure of appropriate action to take, you can direct Information Governance questions to the NHSX IG team.

61 |
62 | 63 |
64 | 65 | 73 | 74 |
75 |
76 | {% endblock %} 77 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/information-governance-guidance/health-care-professionals.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Information Governance for health and care professionals" %} 2 | {% set pageDescription = "data protection and corona virus advice" %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 17 | {% endblock %} 18 | 19 | {% block body %} 20 |
21 |
22 | 23 |

Covid-19 Information Governance advice for health and care professionals

24 | 25 |
26 |
27 | 28 |
29 |
30 |

The health and social care system is going to face significant pressures due to the Covid-19 outbreak. In the current circumstances it could be more harmful not to share health and care information than to share it. The Information Commissioner has assured NHSX that she cannot envisage a situation where she would take action against a health and care professional clearly trying to deliver care. You can read the statement from the Information Commissioner's Office, alongside their Q&A resource. Health regulators have also published a joint statement.

31 |

Information is critical to support health and social care services, protect public health, research, monitor, track and manage the outbreak and incidence of exposure. A new notice has been issued using existing regulations which ensures that when you use confidential patient information for purposes relating to covid-19, you can be confident that you are doing so lawfully.

32 |

We will need to work in different ways from usual and the focus should be what information you share and who you share it with, rather than how you share it. The following advice sets out some of the tools that you can use to support individual care, share information and communicate with colleagues during this time. This includes communications tools where data is stored outside of the UK.

33 |

This advice is endorsed by the Information Commissioner’s Office, the National Data Guardian and NHS Digital.

34 | 35 |

Mobile Messaging

36 |

It is absolutely fine to use mobile messaging to communicate with colleagues and patients/service users as needed. It is also fine to use commercial, off-the-shelf applications such as WhatsApp and Telegram where there is no practical alternative and the benefits outweigh the risk.

37 |

The important thing, as always, is to consider what type of information you are sharing and with whom. And as much as possible limit the use of personal/confidential patient information.

38 | 39 | 40 |

Videoconferencing

41 |

We encourage the use of videoconferencing to carry out consultations with patients and service users. This could help to reduce the spread of Covid-19. It is fine to use video conferencing tools such as Skype, WhatsApp, Facetime as well as commercial products designed specifically for this purpose.

42 |

The consent of the patient or service user is implied by them accepting the invite and entering the consultation. But you should safeguard personal/confidential patient information in the same way you would with any other consultation.

43 | 44 |

Homeworking

45 |

You may well need to work from home - for example, when self-isolating without symptoms.

46 |

If you are working from home and using your own equipment you should check that your internet access is secure (e.g. use a Virtual Private Network and/or if possible avoid public wi-fi) and that any security features are in use.

47 |

If you are taking any physical documents home with you that contain personal/confidential patient information, you should also ensure the security of these documents at your home and when travelling.

48 | 49 |

Using Your Own Device

50 |

You can use your own devices to support video conferencing for consultations, mobile messaging and home working where there is no practical alternative.

51 |

Reasonable steps to ensure this is safe include: setting a strong password; using secure channels to communicate e.g. tools/apps that use encryption; and not storing personal/confidential patient information on the device unless absolutely necessary and appropriate security is in place.

52 |

Information should be safely transferred to the appropriate health and care record as soon as it is practical to do so.

53 | 54 |

Communication between health and social care colleagues

55 |

It is essential that during the Covid-19 outbreak health and social care professionals are able to talk to each other. You will need to share appropriate information about the people in your care including with social care, where possible using secure mail, NHSmail and MS Teams. Where these tools aren’t available you should use this guidance to suggest ways that you can speak to your colleagues.

56 | 57 |

Further information

58 |

If your Data Protection Officer or Caldicott Guardian is unsure of appropriate action to take, you can direct Information Governance questions to the NHSX IG team.

59 | 60 |
61 | 62 |
63 | 64 | 72 | 73 |
74 |
75 | {% endblock %} 76 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/information-governance-guidance/COPI-notice-FAQs.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "COPI Notice - Frequently Asked questions" %} 2 | {% set pageDescription = "COPI Notice - Frequently Asked questions" %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 17 | {% endblock %} 18 | 19 | {% block body %} 20 |
21 |
22 | 23 |

COPI Notice - Frequently Asked Questions

24 | 25 |
26 |
27 | 28 |
29 |
30 | 31 |

Why are you doing this?

32 |

The health and care system is facing an unprecedented challenge and we want to ensure that healthcare organisations, Arms Length Bodies and local authorities are able to process and share the data they need to respond to Covid-19 for example by treating and caring for patients and those at risk, managing the service and identifying patterns and risks.

33 |

As part of a wider package of measures, including guidance and directions, the Secretary of State has issued a range of Notices which require that data is shared for purposes of Covid-19. They will help give healthcare organisations and local authorities the confidence to share the data needed to respond to Covid-19.

34 | 35 |

What are COPI notices?

36 |

The Health Service (Control of Patient Information) Regulations 2002 allow the processing of Confidential Patient Information (CPI) for specific purposes. Regulation 3 provides for the processing of CPI in relation to communicable diseases and other threats to public health and in particular allows the Secretary of State to require organisations to process CPI for purposes related to communicable diseases.

37 |

The Secretary of State has issued four of these notices requiring NHS Digital, NHS England & Improvement, all healthcare organisations, Arms Length Bodies, Local Authorities and GPs (including a specific requirement related to the UK Biobank project) to process CPI for the purposes related to communicable diseases.

38 | 39 |

What does processing mean?

40 |

Under COPI Regulations 2002, processing means:

41 | 48 | 49 |

What purposes are covered?

50 |

The COPI notices cover a range of purposes related to diagnosing, managing, and controlling the spread of communicable diseases. For Covid-19 purposes this could include but is not limited to:

51 | 57 | 58 |

What type of data is covered?

59 |

The notice covers confidential patient information so any data regardless of its identifiability, which is being used for the purposes set out above is covered. It will all be treated in line with the principles of GDPR i.e. fairly, lawfully and securely.

60 | 61 |

How long will the notices be in place?

62 |

These Notices will be reviewed on or before 30 September 2020 and may be extended by further notice in writing. If no further notice is sent, they will expire on 30 September 2020. This means that processing of data will be stopped and information shared for the specific purpose of Covid-19 will be deleted.

63 | 64 |

What if I’m unsure about sharing data?

65 |

If you are unsure about the appropriate action to take, please contact England.IGPolicyTeam@nhs.net.

66 | 67 |

What about GDPR?

68 |

Data controllers are still required to comply with relevant and appropriate data protection standards and to ensure within reason that they operate within statutory and regulatory boundaries. The General Data Protection Regulations (GDPR) allow health and care data to be used as long as one or more of the conditions under Article 6 and Article 9 are met. There are conditions under both Articles which can be relied on for the sharing of health and care data – including ‘the care and treatment of patients’ and ‘public health’. We would expect any organisation to disseminate information within legal requirements set out under GDPR.

69 | 70 |

What if I have opted-out of my data being used (National Data Opt-Out)?

71 |

The national data opt-out does not apply to disclosure of confidential patient information if it is being used to protect public health, for example to:

72 | 78 |

Read a full explanation of the lawful basis of such disclosures in 6.2:Communicable diseases and risks to public health in the operational policy guidance document.

79 | 80 |
81 | 82 |
83 | 84 | 92 | 93 |
94 |
95 | {% endblock %} 96 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/information-governance-guidance/use-of-mobile-devices-by-patients.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "The use of mobile devices by patients in hospitals" %} 2 | {% set pageDescription = "The use of mobile devices by patients in hospitals" %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 17 | {% endblock %} 18 | 19 | {% block body %} 20 |
21 |
22 | 23 |

The Use of Mobile Devices by Patients in Hospitals (e.g. Phones, Tablets and Cameras)

24 | 25 |
26 |
27 | 28 |
29 |
30 | 31 |

Background

32 |

This guidance provides advice for patients using mobile devices such as phones, tablets and cameras in acute hospitals. This is particularly important during the Covid-19 period when patients may be isolated from loved ones.

33 |

During this time you should follow the advice of the Government and the NHS on washing your hands more regularly than usual and take appropriate precautions to ensure any mobile device you use is regularly cleaned.

34 |

This guidance has been endorsed by the Health and Care Information Governance Panel, which includes the National Data Guardian and Information Commissioner's Office.

35 | 36 |

I’m a patient or service user - what does this mean for me?

37 |

We want you to use your mobile device in hospital, it’s an important way of keeping in touch and making use of online resources like the NHS app.

38 |

It’s important that when you use your mobile device in hospital you’re careful not to:

39 | 45 | 46 |

I work in a health and care organisation - what does this mean for me?

47 |

This guidance specifically considers the use of mobile devices by patients and visitors. The same principles apply to staff using a personal mobile device but the purpose of this guidance is to help you support patients’ use of mobile devices.

48 |

There are many benefits for patients that arise from encouraging them to use mobile devices:

49 | 54 | 55 |

Mobile devices can be used safely in hospitals. You can support patients to use their mobile devices appropriately as follows:

56 | 62 | 63 |

I’m an IG professional - what does this mean for me?

64 |

Each organisation is responsible for stating its own policies on the use of mobile devices by staff, patients and visitors. However, this guidance aims to promote a consistent and positive approach to using mobile devices across NHS Trusts that will underpin these policies and assist with the management of risks.

65 |

Trusts should review their policies relating to mobile device use by staff, patients and visitors, including phones, tablets, cameras, video and audio recording devices. The following should be considered:

66 | 72 | 73 |
74 | 75 |
76 | 77 | 85 | 86 |
87 |
88 | {% endblock %} 89 | -------------------------------------------------------------------------------- /app/views/pages/how-we-work.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "How we work" %} 2 | {% set pageDescription = "NHSX's culture and values." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 15 | {% endblock %} 16 | 17 | {% block body %} 18 |
19 |
20 | 21 |

How we work

22 |

Our culture and values.

23 | 31 | 32 |

How we work with digital innovators

33 |

We want the very best digital solutions for citizens and for NHS and social care staff. We know that technology can help us meet our most pressing strategic challenges – improving outcomes, addressing workforce shortages and increasing productivity – this is articulated by NHSX’s five missions.

34 |

We also want to support a thriving digital ecosystem, in which both smaller innovators and larger companies can flourish. We believe that this will bring the best solutions and most choice for patients and staff – as long as systems are built to the same open standards and are interoperable with each other.

35 |

We expect digital innovators who seek to work with the NHS to:

36 |
    37 |
  1. Abide by our guiding principles
  2. 38 |
  3. Be open and transparent
  4. 39 |
  5. Leverage best value for the NHS
  6. 40 |
41 | 42 |

Abide by our guiding principles

43 |

Better use of data between the NHS and partners has the potential to improve diagnosis, treatment, experience of care, efficiency of the system and overall outcomes for the people at the heart of the NHS, public health and the wider healthcare system.

44 |

It must be done in a way which is safe, ethical, evidenced and transparent. People need to know that data about them is being used to develop and test healthcare solutions, and that their privacy and rights are safeguarded. For this reason, and to enable partnerships between the NHS and partners to thrive, the government has published five guiding principles.

45 |

Digital innovators working with NHSX must abide by these guiding principles, the code of conduct for data-driven health and care technology, the Caldicott Principles and the data ethics framework.

46 |

In addition, digital innovators must be in line with all other relevant legislation including the Data Protection Act 2018, Common Law and the Human Rights Act and will need to complete the Data Security and Privacy toolkit. Agreements on data must not be perpetual nor exclusive.

47 | 48 |

Be open and transparent

49 |

We seek to work in the open as far as possible and therefore require those who work with us to:

50 | 58 | 59 |

Leverage best value for the NHS

60 | 68 | 69 |

Find key information and tools

70 | 71 |
72 |
73 | {% endblock %} 74 | -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | # Changelog 2 | 3 | ## 2.10.0 - 08/04/2020 4 | - New page with COPI notice FAQs 5 | - New page on how data is supporting Covid-19 response 6 | - New page on how mobile devices are supporting patients in hospitals 7 | - Example privacy notice PDF included 8 | - Update Information Governance hub page with links to new pages 9 | 10 | ## 2.9.0 - 24/03/2020 11 | 12 | - Break Information Governance into separate pages 13 | 14 | ## 2.8.0 - 20/03/2020 15 | 16 | - Add further guidance for the Information Governance 17 | - Update package dependencies to latest versions 18 | 19 | ## 2.7.0 - 16/03/2020 20 | 21 | - New Information Governance guidance 22 | - Update package dependencies to latest versions 23 | 24 | ## 2.6.0 - 04/03/2020 25 | 26 | - Add new content on How we work with digital innovators 27 | - Grammatical fixes to the tech plan for health and care page 28 | - Update package dependencies to latest versions 29 | - Create a new page for Information Governance guidance 30 | - Move blog posts to the Key information and tools index page 31 | - Change the file path of the favicons to prevent them caching 32 | 33 | ## 2.5.0 - 27/02/2020 34 | 35 | - Add new tech plan for health and care page content 36 | - Add the NHS digital health technology standard draft 37 | 38 | ## 2.4.0 - 19/02/2020 39 | 40 | - Added guidance about Freedom of Interest requests 41 | - Update package dependencies to latest versions including latest NHS.UK frontend (3.0.3) 42 | 43 | ## 2.3.0 - 28/01/2020 44 | 45 | - Content updates across missions, who are are and Artificial Intelligence pages 46 | - Update package dependencies to latest versions 47 | 48 | ## 2.2.0 - 13/01/2020 49 | 50 | - Simplify the Azure Pipelines CI/CD configuration for a smoother and quicker release process 51 | - Update package dependencies to latest versions 52 | - Use the latest cookie logic and content pages 53 | - Self host the cookie banner and change content to relate to the NHSX website 54 | 55 | ## 2.1.2 - 17/12/2019 56 | 57 | - Update package dependencies to latest versions 58 | 59 | ## 2.1.1 - 11/11/2019 60 | 61 | - Update the leadership team members 62 | - Update content on the Digital Innovation Team 63 | - Update package dependencies to latest versions 64 | - Install the latest version of NHS.UK frontend with new focus styles 65 | 66 | ## 2.1.0 - 30/10/2019 67 | 68 | - New content for Data-driven health and care technology and Artificial Intelligence 69 | - Update package dependencies to latest versions 70 | 71 | ## 2.0.5 - 15/10/2019 72 | 73 | - Content updates to "get involved" and "Apps and tools for patient care" 74 | - Added a pdf report to assets, linked to from get involved 75 | 76 | ## 2.0.4 - 24/09/2019 77 | 78 | - Use the latest version of the NHS.UK frontend library (v2.3.1) 79 | - Update package dependencies to latest versions 80 | - Anonymize IP addresses in Google Analytics 81 | - Implement the latest version of the cookie consent solution 82 | - Remove bottom margin on the hero heading 83 | 84 | ## 2.0.3 - 19/08/2019 85 | 86 | - Add content to support new information governance survey 87 | - Updated the leadership team content 88 | - Update package dependencies to latest versions 89 | 90 | ## 2.0.2 - 01/07/2019 91 | 92 | - Content updates across the website for the 1st July launch 93 | - Use correct value for the manifest display property 94 | - Update to NHS.UK frontend v2.2.0 and use the new favicons 95 | - Update package dependencies to latest versions 96 | 97 | ## 2.0.1 - 17/06/2019 98 | 99 | - Self host the cookie consent solution ([Issue 38](https://github.com/nhsx/nhsx-website/issues/38)) 100 | - Add watch task to compile assets when there are any changes ([Issue 40](https://github.com/nhsx/nhsx-website/issues/40)) 101 | - Compile CSS before running the SCSS watch task 102 | 103 | ## 2.0.0 - 17/06/2019 104 | 105 | - Changed cookie policy page rules to only accept cookies when settings are changed and saved 106 | - Changed cookie policy page to keep same url when settings save and confirmation banner shows 107 | - Update package dependencies to latest versions 108 | - Use YouTubes privacy-enhanced mode to stop YouTube setting cookies on the website 109 | 110 | ## 1.1.2 - 12/06/2019 111 | 112 | - Import all the NHS.UK frontend library components for future development 113 | - Update package dependencies to latest versions 114 | - Changed title and description of eRedbook to digital red books 115 | - Add code of conduct and contributing guidelines documentation 116 | 117 | ## 1.1.1 - 17/05/2019 118 | 119 | - Update NHSX survey on AI in health and care link text 120 | - Update package dependency lock file to fix outdated dependencies 121 | - Remove innovation and genomics from the teams joining NHSX list 122 | 123 | ## 1.1.0 - 08/05/2019 124 | 125 | - Add content for the NHSX survey on AI in health and care to the designing and building products and services page 126 | - Update package dependencies to latest versions 127 | 128 | ## 1.0.3 - 30/04/2019 129 | 130 | - Amend heading structure on various pages so there is no jumping from a H1 to a H3 131 | - Add title attribute to iframe video on the homepage 132 | - Selectively import NHS.UK frontend component scss files to reduce the compiled CSS file size 133 | 134 | ## 1.0.2 - 15/04/2019 135 | 136 | - Update package dependencies including latest version (2.1.0) of the NHS.UK frontend 137 | - Add robots.txt and sitemap.xml ([Issue 14](https://github.com/nhsx/nhsx-website/issues/14)) 138 | 139 | ## 1.0.1 - 05/04/2019 140 | 141 | - Reorder the asset `preconnect` and remove unneeded `dns-prefetch` ([Issue 9](https://github.com/nhsx/nhsx-website/issues/9)) 142 | - Terms and conditions content amendments 143 | - Update the default `BASE_URL` to include `www` 144 | - Added simple Web App Manifest file 145 | - Who we are content amendments 146 | 147 | ## 1.0.0 - 04/04/2019 148 | 149 | :rocket: Release of the NHSX website (https://nhsx.nhs.uk) 150 | 151 | ## 0.0.6 - 04/04/2019 152 | 153 | - Document the default `BASE_URL` environment variable 154 | - Tweak spacing below the video container on Homepage 155 | - Add OGL licence to the footer 156 | - Populated the terms and conditions page content 157 | - Populated the privacy policy page content 158 | - Added Matt Hancock video to homepage 159 | 160 | ## 0.0.5 - 04/04/2019 161 | 162 | - Fix issue with menu navigation item hover focus colour 163 | - Add if statement to prevent errors with missing variables 164 | - Add email address and further content amendments 165 | - Tweak the spacing of the right hand navigation on mobile 166 | - Tweak the spacing between page sections on the homepage 167 | - Streamline the documentation for running the application 168 | - Configure variables to be set with environment variables to avoid code changes 169 | - Content amendments across the website with newly signed off content 170 | - Content amendments to include health and social care 171 | - Tweak the width of the hero on mobile and spacing below 172 | - Add promo to Homepage for blogs and updates promotion 173 | - Populate the policies and key information and tools pages with descriptions and lead text 174 | - Set a base URL for the app for any assets that require a full path 175 | - Update the hero header image to the final version 176 | - Build the assets before running in development mode 177 | - Add open graph meta data and image for social media cards 178 | - Tidy up SCSS code by separating into files and lint the code 179 | 180 | ## 0.0.4 - 03/04/2019 181 | 182 | - Remove unused tests and dependencies 183 | - Fix issue with the cookie success banner link hover colour not being accessible 184 | - Combine the key documents page with the policy, strategy and national programmes page 185 | - Fix issue with Google analytics script not being classed as statistics type 186 | - Populate the cookie policy with cookies we use 187 | - Populate the accessibility statement with approved content 188 | - Use the correct URL for the cookies policy page 189 | - Use the approved Hero header image on the homepage 190 | - Fix invalid HTML and add cookie declaration to the sitemap 191 | - Create a 404 page with some basic content 192 | - Improve the README file with a description and contributing 193 | - Use the NHSX blue for the homepage hero background colour 194 | - Fix the spacing and sizing of typography and components on content pages 195 | - Embed videos within content pages, with responsive styling added 196 | - Add missing main element to the Homepage for the skip link component 197 | - Populate pages with approved content 198 | - Add placeholder Homepage sections for video and get involved 199 | - Use an improved SVG icon for the NHSX logo 200 | - Add hero and promo components with additional NHSX styling to the homepage 201 | - Use the correct CSS spelling color for the NHSX colour variables 202 | 203 | ## 0.0.3 - 02/04/2019 204 | 205 | - Fix issue on Internet Explorer with the NHSX logo being auto width 206 | - Use Google Analytics instead of Adobe Analytics due to the jQuery dependency required by Adobe 207 | - Add placeholder content pages and page descriptions 208 | - Populated the sitemap page with a hotfix for nested list spacing [NHS.UK frontend issue 430](https://github.com/nhsuk/nhsuk-frontend/issues/430) 209 | - Add placeholder page title and description fields to each page 210 | - Add placeholder policy and sitemap pages 211 | - Apply NHSX styling to the Header and Footer components 212 | - Use Header component with a navigation menu 213 | - Import JavaScript modules from NHS.UK frontend package rather than local files 214 | - Move build task dependencies to be devDependencies rather than regular 215 | - Use Webpack to compile JavaScript bundles instead of rollup.js 216 | - Add cookie policy page logic with placeholder cookie declaration page 217 | - Add missing '/' to correct the paths for the CSS/JS files 218 | - Use manual express routes and tidy up BrowserSync config 219 | - Use NHS.UK eslint config 220 | - Include JavaScript for the skip link to function properly 221 | - Add NHS.UK cookie consent banner, for cookie management across NHS.UK 222 | 223 | ## 0.0.2 - 29/03/2019 224 | 225 | - Remove production analytics tracking until go live 226 | - Add pull request templates for contributors 227 | - Use gzip compression to increase the speed of web app 228 | 229 | ## 0.0.1 - 29/03/2019 230 | 231 | - Add Adobe Analytics, our chosen analytics platform, to the different environments 232 | - Setup deployment and CI pipelines in Azure 233 | - Use the NHS.UK frontend library and apply basic NHS.UK template 234 | - Initial application structure and configuration 235 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/information-governance-guidance/how-data-is-supporting-covid19.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "How data is supporting the Covid-19 response" %} 2 | {% set pageDescription = "How data is supporting the Covid-19 response" %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 17 | {% endblock %} 18 | 19 | {% block body %} 20 |
21 |
22 | 23 |

How data is supporting the Covid-19 response

24 |

Updated 8th April 2020

25 | 26 |
27 |
28 | 29 |
30 |
31 |

Information is critical to the response to Covid-19. Key pieces of data extracted from health and care settings, combined with information provided by patient’s themselves, will be used in new ways to care for people and help the NHS and social care to better understand and respond to the virus.

32 | 33 |

Protecting privacy and confidentiality

34 |

These are unusual times but data must continue to be used lawfully and, despite the pandemic resulting in a broader legal allowance of data collection and use, the same strict rules that protect citizen privacy apply to how this data is used.

35 |

These rules include collecting the minimum amount of information required; not using the information collected for the Covid-19 response for unrelated purposes; ensuring appropriate safeguards are in place and only keeping the information for as long as the outbreak is ongoing.

36 | 37 |

Transparency and openness

38 |

We must and will be transparent about what we’re doing. We will regularly update this document so you can stay updated on how data is being used. We will also publish a register of those who are provided with access to the information collected nationally and the reason why.

39 | 40 |

Here are some examples of how information is being used to support the response to Covid-19:

41 |
    42 |
  1. Ensuring information is available to support the care of patients/service users
  2. 43 |

    To ensure that those providing care for patients/service users have access to up-to-date information during the Covid-19 period, a comprehensive medical summary from an individual’s GP records will be made available to other GP practices, NHS 111 and other health and care services.

    44 |

    This means that GP practices which provide care to new patients in the event that a nearby practice temporarily closes due to an infection, or health and care professionals who provide advice to people contacting NHS 111, will have the information they need. Controls will be in place to ensure that only those caring for patients/service users have access.

    45 |
  3. Supporting vulnerable people
  4. 46 |

    Using GP records of patients with certain underlying health conditions NHS Digital has compiled a list of people who are the most vulnerable to Covid-19. This is known as the Shielded Patient List, and is being used to support those that are the most vulnerable and have identified themselves as requiring additional support. Information about how this list has been compiled and which organisations it has been shared with and for what Covid-19 related purpose can be found on NHS Digital's website.

    47 |
  5. Planning our response to Covid-19
  6. 48 |

    To understand and anticipate demand on health and care services, we need a robust picture of the virus, how it’s spreading, where it might spread next and how that will affect the NHS and social care services. On the supply side, we need to know where the system is likely to face strain first, be that on ventilators, beds or staff sickness. This includes metrics such as:

    49 |
      50 |
    • Current occupancy levels at hospitals, broken down by general beds and specialist and/or critical care beds
    • 51 |
    • Current capacity of A&E departments and current waiting times
    • 52 |
    • Statistics about the lengths of stay for Covid-19 patients
    • 53 |
    54 |

    NHS England and Improvement and NHSX have developed a single, secure store, that protects the privacy of our citizens, to gather data from across the health and care system to inform the Covid-19 response. A bespoke platform has also been built to allow analysis and interpretation of this data and to support organisations with secure, reliable and timely information to make informed, effective decisions about how to respond to the pandemic. It will also support researchers to understand more about the virus.

    55 |

    The data, which will always remain fully under the control of the NHS, will largely be from existing data sources e.g. data already collected by NHS England and NHS Improvement, Public Health England and NHS Digital. New data sources include 999 call data, real time hospital occupancy and A&E capacity data and ONS data sources as well as data provided by patients themselves - all of which will help us to identify hot spots and trends in order to get the country back to normal in a controlled way, as quickly as possible. All the data held in the platform is subject to strict controls that meet the requirements of data protection legislation.

    56 |

    NHSX and NHS Digital have developed a three-pronged public facing service to give people with Covid-19 symptoms information and better measure the number of people with symptoms nationwide. This will help people support themselves and improve the ability of the NHS to prepare for variations in demand across the country. We are doing this by providing an NHS Coronavirus symptom service comprising three NHS services to citizens. These are:

    57 |
      58 |
    • 111 online Covid-19 service
    • 59 |
    • Text messaging to people who have symptoms to check in, reassure, give advice and treatment
    • 60 |
    • A Coronavirus status checker to allow those who are self isolating and those who have tested positive for Covid-19 to record online geographic data and information about their illness.
    • 61 |
    62 |

    NHSX is also looking at whether app-based solutions might be helpful in tracking and managing coronavirus, and we have assembled expertise from inside and outside the organisation to do this as rapidly as possible.

    63 |

    NHSX is committed to making data and information public; as much as it is appropriate and responsible to do so. There is already a public-facing dashboard available. Access to more detailed data as well as requests for collaboration will be carefully managed by NHSX and NHS England and Improvement through one central mailbox. This approach will ensure that policy makers, commissioners, planners and researchers involved in the national effort against Covid-19 have the information that they need.

    64 |
  7. Undertaking research to understand more about the virus
  8. 65 |

    UK Biobank is studying how the health of 500,000 people is affected by their lifestyle, environment and genes. All participants have volunteered to be involved. This resource could offer further insight into Covid-19 e.g. the factors which make one individual experience more serious symptoms compared to another. To support this Covid-19 work, we have enabled UK Biobank to access data held by GP practices on those individuals who have agreed to be part of the UK Biobank programme.

    66 |

    The National Perinatal Epidemiology Unit at the University of Oxford is undertaking a study to understand the complications of Covid-19. Little information is available about how the virus affects mothers and new-born babies and it is not clear how best to care for mothers and babies affected. Little is also known about how babies become infected with Covid-19 and whether it transmits from mothers to their baby(s) while they are still pregnant, during labour and birth, or whether the infection occurs following birth. The British Paediatric Surveillance Unit (BPSU) will collect via a survey, information from doctors who have looked after a new-born baby or mother with Covid-19. This information will be linked with existing data, such as the National Neonatal Research (NNRD), the Paediatric Intensive Care Audit Network (PICANet), and the national surveillance of maternal and perinatal deaths (MBRRACE-UK) to ensure a complete understanding of the cases. This will mean we can provide better care to mothers and babies and the best advice to pregnant women about the effects of Covid-19 on their baby.

    67 |
68 | 69 |

As time goes on, we will update this information to cover new ways in which data is being used to support the Covid-19 response. This may include examples of research into Covid-19: to understand the virus better, develop potential treatments / a vaccine and inform our response to future pandemics.

70 | 71 | 72 |
73 | 74 |
75 | 76 | 84 | 85 |
86 |
87 | {% endblock %} 88 | -------------------------------------------------------------------------------- /app/views/pages/key-information-and-tools/data-driven-health-and-care-technology.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Data-driven health and care technology" %} 2 | {% set pageDescription = "NHSX wants to make the NHS a world leader in developing ethical and safe data-driven technologies." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 16 | {% endblock %} 17 | 18 | {% block body %} 19 |
20 |
21 | 22 |

Data-driven health and care technology

23 | 24 |
25 |
26 | 27 |
28 |
29 | 30 |

What is Artificial Intelligence?

31 |

There is no single, universally agreed definition of Artificial Intelligence (AI), nor indeed of ‘intelligence’. Intelligence can be defined as ‘problem-solving’, and ‘an intelligent system’ as one which takes the best possible action in a given situation (Accelerating AI in health and care).

32 |

The ‘A’ of AI generally refers to one of the following:

33 | 38 | 39 |

Why Artificial Intelligence (AI)?

40 |

Artificially Intelligent Systems can carry out or augment health and care tasks that have until now been completed by humans, or have not been possible previously. AI presents significant opportunities for saving money, improving care, and saving lives. For example, it could help personalise NHS screening and treatments for cancer, eye disease and a range of other conditions, as well as freeing up staff time.

41 |

Read some of our case studies:

42 | 48 |

You will find more case studies at the end of our latest report Artificial Intelligence: how to get it right. Putting policy into practice for safe data-driven innovation in health and care. 49 | 50 |

51 |
52 |
53 |

What is the future for data-driven technology in the NHS?

54 |

NHSX wants to support data driven technologies that have the potential to improve the quality of health and care services.

55 |
56 |
57 | 58 |

We want to start with the basics and make sure that new technology respects ethical values such as autonomy, transparency, confidentiality and privacy. That’s why to date we have focussed on getting the right ethical frameworks and standards in place so that we can better guide people.

59 |

The code of conduct (Department of Health and Social Care, 2019) sets out what is expected of people developing, deploying and using data-driven technologies.

60 | 61 |

The NHS Artificial Intelligence laboratory

62 | 63 |

Where are we now?

64 |

NHSX has been working hard to understand how Artificial Intelligence (AI) is currently being developed in the NHS; what the greatest opportunities and risks are; and what challenges developers in this field face.

65 |

The result is a report that brings together the rich insight we have gathered together with some guidance for the development and deployment of AI in health and care. You can download the full AI report as a PDF.

66 |

This report is prefaced by the foundation of knowledge obtained from the 2018 Accelerating AI in health and care: results from a state of the nation survey.

67 | 68 |

Overview of the NHS Artificial Intelligence (AI) Laboratory

69 |

The NHS AI Laboratory will develop and deploy practical applications of artificial intelligence in the NHS that can improve the health and quality of life for our citizens. It will harness the power of data science and AI to turbo-charge our ability to make evidence-based decisions in health and social care.

70 |

Understanding there are ethical and safety concerns associated with the use of AI in health and care, the Lab will align to the core founding principles of the NHS; addressing transparency, safety, privacy, explicability and bias. By building on the foundations already laid, such as our code of conduct, these frameworks and best practices will ensure the project maintains the support of the public, and positions the NHS as a world leader in the development of safe and effective AI.

71 |

Through the creation of this Lab, and building on our existing work, we will:

72 | 80 |

We will work closely with the following partners to deliver the objectives of the NHS AI Lab including but not limited to:

81 | 88 | 89 |

Artificial Intelligence in Health and Care Award

90 |

The Artificial Intelligence in Health and Care Award is run by the Accelerated Access Collaborative (AAC) in partnership with NHSX and the National Institute for Health Research (NIHR). It will make £140m available over three years to accelerate the testing and evaluation of the most promising AI technologies which meet the strategic aims set out in the NHS Long Term Plan.

91 |

The Award will support technologies across the spectrum of development: from initial feasibility to evaluation within the NHS. Initially, it will focus on four key areas: screening, diagnosis, decision support and improving system efficiency.

92 |

A call for applications for the AI Award will run at least twice a year through an open competition to identify appropriate AI technologies for support into the NHS. The application process for the first competition is open from 28 January 2020 and closes at 1pm on 4 March 2020. To find out more, visit the AAC website. For further information and enquiries, please contact enquiries@ai-award.info.

93 | 94 |

Guidance and tools for commissioners and developers

95 |

If you are developing a data-driven technology or want to commission a system utilising it, you may find the following helpful:

96 | 102 |
103 | 104 |
105 | 106 | 115 | 116 |
117 |
118 | {% endblock %} 119 | -------------------------------------------------------------------------------- /app/views/pages/our-policies/terms-and-conditions.njk: -------------------------------------------------------------------------------- 1 | {% set pageTitle = "Terms and conditions" %} 2 | {% set pageDescription = "This website is hosted by NHS England. These terms govern your use of it." %} 3 | 4 | {% extends 'includes/layout.njk' %} 5 | 6 | {% block outerBody %} 7 | 16 | {% endblock %} 17 | 18 | {% block body %} 19 |
20 |
21 | 22 |

Terms and conditions

23 | 24 |

Summary

25 |

Use of this website is governed by these terms and conditions.

26 | 27 |

1. About these terms

28 |

1.1    Please read these terms and conditions carefully before you start to use this website (www.nhsx.nhs.uk and all sections and pages). This website is hosted by NHS England and any references to NHSX means NHS England as host. You may access and use this website if you agree to be legally bound by these terms and conditions set out here.

29 | 30 |

If you do not agree to be legally bound by these terms and conditions, please do not access and/or use this website. We recommend that you print a copy of these terms and conditions for future reference.

31 |

1.3    References in these terms and conditions to "NHSX", "we", "our" and "us" means the non-departmental public body responsible for driving digital transformation and leading policy, implementation and change for the NHS by working with partner organisations and teams from the Department of Health and Social Care, NHS England and NHS Improvement. The entire content of this website, and the individual articles, items, media files and assets published are owned by NHSX, unless otherwise indicated.

32 |

1.4    This website is intended for use only by people who live in the United Kingdom. References to "the NHS" mean "the NHS in England", unless otherwise stated. Services and arrangements may differ elsewhere in the UK.

33 |

1.5    If you have any queries in respect of your use of this website, please contact us at: feedback@nhsx.nhs.uk.

34 |

1.6    We may make changes to these terms and conditions, the terms and conditions applicable to any specific sub-site, the privacy and cookies policy and any other policies applicable to your use of this website, at any time. Your continuing use of this website constitutes your acceptance of and agreement to any such changed terms and conditions and policies.

35 |

1.7    Every time you wish to use our site, please check these terms to make sure you understand the terms that apply at the time.

36 |

1.8    We may update and change our site from time to time to reflect changes to our users’ needs and developing priorities for technology, digital and data improvement across the NHS.

37 |

1.9    To the extent that we are practically able to do so, we may terminate your access to any part of this website at any time without notice if you breach any of these terms and conditions.

38 | 39 | 40 |

2. Accessibility and browsers

41 |

2.1    NHSX aims to make this website and the material provided accessible to as many people as possible. This website is designed to work with the latest versions of Microsoft Edge, Google Chrome and Apple Safari, and uses standards which should work on the majority of browsers in use.  We offer no warranty for this website working in any particular browser or configuration. Please note that you may see inconsistencies in the presentation of pages if you are using an older or deprecated version of a browser. Read further information on the accessibility of this website.

42 | 43 |

3. Information about you and your visits to this website

44 |

3.1    NHSX processes information about you in accordance with our privacy policy and cookies policy. By using this website, you consent to such processing and you warrant that all data provided by you is accurate.

45 | 46 |

4. Freedom of Information

47 |

4.1    The data rights and responsibilities of NHSX, its staff and of patients is governed by the Freedom of Information Act 2000 and the EU General Data Protection Regulation. For policy and other information, see Freedom of Information (NHS England website).

48 | 49 |

5. Prohibited uses of this website

50 |

5.1    You may use this website only for lawful purposes. You may not use this website:

51 | 58 |

5.2    You also agree not to access without authority, interfere with, damage or disrupt:

59 | 65 | 66 |

6. Material on this website

67 |

6.1    The material on this website includes information, data, text, images, videos,  interactive services, link to products and apps and other works (“NHSX Content”).  You acknowledge that all rights in copyright, patents, design rights, trade marks and other intellectual property rights (whether registered, capable of registration or otherwise) throughout the world, in this website and all NHSX Content are owned by, or licensed to NHSX, unless otherwise indicated. Some NHSX Content includes identifiable third-party content for which we will have sought permission for its inclusion.

68 |

6.2    Except for your use of this website in accordance with these terms and conditions, you are granted no rights in respect of this website or any NHSX Content.

69 | 70 |

7. Your use of NHSX Content

71 |

7.1   Copyright and database rights in the NHSX Content are released free-of-charge under the current version of the Open Government Licence ("OGL"), except where specified, either in these terms and conditions, elsewhere on this website or in the OGL terms.  This licence does not extend to any other intellectual property rights, including but not limited to patents, design rights and trade marks. If there is any conflict between the OGL terms and these terms and conditions, these terms and conditions shall take precedence.

72 |

7.2    This means that you can use NHSX Content, including copying it, adapting it, and using it for any purpose, including commercially, provided you follow these terms and conditions and the terms of the OGL.

73 |

7.3    The OGL terms do not apply to the following categories of NHSX Content, and therefore these must not be used without our or the relevant owner’s prior consent:

74 | 81 | 82 |

7.4    If you do use any NHSX Content you must attribute it with the following statement:

83 |

“Information from NHSX, licenced under the current version of the Open Government Licence”

84 |

or in cases where the NHSX Content is combined, adapted, or otherwise modified in line with these terms and conditions:

85 |

“Contains information from NHSX, licenced under the current version of the Open Government Licence”.

86 |

7.5    By using any NHSX Content you accept and agree to the following terms:

87 | 94 |

8. Uploading material to this website

95 |

8.1    Whenever you make use of a feature that allows you to upload material to this website, for example when you participate in online discussions, contact other users of this website or submit any apps or products, you must comply with the standards set out in the comments and moderation policy. You warrant that any such contribution does comply with those standards, and you indemnify us for any breach of that warranty. You acknowledge that such uploaded material has not been verified or approved by us.

96 |

8.2    Any material you upload to this website will be considered non-confidential and non-proprietary, and NHSX has the right to use, copy, distribute and disclose to third-parties any such material for any purpose. Furthermore NHSX also has the right to disclose your identity to any third-party who is claiming that any material posted or uploaded by you to this website constitutes a violation of their intellectual property rights, or their right to privacy.

97 |

8.3    NHSX will not be responsible, or liable to any third-party, for the content or accuracy of any materials posted by you or any other user of this website.

98 |

8.4    NHSX has the right to remove any material or posting you make on this website if, in our opinion, such material does not comply with the standards set out in these terms and conditions and the comments and moderation policy.

99 |

8.5    Comments posted should relate to your personal experience or that of someone close to you. You should not name any individuals (other than yourself) or include information through which someone else could identify an individual about whom you are writing. If you want to comment on someone else’s experience, (e.g. a relative or someone you care for), then you may do so if you make sure that you are not named in the posting and you state how the other person is connected to you (e.g. “my father”). You warrant that all statements of fact in any comment you submit are true, and that any expression of opinion is your honestly held opinion on those facts, or that of the person on whose behalf you are writing.

100 |

8.6    If you find any comments offensive or objectionable, you may make a complaint to the moderator using the ‘Report’ link provided at the foot of each published comment.

101 |

8.7    We have many measures in place to keep your information safe. But it is important that you also play your part – visit the Government's Get Safe Online website for advice on how to do this.

102 | 103 |

9. Social media, bookmarking, and digital engagement

104 |

9.1    NHSX may from time to time provide third party or owned social media and interactive services on this website or linked to this website. Currently this includes and is not limited to:

105 | 113 |

9.2    NHSX is under no obligation to oversee, monitor or moderate any interactive services we provide from this website, and we expressly exclude our liability for any loss or damage arising from the use of these interactive services by a user in contravention of these terms and conditions, whether the service is moderated or not.

114 |

9.3    Our RSS feeds can be used as part of your website; however, we do require that proper format and attribution are used. The attribution text should read “NHSX RSS feeds”. We reserve the right from time to time to restrict the distribution of NHSX RSS feed content and do not accept any liability for these feeds.

115 |

9.4    Use of our social bookmarking links is subject to these terms and conditions. See ‘Linking from this website’ below.

116 |

9.5    Although we do monitor and review discussions, chat, postings, transmissions, bulletin boards and the like on this website and its subsections, we are under no obligation to do so and assume no responsibility or liability arising from the content of any such locations nor for any error, omission, infringement, defamation, obscenity, or inaccuracy contained in any information within such locations on this website.

117 |

9.6    The use of any of the interactive features on this website by a minor is subject to the consent of their parent or guardian, and we advise parents to communicate with their children about their safety online, as moderation is not foolproof. Minors who are using any interactive service should be made aware of the potential risks to them. Where we do moderate any of the interactive features on this website, we will normally provide you with a means of contacting the moderator, should a concern or difficulty arise.

118 |

10. Linking to this website

119 |

10.1    We do not object to you linking directly to pages on this website, provided you do so in a way that is fair and legal and does not damage our reputation or take advantage of it. We reserve the right to move or change this website’s URLs at any time. Rather than deep linking, we recommend linking to section homepages, which are less likely to move or change.

120 |

10.2    However, we don’t give permission to suggest that your website is associated, or endorsed by us.

121 |

10.3    We reserve the right to withdraw linking permission without notice.

122 | 123 |

11. Linking from this website

124 |

11.1    We are not responsible for the content or reliability of the websites we link to and do not necessarily endorse the views expressed within them. We aim to replace broken links to other sites but cannot guarantee that these links will always work as we have no control over the availability of other sites.

125 |

11.2    Due to the very nature of the internet we cannot guarantee this website or other websites we link to will always be available to you.

126 | 127 |

12. Disclaimer and liabilities

128 |

12.1    This website, all NHSX Content and all material relating to Government information, products and services (or to third-party information, products and services) is provided "as is", without any endorsement and without warranty of any kind whether express or implied, including but not limited to the implied warranties of satisfactory quality, fitness for a particular purpose, non-infringement, compatibility, security and accuracy.  This means that, while we do try to make sure that all our information is correct, we are not liable for any errors or omissions, and cannot be responsible for any impact these have on you.

129 |

12.2    If the need arises, we reserve the right to amend, delete, suspend or withdraw all or any part of this website without notice. NHSX will not be liable if for any reason this website or any parts are unavailable at any time.

130 |

12.3    We do not warrant that the functions of this website will be uninterrupted or error free, that defects will be corrected, or that this website or the server that makes it available will be free of viruses or represent the full functionality, accuracy or reliability of the materials. You should use your own virus protection software.

131 |

12.4    NHSX and any approving bodies are not the owners, managers or suppliers of various products which can be accessed from this website. NHSX or the approving body sets standards for reviewing the products, but this does not mean that NHSX or the approving body has itself reviewed all aspects of each product, or version of the same product. NHSX or the approving body is not responsible or liable for any advice, or any other information, services or products that you obtain using any such products.

132 |

12.5    Material on this website is provided for information and educational purposes only and we do not guarantee that information we provide will meet your health or medical requirements. NHSX does not give medical advice in relation to any individual case or patient, nor does NHSX provide medical or diagnostic services.

133 | 138 |

12.6    In no event will we be liable for any loss or damage including, without limitation, indirect or consequential loss or damage, or any loss or damages whatsoever arising from use or loss of use of, data or profits arising out of or in connection with the use of this website. Nothing in these terms and conditions will operate to limit or exclude liability for death or personal injury arising from our negligence, nor our liability for fraudulent misrepresentation, nor any other liability which cannot be excluded or limited under applicable law.

139 |

13. General

140 |

13.1    If any of these terms and conditions are determined to be illegal, invalid or otherwise unenforceable, then the remaining terms and conditions shall remain in full force and effect.

141 |

13.2    The laws of England shall apply exclusively to these terms and conditions and to all matters relating to use of this website. Any cause of action arising under these terms and conditions or the use of this website shall be subject to the exclusive jurisdiction of the courts of England and Wales.

142 | 143 |
144 |
145 | {% endblock %} 146 | --------------------------------------------------------------------------------