DTAC v2: what changed, what NHS buyers look for, and how to prepare
The Digital Technology Assessment Criteria moved to v2 with sharper expectations on clinical safety, AI, accessibility and interoperability. Here's the plain-English version.
DTAC, the Digital Technology Assessment Criteria, is the baseline NHS buyers use to assess digital health products. Version 2 raises the bar on clinical safety evidence, AI assurance, accessibility and interoperability, and ties the criteria more tightly to ongoing tenders.
The five DTAC pillars
- Clinical safety (DCB0129 with a real Safety Case, not just a policy)
- Data protection (DPIA, Named DPO, lawful basis articulated)
- Technical assurance (Cyber Essentials Plus or ISO 27001, secure development)
- Interoperability (FHIR, standards-based APIs, where relevant)
- Usability and accessibility (WCAG 2.2 AA, real-user testing)
What's tougher in v2
Buyers now want evidence, not assertions. 'We follow DCB0129' is no longer enough, they expect to see the Safety Case Report, the Hazard Log and the named CSO. The AI section expects classification against the NHS AI Assurance Classification Framework where applicable.
Accessibility went from 'we considered it' to evidence of testing with disabled users. Interoperability went from 'we have an API' to evidence the API conforms to NHS-supported standards.
How DigiSafe helps
We build complete, defensible DTAC v2 packs and review them as a critical friend before submission. Most suppliers we work with pass first time, those who don't get a clear remediation list, not a vague 'try again'.
Want this applied to your product?
We turn standards like this into evidence packs, safety cases and embedded CSO support, so you can focus on building.
Keep reading
- Standards
DCB0129: Clinical Risk Management for Health IT Manufacturers, explained
What DCB0129 actually requires, why NHS buyers ask for it, and how to build a Safety Case that holds up to scrutiny.
- Standards
DCB0160: Clinical Risk Management for NHS Deployers, explained
DCB0160 is the deployer's responsibility, and it doesn't disappear just because your supplier has DCB0129. Here's what NHS organisations actually need to do.
- Medical Devices
Software as a Medical Device (SaMD) in the UK, do you need to register?
Not every health app is a medical device. But many that don't think they are, are. Here's how to make the right call without over- or under-classifying.
