Transcript for "Revolutionizing Payer-Provider Contracts: Smarter CLM for Compliance & Network Success":
Hello, everyone. Welcome. We'll give it just a minute before we get started while folks join. Alright. I think we've got, a few folks, still coming in, but let's go ahead and get started. Hi, everyone. I'm Danielle Haughland, senior director of Global Alliances at Agiloft, and I will be your host today for this important and timely webinar, revolutionizing revolutionizing payer provider contracts, smarter CLM for compliance and network success. Bit of background on me really quickly. I started my career in big law as an antitrust and complex commercial litigator, and I had the pleasure or not of litigating the downfall of massive contracts in a variety of industries. And let's just say I've seen some things, And I've been on the other side of the contracting fence for about ten years now, working tirelessly to improve the contracting process, insights, and at the end of the day, improve business outcomes. Now on to today's topic. As value based care models continue to evolve and accelerate in 2025, payers and providers are facing complex challenges, managing increasingly sophisticated contracts, adapting to rapidly shifting regulations, and ensuring their provider networks remain both compliant and adequate. And at the same time, inefficient workflows and manual processes put unnecessary pressure on operations and ultimately patient outcomes. And this is where smart contracts smart contract life cycle management comes into play. And today, I am so excited to be joined by Bryan Kowalski, vice president at Epiq. He brings a wealth of expertise in health care operations, legal process optimization, and regulatory compliance. And together, we're going to explore how harnessing contract data can transform how health care organizations navigate the complexity and provide the agility needed to adapt to regulatory and market changes. So payers and providers alike can focus on what truly matters and that is delivering high quality patient care. So welcome, Bryan. It is great to have you with us today. Thanks, Danielle. I'm excited to be here. This is definitely a topic that, hits home for me. I began my career network development at Blue Cross Blue Shield of Michigan where we built a Medicare Advantage PPO from the ground up. We contracted more than 30,000 providers as part of that effort. It was one of the most rewarding experiences considering the amount of effort that went into it from market analysis to planning, preparation, execution of the actual contracting effort. And that was all long before CLM was even on the radar. From there, I joined BlueCare Network where I manage their CLM platform and saw kind of firsthand how automation and standardization can really streamline and workflows and reduce risk. I also got the opportunity to work with WellCare where I led an implementation and national CLM rollout spanning across over a dozen states. As part of that effort, we standardize real complex agreement structures for providers, built scalable workflows, and train users across the country. As it relates to health care, I had a few other stops along the way, led an effort to transform and centralized contracting for a national health care system as part of a CLM implementation, and also ended up certainly back to the blues where I worked on health care reform act as when the ACA was introduced. So those experiences, especially as it relates to network development provider contracting, gave me quite a deep appreciation for just how powerful CLM can be. And not just as a technology solution, but really a catalyst for consistency, compliance, and be able to scale in the health care industry. So I'm looking forward to our discussion today, some of what and to share really some of what I've learned along the way. That is awesome. We are so lucky to have you. Before we dive in though, a few housekeeping items. We are aiming for a forty ish minute discussion with q and a following. You can post your questions, in the q and a section to the right of your screen. We're gonna try to squeeze in a demo, after, Bryan and I do some q and a about his experience and what he's seen along the way. So I'll be watching the clock like a hawk to make sure we can, get that in. So let's dig in. Bryan, from your perspective, what are the most pressing challenges face what are the most pressing challenges facing payers and providers today? And, look, I know we're here to talk about contracting, but let's set that aside for a minute and focus on, from your perspective again, what are the biggest challenges in general. And my hunch is that those challenges relate to contracts or the contracting process. I think you're gonna prove me right. So let's go. What are what are some of the biggest challenges you're seeing? Yeah. I mean, one of the biggest challenges just from a pure execution standpoint is just how cross functional and coordinated of a of an effort this is from provider relations to network operations to the providers themselves and legal compliance, finance, credentialing, claims. I mean, all while managing a high volume of of provider agreements in the process. But, you know, more namely, and to name a few, you know, managing the complex agreements themselves that include dynamic variations for provider types from physicians to PHOs, IPAs, you know, behavioral health hospitals, and then commercial state federal lines of business and complex models around compensation and incentive programs. You have the constant changes with federal regulations as part of this, and of course, you know, heavy emphasis on compliance, fraud, waste, and abuse prevention, and then just maintaining your network adequacy for your your member base. So, you know, to get you know, talk a little bit more in detail from an experience standpoint. When when we were building the Medicare Advantage PPO, we're essentially trying to build 80% of commercial network from scratch. So as I mentioned, like, 30,000 providers, and we didn't have automation back then. So we tracked everything in an access database. We we manually verified credentials. We had to be incredibly coordinated to meet, you know, CMS deadlines for submission. We also had to ensure that we're pulling the right templates and fee schedules. And in some instances, we had to amend signed agreements, and we were manually analyzing analyzing which providers were were impacted as part of that. And that was for a single state. So a CLM at that point would have been an absolute luxury to have. And when you think about managing networks across multiple states and lines of business, it only exponentially gets more complex. Yes. It does. And I think you did prove me right, but but let's start to get granular. You touched on this a little bit, but how do these challenge implicate contract management? And going one step further, how can contract management improve or work to alleviate some of the the challenges that providers are facing or payers and providers are facing? Yeah. Great question. At WellCare, for instance, we're managing provider contracts across more than a dozen states. So each market had its own nuances, different templates, payment methodologies, state regulations, you name it. Before we implemented CLM, we're dealing with a lot of inconsistent processes. So heavy manual routing of approvals, a lot of version control issues, and agreements weren't exactly always stored in a centralized location. So as you would imagine, that translated into long turnaround times. More effort has to keep things compliant within the contract language itself, and visibility was always very challenging. So when we introduced CLM into the process, it gave us one place to manage it all. So everyone was now using the same template. You got you had built in approvals as part of that process. You can actually see where the contract is and where it stands within the the contracting process. So instead of really chasing down files, digging through emails, you're making decisions more quickly and confidently, and it really cut down on the the chaos. So to answer your question, yes. These challenges absolutely tie back to contract management, and without a solution, it's really hard to move quickly while staying compliant, as well as when you think about scaling across multiple markets for those use cases. Right. So it sounds like you've been on the forefront of introducing CLM into the pair provider space. I mean, you said in your career, you've gone from, like, literally working with everything manually and in a massive database to introducing CLM. I mean, we're we are talking about large sophisticated organizations. In your experience, you know, what are organizations today working with? Is CLM prevalent in this industry? Are companies still kind of catching up? What what are you seeing out there? Yeah. I'll I'll start by saying the individuals that I've had the pleasure of working with in this industry are some of the brightest people that I've encountered. Some that I still to this day consider mentors. Just highly sophisticated, deeply knowledgeable. If you were to sit in one of these meetings, just the sheer number of acronyms you need to keep up with can feel like you're learning like an entirely new language. But to your question, yes, some still rely on spreadsheets, shared drives, legacy systems, including legacy CLMs. As I mentioned earlier in my career, we used just an access database, and later we used what's now legacy CLM. It worked, but it did require a lot of manual upkeep, a lot of room for error. Without automation and a way to really standardize and put controls, it's easy for real issues to come into play that, can have significant impacts including financial and otherwise. Yes. I actually wanna drill down a little bit on what, some of those real issues might be. So what are the consequences, not necessarily in in your experience because I don't want you to call out any former employers or anything like that. But what are some of the consequences that you can envision, of not having a robust contract life cycle management process and solution in place to navigate this complexity? Yeah. That's a great question. And, you know, I'll talk about a little bit about overcoming some some hurdles as part of that as well. You know, one example, you know, I'll go back to WellCare. As I mentioned, we're operating in over a dozen states, and the contracting process varied for each market. So our templates included hundreds of permutations, different fee schedules, different state regulations. And when we implemented CLM, we standardized all the templates. We built in logic and really created intake questionnaires. So, that data we're collecting through the intake really help teams generate the right contracts based on just a few inputs. So that along with workflow automation, I mean, it really did save weeks of back and forth as part of that process. Right. Right. Right. So let's let's talk a little bit more about, solutions. Can you share some real world, more real world examples of how leveraging contract data via CLM has helped payer providers over payer or providers overcome these hurdles? And earlier in the program, you talked about four distinct challenges. So let's break them down one by one. So first up, you talked about not just navigating and negotiating complex multiparty agreements in value care value based care models. It seems pretty obvious on its face that solid contract management can help here, but as with well, things don't with, as with most things in health care, there's a lot to unpack here. Things like, contract drafting, negotiating, compliance. How can a modern CLM solution support in these areas? Yeah. Great question as well. We just talked about how it can impact some of the drafting process. Mhmm. When we get into negotiation, you know, historical data is gold. You know, with a a good CLM in place like Agiloft, you can look back at previous contracts. You'd see how rates trended, what that initial offer was, what the rate ended up being, how that compared to internal benchmarks or market averages. I've worked with organizations where being able to say, we secured 8% last year when most plans were securing 6% made a big difference in setting expectations internally and with providers. So that transparency really helps teams go into negotiations, informed and aligned. On the compliance side of things, CLM enforces checkpoints, like making sure specific regulatory language is included or that agreements don't move forward without approvals. And then for obligation management, having all your agreements in one system with metadata tied to key terms means we're tracking what's been committed to. Renewals, notice periods, performance standards. So it really does take that shift from reactive to proactive. Right. So the next challenge you mentioned, and and this is a biggie, especially in today's, well, especially today. You mentioned keeping up with ever changing state and federal regulations. And for organizations that operate in several jurisdictions, this can be really tricky. Right? Absolutely. You know, just speaking with from Agiloft standpoint in particular, you can manage updates centrally. So there's a if there's a new regulation, you update the clause library or your templates, and it cascades down into all contracts. So you can also apply version control and track which agreements include updated language. I mean, that makes it easier to stay compliant without relying on heavy manual review of each and every agreement, when something changes. Awesome. And moving on to waste, fraud, and abuse. That's something that we've heard a lot about lately. What can a robust CLM solution help, or how can a robust CLM solution help detect waste, fraud, and abuse? I think it starts with just having visibility and controls in place. Agile, for instance, it literally logs every change. So, you know, who edited the contract, when and where, if someone tries to use outdated language or skip a review, you know, this the system has controls in place or flags, to be able to identify that. And it also helps to ensure contracts are only executed after approvals are completed. So that traceability is important when you're trying to enforce internal controls for compliance and prevention measures. Got it. So quick time check here. We're about fifteen minutes after the hour. And like I said, I do wanna fit in a demo, but I think I have time for one more question about, network adequacy and credentialing compliance. And I know, Bryan, you've kind of touched on all of these things or your or this issue kind of throughout your con your talk, but, kind of pinpoint focusing on, network adequacy and credentialing compliance. How does the CLM support these functions? Yeah. Great question. The ability, I think, to easily pull reports on contracted providers by type, specialty, state, geography, That becomes incredibly useful when you're analyzing your network, really trying to identify gaps. It also helps when you're preparing for CMS submission. So, as part of that effort, you need to you need all that provider data to populate HSD tables, which are included in your submissions for senate for centers of Medicare and Medicaid, especially for, like, Medicare networks. So, on the credentialing side of things, there's a lot of upfront verification that happens during the contracting process. Things like NPI validation, we do through, like, CAQH and check checking credentialing status through systems like Visual Cactus. The great part about CLM, and especially systems flexible and robust as Agiloft, is that you can track all those data points within the contract record, and you can trigger alerts and create workflows based on those details. Well, that all sounds absolutely amazing. Can we see it in action? Do you have a demo ready for us? Let's do it. Let's do it. Let me share my screen here. By the way, I love your passion for this, subject. It it really shows through. Thank you. Thank you. Yeah. Let's start with the big picture here. So why provider contracting matters? For health care payers, provider contracts are at the core of almost every strategic priority, whether you're expanding coverage, integrating acquisitions, or shifting to value based care. None of that happens without effective scalable contracting. And the reality is most provider contracting today is still heavily manual. It's time intensive, requires a lot of institutional knowledge, and has way too many points of potential breakdown. So it creates delays, visibility gaps, makes it tough to adapt quickly when, for example, a new regulation is introduced or changes to reimbursement models. A modern platform like Agiloft can really streamline how stakeholders collaborate with the right workflows in place. You can cut down cycle times dramatically, improve the entire provider experience. Legal can now leverage playbooks, tools are automated, network development has clear visibility into the contracting status, all from one solution. Where this really gets exciting is when we can enable the future state. Automating routine tasks, bulk amendments, accelerating m and a readiness, safely enabling business users to really self serve in some areas. Agiloft provide Agiloft the Agiloft platform really brings AI capabilities like red line analysis, clause interrogation, and and prebuilt integrations that plug right into your broader ecosystem. At Epiq, we've worked with some of the largest health care and life sciences organizations in the country. Our combined experience with Agiloft gives us the playbook not just for implementing the tech, but for designing a CLM program that fits your specific strategy. So it's not just about automating the process, it's about preparing your organization to contract at scale with clarity and control. And before we jump into the demo, I wanna quickly highlight what this looks like in practice. So what you see here is the front end of a target workflow and target state workflow. It starts with capturing the basic provider information, the type, the line of business, but then gets into compensation models, service funds, and how those details influence the structure of the agreement when it's generated. So if you got a if you have a provider group coming in with shared risk arrangement under a capitation model, or if you're layering on upside bonus or value based payments, this workflow supports all of it. It it's built to really adapt. What's powerful is that Agiloft doesn't just store this data, it's used to drive contract generation and conditional logic. So instead of starting from scratch or pulling templates manually, the system builds the right agreement based on those inputs. So now we'll show I'll show an actual demo on how this plays out. I'm going to act, initially as a network specialist on the payer side and create a provider agreement. Give me a second here. Mhmm. Hey, Bryan. Can you do me a favor? Before you push play on that, you've already talked about kind of the first persona you're going to be basically playing. Can you just run through the personas that you're going to be touching on today just so everybody kind of knows what to expect throughout? Yeah. Thanks for teeing that up. I'm gonna go through the entire work flow from end to end here. So I'm gonna initially act as the network specialist. I'm gonna come in and generate an, a provider agreement. From there, I'm going to send it to our provider for review. As part of that, we'll have the provider, mark up the agreement, send it back to the the network specialist to upload back into our contract record. I'm going to leverage some AI capabilities to really analyze some of those red lines and see what has changed. Mhmm. And then once I'm ready, I'm gonna send it for, an initial risk assessment. So we're gonna create tasks, through automation so that different, groups can review and determine whether or not the agreement is preferred, acceptable, discouraged, or or unacceptable. And based on, that risk review, we're gonna generate some approvals. And so I'll also act as an approver, health plan VP and a president to to run through the approval process. So that at that stage, we're then prepared to send it out for signature with our provider. Sounds great. Let's go. Alright. To kick things off here, this is really our dashboard here that can be configured for any user type. So you can see we have drill down reports, we're able to track obligations in the upper left hand corner. And as I scroll down here, I can see which contracts are pending review and approval. And we can really tailor any of the dashboards to any of the user types. And I'll just pause it here. We're getting into actually creating the contract, at this point. So you can see I selected a provider agreement in the upper left corner, and here, I'm able to search for a provider in the system. So I'm able to do a lookup within the system to my my master data and select the provider that automatically populates along with all of the requisite information. I'm able to select some contract terms, and then you can see here as well that I have a drop down list of various provider types. And this is going to to drive some of the permutations of the actual agreement once it's created. So for this instance, I'll select practitioner or group, I'll add some delegated function, answer a few other questions around employed and pervert pricing, and then select my health plan. So you'll see here as I look up the health plan, I selected, Epiq Healthcare of New York, and this drove if you it's skipped ahead a little bit here, but this drove in the bottom left hand corner, a list of lines of business. So you can see on the bottom left PPO, HMO, Medicare Advantage, Medicaid, and marketplace. And how this can be dynamic is now I'm searching for, Epiq Healthcare of Texas, which is a different entity, and this will show that it populates, a subset of those lines of business, and just show Medicare Advantage, Medicaid, and marketplace. So you can see up above in the lines of business there, I selected Medicaid. I also selected, Medicare. And as I'm selecting the different compensation types, it's only presenting me with the applicable, values to to populate. So I have, values defaulted to a %, and I have a note up above that says, any compensation below 40% or above a 5% will trigger approval. So we can default some of this information and allow the user to to change. And then finally, as part of this, I'm gonna select an incentive program, select upside bonus to shared risk, and then I'll be able to now generate my agreement. So you can see within just a few inputs, I'm leveraging all that data to determine what permutations of the agreement, need to be included as part of generating the contract. And you can see here, I I did generate the agreement, and I went back to the details page. What I wanted to show here is that below, I'm tracking a host of other information. So a lot of other data tied to the agreement record that wasn't presented as part of the intake. This is information that we typically would default, within our agreements, and we wouldn't typically negotiate or change up at the onset, but we're tracking in addition to what we we needed just on the intake to create the agreement. And then you can see my contract has been created. I'm now gonna email the contract to our provider. I'm gonna leverage a preconfigured, email notification, add the provider who I want to to send it to. I can add a new contact if needed, and then send it out, via email. And so this will attach the agreement that I created directly to a email notification all from the solution itself. In a second here, I'll pull in the actual email notification that has been sent to the provider, and now I'm gonna flip personas. So now I'm gonna be acting as the provider. So I'm gonna open up the agreement in word, and I'm gonna make a few red lines. And let's do a few things that would be fairly impactful. So I'm gonna navigate down to some credentialing language, and I'm gonna change the credentialing language to say that I only wanna be recredentialed every five years. And then furthermore, I'll make a a dramatic change here, just for demo purposes and say that, you know, let's make a big change literally within some of the compensation. And then also, let's update the the compensation from a % to a hundred and five. And now you can save this agreement, the provider can respond via email, and this will be automatically ingested via email into Agiloft once the email is received. For the sake of the demo, I'm gonna show another approach where you can also if they were to email it back, directly, you can also manually up, attach it to the record as well. So that's what I'm doing here is I'm up updating the record, and attaching the file. And you'll see here, as I explained earlier, when through our q and a, that it's tracking each version of the agreement. Right? So red lines have occurred. I have a new version of the agreement loaded in the record. So now flipping back to network specialist, I'm gonna open the agreement and I'm gonna leverage some AI to help me really analyze some of the changes in the agreement. So, Agiloft has a AI solution called Screens AI. And on the upper right hand corner, there's a plug in where you can see open screens where I'm able to open screens and run a framework of rules that AI can review the agreement for these specific rules and determine whether or not certain conditions passed or failed based on the rules that I've created. And so right now, the contract is being analyzed through AI. We can group those conditions or or rules into high, medium, low categories. We can prompt the, the, the contract for certain questions. In this case, it did pick up that red line around, the the credentialing. And so it will can also suggest red lines. So we can have our preferred position, and it can review that based on our preferred position and craft a red line for us. And it also will pop in a position and craft a red line for us. And it also will pop in a comment to help really clarify and justify the red line. And now I'm gonna use a prompt to say, you know, just in in, natural language, what is the termination notice period? And really query the contract for that. And so AI can quickly bring back and tell me that the termination period is ninety days, and then, link to that that, that language. And also, Agiloft has a contract assistance. So as legal, you can live where you where you work the most within the word document, and you can identify clauses and tags within the agreement, and see where certain things have been changed and leverage your playbook. So at this point, I'm publishing the the changes back to our agreement record. And now I'm ready to send it for the the risk assessment. So as I scroll up here, I'm able to see that I have a new button that says initiate our PADU process, which is our risk assessment process. And as part of this, you can see that it did build out a number of, risk assessment, task for different groups, for our contract team, our network operations team, and our finance team. So in doing this, I'm going to, once again, switch personas and change to, one of the risk assessment groups. And as we log in, we'll be able to log in to our dashboard as part of the risk assessment process and see which tasks are pending. So I'll flip here to the the risk assessment dashboard, and I can see a number of tasks are pending. So as part of this, I'll open up a task. From the task itself, it has all of the the contract record and and information linked directly to the task. So I can complete my review right here, and then I can, assign a value based on my assessment. So in this case, we'll we'll include it as discouraged and mark that as complete. And for sake of time here, I'll complete the other pending, pending task and risk assessments here. And so as I wrap up this process, I'm going to flip back to the network specialist persona, and I'll I'll see that the review has been completed right within my navigation bar. So you can see here review complete, and I have a new button in the upper left hand corner that says create approvals. So now the approvals will be created based based on that risk assessment. And we'll show you here how the approvals are built out. And we can see here that the network VP, the contract is is being routed to the network VP for approval, and also the plan president because there were some discouraged, values as part of that that risk accepts assessment process. And I'd also like to highlight on the right hand side of the screen, you'll see an executive summary prepared as part of that, which I'll show you the details of that in a second here. So last back and forth here, but I'm gonna once again flip to another persona and act as an approver, and we'll open up our approval dashboard to see what approvals are pending. You can also just simply do this on a mobile device or or via email, and I'll show you how that's possible once we actually open up the approval. So within the approval notice, you'll see this executive summary attached. This executive summary will have all of the details surrounding the metadata related to the the compensation, the provider type, all of the details up top here. And then as we scroll down here, you'll be able to see any clauses that have been redlined or impacted, as part of the negotiation process. So you can see that big change highlighted in red there. And as I scroll down further, you'll be able to see the compensation that's been modified as well. So an approver can review all of that information from a single executive summary notification and be able to make a decision whether or not to approve, you know, right from the notification. So last switch here, I'll flip back to our network specialist. My contract is is officially been approved. I can now route it for signature. But as we're doing that, I do wanna show you the actual email notification that's sent out to the approvers, that just takes a second, to get to me via email. So as we're doing that, here we're now preparing to send the contract for signature. So I can I'll be able to add in my external signatory. We can even leverage automation for delegation of authority to determine who the internal signatory would be based on use cases. And there's that approval notice that was sent to my approver. And you can see attached to that executive summary and also a copy of the actual agreement itself right within the notification. So here, I'm just gonna route the agreement for esignature. And in this case, I have DocuSign, integrated with with Agiloft. So it prepares all the information for me. The tags are embedded in the actual agreement itself, so it makes it very easy and, seamless to send the agreement for for signature right right from the Agiloft solution. And let me just navigate to a contract that's already been executed to show you what that that looks and feels like once we have the executed agreement fully signed. So here, I'm just pulling up a summary of the electronic signature verification, and then you can see that we also have the the fully executed agreement, linked within the record, and we'll navigate down there to to be able to see that the agreement's been fully executed. So that gives you a quick quick view of an end to end solution that we'd love to dive into some more details with you. That was awesome. Thank you so much. Okay. Before we, jump over to q and a, the last question I have for you, Bryan, is, what advice would you give to organizations that are just starting out on their journey? We've talked about a lot. You showed a lot. I think it can be kind of overwhelming. Where do you start? How do you start? Yeah. Really gaining alignment, I think, early from the top down and setting expectations. As part of that, you know, ensure as part of this process that we're bringing along all the various stakeholder groups along in the process, and then plan and prepare. Right? And really don't shortchange change management as part of this process. You know, one of my colleagues, you know, always said that CLM is not essentially a build it and they will come type of application. We really do have to meet users where they're at. So training is is a critical piece of this to for end users really to understand how to adopt and acclimate. That is great advice. Okay. So we've got a few minutes left for questions. Mhmm. Let's see. Actually, I'm gonna start with something that, question that popped up, and it it relates to something that you just touched on, change management. So a contract life cycle management tool like everybody has just seen in Agiloft, as a piece of software, it takes people it takes, you know, consultants to really kinda bring it to life. What do what kind of how do you approach how does Epiq approach, CLM implementation, and what other things do you kind of do aside from, you know, just actually implementing the software? Are there other considerations, kind of pre implementation, post implementation? Like, how do you approach it? Yep. That's that's a great question. Our approach, we like to first and foremost understand, around the readiness activities even prior to looking at implementation. So what is your objectives? Outlining your pain points and really ultimately determining what is our success criteria. That really becomes our North Star throughout the entire implementation process. And then really taking solutioning out of things is start going through some of the readiness effort around organizing our templates and preparing our our inventory of templates, understanding what our initial data model would look like. If we don't have a well defined approval process, what does that look and feel like, and how can we help, streamline that in conjunction with the solution. So doing a lot of that upfront work so that when we're actually behind the eight ball and we start the project and we do have a strict timeline to stick to, you know, we mitigate a lot of those delays as part of the implementation process. And then we're also enabling the organizations to feel much more comfortable with the subject matter, as part that's going to be required as inputs into the implementation process. That's awesome. Okay. Another question. Bryan, all of the everything we've talked about today, I think, kind of leads to the ultimate conclusion that, well, really for any organization, but particularly for payer providers in the health care space, CLM really is kind of a core platform for a business. And in that sense, can you give us an idea of kind of what other course, platforms or tech ecosystems does or should a CLM solution plug into? Yeah. And talking about Agiloft in particular, Agiloft integrates with a wide range of systems and has a robust integration hub that's backed by Workato. So you can integrate with enterprise apps like Salesforce, Dynamics, SAP, Oracle to three sixty five and SharePoint, and, of course, your esignature solutions to to name a few. Awesome. Okay. One more question. So what we saw today and what we're talking about today is really kind of specific to payer provider. Obviously, their the health care space is broader and bigger than just payer provider networks. Can Agiloft be configured for other use cases like clinical trial agreements, life sciences, things like that? Absolutely. It's flexible enough to handle everything from vendor agreements to payer contracts, facility leases, virtually any type of agreement. You can set up unique templates and workflows for each contract type. So everything really lives in one system but reflects the process that you need. Awesome. Thank you. Well, we are, just about out of time. I don't see any more questions in the chat, so we'll go ahead and wrap it up. Thank you so much to everyone who joined us today and a huge thank you to Bryan for sharing your expertise and your real world experience. And if you are ready to streamline your contracting experience, reduce compliance risk, and stay ahead of regulatory change, we invite you to connect with us after the webinar. You can also visit visitagilelock.com or epiqglobal.com to schedule a demo or learn more. Thank you again, and we hope to see you at a future session. Thank you. Thanks.