Last reviewed: May 2026

Clinical Safety & Intended Use (DCB0129)

This page explains what GPWidget is for, what it is deliberately not for, and how we manage clinical safety. It is the public summary of our Clinical Risk Management System and Clinical Safety Case Report.

In short

GPWidget is a non-clinical operational support and knowledge platform for GP practices and PCNs. It is not a clinical system and is not for diagnosis, treatment or patient records. We run a clinical risk management system aligned with DCB0129 (the NHS clinical safety standard for health IT suppliers), overseen by a Clinical Safety Officer, and assess residual risk as low and tolerable for its intended use.

1. What GPWidget is for

GPWidget helps authorised practice and PCN staff locate, retrieve and summarise their organisation's own operational information — policies, workflows, escalation processes, guidance and onboarding material — to save time and improve consistency. An optional AI-assisted search feature can be enabled or disabled per site and includes citations back to source content.

2. What GPWidget is not for

GPWidget is explicitly not designed or intended for:

diagnosis, triage or treatment recommendations;
clinical decision support or prescribing advice;
storing or managing patient medical records;
connecting to NHS clinical or electronic patient record systems.

It is not designed to process patient-identifiable data; inadvertent entry of such data is treated as foreseeable misuse and managed by our safety and moderation controls — see Patient Data Protection in AI.

3. How we manage clinical safety

DCB0129-aligned process — a Clinical Risk Management System identifies, assesses, controls, monitors and reviews safety risks across design, deployment and operation.
Clinical Safety Officer oversight — a named CSO governs the hazard log, safety case and clinical sign-off of changes.
Hazard log & safety case — key hazards (information quality, search relevance, AI accuracy and scope, availability, patient-data-in-free-text) are documented with their controls.
Change control — material changes undergo a safety impact assessment before release.
Regular review — the safety case is reviewed quarterly, or sooner following any material change.

4. Shared responsibility (DCB0160)

As the supplier, Build IT Medical Ltd maintains the platform's safety controls and governance. Deploying organisations (practices/PCNs) remain responsible for local clinical safety governance under DCB0160 (the NHS clinical safety standard for organisations that deploy and use health IT), appropriate use, and ensuring content within their environment is accurate and current.

The bottom line

A non-clinical operational support tool with a DCB0129-aligned clinical risk management system, Clinical Safety Officer oversight, a maintained hazard log and safety case, and residual clinical risk assessed as low and tolerable for its intended use.