Pricing
Priced by what you deploy, not per seat
SafeDeploy is priced against the size of your clinical safety obligation: how many systems you deploy, how often they change, and whether you need a Clinical Safety Officer. Per-seat pricing makes no sense for a document that one named person signs.
Last reviewed
What each level includes
Three levels, matched to the three groups that carry duties under DCB0129 and DCB0160. Every level includes Clinical Safety Officer review by a registered clinician.
Practice
A single GP practice or dental practice carrying DCB0160 duties for the software it deploys.
[PLACEHOLDER: practice price]
[PLACEHOLDER: billing unit, e.g. per practice per year]
- Deployment-side hazard log
- Clinical Risk Management Plan for your organisation
- Clinical Safety Case Report per deployed system
- Change tracking when a supplier ships a release
- Clinical Safety Officer review by a registered clinician
Group or PCN
A dental group or Primary Care Network deploying the same systems across several sites.
[PLACEHOLDER: group price]
[PLACEHOLDER: billing unit, e.g. per site per year]
- Everything in Practice
- Shared hazard log across sites, with per-site deployment context
- Consolidated reporting for the group
- [PLACEHOLDER: any group-specific inclusions]
Supplier
A primary care software supplier that needs a DCB0129 safety case to sell into the NHS.
[PLACEHOLDER: supplier price]
[PLACEHOLDER: billing unit]
- Product hazard log organised by feature
- Clinical Risk Management Plan and Clinical Safety Case Report, versioned per release
- Deployment packs that turn your DCB0129 evidence into your customers' DCB0160 documentation
- Change tracking across releases
- Clinical Safety Officer review by a registered clinician
What drives the price
Four things change the number. We publish them so you can work out roughly where you sit before you speak to us.
- How many systems you deploy
- A practice running one clinical system and one AI scribe has a smaller deployment-side safety case than a practice running six patient-facing tools.
- How often your software changes
- For suppliers, the Clinical Safety Case Report is reissued per significant release. A monthly release cadence is more work than a quarterly one.
- How many sites
- Deployment context is per-site: the building, the staff and the workflow. Sites that share a workflow share most of the analysis.
- Whether you need a Clinical Safety Officer
- Some organisations have a registered clinician who can hold the role. Some do not and need ours. That is the largest single difference in price.
What you are not buying
Get a quote
Tell us how many sites you have, which systems you deploy and whether you have a Clinical Safety Officer. We will come back with a number, not a discovery call.