Clinical
documentation.
What clinical safety officers, commissioners, and procurement teams need to see before a pilot. Each section here is a summary. Documentation is available to commissioners on request under NDA.
What Labas does.
Collects the patient's account before the appointment: structured questions, and the patient's own words kept exactly.
The questions and the summary's wording are signed by our Clinical Safety Officer.
No generative AI.
Every change a patient reports to their record goes to the GP; nothing updates the record by itself.
Shows every patient the 999 and NHS 111 emergency advice.
Clinical Safety
Officer.
NICE recall
intervals.
Clinical decision-making is the GP's job. Labas does not make clinical decisions. What Labas does is track your patient list against the monitoring and recall intervals NICE specifies, and surface patients who are due. The GP decides what to do about them.
A GP may legitimately see a diabetic patient annually if clinical judgment says so. Care Intelligence does not correct the GP. It only raises a hand when the calendar has moved past the NICE interval and asks whether the GP wants to act.
DCB0160 deployer pack.
DCB0160 is the complement to DCB0129. Where DCB0129 is the manufacturer's clinical risk case, DCB0160 is the deploying organisation's. Each GP practice or care home operating Labas is responsible for their own DCB0160 safety case file.
To support this, Labas provides every pilot site with a DCB0160 implementation pack: a pre-filled template safety case covering the deployment scope, integration points, local hazards, and the mitigations Labas has already put in place upstream. The deployer reviews, localises, and signs. A single named contact at Labas is assigned to each deployer for the lifetime of the pilot.
Request documentation.
Commissioners, Clinical Safety Officers, and procurement teams can request the DCB0160 deployer pack template and the NICE recall configuration schedule. We send under NDA, typically within one working day.