Skip to content

2025

Designing a Patient Self-Reporting Stack Around Humans and AI

Every care team I talk to has the same complaint: patients happily text, leave voicemails, and fill out surveys, but those signals rarely make it into the plan of care.

Electronic records were never built to absorb that ambient context, and the people who could act on it are already drowning in portal messages and follow-up calls. Yet the value is obvious, timely symptom reporting keeps people out of the ED, surfaces social needs, and lets providers adjust therapy before a flare turns into a crisis.

What we need is a stack that captures self-reported data, triages it with large language models, and still gives clinicians the last word. The winning pattern blends thoughtful UX, observability, and a human-in-the-loop workflow.

Recursive Summarization Unlocks Effective LLM Integration in Healthcare

Your patient has 247 pages of medical records spanning 8 years. Two ER visits, three specialists, ongoing knee osteoarthritis, recent ACL reconstruction. How do you create a coherent summary that preserves critical information while making it digestible for both clinicians and AI systems?

The answer isn't just summarization, it's recursive summarization. And the secret isn't just what you summarize, but what you choose to preserve at each level of abstraction.

How Claude Code Made Me Fall in Love with the Terminal

Like many of you, I recently made the full switch from Cursor to Claude Code. This transition marked more than just a tool change – it fundamentally transformed how I think about development environments.

For years, I lived in VSCode (recently Cursor), relying heavily on mouse navigation and minimal keyboard shortcuts. I resisted the pull of Neovim and keyboard-centric workflows. But after embracing Claude Code, I discovered something profound: the terminal is the new IDE. You can run it everywhere with a consistent workflow – be it a Linux box, your Mac, or a VPS. That's all you need.