Latest / CareTalk: Healthcare. Unfiltered. / Turning Clinical Data Chaos into Clarity w/ John Laursen, SVP of Communications, IMO Health

Transcript

Turning Clinical Data Chaos into Clarity w/ John Laursen, SVP of Communications, IMO Health · CareTalk: Healthcare. Unfiltered.

• 0:00
  David: Healthcare AI is evolving faster than ever, but in the rush to innovate organizations, risk trading, accuracy, and safety for speed.
• 0:08
  David: Call it the fast fashion era of ai.
• 0:18
  David: Welcome to Care Talk Executive features a series where we spotlight innovative companies and leaders working to advance the healthcare field.
• 0:25
  David: I'm David Williams, president of Health Business Group, and my guest today is John Laursen.
• 0:30
  David: He is SVP of Product Commercialization at IMO Health, a clinical data intelligence company, improving how data is used in healthcare.
• 0:39
  David: John, welcome to Care Talk.
• 0:41
  John: Thank you, David.
• 0:42
  John: It's great to be here.
• 0:43
  David: You know, I love that term fast fashion, but I'd like you to explain, you know, what is fast fashion?
• 0:48
  David: What's the fast fashion era of ai and why are you using that term these days?
• 0:54
  John: Yeah, I mean, I think we can all think about fast fashion in, um, whether our daughters or sons are buying from h and m and, and the speed that that market, the, the fashion market kind of creates to match the immediate trends.
• 1:08
  John: Um, as I apply that to healthcare.
• 1:10
  John: I think healthcare always has had kind of ebbs and flows of, of fast fashion.
• 1:15
  John: Like some, a lot of organizations can start to follow a trend really quickly in healthcare.
• 1:22
  John: Um, and I feel like we're in one of those today.
• 1:26
  John: Um, what you often see in that is a lot of those organizations then fall out of favor as they can't demonstrate meaningful value over a long period of time.
• 1:36
  John: The fundamentals of healthcare.
• 1:38
  John: Don't often shift that much, um, despite some of the frothiness that you'll experience in one given year or a couple years.
• 1:45
  John: So organizations that pop up show a try to align to a near term trend but aren't underlying fixing the underlying problems really fit that fast fashion definition to me.
• 1:56
  John: So I feel in the AI space, we're, we're there again.
• 1:59
  John: Um, we'll have more in the future, but we're back into an area where somebody can claim they do ai and that's enough to get.
• 2:06
  John: In the market, but it's not enough to sustain the market.
• 2:09
  David: Got it.
• 2:10
  David: You know, we've had other moments of health tech hype in the past.
• 2:14
  David: Is there something different about this moment with ai or is it just kind of one in a series?
• 2:21
  John: I think the, the big thing I think is different in this moment is that AI enables.
• 2:27
  John: It's a lower barrier to entry into the market, um, both from a pers from a funding perspective or from a marketing perspective.
• 2:36
  John: But honestly, either you and I, David, we could, we could stand up an AI healthcare tech company pretty quickly.
• 2:42
  John: The foundational and frontier models that are now available to everybody do create a higher step.
• 2:49
  John: I think what, uh, is the same though as the other fast fashion periods is that that doesn't mean just because you can get in, you can demonstrate meaningful value to the provider market.
• 2:59
  John: And again, those fundamentals of their funds flow haven't shifted.
• 3:03
  John: So if you're not aligned and having a deep impact there, you're still gonna go out of favor quickly.
• 3:10
  David: What sort of risks do you see arising when organizations, you know, rush to adopt AI as many are doing now, perhaps without that rigorous evaluation?
• 3:20
  John: I think, I mean, um, again, we're in that period where hype can kind of out see our outpace right reality.
• 3:27
  John: Our provider customers at IMO and we've, we work with thousands of hospitals and, and clinicians across the country.
• 3:35
  John: Um, they're taking a very major approach to ai, um, uh, doing really concerted pilots to understand the impact in particularly in the clinical workflow, but also in the billing workflow.
• 3:46
  John: And so I, I don't see a rush to adopt.
• 3:48
  John: I see measured, um, implementation and evaluation, um, because they know the risks.
• 3:54
  John: Um, healthcare.
• 3:57
  John: Has in numerous end end cases or use cases that kind of bleed out.
