Our test site

<p>Flowchart diagram - accessible</p>
<p>///mermaid
%%{init: {
  "theme": "base",
  "themeVariables": {
    "primaryColor": "#005eb8",        // NHS Blue for flow boxes
    "edgeLabelBackground":"#ffffff",
    "nodeTextColor": "#000000",       // NHS Black text
    "fontSize": "16px",
    "tertiaryColor": "#768692",       // NHS mid-grey for alternate states
    "secondaryColor": "#007f3b"       // NHS Green for decision outcomes
  }
}}%%
graph TD
accTitle: Example flowchart
    accDescr: During Christmas, you receive money and decide to go shopping. As you consider your options, you reach a decision point where you think about what to buy. You have three choices: purchasing a laptop, buying an iPhone, or selecting an unspecified third option. This flowchart represents the simple decision-making process of spending money received during the holiday season.
    A[Christmas]--&gt;|Get money| B(Go shopping)
    B--&gt;C{Let me think}
    C--&gt;|One| D[Laptop]
    C--&gt;|Two| E[iPhone]
    C--&gt;|Three| F
</p>
<ul class="details">
<li>
<a href="">Explain the example flowchart diagram</a>
<div>During Christmas, you receive money and decide to go shopping. As you consider your options, you reach a decision point where you think about what to buy. You have three choices: purchasing a laptop, buying an iPhone, or selecting an unspecified third option. This flowchart represents the simple decision-making process of spending money received during the holiday season.</div>
</li>
</ul>
<p>Mindmap - accessible when not paired with Sankey diagram due to duplicate ids (node-1)</p>
<p>///mermaid
%%{init: {
  "theme": "base",
  "themeVariables": {
    "fontSize": "18px",
    "primaryColor": "#003087",
    "primaryTextColor": "#ffffff",
    "primaryBorderColor": "#003087",
    "secondaryColor": "#F0F4F5",
    "secondaryTextColor": "#212B32",
    "secondaryBorderColor": "#AEB7BD",
    "tertiaryColor": "#005EB8",
    "tertiaryTextColor": "#ffffff",
    "tertiaryBorderColor": "#005EB8",
    "nodeBorderRadius": 10
  },
  "mindmap": {
    "padding": 15,
    "maxNodeWidth": 300
  }
}%%
mindmap
  root(NHS Number)
    (Costs to implement)
    (Benefits)
      (Cost savings)
      ::icon(fa fa-sterling-sign)
    (Progress)
        (Highly adopted)
            (95% of the NHS)
    (Used by)
        (ISB 0149-01 NHS Number for General Practice)
        ::icon(fa fa-book)
        (ISB 0149-02 NHS Number for Secondary care)
        ::icon(fa fa-book)
    (Related to)
            (ISB 0086 Information Governance Toolkit)
            ::icon(fa fa-book-open)
            (ISB 1512 Information Governance Standards Framework)
            ::icon(fa fa-book-open)
            (ISB 1572 Sensitive Data)
            ::icon(fa fa-book-open)
            (ISB 1077 AIDC for Patient Identification)
            ::icon(fa fa-book-open)
            (ISB 1555 NHS Number for Babies)
            ::icon(fa fa-book-open)
    (Care settings)
        (Community health)
        (GP / Primary care)
        (Acute)
            (Hospital)
            (Maternity)
            (Mental health)
            (Urgent and Emergency Care)
    (Legal obligations)
      (Mandatory)
        (for NHS providers)
        ::icon(fa fa-hospital)
            (Due to)  
                (Section 250)
                ::icon(fa fa-scale-balanced)
    (About)
        (Access to records)
        (Appointment / scheduling)
        (Continuity of care)
        (Demographics)
        (Key care information)
        (Patient communication)
        (Referrals)
</p>
<ul class="details">
<li>
<a href="">Explain the NHS Number standard mindmap</a>
<div>This diagram shows how the NHS Number is used across the health and care system to help keep your information safe, accurate, and easy to find. It explains that using the NHS Number is required by law for NHS services, and it’s already used by nearly all of them. It helps link your records when you go to different places for care—like your GP, hospital, or mental health services—so staff can see the right details about you. The diagram also shows how the NHS Number connects to other important rules and standards that protect your data and support good care. Overall, it helps make sure everyone involved in your care is on the same page.</div>
</li>
</ul>
<p>Standards Directory Roadmap (2024 - 2026) Gantt chart - accessible</p>
<p>///mermaid
%%{init: {
  "theme": "default",
  "displayMode:" "compact",
  "themeVariables": {
    "primaryColor": "#005eb8",         // NHS Blue for bars
    "primaryTextColor": "#ffffff",     // White text for contrast
    "primaryBorderColor": "#003a70",   // Darker NHS Blue border
    "secondaryColor": "#007f3b",       // NHS Green for optional bars
    "tertiaryColor": "#768692",        // NHS Mid Grey for milestones
    "fontSize": "16px",
    "textColor": "#231f20",            // NHS Black for general text
    "lineColor": "#231f20",            // NHS Black for grid lines
    "background": "#f0f4f5"            // NHS Pale Grey background
  }
}}%%
gantt
accTitle: Standards Directory Roadmap (2025 - 2026)
    accDescr: This gantt chart shows work on the NHS Standards Directory from January 2025 to March 2026. Key documents were made more accessible, with full WCAG 2.2 compliance achieved by May 2025.
    title Standards Directory Roadmap (2024 - 2026)
    dateFormat  YYYY-MM-DD
    tickinterval 12month
    section Project
    WCAG 2.2 accessible      :done, q1_2025, 2025-01-01, 2025-05-15
    GDS live certified:done, q1_2026, 2025-12-01, 2026-03-30
    Business cases:done, q1_2026, 2025-10-01, 2026-03-30
    section Content
    Open standards         :done, q2_2025, 2025-05-01, 2025-06-30
    ISO TC215 standards        :done, q1_2025, 2025-01-01, 2025-05-30
    Create taxonomy        :done, q3_2025, 2025-07-01, 2025-08-30
    Create ontology       :done, q4_2025, 2025-09-01, 2025-10-31
    Data elements :done, q2_2025, 2025-04-01, 2025-07-31
    Glossaries :done, q2_2025, 2025-05-01, 2025-10-30
    Simplify standards :done, q2_2025, 2025-03-01, 2025-05-30
    Requirements/Benefits:done, q2_2025, 2025-05-01, 2025-09-30
    section Capability
    Data model upgrade :done, q1_2025, 2025-01-01, 2025-05-01
    Email notifications  :done, q1_2025, 2025-01-01, 2025-06-30
    Integrate taxonomies        :done, q3_2025, 2025-06-01, 2025-09-01
    Content Management System        :done, q4_2025, 2025-09-01, 2026-01-30
    Autocomplete search       :done, q1_2025, 2025-01-01, 2025-01-31
    Accessible diagrams        :done, q1_2025, 2025-01-01, 2025-05-31
    Accessible documents     :done, q1_2025, 2025-01-01, 2025-06-30
</p>
<ul class="details">
<li>
<a href="">Explain the Standards Directory roadmap</a>
<div>This chart shows the plan for improving the NHS Standards Directory from early 2025 to spring 2026. It starts with making documents easier to read and fully accessible by May 2025. During the year, important content like international and open standards was added, and the information was better organised using clear categories. Helpful features like search suggestions, email updates, and easier navigation were added throughout 2025. A system to manage content was put in place by early 2026. The project reaches a major milestone in March 2026 with official GDS live certification and completed business plans.</div>
</li>
</ul>
<p>Pie chart - accessible</p>
<p>///mermaid
%%{init: {
  "pie": {
    "textPosition": 0.5
  },
  "theme": "default",
  "themeVariables": {
    "pieOuterStrokeWidth": "2px",
    "pieStrokeColor": "#003087",        // Dark NHS Blue border
    "pie1": "#005eb8",                  // NHS Blue
    "pie2": "#007f3b",                  // NHS Green
    "pie3": "#8a1538",                  // NHS Dark Red
    "pie4": "#330072",                  // NHS Purple (optional)
    "pie5": "#768692"                   // NHS Dark Grey (supporting)
  }
}}%%
pie showData
accTitle: Example piechart
    accDescr: This pie chart shows the main elements found in a product, using both colours and labels to help you understand the amounts. Potassium is the largest part, making up 50.05% of the product. Calcium is next, at 42.96%. Magnesium is much smaller at 10.01%, and Iron is the smallest part at 5%.
    title Key elements in Product X
    "Calcium" : 42.96
    "Potassium" : 50.05
    "Magnesium" : 10.01
    "Iron" :  5
</p>
<ul class="details">
<li>
</li></ul>
<a href="">Explain the example Pie chart</a>
<div>This pie chart shows the main elements found in a product, using both colours and labels to help you understand the amounts. Potassium is the largest part, making up 50.05% of the product. Calcium is next, at 42.96%. Magnesium is much smaller at 10.01%, and Iron is the smallest part at 5%.</div>
<p>Entity relationship diagram - accessible</p>
<p>///mermaid
%%{init: {
  "theme": "default",
  "themeVariables": {
    "primaryColor": "#005eb8",         // NHS Blue for entity background
    "primaryTextColor": "#ffffff",     // White text for contrast
    "primaryBorderColor": "#003087",   // Dark NHS Blue border
    "lineColor": "#330072",            // Supporting Purple for relationships
    "fontSize": "14px"
  }
}}%%
erDiagram
accTitle: Example entity relationship diagram
    accDescr: This diagram shows how different parts of an online shopping system are connected. It starts with the customer, who can place orders, receive invoices, and has one or more delivery addresses. Each delivery address can be linked to several orders. Every order includes order items, and each order item is linked to a product. Products belong to a product category, which helps group similar items together. An invoice is linked to the order it covers, and customers are responsible for their invoices. The diagram helps explain how customers, products, orders, and delivery information all work together in a shopping system. 
    CUSTOMER }|..|{ DELIVERY-ADDRESS : has
    CUSTOMER ||--o{ ORDER : places
    CUSTOMER ||--o{ INVOICE : "liable for"
    DELIVERY-ADDRESS ||--o{ ORDER : receives
    INVOICE ||--|{ ORDER : covers
    ORDER ||--|{ ORDER-ITEM : includes
    PRODUCT-CATEGORY ||--|{ PRODUCT : contains
    PRODUCT ||--o{ ORDER-ITEM : "ordered in"
</p>
<ul class="details">
<li>
<a href="">Explain the example Entity relationship diagram</a>
<div>This diagram shows how different parts of an online shopping system are connected. It starts with the customer, who can place orders, receive invoices, and has one or more delivery addresses. Each delivery address can be linked to several orders. Every order includes order items, and each order item is linked to a product. Products belong to a product category, which helps group similar items together. An invoice is linked to the order it covers, and customers are responsible for their invoices. The diagram helps explain how customers, products, orders, and delivery information all work together in a shopping system. </div>
</li>
</ul>
<p>Class diagram - accessible</p>
<p>///mermaid
%%{init: {
  "theme": "default",
  "themeVariables": {
    "primaryColor": "#005eb8",         // NHS Blue for node fill
    "primaryTextColor": "#ffffff",     // White text for high contrast
    "primaryBorderColor": "#003087",   // Darker NHS Blue border
    "lineColor": "#330072",            // Supporting Purple for relationships
    "fontSize": "14px"
  }
}}%%
classDiagram
accTitle: Example class diagram
    accDescr: This class diagram shows how different animals are grouped and what features they have. At the top is a general group called Animal, which includes all animals in the diagram. Every animal has an age (a number), a gender (a word), and two actions they can do: isMammal, which checks if the animal is a mammal, and mate, which means to have babies. There are three types of animals shown: Duck, Fish, and Zebra. Each one belongs to the Animal group but also has its own special features. Ducks have a beak colour and can swim and quack. Fish have a size in feet (which is private) and can eat. Zebras have a wild or not setting and can run. This diagram helps explain how animals can be sorted into a general group with shared traits, while still keeping their unique features.
    Animal &lt;|-- Ducks
    Animal &lt;|-- Fish
    Animal &lt;|-- Zebra
    Animal : +int age
    Animal : +String gender
    Animal: +isMammal()
    Animal: +mate()
    class Duck{
      +String beakColor
      +swim()
      +quack()
    }
    class Fish{
      -int sizeInFeet
      -canEat()
    }
    class Zebra{
      +bool is_wild
      +run()
    }
</p>
<ul class="details">
<li>
<a href="">Explain the example Class diagram</a>
<div>This class diagram shows how different animals are grouped and what features they have. At the top is a general group called Animal, which includes all animals in the diagram. Every animal has an age (a number), a gender (a word), and two actions they can do: isMammal, which checks if the animal is a mammal, and mate, which means to have babies. There are three types of animals shown: Duck, Fish, and Zebra. Each one belongs to the Animal group but also has its own special features. Ducks have a beak colour and can swim and quack. Fish have a size in feet (which is private) and can eat. Zebras have a wild or not setting and can run. This diagram helps explain how animals can be sorted into a general group with shared traits, while still keeping their unique features.</div>
</li>
</ul>
<p>Quadrant diagram - accessible</p>
<p>///mermaid
%%{init: {
  "theme": "default",
  "themeVariables": {
    "quadrant1Fill": "#007f3b",   // NHS Green – positive (We should expand)
    "quadrant2Fill": "#005eb8",   // NHS Blue – strategic (Need to promote)
    "quadrant3Fill": "#8a1538",   // NHS Dark Red – warning (Re-evaluate)
    "quadrant4Fill": "#768692",   // NHS Dark Grey – neutral (May be improved)
    "textColor": "#ffffff",       // High contrast white text
    "fontSize": "14px"
  }
}}%%
quadrantChart
accTitle: Example quadrant diagram
    accDescr: This quadrant chart shows how six campaigns are performing based on two things: how many people saw them (reach) and how many interacted with them (engagement). Both scores range from 0 to 1, where 1 is the highest possible score, meaning the campaign reached or engaged with everyone in the target group. The chart is split into four areas to make it easier to understand. Campaign C (0.57 reach, 0.69 engagement) and Campaign F (0.35, 0.78) are in the top right, showing high reach and high engagement — these fall under “We should expand.” Campaign A (0.3, 0.6) has strong engagement but lower reach, so it’s in the “Need to promote” area. Campaign D (0.78, 0.34) has good reach but low engagement and may need improving. Campaigns B (0.45, 0.23) and E (0.40, 0.34) have lower scores for both and may need to be re-evaluated.
    title Reach and engagement of campaigns
    x-axis Low Reach --&gt; High Reach
    y-axis Low Engagement --&gt; High Engagement
    quadrant-1 We should expand
    quadrant-2 Need to promote
    quadrant-3 Re-evaluate
    quadrant-4 May be improved
    Campaign A: [0.3, 0.6]
    Campaign B: [0.45, 0.23]
    Campaign C: [0.57, 0.69]
    Campaign D: [0.78, 0.34]
    Campaign E: [0.40, 0.34]
    Campaign F: [0.35, 0.78]
</p>
<ul class="details">
<li>
<a href="">Explain the example Quadrant diagram</a>
<div>This quadrant chart shows how six campaigns are performing based on two things: how many people saw them (reach) and how many interacted with them (engagement). Both scores range from 0 to 1, where 1 is the highest possible score, meaning the campaign reached or engaged with everyone in the target group. The chart is split into four areas to make it easier to understand. Campaign C (0.57 reach, 0.69 engagement) and Campaign F (0.35, 0.78) are in the top right, showing high reach and high engagement — these fall under “We should expand.” Campaign A (0.3, 0.6) has strong engagement but lower reach, so it’s in the “Need to promote” area. Campaign D (0.78, 0.34) has good reach but low engagement and may need improving. Campaigns B (0.45, 0.23) and E (0.40, 0.34) have lower scores for both and may need to be re-evaluated.</div>
</li>
</ul>
<p>Xy bar line chart - accessible</p>
<p>///mermaid
%%{init: {'look': 'handDrawn', 'theme': 'neutral', 'themeVariables': {'primaryColor': '#005EB8'}}}%%
xychart-beta
accTitle: Example bar chart
    accDescr: This XY bar chart shows the amount of time spent training each day over the course of a week. The x-axis represents the days of the week, from Monday to Sunday, and the y-axis shows the time trained in minutes, ranging from 0 to 300 minutes. The chart shows that on Monday, 60 minutes were spent training, Wednesday had 120 minutes, Thursday had 180 minutes, Friday had 230 minutes, and Saturday had the most time trained with 300 minutes. Tuesday and Sunday had no training time, both showing 0 minutes.
    title "Training progress"
    x-axis [mon, tues, wed, thur, fri, sat, sun]
    y-axis "Time trained (minutes)" 0 --&gt; 300
    bar [60, 0, 120, 180, 230, 300, 0]
</p>
<ul class="details">
<li>
<a href="">Explain the example Bar chart</a>
<div>This XY bar chart shows the amount of time spent training each day over the course of a week. The x-axis represents the days of the week, from Monday to Sunday, and the y-axis shows the time trained in minutes, ranging from 0 to 300 minutes. The chart shows that on Monday, 60 minutes were spent training, Wednesday had 120 minutes, Thursday had 180 minutes, Friday had 230 minutes, and Saturday had the most time trained with 300 minutes. Tuesday and Sunday had no training time, both showing 0 minutes.</div>
</li>
</ul>
<p>Git diagram - accessible</p>
<p>///mermaid
%%{init: {
  "theme": "default",
  "themeVariables": {
    "git0": "#005eb8",        // NHS Blue for base
    "git1": "#231f20",        // NHS Black for highlights
    "git2": "#425563",        // NHS Dark Grey
    "gitBranchLabelColor": "#ffffff",
    "gitLabelColor": "#231f20",
    "lineColor": "#005eb8",
    "textColor": "#231f20"
  }
}}%%
gitGraph
accTitle: Example release diagram
    accDescr: This release diagram shows the timeline of key stages in the development and release of a project. It starts with the "Front door" stage, marking the beginning of the project. The next milestone is "Prototype standard:", which is tagged with version v1.0.0, indicating the first official version of the prototype. After that, the project reaches the "FCAP approved" stage, followed by the "Review" phase, which is tagged with RC_1, representing the review for release candidate 1. The project then moves to the "Standard published" milestone, marking the official publication of the standard. Following that, the "Adopted" stage is highlighted and tagged with version 8.8.4, showing that the standard has been formally accepted. Finally, the project reaches the "Retired" stage, signifying the end of its active development phase.
          commit id: "Front door"
          commit id: "Prototype standard:" type: NORMAL tag: "v1.0.0"
          commit id: "FCAP approved"
          commit id: "Review"  type: REVERSE tag: "RC_1"
          commit id: "Standard published"
          commit id: "Adopted" type: HIGHLIGHT tag: "8.8.4"
          commit id: "Retired"
</p>
<ul class="details">
<li>
<a href="">Explain the example Progress diagram</a>
<div>This release diagram shows the timeline of key stages in the development and release of a project. It starts with the "Front door" stage, marki</div>
</li>
</ul>


Implementation guidance pdf doc

<h2>National Workforce Data Set (NWD) Version 3.6 – Requirements Specification</h2>

<p><strong>Document Reference:</strong> DAPB1067 Amd 2/2025</p>
<p><strong>Publication Date:</strong> 18 February 2025</p>
<p><strong>Authors:</strong> Jill Clark, Lalita Wakde</p>
<p><strong>Owner:</strong> Alyson Whitmarsh</p>
<p><strong>Status:</strong> Final</p>

<hr>

<h2>Glossary of Terms</h2>
<ul>
  <li><strong>AHP</strong>: Allied Health Professions</li>
  <li><strong>ESR</strong>: Electronic Staff Record</li>
  <li><strong>HR</strong>: Human Resources</li>
  <li><strong>NHSE</strong>: NHS England</li>
  <li><strong>Third Sector</strong>: Charities, voluntary orgs, CICs</li>
  <li><strong>Trac</strong>: NHS recruitment platform</li>
  <li><strong>WIRG</strong>: Workforce Information Review Group</li>
  <li><strong>wMDS</strong>: Workforce Minimum Data Set</li>
</ul>

<h2>1. Overview</h2>

<h3>1.1 Background and Context</h3>

<p>The NWD facilitates the capture of consistent NHS workforce data via structured data definitions. It supports the wMDS and is embedded in operational systems like ESR and Trac.</p>

<p>Key data items include:</p>
<ul>
  <li>Staff Group</li>
  <li>Job Role</li>
  <li>Area of Work</li>
  <li>NHS Occupation Code</li>
</ul>

<p>///mermaid
graph TD  
    StaffGroup --&gt; JobRole  
    JobRole --&gt;|Flexible relationship| AreaOfWork  
    JobRole --&gt; NHSOccupationCode  
    StaffGroup --&gt;|Constrained| JobRole  
</p>

<p>Data values must be kept current to ensure appropriate role combinations. NWD supports a wide range of use cases, including HR, training, diversity monitoring, and planning.</p>

<h3>1.2 Supporting Documents</h3>
<ul>
  <li>NWD3.6 Implementation Guidance</li>
  <li>NWD3.6 Data Set Specification</li>
  <li>NHS Occupation Code Manual v22</li>
</ul>

<h3>1.3 Scope</h3>
<p>NWD is a reference data standard, not a data flow. It can be embedded in various HR systems across providers of NHS-funded care.</p>

<h4>1.3.1 Users of the NWD</h4>
<p>The following groups use NWD:</p>
<ul>
  <li>NHS HR and Workforce planners</li>
  <li>Trusts, GPs, PCNs</li>
  <li>Regulators, e.g. CQC</li>
  <li>Third Sector, Social Enterprises</li>
  <li>NHS England &amp; regions</li>
</ul>

<p>///mermaid
graph LR  
    NHS_England --&gt;|Implements| NWD  
    HR --&gt;|Uses| NWD  
    Planners --&gt;|Uses| NWD  
    GP_Practices --&gt;|Uses| NWD  
    ThirdSector --&gt;|Uses| NWD  
</p>

<h4>1.3.2 Exclusions</h4>
<p>NWD does not:</p>
<ul>
  <li>Act as a data collection mechanism</li>
  <li>Define full HR systems</li>
  <li>Replace postgraduate deanery systems</li>
  <li>Define local organisation structures</li>
</ul>

<h4>1.3.3 Future Development</h4>
<p>Ongoing developments target improved coverage for:</p>
<ul>
  <li>DDaT workforce (Digital, Data and Tech roles)</li>
  <li>Equality monitoring fields</li>
  <li>Retirement of outdated matrices</li>
</ul>

<h3>1.4 Related Standards</h3>
<ul>
  <li>DCB0028: Treatment Function</li>
  <li>DAPB0011: Mental Health Services Data Set</li>
  <li>DAPB1069: Community Services Data Set</li>
  <li>DAPB4034: Primary Care Network Workforce Data</li>
</ul>




<h2>2. Requirements</h2>

<p>This section outlines the responsibilities for Health and Care organisations, IT system suppliers, and NHS England in implementing the NWD Standard.</p>

<h3>2.1 Health and Care Organisations – Requirements</h3>

<ul>
  <li>NWD must be used for:
    <ul>
      <li>Workforce Minimum Data Set submissions (e.g. R00433, DAPB4034)</li>
      <li>Earnings surveys and sickness/absence returns</li>
      <li>Workforce Planning, Equality Standards reporting</li>
    </ul>
  </li>
  <li>Compliance is required by <strong>1 March 2026</strong>, with systems updated by <strong>1 September 2025</strong>.</li>
  <li>NWD should also be used for local, regional, and national workforce planning.</li>
</ul>

<p>///mermaid
flowchart TD  
    A[Health &amp; Care Orgs] --&gt; B[NWD Use in HR &amp; Planning]  
    B --&gt; C[wMDS, Sickness, Earnings Surveys]  
    B --&gt; D[Workforce Planning Reports]  
</p>

<h4>2.1.1 Conformance Criteria – Health and Care Organisations</h4>

<ul>
  <li>Staff awareness of ISN 2/2025 by September 2025</li>
  <li>Staff training completed by March 2026</li>
  <li>System values updated by September 2025</li>
  <li>Internal processes aligned by March 2026</li>
  <li>Implementation monitored through query and complaint volumes</li>
</ul>

<h3>2.2 IT Systems – Requirements</h3>

<p>All system suppliers (e.g. ESR, Trac, NHS Jobs) must update their systems to reflect changes described in the Information Standards Notice (ISN) within six months of its publication.</p>

<ul>
  <li>System owners should subscribe to standard ISN communications</li>
  <li>Changes must be implemented by <strong>1 September 2025</strong></li>
</ul>

<h4>2.2.1 Conformance Criteria – IT Systems</h4>

<ul>
  <li>Systems must reflect updated values within six months of ISN</li>
  <li>Suppliers must work with stakeholders to ensure updates are correct</li>
  <li>Guidance documentation must inform any local extensions</li>
</ul>

<p>///mermaid
graph LR  
    A[ISN Published] --&gt; B[Suppliers Update Systems]  
    B --&gt; C[NWD Values Available in UI]  
    C --&gt; D[Data Captured at Source]  
    D --&gt; E[Compliance by Sept 2025]  
</p>

<h3>2.3 NHS England – Requirements</h3>

<ul>
  <li>Must provide updated guidance by August 2025</li>
  <li>Must issue communications plan by August 2025</li>
  <li>Must monitor uptake and report issues to stakeholders</li>
</ul>

<h4>2.3.1 Conformance Criteria – NHS England</h4>

<ul>
  <li>Effective guidance and communication visible by drop in queries/complaints</li>
  <li>Feedback from ESR HR SIG and stakeholders used to verify success</li>
</ul>

<p>///mermaid
flowchart TD  
    NHS_England --&gt;|Publishes| Guidance  
    NHS_England --&gt;|Notifies| Suppliers &amp; Users  
    NHS_England --&gt;|Monitors| Progress  
    NHS_England --&gt;|Responds to| Feedback  
</p>

<h2>3. Information Governance Assessment</h2>

<p>As NWD is a reference standard and contains no patient data, a Privacy Impact Assessment is not required.</p>

<h2>4. Patient Safety Assessment</h2>

<p>The NHS England Clinical Safety team confirmed that NWD changes do not impact clinical safety as they relate only to staff data.</p>

<h2>5. Points of Contact</h2>

<p>For queries or change requests:</p>
<ul>
  <li><strong>Email:</strong> <a href="mailto:enquiries@nhsdigital.nhs.uk">enquiries@nhsdigital.nhs.uk</a> (Subject: "National Workforce Data Set")</li>
  <li><strong>Phone:</strong> 0300 303 5678</li>
</ul>

<h2>6. Useful Resources</h2>

<ul>
  <li><a href="https://digital.nhs.uk/data-and-information/areas-of-interest/workforce/workforce-minimum-data-set-wmds">Workforce Minimum Data Set (wMDS)</a></li>
  <li><a href="https://digital.nhs.uk/data-and-information/data-collections-and-data-sets/data-sets/national-workforce-data-set-nwd-and-nhs-occupation-codes">NWD and NHS Occupation Codes</a></li>
  <li><a href="https://digital.nhs.uk/data-and-information/areas-of-interest/workforce/national-workforce-data-set-nwd-guidance-documents">NWD Guidance Documents</a></li>
  <li><a href="https://digital.nhs.uk/data-and-information/information-standards/publications-and-notifications/standards-and-collections/dcb0028-treatment-function-and-main-specialty-standard">DCB0028: Treatment Function Standard</a></li>
  <li><a href="http://www.legislation.gov.uk/ukpga/2012/7/section/250">Health and Social Care Act 2012 – Section 250</a></li>
</ul>

Implementation Guidance

A mandatory Information Standard is a standard in relation to the processing of information. They set out requirements that must be followed when health and adult social care information is used, processed and shared.

<h2>What are mandatory Information Standards</h2>

- A mandatory Information Standard is a standard in relation to the processing of information. They set out requirements that must be followed when health and adult social care information is used, processed and shared.  

- Information Standards also relate to information technology (IT), or IT services used, or intended to be used, in connection with the processing of information.

<h3>What is the legal basis for publishing an information standard</h3>

- Information Standards are published under section 250 of the Health and Social Care Act 2012, as amended by the Health and Care Act 2022 and the Data (Use and Access) Act 2025.  

- NHS England (on behalf of the Department of Health and Social Care) maintains a list of published Information Standards which are approved for publication by the Data Alliance Partnership Board (on behalf of Secretary of State). 

- The publication of an Information Standards Notice sets out the legal basis for an Information Standard, the nature of the legal duty and to whom it applies. An Information Standards Notice is accompanied by a suite of supporting documents to assist with the successful implementation of an Information Standard. 

- Providers should be aware that as amendments made by the Health and Care Act 2022 have now   commenced, you could be asked to provide information on your compliance with an Information Standard for the purposes of monitoring and compliance.

<h2>How has the law changed</h2>

- Previously, public health and adult social care providers had a statutory duty to “have regard” to Information Standards but were not obliged to comply if there was a justification.  

- However, the law has now changed which means both public and private health and adult social care providers will have a statutory duty to comply with any mandatory Information Standards that apply to them.  

- The legislative changes will also allow for monitoring and enforcement action to be taken against private health and adult social care providers where they fail to comply.  

- NHS bodies are required to comply with a mandatory Information Standard as a condition of the Provider License. 

These legislative changes are part of a wider suite of reform. Forthcoming changes will also make compliance with Information Standards mandatory for providers of information technology, IT services or processing of information using IT in the provision of health care and adult social care. 

This will ensure that both providers and IT suppliers are working towards a consistent set of rules – making seamless and safe information exchange possible across the health and adult social care system.

<h3>Why were these changes necessary</h3>

- Providers and IT suppliers have told us that they would welcome greater clarity on priority Information Standards and where they should apply. 

- Inconsistent adoption of Information Standards continues to limit seamless data sharing between health and adult social care providers.  

- By strengthening previous legislation, we can enforce compliance with priority Information Standards and ensure that information can be shared more effectively across our health and adult social care system.

<h4>What do providers need to do</h4>

An Information Standard Notice will set out the statutory duty that is placed on providers. Providers are then required to meet their statutory duty to comply with a mandatory Information Standard within the specified timeframes. 

Providers should be aware that they could be asked to provide information on their compliance with Information Standards for the purposes of monitoring compliance. 

NHS bodies are required to comply with an Information Standard Notice as a condition of the Provider License. In the future, private providers may face enforcement action if they fail to evidence compliance with mandatory Information Standards within the specified timeframes.  

Enhanced assurance of Information Standards will ensure that consideration has been given to how conformance will be monitored and enforcement action taken - and to ensure that the statutory duty that is being placed on providers is realistic and achievable. 

Who to contact for more information 

Please contact england.standards.assurance@nhs.net  to understand more about these legislative changes and what they mean for you.

What are mandatory Information Standards

Guidance for CQC registered adult social care providers and their associated suppliers implementing the Adult Social Care Record (MODS) which represents the minimum operational data standard for direct care data in England.

Data Dictionary (Online Data Catalogue)

Data Dictionary Downloads (under Resources)

Conceptual Model

https://digitalsocialcare.refined.site/space/DHSC1/2053865910/Requirements+and+use+Cases

Related Standard

MODS Implementation Guidance

<span>All legal basis selected and guidance appears here</span>


Open government license

ztest-standard4

Metadataworks exchange

Miss any should requirements in the event you are using a system that was procured this year

Ztest standard4: Implementation Guidance

About this document