Choose which optional cookies and similar storage we may use. Strictly necessary storage is always on, because the site cannot work without it.

Healthcare and NHS development

We build software and AI to the standards NHS and private hospitals expect, with clinicians in the team. We manage clinical risk under DCB0129 as the manufacturer, with our own Clinical Safety Officer.

Last updated

What we build

  • Clinical workflow tools.
  • Patient communication, including voice AI.
  • Data platforms.
  • AI assistants for staff.
Draft (F14): Which clinical systems we integrate with.
  • Integrations with clinical systems. [TO CONFIRM which]

Standards we work to

We are the manufacturer under DCB0129, and our Clinical Safety Officer leads our clinical risk management. Our status against each standard is stated exactly.

Our status against each standard and scheme
Standard or scheme Our status
DCB0129 Prime Assist has a clinical safety case under DCB0129
DCB0160 [TO CONFIRM: What we provide to support customers' DCB0160 work, now offered as clinical safety for AI you deploy.]
Digital Technology Assessment Criteria (DTAC) [TO CONFIRM: DTAC version and date for Prime Assist.]
Data Security and Protection Toolkit (DSPT) [TO CONFIRM: Exact published status and year.]
ISO/IEC 27001 [TO CONFIRM: Certifying body]
Cyber Essentials [TO CONFIRM: Cyber Essentials or Cyber Essentials Plus]
ICO registration Registered with the ICO, the UK data protection regulator, registration number ZB592265
WCAG 2.2 AA Our target for this website
EU AI Act transparency (Article 50) We tell people when they are dealing with AI: our voice agents say so at the start of every call, chat assistants label themselves, and AI-generated content we publish is labelled where relevant.
Draft (F14): Interoperability standards such as FHIR.

Interoperability standards: [TO CONFIRM, for example FHIR]

Clinicians in the team

Our clinicians work with our engineers from the first design, and our Clinical Safety Officer signs off the clinical safety of what we build.

Meet the team
Draft (K4): Name the Clinical Safety Officer, with his consent.

Our Clinical Safety Officer is Dr Humzah Jessa, a practising doctor.

For NHS and private hospitals

NHS and private hospitals get the same clinical safety process.

Draft (F14): How to buy from us. Do not claim framework listings (for example G-Cloud) unless confirmed.

How to buy from us

[TO CONFIRM routes]

Our policy work

In 2026 we submitted written evidence to the House of Lords Science and Technology Committee on why UK small businesses find it hard to deploy technology into the NHS.

Read our House of Lords evidence

Questions people ask

Can you provide a clinical safety case?

Yes. As the manufacturer we manage clinical risk under DCB0129, and our Clinical Safety Officer signs off the clinical safety case.

Do you support our DCB0160 work?

Yes. Our clinical safety for AI you deploy service helps the deploying organisation with its DCB0160 work: checking the supplier's evidence, writing the safety case and hazard log with you, and reviewing safety after go-live and at every change. Your accountable officer and Clinical Safety Officer sign it off.

Draft (D5): DTAC version and date.
Have you completed DTAC?

[TO CONFIRM: DTAC version and date.]

Draft (K7): Which clinical system integrations are live.
Do you integrate with EMIS or SystmOne?

[TO CONFIRM: Which clinical system integrations are live.]