What Doogie is built to do, what it is built never to do, the deterministic controls that enforce the difference, how we evaluate it, how patient data is protected — and what is not built yet. This is the page to read before any other page on this site.
Safety, the spine of everything
Doogie never closes a clinical encounter on its own. Every brief is a draft for a qualified clinician to review, accept, edit or discard. Accountability stays with the human.
Doogie’s replies pass through deterministic, rule-based code before a patient sees anything — never a model. It won’t comment on medication or dose, and a red-flag screen runs on every message. See Evidence for how well it performs.
Doogie stays inside collecting and structuring what the patient reports. It will decline to advise on treatment or medication, and says clearly when something is outside what it can safely help with.
Escalation is built to stop the conversation, not just describe it. When Doogie’s deterministic red-flag screen fires, it ends the history, shows the local emergency number with a tap-to-call link, and alerts the practice. It never asks a patient in danger to keep answering questions. That flow is built and enforced in code today. Whether it catches everything it should has not yet been independently measured — see Evidence.
The gap we say out loud
We would rather under-promise and earn trust step by step, so here is what this page is not claiming.
No Clinical Safety Officer yet. Doogie has no appointed Clinical Safety Officer, no approved clinical safety case, and no clinical validation in any market. The controls described above are written and enforced in code; they have not been signed off by a named clinical safety authority.
Nothing on this site may be presented to a customer, commissioner, health body, investor or regulator as evidence of regulatory compliance or clinical approval. Where a control is built but its performance is unmeasured, we say so rather than imply the opposite.
Clinical evidence & quality
We grade Doogie internally against a defined quality framework today. Formal benchmarking with practising clinicians in partner markets has not started yet — it is the next stage on our roadmap. These are the dimensions we grade, and the bar we are building toward.
We evaluate Doogie the way medicine evaluates itself: against expert consensus and documented pathways, with safety weighted above everything else.
Illustrative targets from our evaluation framework. Formal clinical benchmarking with partner practices is planned; we will publish results.
Data protection & interoperability
Doogie speaks the standards health systems already run on, and treats data protection as an engineering requirement, not an afterthought. It is architected toward POPIA and GDPR; we have not had this independently audited, and we say so rather than claim compliance.
Architected toward the strictest of the data-protection regimes we operate under, POPIA and GDPR: lawful basis, purpose limitation and data minimisation designed in from the ground up, with encryption in transit and at rest. This has not yet been independently audited.
POPIA · GDPR · Designed inThe health profile belongs to the patient, not to a practice or a funder. Consent is granted per practice, in plain language, and can be withdrawn at any time.
Consent by designFindings coded against SNOMED CT via the SNOMED CT terminology services, so the record holds clean structured data instead of free text to retype.
SNOMED CT terminology servicesStructured output as FHIR R4 resources, so a Doogie brief can slot into modern clinical systems without bespoke plumbing.
Standards-firstA clear path to structured write-back into the practice management and health record systems clinics already run, so briefs land where clinicians already work.
FHIR write-backDoogie is developed under a clinical risk-management process with a living hazard log, tracked against recognised clinical safety standards. As stated above, that process does not yet have an appointed Clinical Safety Officer or an approved safety case.
Hazard log, no CSO yetSee it for yourself
Patient-reported context first, clinician always in charge. Join the waitlist, or see how the product works end to end.