Insights · 20 articles · 5 topics
How this softwareactually gets built.
Notes from the people building hospital platforms, clinical AI and the integrations between them. Written for the engineers, clinicians and security teams who have to live with the result.
No thought-leadership theatre. What we decided, why, and what we would do differently.
Reading
Latest articles.
Newest first. Filter by what you work on.
Responsible AIDrift is the failure mode you will not noticeA model that fails on day one gets fixed. One that degrades slowly as the population, the coding practice or the upstream data changes will keep producing plausible output while quietly becoming wrong. What we monitor, and why the alerting points at inputs rather than accuracy.Responsible AIAI that hands you something to check, not something to trustA model that cannot explain itself has no business near a bedside. How Zypo Clinical AI is built so a clinician gets a suggestion with the reasoning attached and keeps the decision, the override and the audit trail.Responsible AIWhat we ask before a model goes near a patientGoverning clinical AI is mostly a set of questions asked early enough to still change the answer. The ones we work through before anything is built, and the ones that have stopped features.Responsible AIModel documentation a clinician will actually readTechnical model cards are written for reviewers and read by nobody at the bedside. What a one-page description has to contain for the person deciding whether to act on an output.
Stay in the loop
Get new writing when it lands.
Occasional, technical, and never a newsletter for the sake of one. We will only write when we have something worth your time.