• 4:03
  John: And the, if you don't get those right, you can have a very negative impact both financially and clinically to your, to your organization.
• 4:10
  John: So I think most organizations realize that and are gonna take a very measured approach into evaluating an AI partner.
• 4:18
  David: So when they do that, what are some of the top criteria that a provider or a payer should be using when they're evaluating an AI tool?
• 4:28
  John: Yeah, I think, I mean, again, working with health systems over the last 30 years at IMO and, and, um, health systems are rational buyers.
• 4:39
  John: They're rational decision makers.
• 4:41
  John: They are gonna have to understand your value proposition in a way that fundamentally impacts their clinical delivery or financial, um, financial models.
• 4:51
  John: So that will always be the case.
• 4:52
  John: And if you're AI.
• 4:54
  John: If you, if your use of AI accentuates that, great, if it doesn't impact that, then you're just screaming into the wind.
• 5:01
  John: Um, so that's criteria number one.
• 5:04
  John: Uh, the second I, I see them really looking for a deep understanding of.
• 5:10
  John: The clinical workflow and the data requirements necessary for healthcare.
• 5:15
  John: I mean, IMO is a data quality company.
• 5:18
  John: We have been working with organizations to improve data capture and the, the, the use of their data and analytic models for 30 years.
• 5:27
  John: So we're trusted in that space.
• 5:29
  John: But if you don't understand the nuance of billing codes and how that translates to the clinical terms used by clinicians, your AI model's not gonna function.
• 5:40
  John: Um, so it's both that understanding that data and that governance function.
• 5:44
  John: And probably the last thing is clinicians, they're gonna wanna see some human in the loop function for a while now.
• 5:51
  John: So those that are overpromising in terms of their ability to automate everything at this point, I would have some skepticism because of those, um, those end cases that get, that are pretty wonky.
• 6:05
  John: You're still gonna need some review now that.
• 6:08
  John: You could comment that your AI solution eliminates 80%, 90%, but if you don't show a meaningful way to let the clinician or a coder influence that, then you may be, uh, you may be viewed with skepticism.
• 6:24
  David: Yeah.
• 6:24
  David: I think in any of these.
• 6:25
  David: Uh, decisions organizations are, are looking at balancing different factors, and I'm, I'm thinking here, things like speed, accuracy, you know, safety, compliance.
• 6:35
  David: How do you balance all those things when you're trying to do an AI initiative?
• 6:40
  John: When we bring, um, well, first, when, whenever we're starting to bring something new to market, we, we kind of think about not is it AI driven or not, it's like, what is the fundamental value we're gonna do?
• 6:52
  John: What's the superpower that we wanna bring to market that we know we can do better than anybody else?
• 6:57
  John: If AI can help us deliver that, we're gonna do that and use that to do that.
• 7:02
  John: Um, so that's just kind of grounding.
• 7:05
  John: And then from a, from balancing of all those things, when we bring something to market in the provider market, we rely on our, essentially our council of our thousands, of, of clinicians and our systems to guide us.
• 7:19
  John: Our customer advisory council guides us.
• 7:21
  John: Our feedback with our customer success team guides us.
• 7:24
  John: Um, and then we have a rigorous development partner platform that we bring those products to bear and pressure test through before they're GAed out, out into the world.
• 7:35
  John: So I think we're just measured in both evaluating the impact, gathering customer feedback, and then pressure testing that live with clinicians before we, we launch.
• 7:46
  David: Got it.
• 7:47
  David: So I, I get your caution before about, uh, needing human in the loop and, you know, not going to, uh, a hundred percent, but pretty much everybody is talking one way or the other about, you know, streamlining workflows.
• 7:59
  David: And so how, you know, if I'm sitting there in the, in the chair of a purchaser, how do I evaluate against the different ones?
• 8:07
  David: Everyone who's telling me they're gonna streamline my workflow?
• 8:10
  John: Yeah.
• 8:10
  John: Again, I think, um.
• 8:13
  John: When you're, when you're looking to streamline workflow, um, there's a lot of opportunity to do that in, in the, the morass of healthcare delivery.
• 8:21
  John: I think some of those are gonna be more impactful financially than others.
• 8:25
  John: And, and so that, that's kind of the, the risk calculation you're gonna be making, um, in terms of where am I gonna spend time?
