... 'cause defensible is a word that gets thrown around, and when you say a decision is defensible, what specifically has to be true, say, the night before somebody asked that question?

Y- you, you have to have the, the clear decision pathways set out.

So decision support's always been something that, th- that's been part of what organizations do, and like, uh, particularly in, in the years I've been around healthcare, I've seen this a lot.

Um, but I inherited a system at one point, it was being used for charge capture, and it was actually connecting to an OR schedule and connecting to a billing system, connecting to a patient demographic, um, system, and it was making decisions on whether to generate a case or not.

And it's for this, a system that was actually inside of the ORs.

And when I started to look at it, I said, "Well, how do we know why something gets a case versus doesn't get a case?" And a technical wizard is sitting there explaining the whole thing to me.

Like, "Well, well that's great, but what happens if something goes wrong and I need to understand how that decision got made? Where is it?" "Well, it's in the code." I'm like, "Well, that's not a, that's not a good enough answer." Um, I'm not gonna have an engineer from the legal team go look at that code.

But how do we maintain, how do you maintain safety when you're going 400 miles an hour?