Interoperability’s next frontier: The Individual Access Layer

An interview about the basics of the individual access layer of healthcare IT—including what individual access services consists of, the companies that are major players, and opportunities and challenges for various market participants.

Amanda Berra
Amanda Berra
13 min read

An Interview with Brendan Keeler, AKA ‘Health API Guy’

Over the next few years, we all need to be tracking a new and highly active front in Health IT innovation and change: The emergence of an “individual access layer” that lets patients control how their data moves across tools and apps—and all the related healthcare industry ecosystem opportunities and risks that come that new infrastructure. I’m talking about a new class of players, known as Individual Access Services (IAS) companies. These companies, backed by fresh capital and reinforced Trusted Exchange Framework and Common Agreement (TEFCA)—an interoperability effort that we’ll dive into later—stepped up information‑blocking enforcement. We’re also seeing rising demand for patient‑authorized data that flows into AI tools and consumer apps, all of which is working to turn patient‑directed exchange into a real market. If/as this real market solidifies, it will have strategic and operational consequences for everyone in the healthcare ecosystem.

To help make sense of what this “individual access layer” actually is, who the key players are, and what all of this means for health systems, I sat down with Brendan Keeler—better known as Health API Guy—for a quick tour of the landscape.

Let’s talk.

Questions? Want to learn more about what Union can do for you? We’d love to hear from you.