• 8:34
  John: Money, but also time and effort of my health system to kind of say, what, what thing am I going to streamline?
• 8:41
  John: Um, the workflow reduction opportunity is pretty massive though, so I, I do think in the near term we're gonna see a lot of focus on operational efficiency before we get into the clinical, into the clinical world.
• 8:58
  John: Most of that will be in the revenue cycle in the near term.
• 9:01
  John: I think there's a lot of opportunity there.
• 9:02
  John: And then we'll move into some of the other administrative functions of healthcare.
• 9:07
  David: So let's talk a little bit more about people, and I'm talking both in terms of human oversight in these processes where there's a lot of technology and AI in particular.
• 9:17
  David: And then also, I know we're talking mostly about the administrative side to get started, but we think about clinicians.
• 9:24
  David: Some of whom have been quite untrustworthy about ai, how do we build trust there with the clinicians?
• 9:32
  John: Yeah.
• 9:32
  John: So let's, let's maybe start on the clinician side first.
• 9:35
  John: So I think, um, you have a very skeptical user base there, right?
• 9:39
  John: Um, and so you need to, to recognize that when you're developing your AI application, your AI workflow, um.
• 9:49
  John: Again, we at IMO, we've thought a lot about essentially helping clinicians use their electronic health records.
• 9:56
  John: That's kind of one of our core value propositions over the years, helping them capture data in those EHRs so we understand.
• 10:03
  John: One key thing is you have to put information in front of the clinician that they understand, can contextualize before they it to document.
• 10:11
  John: Um.
• 10:14
  John: If you're building an AI workflow, you're gonna, you need to be thoughtful about what language you're going to use to present something in front of a physician.
• 10:22
  John: If you misinterpret or even use something language y, may it be directly correct but not accurate for that patient's clinical condition.
• 10:31
  John: You're gonna lose trust very quickly.
• 10:34
  John: So I would just caution all AI organizations to be very thoughtful about.
• 10:40
  John: Be thoughtful and nuanced about what you put in front of those clinicians to help them gain trust that you understand clinically what's going on with that patient.
• 10:51
  David: Makes sense and let's talk about some of the safeguards that can be put in place because a lot of the critique of AI has been about things like bias that it may display some of that coming from the data sets that's trained on hallucinations is a big topic or even, you know, unsafe outputs that aren't exactly hallucinations.
• 11:12
  David: These things are all important.
• 11:14
  David: In their own, just absolute right.
• 11:16
  David: But also for building trust.
• 11:18
  David: Yeah.
• 11:18
  David: How, how do you make sure to keep an eye on all those items?
• 11:22
  John: There's a, there's a concept of grounding that we would advocate most organizations to think about with their AI models.
• 11:29
  John: Um, the, and part of grounding is essentially is finding a trusted content partner to essentially say, Hey.
• 11:39
  John: I wanna bump this up against your assessment of the situation, whether it be a rag model or any other thing else.
• 11:44
  John: And so, um, if you're looking for that trusted partner, and that's one role IMO plays in those supporting AI vendors is that should be looking for somebody that has pressure tested content.
• 11:57
  John: So we have close to seven 50 physicians using our content every day, has a deep editorial policy that's been.
• 12:07
  John: Withstood the test of time and has kept up to date.
• 12:10
  John: And then for us, we have about 65 clinicians and informaticists that are constantly pressure testing internally, checking our, our content as well.
• 12:19
  John: So that's one reason the EHRs have relied upon us to power content documentation.
• 12:25
  John: I would say that's a good what those factors are good things for AI models to look at when they're looking for a, a governor to put on some of those hallucinations or biases.
• 12:35
  David: There's a lot of discussion now about, uh, clinician shortages, and particularly in primary care and the kind of, uh, burden that folks have and, you know, the potential for, uh, for burnout or just, you know, mistakes and, and all sorts of challenges.
• 12:51
  David: And AI sometimes can seem like, well, one more thing that, you know, sounds good from above but isn't really gonna work if, if we look at this objectively, is AI today in a place where it can realistically.
• 13:04
  David: Reduce clinician burden.
• 13:06
  John: I think, um, we're just starting to get close to that.
• 13:10
  John: I think there is line of sight into key areas where reduc, where burden reduction can happen.
