Skip to main content
    NHS DSPT for Software Vendors and Care Providers, Explained
    Compliance

    NHS DSPT for Software Vendors and Care Providers, Explained

    What the NHS Data Security and Protection Toolkit actually requires, who needs to submit, and how to align Salesforce and adjacent platforms.

    Digitalised Solutions Team
    May 29, 2026
    7 min read

    What the DSPT is, in one paragraph

    The NHS Data Security and Protection Toolkit (DSPT) is an annual self-assessment that any organisation handling NHS patient information or systems is expected to complete. It maps to the National Data Guardian's ten data security standards and to UK GDPR. The submission window runs to 30 June each year for the current toolkit version.

    Who actually has to submit

    The DSPT applies more widely than many UK care providers realise. You need a submission if you are:

  1. An NHS organisation or NHS-funded service.
  2. A CQC-registered adult social care provider (a separate, lighter assessment route is available).
  3. A software vendor processing NHS personal data on behalf of a customer.
  4. A supplier whose contract with an NHS body requires DSPT compliance.
  5. If you are unsure, the safer assumption is that you need to submit. The penalty for a missing submission is rarely a fine; it is being excluded from procurement.

    The four levels in practice

    DSPT outcomes are reported as Standards Not Met, Approaching Standards, Standards Met, or Standards Exceeded. For most UK providers and vendors, the working target is Standards Met. Approaching Standards is a recoverable position but a procurement disadvantage. Standards Not Met will block NHS contracting.

    What it actually asks for

    The toolkit groups its questions around the ten National Data Guardian standards. In practice, the recurring evidence requirements are:

  6. A current information asset register and data flow map.
  7. Named senior information risk owner (SIRO) and Caldicott Guardian where applicable.
  8. Documented data protection impact assessments for high-risk processing.
  9. Up-to-date staff data security training, with completion evidence.
  10. Access control: least privilege, named accounts, joiner/mover/leaver process.
  11. Patch management, supported operating systems, anti-malware controls.
  12. Incident management and breach reporting procedures, tested.
  13. Business continuity and disaster recovery plans, tested.
  14. Supplier assurance, including DSPT or equivalent from your own processors.
  15. Where Salesforce and adjacent platforms fit

    Salesforce itself runs in environments aligned to recognised security standards, but the deploying organisation is responsible for how it is configured, who has access, and what data flows in and out. DSPT evidence for a Salesforce org typically covers:

  16. Profile, permission set, and sharing rule configuration.
  17. Login IP and session controls.
  18. Field-level encryption where appropriate, especially for special category data.
  19. Integration patterns and the security of any middleware.
  20. Backup and restore procedure, with a test record.
  21. A data flow map covering Salesforce and every system it integrates with.
  22. The same logic applies to care planning, eMAR, rostering, and finance platforms.

    Practical alignment steps

    A pragmatic sequence for organisations that have let DSPT slip:

    1. Pull last year's submission and identify any questions where evidence is stale or missing.

    2. Refresh the information asset register against the current software estate.

    3. Walk the joiner/mover/leaver process end-to-end for each system.

    4. Re-run staff training and capture completion centrally.

    5. Test the incident response and backup procedures, and write down what happened.

    6. Collect DSPT or equivalent assurance from every processor.

    7. Submit and publish the assertion against each standard.

    The work is rarely the assessment itself; it is the evidence collection.

    Common pitfalls

  23. Treating DSPT as an IT exercise rather than a board-level information governance one.
  24. Assuming a SaaS vendor's certifications cover the deploying organisation's responsibilities.
  25. Stale data flow maps that do not reflect recent integrations.
  26. Training completion records that cannot be evidenced for individuals.
  27. Incident response plans that have never been tested.
  28. Where this fits in the wider estate

    DSPT is one of several frameworks shaping UK healthcare software decisions, alongside UK GDPR, the Caldicott Principles, and clinical safety standards. The Healthcare Software Solutions hub maps how these come together across CRM, care planning, finance, and reporting. If the immediate work is tightening configuration and access control on an existing Salesforce org, see CRM Stabilisation.

    Healthcare software decisions

    Turn research into a practical review of CRM, CQC evidence, reporting, integrations, and operational risk.