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.
HealthcareDesigning for three in the morningSoftware in a hospital is clinical equipment. It gets used by someone who has been awake for fourteen hours, not by someone at a demo. What that single constraint changes about interface, error messages and defaults.HealthcareBuilding for ABDM: ABHA, consent and national registriesIndia's digital health stack is not a compliance chore bolted on at the end. How ABHA identity, consent-driven exchange and standards-based records fit into everyday hospital workflows rather than sitting beside them.HealthcareThe ward round is the specYou cannot design clinical software from a requirements document, because the document describes the process as somebody believes it works. Watching a ward round for two hours changes what you build.HealthcareWhat a discharge summary is actually forIt is the only part of an admission most of the outside world will ever read, and it is usually written last, fastest, and by the person with the least context. A look at the document as a design problem.
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.