• 13:17
  John: Um, I think you'll look at some of the automation of, of patient engagement that clinicians often had to, um, self-initiate.
• 13:29
  John: Now that can be more of a triage role.
• 13:31
  John: You look at the rise of the ambient listening and the ambient transcription, um, that gives, it's no different than the transcription kind of services we've had years ago, but now it's automated, scaled in a different way.
• 13:44
  John: So I think they're, they're starting to move in that direction.
• 13:47
  John: Um.
• 13:48
  John: You, you think about that from the physician perspective, there's shortages there.
• 13:52
  John: You think about it from the nursing perspective, there's also massive opportunity in that space, um, as both of those disciplines need are gonna face shortages over time.
• 14:01
  John: So I think we're getting closer, we're getting more to the heart of some of the inefficiencies.
• 14:06
  John: Um, so I do see that having a role over the next few years.
• 14:13
  David: I've been reading a lot about just the huge amount of spending that's going on in ai.
• 14:17
  David: A lot of this is from the vendor side and building data centers and buying chips and hiring people and all that.
• 14:24
  David: And I'm wondering whether in the overall AI industry, there's gonna be return on investment, but looking here in the sector that you're serving, how should provider organizations think about measuring their return on investment?
• 14:37
  David: And should that be purely on a financial yardstick?
• 14:41
  David: Clinical impact, you know, what are the, what are the sort of metrics that, uh, should be employed?
• 14:49
  John: Um, I mean, both.
• 14:50
  John: Ideally, I think each, each health system will look at their book of business and, and their, their, um, population of patients to determine how to flex between those appropriately.
• 15:02
  John: Um, ideally they're aligned in your value-based care model.
• 15:06
  John: Um, but.
• 15:08
  John: I think you can work on both in parallel, and I think both are being worked on parallel.
• 15:11
  John: I think the revenue cycle billing side will, will have more rapid um, achievement using AI and some of the clinical interventions where again.
• 15:24
  John: If you mess up a use case there or, um, uh, an esoteric presentation of a patient, the risks are higher than not getting denied by a payer.
• 15:34
  John: So those will, will take a little longer.
• 15:37
  John: Um, and I think those is where you'll see more scrutiny from these health systems before they make big investments
• 15:44
  David: on the administrative side.
• 15:45
  David: Just to talk about revenue cycle for a minute, I think that, um.
• 15:50
  David: You know, as the computers were first introduced into the healthcare and it was started for, you know, financial purposes and even physicians wanted to use it to measure, to manage their stock portfolios before they got into the clinical side.
• 16:02
  David: So on the, on the revenue cycle side, you know what's going on there.
• 16:06
  David: I can see how the AI's gonna be useful.
• 16:09
  David: From a submission standpoint, but I could also see kind of an arms race or standoff between the providers and the payers, both using AI kind of against one another.
• 16:18
  David: In some ways, you could say, well, that's great, let the, you know, let the AI go and fight it out.
• 16:22
  David: But what's, what's actually going on in that space at the moment, whether I'm not, that may, may not be directly related to what you're doing, but.
• 16:28
  John: It, it is, I think, um, I mean the translation of the clinical terminology used by physicians to those billing codes is one key role Immo has played for 30 years, and so we have a meaningful role in the generation of, of, of claims in the downstream revenue cycle functions.
• 16:50
  John: Um.
• 16:52
  John: I mean, there's certainly early entries on the autonomous coding side that are leveraging AI and advanced machine learning models to drive autonomous coding functions and removing some of the effort, or at least focusing the effort by organizations to focus on higher dollar, more complex coding efforts.
• 17:10
  John: On the ambient side, you're seeing the interplay of the MA encounter and the note more directly tied to medical necessity.
• 17:21
  John: The, the billing regulations necessary to justify that invoice and potentially reduce the denial or overturn the denial if it does come down from a payer.
• 17:31
  John: So I think you're starting to see some of those clinical efficiency or operational efficiency for a physician tied to the revenue cycle benefit of that by automating the note generation, but making sure it's compliant with the billable event as well.
• 17:46
  John: Um, so I see those as both exciting opportunities.
• 17:50
  John: On the flip side, yes, payers are gonna apply their own AI and ML models to, to look for opportunity.
• 17:56
  John: Um, so as it always has been, David, they'll continue to be an arms race here to, to, to make the funds flow continue to work.
