Two clinical safety officers, our hazard log handed over on day one, and nothing to unpick if you stop.
wai is a clinical operating system built inside a working private clinic in London and used by its clinicians every day. It writes the consultation as it happens, refuses to send a letter with a gap in it, runs the round, and keeps the organisation's records in the organisation's own tenancy.
The clinician talks to the patient. The note, the coding and the letter are drafted from the conversation and held for the clinician to change or reject before anything is signed.
A letter with a gap in it is refused rather than sent. Every draft carries the name of the person who accepted it and the time they did, in an event log the organisation can export.
Results, follow ups and the things that fall between appointments are worked as a list, with the next action named on each one.
Enquiries, bookings and repeat requests are drafted and queued for a person to approve, which is where most of the time in a practice actually goes.
Records stay in the organisation's own tenancy, in its own country, and an organisation that wants to hold its own model can.
DCB0129 applies to whoever manufactures a health IT system. That is us, and the hazard log, the safety case and the risk management plan below are ours to write and ours to keep current.
DCB0160 applies to whoever deploys and uses one. That is you, and the case is yours to make. It is made on our evidence, handed over at the start of a pilot rather than at the end of one, and we sit in the meetings where you make it.
Both standards require a Clinical Safety Officer who is a registered healthcare professional, and the two cannot be the same person. Ours is not yet appointed and the month is against it below, which is the honest answer to the first question you are going to ask.
Records stay in your own tenancy, in your own country. An organisation that wants to hold its own model can. Nothing clinical is used to train a model of ours.
Version 0.1, dated 6 September 2026. 71 hazards across 156 agent actions, each scored against the criteria in our clinical risk management plan.
A structured argument under DCB0129 3.4.1 and DCB0160 3.4.1, with the risk management plan that sets the scoring.
Every place in the system where a model acts or proposes, read out of the source. 156 actions, of which 33 reach a patient or the record with nobody accepting them.
Not appointed, expected October 2026. Until one is, every score in the hazard log is a proposal rather than an approved risk assessment.
The five areas of the Digital Technology Assessment Criteria are Clinical safety, Data protection, Technical assurance, Interoperability and usability and accessibility. The second version of the form was published in February 2026 and the previous one retired on 6 April 2026.
Not submitted, expected January 2027. Its clinical safety section asks for a Clinical Safety Officer, so it follows that appointment rather than running beside it.
Not submitted, expected November 2026. The self assessment built on the ten National Data Guardian data security standards, now aligned to the NCSC Cyber Assessment Framework.
Not held, expected December 2026. Mandatory across every G-Cloud lot and Plus for the cloud lots.
Not held, expected June 2027. Started rather than claimed, because underway by the deadline is accepted and a certificate we do not have is not.
Not listed, expected December 2026. NHS England opened a self certified supplier registry in January 2026 and applications remain open. It asks for the Clinical Safety Officer, the assessment criteria and a device position first.
No written opinion held, expected November 2026. Guidance of 29 July 2026 exempts transcription, summarising, drafting correspondence and suggesting codes for a clinician to review. Ours does more than that list, so we are asking rather than asserting.
The hazard log, the safety case and the agent actions inventory go to a named clinical safety or information governance team, as they stand. If it is a fit, you hear from us within 24 hours.
Insurance, registration, the data flow, the sub processors and the security statement, each with a status and a date, are in the Trust Centre. Frameworks and how we can be bought are on the public sector page.