Jonathan Palmer

But, you know, can we think about how do we think about, you know, all the different areas where AI is touching the workflow?

And I guess from your perspective, you know, what's real and what's maybe a little bit hype for lack of a better term?

Interesting.

So when we think about what you're doing in this area, how much of it is partnering with some of these providers that you might have referred to before?

You're not doing the ambient piece with somebody else, but you're building it yourself versus the de novo investment.

Can you talk a little bit about what you have to do to stand that up?

And if you could frame it in any way around dollars or people or engineers, I don't know what the right measure is, but that would be helpful.

Interesting.

But in terms of building your own products, can you talk about the... One of the themes that comes up in these discussions is just...

The challenges of actually getting the right people with the right skill sets to build these products.

I mean, is there a war for talent that you're seeing for these engineers?

Look, there's always been a war for talent, you know, for the best.

Maybe just going back to the marketplace and the APIs, how do you balance maybe the challenges of having this open marketplace versus maybe wanting to own some of these workflows ultimately?

Well, is the right way to think about then that to summarize maybe what you're saying there is that the way competitors are thinking about ambulatory services

The idea of a closed system is ultimately not going to work for them in the long term.

I don't believe so.

Well said.

If you think about how customers look at you guys today and how they're evaluating, let's say, Athena versus maybe their their legacy system or one of your competitors.

What is the tip of the spear, I guess, that's maybe leading to the tipping point in going with Athena versus somebody else?

A couple things.