• 18:05
  David: Let's talk about it from the patient perspective, uh, for a moment.
• 18:08
  David: 'cause we've talked about the clinical side, administrative side.
• 18:11
  David: Does it feel any different to a patient?
• 18:13
  David: I sometimes think about, you know, we talk a lot about the different payment models and value-based payment and so on, and I'm thinking like, does a patient know that they're involved in this?
• 18:23
  David: And, and how about on the, with the AI side is, is the appointment feel any different?
• 18:28
  David: Does the whole interaction seem any different?
• 18:30
  David: Are there measurable changes?
• 18:33
  John: Um, I don't, not yet.
• 18:37
  John: I think, um, I mean, in healthcare you've always had kind of three different lenses.
• 18:41
  John: You've had the billing lens and the, the kind of the payer lens that you just described, brown value-based care.
• 18:46
  John: You've had the deep clinical lens and you've had this patient interpersonal lens, and all three of them have never really spoken well to each other.
• 18:55
  John: And so you've had translation and frustration.
• 18:58
  John: Um, through that IMO has often bridged that clinical to payer.
• 19:02
  John: We actually support a lot of the patient translation as well.
• 19:06
  John: We have patient friendly terminology that maps to billing codes and maps to, to the clinical terms as well.
• 19:13
  John: Um, I think AI can play a role in essentially translating and translating to help patients understand the complexity that is inherent in the.
• 19:25
  John: Billing and revenue cycle process and complexity on the clinical side.
• 19:29
  John: But again, that data governance and that underlining data infrastructure has to be well thought out.
• 19:35
  John: Um, because if you have a patient that doesn't understand that breast cancer metastasized to pelvis stage four, to them, they just need to understand that's breast cancer, that's spread, right?
• 19:45
  John: Like you gotta be really thoughtful about that translation function.
• 19:49
  John: Um, and that requires a good data governance and good data modeling.
• 19:53
  David: John, what is your reaction to some of the early research that has shown in the clinical accuracy using AI and, and does it, you know, doctor using ai, patient using AI themselves or the doctor themself, and it's sometimes not very flattering, uh, to see what the results there are.
• 20:11
  David: And I know there's been speculation about what it means.
• 20:13
  David: What, what's your take on, uh, this type of research?
• 20:17
  John: I think it's still fairly early game, right?
• 20:19
  John: I think, um, it.
• 20:21
  John: On both sides.
• 20:22
  John: It's showing potential of, of AI's de AI models demonstrating and very controlled, uh, controlled data, data assets, and controlled experiences.
• 20:34
  John: Um, so it shows opportunity there.
• 20:36
  John: I mean, the models have, the frontier models have advanced very quickly, and thus that creates the ability for people to enter the market, as we talked about at the beginning.
• 20:47
  John: Worked in hospitals for years.
• 20:48
  John: If you go into hospital, it is organized.
• 20:51
  John: Chaos can be sometimes.
• 20:52
  John: So, um, those models have not demonstrated that in the complexity of one patient, let alone a unit, let alone a care team interacting with multiple patients at once.
• 21:03
  John: So I think there's still a long way to go before, um, we really can assess the model's impact there.
• 21:11
  David: So you mentioned how the AI is developing quickly some of these frontier models just from, you know, month to month, certainly from year to year, making big, big changes in what they're doing, big advances.
• 21:22
  David: And at the same time you've got, you know, decades of experience in applying structured data at IMO Health to, to improve care, to support the clinician.
• 21:33
  David: What's the role between.
• 21:35
  David: Kind of your expertise on the structured data side and making those AI models themselves more, uh, precise, more appropriate for use in healthcare?
• 21:45
  John: I mean, to me, that, that, that we view that as one of our opportunities to have a meaningful impact on this moment, right at IMO.
• 21:53
  John: And those frontier and foundational models will improve, but again, the long tail of clinical terminology and clinical data will challenge them.
• 22:02
  John: I think in perpetuity, I mean, and what IMO can offer is essentially, like I said, uh, a data asset that's been pressure tested and continues to be pressure tested billions of times a year.
• 22:16
  John: Editorial PO policy and governance that is driven by clinicians and then constant human in the loop pressure testing by our team, but also those physicians out out in the world.
