

A healthcare AI system can do exactly what it was built to do and still leave a care team with more work. Flagging a change between appointments may help a patient receive care sooner, but it also creates a review task for someone already caring for other patients.
Before expanding AI-supported monitoring, I would want evidence that it reduces avoidable review work and that care teams have the time, context, and authority to act on changes that matter.
Earlier this year, I wrote that browser automation was a bridge period.
At the time, my focus was trust. Agents could technically complete workflows, but the systems around them were not really designed to know who was behind the request, what the agent was authorized to do, or whether the interaction should be trusted.
In June, the U.S. Department of Health and Human Services announced that more than one billion health records had been exchanged through TEFCA, the national interoperability network. The volume grew from 10 million to more than one billion in less than a year. Healthcare is developing the infrastructure required to exchange information across the system at a scale we have not seen before.
Voice AI’s next executive benchmark is inbound ability, because the voice is the interface, but the workflow is the value.
I’ve written before that voice AI’s missing piece is the ability to listen while it talks.
That’s still true. A voice agent that can speak back is no longer the interesting benchmark. The more useful question is what happens after somebody starts talking.