← Back to All Podcasts Locking Down Corporate AI Usage Webinar In this episode, Jason Nadal, Besler Holdings’ and Sypher Security’s Information Security Officer, will provide us with a glimpse into the next Hospital Finance Academy Webinar, “Locking Down Corporate AI Usage,” live on Wednesday, October 7th, at 1 PM ET. Highlights of this episode include: How companies deal with artificial intelligence and how they should make the decision to embrace this technologyWhat the benefits and detriments of AI usage are What tools out there to help protect your company and your dataWhat other challenges you have in keeping aware of AI usageHow you manage third parties not directly under your controlThe key takeaways Subscribe Today! Kelly Wisness: Hi, this is Kelly Wisness. Welcome back to the award-winning Hospital Finance Podcast. We’re pleased to welcome back Jason Nadal, Besler Holdings’ and Sypher Security’s Information Security Officer. In this episode, Jason will provide us with a glimpse into our next Hospital Finance Academy Webinar, “Locking Down Corporate AI Usage,” live on Wednesday, October 7th, at 1 PM Eastern Time. Welcome back, and thank you for joining us, Jason. Jason Nadal: Hi. Thanks for having me. Kelly: All right. Well, let’s go ahead and jump in. So, we know artificial intelligence is everywhere now. How should companies deal with this and make the decision to embrace this technology? Jason: Well, if you run a company right now, somebody on your team is likely already using AI. So ideally, that would be via an approved path that you have already set up, but maybe it’s just a browser tab they opened up at lunch, putting something in Google and getting AI results. Either way, the question is not, “Should we use AI?” It’s already embedded in a lot of the approved corporate tools that are already out there. So, the question is, “Do we know what we allow, what we forbid, and how do we keep that promise when the tools keep changing under our feet?” So those are the kinds of conversations that security and IT folks have when leadership asks for a practical plan around AI. So, over the next 10 minutes or so, I’ll walk through some of the benefits and risks. We’ll get into that a bit deeper during the webinar that’s upcoming, but this will give you a methodology of control you can actually run, some of the categories of tooling that support it, and the challenge of feature creep in tools that you’ve already approved. And we’re also going to look at how a vendor and open-source software assessment has to catch up. Kelly: Yeah. I mean, it is really everywhere. It’s embedded in everything now, it seems like. [laughter] Yeah. It’s a lot to keep up with. So, what are the benefits and detriments of AI usage? Jason: Sure. There’s a lot of benefits, and there’s definitely a lot of detriments as well. So, AI earns its value when it shortens the work that you’re already doing, especially that work that used to waste a lot of your time through just tedium, repeated tasks, and things like that. So, I find it really shines at drafting, summarizing, searching or researching, coding assists, and also triaging helpdesk tickets. So those are real-time gains when the data and the use case match the risk. So, in healthcare and adjacent work, that might be a little less clear. So, a nurse or revenue cycle analyst can summarize a long chart note, draft a patient letter, or speed up some prior auth paperwork. A cost report or appeals team can find patterns faster. So done carefully, ideally with this human oversight as to what’s produced, that is time returned to care and to accurate billing. But the downside is just as concrete. So, paste the wrong note into a public chatbot, and you may have moved protected health information, PHI, or something else confidential or sensitive, outside your control. So, a helpful summarizer can invent a fact, called hallucinations, that then gets treated like clinical or financial truth. There’s really a huge downside to that if it’s not checked over by humans with clinical experience. An automation that writes into scheduling, ticketing, or an EHR-adjacent system can turn a bad model answer into a real patient or operations problem. Outside of healthcare, the pattern is much the same. So, marketing could paste customer lists into a public model. Finance could paste financial forecasts. Engineering could paste source code or API keys, maybe in a hurry or just this one time, and leak information that you don’t really intend to leak. Legal can paste contract language. You get the benefit of speed, but the detriment of leaking your data, over trusting the AI, and a trail that, once it’s out there, you can’t really tidy it up after the fact. So, a key point to establishing governance is having frank discussions of what data is acceptable to this risk if it were to leak. I really can’t say...
Show More
Show Less