• 22:27
  John: So for those that want to lean in and solve that last 80%, that the foundational models, that really will help you build the trust to go to market with the providers, then I think that's what you should be looking for, data assets in that, in that space to help ground your AI model.
• 22:46
  David: How much, uh, are you able to differentiate what you're doing from these, you know, fast, fast fashion models that we discussed, uh, earlier?
• 22:55
  David: Is it easy for a customer to discern the difference?
• 22:59
  David: Yeah.
• 23:00
  John: Yes.
• 23:01
  John: I mean, put it in front of a physician and let them document or talk the way that they normally talk, that the way they learned in residency and fellowship.
• 23:12
  John: And if your model doesn't.
• 23:14
  John: Accurately reflect that the, the, the language of a clinician, your model's gonna not generate the trust.
• 23:21
  John: So when organizations use IMO or we put products in front of them, clinician's like, oh yeah, that makes sense.
• 23:28
  John: When I, when I translate a billing denial to, to help a physician understand maybe why that coding may not necessarily, they're like, oh, that makes sense to me.
• 23:37
  John: Um, so I think that to me right now, that's trust is the, the has always, I guess trust has always been the currency for adoption in healthcare and I think it will remain.
• 23:48
  John: So
• 23:49
  David: I'd love to hear if you have an example or two to, to bring this down maybe to the level of an individual.
• 23:56
  David: A patient or encounter or even a, uh, you know, customer level.
• 24:01
  David: Any examples where your technology's really helped to improve outcomes or even to give greater insight?
• 24:09
  John: Yeah, I think, um, in our cases working with, uh, some of our ambient partners we can support.
• 24:17
  John: Here's a great example of where.
• 24:20
  John: Um, after the transcription is complete, IMO can, can help within that transcription, essentially find the potential reason for visit at the right level of specificity.
• 24:32
  John: Um, uh, you and I talking, if I was your physician, David, we're gonna talk about diabetes, but we may not talk about it in a clinical sense.
• 24:42
  John: Diabetes with retinopathy.
• 24:44
  John: And, uh, insulin dependency.
• 24:46
  John: We're not gonna say that in a physician and patient interaction, but can IMO working with our trusted partners help, uh, understand the context of that patient's encounter, and essentially say physician, it's not just diabetes, it's diabetes with retinopathy insulin dependency.
• 25:03
  John: That not only has a clinical impact that moves to that patient's problem list and is stored as a chronic condition that needs to be managed at that level, but it has a pretty big billing impact on that patient encounter and that patient's overall acuity score.
• 25:16
  John: So those are examples where we're using our understanding of how clinicians have documented diabetes with retinopathy billions of times over the last 30 years, and understand what context that occurred in.
• 25:30
  John: To help that individual patient interaction to be coded appropriately.
• 25:35
  David: A big area here that it seems to be a, a chronic and unsolvable problem is the shortage of primary care clinicians, and I've seen this being dealt with by, you know, having advanced practice.
• 25:49
  David: Nurses or physician assistants trying to do telehealth.
• 25:54
  David: Uh, but more recently I've seen some partnerships on the AI side, whereas for, for patients that don't have an assigned physician, they'll do a kind of a, a AI pre-visit.
• 26:05
  David: Are you, are you involved in that?
• 26:06
  David: Do you have a perspective on that?
• 26:09
  John: Um, we have organizations that we partner with that are moving, that are exploring those types of clinical interventions.
• 26:18
  John: Um, again, I don't think anything kind of the, the, the evaluations, the, um, thoughtfulness that you need to deploy, that changes.
• 26:29
  John: Um, I think this is probably on the, the, the farther edge of that, that spectrum of adoption.
• 26:36
  John: Um.
• 26:38
  John: But, uh, as there's opportunity there to deal with the vast majority of less, uh, maybe less acute instances, but then again, those, those use cases that are more esoteric, you definitely need a thoughtful strategy to deal with those.
• 26:53
  John: So I think there's validity here.
• 26:56
  John: Um.
• 26:57
  John: But I would, I would treat that with utmost caution.
• 27:00
  David: Yeah.
• 27:00
  David: I mean, my sense is that, you know, they're not comparing it with the ideal.
