Musings on healthcare IT, FHIR, EHR systems, and digital health innovation

🔥 FHIR in the hole!
Back to posts

This architecture is the forcing function for recognizing (explicitly or…

Original post on LinkedIn

This architecture is the forcing function for recognizing (explicitly or tacitly) AI agents as drivers of interoperability. Agents will increasingly be tools like a mouse and keyboard — i.e., the interfaces by which users interact with apps. Locking them out won’t be the answer. Claiming every pixel is a licensed “interoperability element” is also a non answer.

Brendan Keeler (original on LinkedIn):

An open-source AI agent by Fan Pier Labs now logs into MyChart with patient credentials, handles 2FA, and exposes 35+ MCP tools for reading and writing patient data, messages, refills, appointments, the works. Unlike FHIR APIs or TEFCA IAS, this thing can do anything the patient can do in the UI.

The tool is raw and buggy, but the implications are sharp: the RPA horde is not just coming - they’re here. EHRs can fight this trend or lean into it. And there’s a real argument that to allow is to control.

Conversation on LinkedIn

2 comments · 76 reactionsReply on LinkedIn
  • Alexander GoelMar 24, 2026

    COO@PhenoML|Talk to Me About Connecting Healthcare Data

    I hope the horde convinces more API access which already seems to be a trend from some players.

    APIs seem like the best way to exercise control

    2 reactions

  • Doug HornerApr 18, 2026

    Changing the world... would be easier with the source code.

    This is cool. We need to allow patients to grant and track agency to their physicians as well as agents. I was just talking to a neurologist who spends 10 mins per patient fetching information from Epic and Cerner.