Clinical workflow tools
Checklists and handovers for staff working under time pressure.
Healthcare
Healthcare software where the safety case comes first
Clinical workflow tools and patient-facing apps built around the clinical risk rules from day one. We have moved years of sensitive records for a national platform without downtime.
2025Year the clinical safety standards became a legal duty
0Downtime during a sensitive data migration
3Security testing regimes on that build
40+Developers on staff
What this is
Clinical safety is a named person and a lifecycle
In England, makers of health IT work to DCB0129 and the organisations that deploy it work to DCB0160. Both need a named Clinical Safety Officer. Planning for that on day one changes the project plan.
Where we have proof
Sensitive-data migration and layered security testing on a national education platform. It is the nearest build we can show you.
Where we have not yet
We have no published healthcare case. We say so on the first call and show the closest work.
Services
What we build for healthcare teams
Patient-facing apps
Built to the accessibility and privacy rules the audience expects.
Data migration
Analysis, mapping and structured transfer of records that cannot be lost or exposed.
Security testing
Penetration testing, static analysis and network assessment during delivery.
Clinical safety documentation
Hazard log and safety case evidence assembled from the engineering record.
Integration with records systems
The data has to land where the clinician already looks.
Standards
What the clinical risk rules require
These decide who signs what before a release, so they belong in the plan.
DCB0129 for manufacturersClinical risk management for makers of health IT: proportionate processes, clinical safety documentation and a named Clinical Safety Officer through development.
DCB0160 for deployersThe organisation using the system appoints its own Clinical Safety Officer. The role is not shared with the supplier.
A legal duty since 7 July 2025Section 95 of the Health and Care Act 2022 changed the position from have regard to must comply.
Under reviewNHS England is consulting on both standards. Current versions are DCB0129 v4.2 and DCB0160 v3.2, so build the process to absorb a change.
Case study
The nearest build we can show you
Sensitive data, Norway
National education analytics platform
Different sector, same discipline. A Norwegian technology company needed its national platform modernised after a previous vendor missed the deadline. A dedicated team moved years of sensitive records, with penetration testing, static analysis and network assessment during delivery.
0Downtime during the migration
Who we build for
The teams who call us
Digital health start-ups
Teams that need the clinical safety process built into delivery from the first sprint.
NHS suppliers
Vendors working to DCB0129 who want engineering evidence that is easy to produce.
Clinics and care providers
Organisations deploying software under DCB0160 with their own Clinical Safety Officer.
Device and monitoring makers
Product teams who need the app and the data pipeline behind the device.
Related reading: the sensitive data migration case study and custom software development.
FAQs
What buyers ask first
Do you have a healthcare case?
Not yet published. We say so on the first call and show the closest work, which is sensitive-data migration and security testing on a national platform.
Can you work to DCB0129?
We build to the process your Clinical Safety Officer sets. The officer owns the clinical safety case, and our job is to make the engineering evidence easy to produce.
How do you handle sensitive data?
Migration gets its own team and plan, and testing runs alongside the build, well before go-live.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us who your Clinical Safety Officer is
Thirty minutes with the engineers on the product, the standard you work to and the evidence you will be asked for.