• 27:04
  David: They're comparing it with, okay, this patient doesn't have a, the absence primary care doctor, and they're gonna go into the hospital and I think they end up, the idea is you'll do the AI pre-visit, but then a, a physician somewhere is gonna review it and, and be in discussion.
• 27:18
  David: Where I was gonna go with that is to ask you about, let's say it's one thing, you know, don't have a doctor, but.
• 27:23
  David: Maybe that type of visit is good for, or that type of interaction and workflow is good for the patient that does have a primary care physician, so that, that when you actually have the time to spend with them, they've really made the most of the technology upfront so they're well prepared.
• 27:37
  John: Yeah, I think there's, there's a lot to think through and if you think about the incentive alignment and how that generates trust in that patient.
• 27:46
  John: Digital, digital physician interaction will be critical.
• 27:50
  John: As this matures a little bit, if this is coming from your existing primary care, I think there could be a trust dynamic that's stronger.
• 27:58
  John: I think if you think about it coming from your payer or your insurance company as a kind of a, an evaluation potential, um, there may be some more skepticism.
• 28:08
  John: Both may have valid uses.
• 28:09
  John: So I think there's still a lot to figure out, not only in just the tech side, but how will.
• 28:15
  John: Patients, uh, trust this, this new interaction, um, uh, with, with this new mode of, of communication.
• 28:25
  David: So the fast fashion, you know, that's something that's gonna be here today, gone.
• 28:29
  David: Gone tomorrow, and, and these.
• 28:31
  David: Well established provider organizations in particular are gonna be thoughtful about what they do, um, in the long term, and at the same time, they, they can't stand still.
• 28:39
  David: So I'm wondering what you're doing at IMO to help your partners to scale, maybe responsibly across the overall, uh, ecosystem.
• 28:48
  David: What does that look like for you, your vision of it, and then what do you do in pragmatic terms?
• 28:55
  John: Yeah, I think, um, so where we play with most of our large health systems and physician practices is really ensured high quality data capture and data quality within their, their EHRs and maybe their data repositories that they're using for analytics.
• 29:12
  John: Um, the first thing we're doing is essentially making sure they understand the risk and benefit of working with vendors that are using ai.
• 29:21
  John: Are gonna push structured data back into the EHR and helping them understand what if they don't do it well, what gets degraded?
• 29:31
  John: What gets degraded clinically from what goes to that patient's problem list and is managed?
• 29:35
  John: What gets degraded financially if you're not capturing that?
• 29:38
  John: Diabetes versus diabetes retinopathy is great example.
• 29:42
  John: So right now we're essentially helping them pressure test some of those AI models and how they should be thinking about what is the data quality that they're gonna push back into the hr.
• 29:53
  John: Um, those that are concerned, we would welcome the opportunity to talk with them and say, Hey, let's, let's think about how we can make sure that data doesn't degrade.
• 30:03
  John: Um, you can still get the operational efficiency, but we need to ensure high data quality that comes outta that.
• 30:09
  David: This is a very, uh, sobering approach and hopefully, uh, will be picked up, picked up appropriately.
• 30:15
  David: It's,
• 30:15
  John: uh, it's, it's required and there's too much Yeah.
• 30:17
  John: At stake not to, and put yourself in a chief financial officer's role.
• 30:22
  John: Um, ambient provides a lot of value from a clinician efficiency, but if I am.
• 30:27
  John: Starting to degrade my coded outcome, I either have to throw middle revenue cycle functions at it and spend more money there.
• 30:34
  John: Yep.
• 30:35
  John: Or I'm gonna have to accept a lower, uh, lower reimbursement model.
• 30:38
  John: And that just, just can't fly.
• 30:40
  David: Yeah.
• 30:40
  David: No it doesn't.
• 30:40
  John: Yep.
• 30:43
  David: That's it for another episode of Cure Talk Executive Features.
• 30:46
  David: My guest today has been John Laursen.
• 30:48
  David: He's SVP of Product Commercialization.
• 30:50
  David: At IMO Health, we've been discussing what to look for when evaluating AI tools in healthcare to ensure accuracy and safety.
• 30:59
  David: I'm David Williams, president of Health Business Group.
• 31:01
  David: If you like what you heard, please subscribe on your favorite podcast platform and thank you, John.
• 31:08
  John: Thanks, David.
• 31:08
  John: It's been a pleasure.
• 31:09
  John: Talk to you soon.