Walk into any hospital today and you’ll see the same bottleneck: a single, massive model trying to play every role at once. One model and one generic interface. We are asking a single, general purpose model to list differentials, draft clinical notes, check billing codes, and write patients letters.

Dear readers, When we tell the market that Isaree refuses to build thin wrappers around closed cloud models, the critique is immediate: Why not just use the best available API? Why insist on on-device, open-source or open weight based agents? You are being dogmatic about technology. We are

I still remember a conversation I had with a physician friend late one evening. She told me how she was struggling to integrate AI tools into her clinical workflow, each one promising to help, but none fitting naturally into how she actually practiced medicine. Every new model meant another login,

By Bart de Witte, Founder, Isaree 24 June 2026 We shipped our macOS agent harness, integrated openEHR, survived a hackathon, and watched the cloud-vs-on-device debate collapse under its own weight. Here's what happened. Last week, in the previous post, I argued that the long tail