Most healthcare product thinking runs through two lenses: what the patient experiences, and what the provider experiences. Roadmaps and design reviews optimize for one or the other.
A third lens gets skipped almost every time: whoever has to operate and maintain the thing after it ships. Call it clinical ops, call it the admin — the person who has to update a rule or fix a workflow six months from now without an engineer in the room.
That's always mattered, but it's urgent now. Claude Code makes it possible to build custom interfaces, configs, and business logic almost as fast as you can describe them. More of that logic is quietly moving from vendor config screens into code only an engineer (..or Claude) can read.
Patient and provider lenses tell you if a feature should exist. The ops lens tells you if it survives contact with reality. Whether someone without a codebase can see what the logic does, change it, or turn it off. Skip that, and you've shipped a liability with a UI.
The fix: treat the third lens as a design requirement, not an afterthought. Build the admin surface alongside the feature, not after someone gets stuck.
Who owns that on your team right now?