Name: Transforming the Healthcare Provider Experience with Oracle Cloud Infrastructure
Uploaded: 2025-04-16T19:30:56.828Z
Duration: 49 min
Description: Transforming the Healthcare Provider Experience with Oracle Cloud Infrastructure

Transcript for "Transforming the Healthcare Provider Experience with Oracle Cloud Infrastructure": Welcome, everyone, and thank you for attending today's webinar, transforming the health care provider experience with Oracle Cloud Infrastructure. Before we begin, I wanted to cover a few housekeeping items. If you have technical or content related questions during the presentation, please use the q and a window. We will address your questions. Closed captioning is available by hovering over the stage area and clicking the CC button at the bottom of the screen. You can expand, minimize, and move each of the window panes displayed on your screen. And don't forget to visit our additional resources available in the resource list. We encourage you to download any resources or links that you might find useful. I would like to now introduce our moderator for today, Tomasz Zarzycki. Thomas is Argano senior vice president and health care industry lead, helping Prospect Medical and other clients transition to Oracle Cloud solutions. With twenty five years in IT, he excels in cloud ERP and supply chain management projects and has extensive experience with Oracle products like PeopleSoft, EBS, and JD Edwards. Thomas, welcome. You may now begin. Fantastic. Thank you, Carrie. Thank you for the introduction. We are Argano, premier Oracle partner for health care with over 800 practitioners in Oracle cloud space. Fantastic net promoter score indicating our excellence in delivery of all components of Oracle technology for health care space. We also, won 2,024 partner awards for innovation in space, and we are extremely excited to share the stage today with, Esteban Rubens, health care field CTO on Oracle side. We're working with, Esteban in setting the, strategy for our offering for health care. Esteban, thank you for joining me today. Yeah. It's a pleasure. Thank you. Fantastic. So to, go straight to the content, exciting content for today, we would like to explore and share some meaningful examples of how Oracle Cloud infrastructure can solve common health care provider problems, specifically how, OCI can automate both, clinical and nonclinical workflows. We would specifically like to, see how Oracle technology can tie electronic medical records, ERP revenue cycle, areas in health care provider space. So the plan for today is to start with a, with a with an overview of Oracle Cloud infrastructure capabilities and Oracle viewpoints on on this space. And we will then, walk you through some common patterns that Argano found helpful when using Oracle Cloud Infrastructure Technology and automating, health care provider workflows, and then specifically walk you through a great example of how Oracle can help with automating those specifically, eFax, patients, referrals automation. So, Esteban, with that, I will advance the slide to an overview of the Urgo Cloud infrastructure platform. But I think, you know, maybe the question would be, why we are talking about OCI in the context of efax patient referrals? What's the overall view of, of Oracle on life science providers, public health, and payers? That's a great question, one that comes up often. And I'll I'll start answering by saying that if you haven't heard, Oracle refers to itself as a health care company now. After the acquisition of Cerner, the creation of the Oracle Health business unit that comprises the electronic health record, public health, analytics, our clinical trials unit, and pharmacovigilance, We have a real world data, real world evidence consulting. So there's a lot that we do under the new Oracle health umbrella. And beyond the fact that our founders now referring to Oracle as a health care company and is keenly interested in having Oracle contribute to, solving some of the problems that health care has, not only in The US, but globally. We also have the Oracle Cloud, which is really what is driving a lot of the growth for Oracle. So I have to say, for myself, being at the intersection of cloud and health care at Oracle is very exciting because it's where everything is happening. So it's it's a it's a great time. We have a lot of really good people working on these problems. We've announced really fascinating developments, like the new version of the electronic health record that's switching the paradigm from a keyboard driven, interaction to a conversational EHR that's cloud native, and that is really a big deal. And what we see here really is kind of that that viewpoint of Oracle as a health focus or health centric company that has built everything on the foundation, you know, the bedrock of the Oracle Cloud Infrastructure. Everything we do now is based on our second generation cloud, Oracle Cloud infrastructure that we refer to as OCI. And, we add some something a lot of people don't even know. We go to HIMSS or we go to VIVE or health, a lot of the health conferences, and people, wanna talk about the fact that, oh, Oracle actually has a hyperscaler. Oracle has a public cloud. Yes. We indeed indeed do. And it's not only a public cloud, but it is a very, significant player. We have a huge global footprint. We have regions where others don't. And, so because of that, we have our infrastructure layer, then we have our PaaS, yeah, infrastructure services layer. And then on the health care side, we have a lot of applications built on that foundation. And, if you look at what applications we have, it's interesting because there are parallels between all these applications and the focus that Oracle has had for almost fifty years on the enterprise. So we we are viewing this as an enterprise problem that is similar to other enterprise problems that Oracle has been very successful in helping with over the last forty seven, forty eight years. So that that's kind of in a nutshell, right, why why we're here and why it makes sense to to talk about this. And then just briefly to kind of go into it a little a little more, I refer to this as a second generation cloud, which is true. We we had a first generation cloud that we vastly improved with with this cloud. And we at the core, you have all the infrastructure that you would expect, CPU, GPU compute. We have, all the storage block object, everything that you expect. Right? This is no different than than the other hyperscalers surrounded by, very specific platform services and, back office applications like, you know, Argano has worked with for a long time, you know, in the the fusion ERP side. And the fascinating thing is that as the only hyperscaler that has a health care component that that owns an EHR, electronic health record, and owns the, population health platform, we can now fulfill that promise of bringing in all this data into the health care enterprise, not just clinical data from the EHR and pop health, but also things like, inventory control or supply chain or financials. There's a lot to talk about, but in a in a nutshell, that is that is why we're we're talking about this and and the ability to integrate this, right, and and transform that data into something useful to derive the right insights without losing focus on the fact that, in The US, in Western Europe, in a lot of the world, the electronic health record is the hub that the clinicians use. Right? Doctors, nurses, everybody lives in the EHR. So we want the useful, actionable insights such as the ones that you're gonna be talking about to eventually make their way back into the EHR because that's where the clinicians need them. Right? And so completing that loop is really huge, and it shows kind of the flexibility of how you can do work. And it also, pays testament to the way that we approach this as a very open ecosystem, publishing h l seven fire APIs that allow for all this, interoperability to take place and, you know, really also underscoring how much we appreciate partners, you know, and how much work we do we do with partners. So, you know, I'll I'll leave it at that for now. Thank you. Fantastic. Thank you, Subhan. So then the question becomes why, in the context of, you know, modern, complete platform in health care, why do we why are we talking about such an ancient technology as fax, eFax transmission, and, why did we pick it up as, as a topic for today? Well, the reason for it is, Esteban, as we spoke earlier, faxes are everywhere, right, for many, many reasons. Right? It's a it's that primary vehicle for sharing patient data, whether whether driven by regulatory reasons, technology adoption. So our thinking, for today's panel is that we could use that, the paradox of having all those wonderful technology elements at our disposal. Machine learning, big data integration services, new generation of Oracle Integration Cloud Healthcare Platform. How can we apply it to, tackle a, you know, that's the prevalence of facts in in a healthcare provider space in in The US? Before we get to example of how we were able to, you know, very rapidly automate the patient referral process, using OCI, I I would like to maybe spend just a moment, talking about the common healthcare pattern that we've seen, in health provider space, because that would help us understand how we build the patient referral solution. So on the left hand side, you have a typical very, very, common scenario in health care. We have where you have, a good amount of structured data sources, electronic medical records, ERP, HCM, rev cycle. That's where Argano capabilities in health care space started. But then you've got tons of data, tons of information being exchanged using fairly unstructured, messy means of communication, faxes, blurry images, usually tons of them. And so and with that, a lot of manual work involved in looking at them, extracting meaningful data for both clinician and back office employees. So, our approach is to, first, use Oracle Integration Cloud to ingest all possible data sources, both structured, unstructured, and move them over to Oracle Cloud Storage, run document understanding services, a powerful feature that allows you to look at PDFs, images, extract keywords, understand what's inside those documents, patient referral packets being one of them. Then we we can use health care specific AI and machine learning models to essentially understand what's in those documents, what's in the keywords that we have extracted, what's the, what's the content meaning, what are clinical data entities in in in those documents? Then once we have all those pieces of information in one single place, data warehouse, we can then drive process automation. So sends information back or clarify information back to, to EMR or or ERP. When necessary, involve, operators, users to review, the results of that analysis if needed, aggregate the data for analytics, and allow users to, have a conversation, live conversation with the content of those documents. Specifically, we'll come back to this, which technologies, protocols we can we can use. I would just like to highlight, one of the fantastic features that, became available with the latest, addition of, health care edition of Oracle Integration Cloud, which is ability to, communicate natively using Fire h l seven protocols. And, then when we, when we switch to, walk through of the eFax and patient referral solutions, I'm hoping that it will be, that this frame would be easier for us to understand how we solved and automated the problem. And just let me let me add something very quickly. I love how you're doing this because it's not passing judgment on how old or, annoying faxes are. They're a fact of life in health care. You know, if you're in health care, you're dealing with faxes. As a patient, consumer of health care, as a clinician, practitioner, no matter where you are, you see them. And so this is actually rolling up your sleeves and doing something about it because it is a problem. It's not going away anytime soon. I would love for it to, you know, be like Thanos and have 50% of faxes, you know, just, like, disappear immediately, but that's not happening anytime soon. So this is very pragmatic, and it's absolutely necessary. There's almost no one in health care in The US, who would not benefit from this because it is an actual problem in search of a solution. It's not coming up with solution in search of a problem. So this is excellent. Fantastic. Thank you, Esteban. So let's take a quick look at, what the actual application of, Oracle Cloud Infrastructure tool sets could look like. On the screen right now, you you can see just a brief summary of, the process that we were able to automate using OCI in the context of patient referrals. So the first step, hundreds, thousands of patient referral packets arrive through, fax numbers, eFax, APIs, in our health care provider landscape. In the sort of prior to application of the OCI automation toolset, one of the providers where we are implementing this solution, essentially a the whole department of people, patient referral coordinators, have to look at every single PDF and every single fax transmission, page by page, sometimes dozens of pages for a single referral packet to extract, to understand, what's the patient name, what's the, content of that packet, who's referring that patient to to us. So, our approach here was to, again, connect to the inbound fax channels, capture those documents that are coming in and through fax, store them as as, as images, clean clean them up, but then run the document understanding through them. So essentially extract all the information from them. Once we do that, we can, do, well, we can perform one single step, which is, which are patient referral packets, which are not. And surprisingly, in the world of messy fax transmission, answering that question, which is what is this document or does it represent what's already a meaningful, input for patient referral coordinators. But once we, once we run the PDFs through document understanding, we were able to we are able to extract patient data, compare it with, the data that is already stored in electronic medical records. If there is a match presented to the to the coordinator. If if if not, run it for manual adjustment process. So, let's take a look at what, you know, what what's the end user experience could be. So, obviously, we are able to present a queue of incoming documents and separate them between new patient referrals that require review or pending, that's automated analysis. When you see warning status for the incoming documents, those are the messy transmissions that's where we don't have a clear understanding of, or or where the models had difficulty in extracting that up and matching it with the EMR records. And then you can see not a referral status. This is noise. Secondly, obviously, we can produce some statistics around, the queue, the aging of that queue where those, packets on which they they they were received. And, you know, importantly, split them by department. Right? So, so make a make a selection either based on the content of the documents or the incoming channel whether they are they should be routed to, pediatric oncology or ER or, an ICU. Lastly, if we can extract the physician information, we can also make that, provide that provide that summary. But, this is this is a view of a department queue, so you can see that, in the test environment, we have a handful of documents that require, that will require review. The solution then split them between each individual department that's, for which we need to perform a a review. And for each department, we can assign them to a referral coordinator based on either workload or other rules that we can we can put in place or learn automatically based on based on documents history. So this is this is just a very, very basic view to, to highlight the fact that we that the solution can work with multiple departments, multiple coordinators as a workflow component embedded in that. Obviously, if we have an indication of, any of those, received efax transmissions being urgent, that can be flagged. And, and on the screen right now, we have, selected, our queue to start with urgent transmissions. So let let's then take a look at the verification queue. This is sample data, synthetic data. Obviously, we are not showing any real referrals. So no real patients are shown on the screen. This is, this is, obviously sample data test environment. But you can see a referral queue with multiple departments, providers, coordinators assigned to each and every document. For each document, we can obviously then take a closer look at the contact, contents of that fax transmission. But I would like to go straight to where, you know, the real power of Oracle technology really, really, really shows, the automation potential. So right now, we can see a we have clicked on one of the one of the documents. And what you can see on the screen on the right hand side is that using document understanding feature, we can extract and summarize from those dozens of pages of patient referral packets provided in multiple formats, sometimes messy, sometimes blurry, but this is an example where document understanding model was able to extract and summarize some demographic details about the patient, observation, diagnosis. That's on in the top right corner of the screen. So a summary of hundreds of pages of documentation that is behind that referral packet, that is presented to the referral coordinator for initial review, and then suggested match. So if there is already a patient records, that meets with confidence criteria, that that were set for, for the system, Our solution can then provide a suggested match with existing patient record. So this already serves saves tons of tons of time on the, patient referral coordinator side. We have a, identification of existing records. We can now look at the content of the document, double check everything. And if we hit confirm, back to the diagram that Esteban Rubens showed at the very, very beginning of the webinar where we had the that loop between Oracle Integration Cloud toolset and EMR using, available APIs from Oracle Health or other EMRs, we can add this referral packet as reviewed to the existing, patient record. If there are other matches, that are possible with lower confidence, they are also presented to the user. But, you know, I quite on purpose wanted to to pause and to focus on this particular screen print because that's where the essence, of the automation potential really, really lies. Alright? So one, ability to extract the text from fax images, summarize it, present it in a meaningful manner to both administrative staff as well as physicians, and then suggest a match or automation opportunity by attaching this package to to the underlying EML system. That's, that is that is really the, the reason why, we we we we started with with with this use case because it's clearly, for for, one of the leading, pediatric hospitals where we are implementing the solution today. This is the opportunity for them to to save tons of time, both on the, back office as well as physician side. Obviously, with that solution, we have ability to confirm matches, look at the, all pages of the documents, of the original document if needed. But if approved, that summarized version of the packet is then sent to to EMR. One thing where we probably may want to pause here and also add a comment, Esteban. There is a common perception notion or maybe maybe worry about, applying, AI machine learning in, intersection of, clinical non workflow, like a nonclinical workflow settings. I wanted to just take a pause here and and talk a little bit about the human in the loop. Right? So to maybe underscore the fact that even if that summary is presented to the user, we add a component of a review, we add a component of human in the loop. Any comments here, Esteban? I I absolutely agree that there are, well founded concerns, and we need to tackle them head on. So first of all, the human in the loop, as you're saying, is vital because with that, we ensure that we're using automation for what it does best, but we're not putting all the eggs in one basket. Right? We're we're using automation, and then we're making sure that things are working the way they should. And so, you know, at one point, I think you had mentioned this idea of, approaching this in stages. And so this is absolutely the first stage. There is no need to go beyond it. This is already not only a time saver, as you said, but it has direct relevance to patient care. Because right now, not only do these referral processes often take too long, but, patients fall through the cracks. We we hear about that all the time. Things get lost. They don't get processed. They go into the wrong queue. So having, an automated system to make sure those things don't happen is, again, not only a a a kind of flashing red lights technology solution, but it's you know, I I always like to think about, everything in terms of the quintuple a. Right? You know, does this improve patient care? Does it reduce cost? Well, yes and yes. Does it improve the quality of life for clinicians? Well, yes. Of course, it does. Does it increase, equity? Yes. Of course, it does. So it's almost like a a home run. Right? This this almost hits every, every item in the quintuple aim, every aim, and with something that is then absolutely necessary. And then beyond that, in one of the slides you showed before, there was a concept of, bring your own model. Right? And in in OCI, Oracle, we have this concept that we meet you where you are. You can bring whatever tool, you want, open source or not. You know, you can bring your own models. We have some open source models. We have our own models. Whatever works best. And then on top of it, the idea that if you wanna bring your own model and you wanna do some further training refinement, you can do so in isolation. We can guarantee that you have an environment in which the model only sees the data that you wanted to see, so there is no contamination. Right? There is nothing going exposing the model to things that are irrelevant or problematic. So that's another good thing about doing this, you know, in this way. And then, of course, the the the possibilities are endless for the future because you can you know, if if if we wanna do more automation, we can introduce RAG, you know, which will augmented generation so that maybe each facility's procedures for, for referrals are taken into account when processing the referrals. Or if you, introduce some kind of, chatbot interface for people to work with their queues, that that is kind of guaranteed not to have hallucinations because you are, filtering everything through the lens of your own internal, procedures. So it is, absolutely right to talk about any concerns, but there are a lot of good answers that are not just hand waving, you know, smoke and mirrors. There are real solutions to to these concerns, and everybody can take it at their own speed. There's no no no one size fits all. The solution is here. You can start with this, and then you can stop. You can automate more. You can go in so many other directions, always making sure that the end users are comfortable and that we have the, the accuracy. Right? The specificity, sensitivity, area under the curve, however you wanna define it, that we're looking for. So it's actually better. Fantastic. And you you mentioned noise. You mentioned, you know, fine tuning, either generic or customer owned models to detect transactions that are absolutely irrelevant for our queue. On the screen right now, we have this is one of the stages of the, initial training and deployment where we are effectively testing the incoming patient referral queue to, detect documents and transmissions that are absolutely irrelevant. And on the screen, we have invoice, some random, lab results transmission, and then op report that is not a patient referral. We can we can we can fine tune that ability to, remove whatever is not a patient referral from the incoming queue. Users can then confirm that this indeed is a document that is irrelevant for for the review. And by the way, all those user actions, that's human in the loop interaction, over time will obviously improve the accuracy of the model. So, every single action where the user says, you're right. This is not a patient referral. This is an invoice. For some reason, someone used the wrong efax or fax, fax number. That obviously is a is a data point that would, allow us to to fine tune the model, going forward. So that was a that was a brief introduction of, eFax patient solutions back to, that common framework that we talked about earlier. So you can see that, first step, Oracle Integration Cloud, you know, ingesting patient referrals, storing them in, in Oracle Cloud, extracting patient info, matching with existing patients or future, existing of future planned encounter in EMR, and attaching the process review documents into the EMR solution. Before we, maybe then talk about, you know, well, how does this apply to a wider array of problems in in health care? Patient referrals is just one one area where, Argano was able to use Oracle, cloud infrastructure to, automate provider workflows. But there are tons of other areas, Esteban, that I think we were going to talk about just in a few brief moments. There's a great potential, looking at the overlap with revenue cycle, revenue managements. Just one thing alone that's, we should have mentioned. Global search across all the documents that we have, we we are providing that ability with, so so, both, referral coordinators and physicians can look for any part, any fragments of, of the documents that are that were received. We talked about ability to aggregate that, provides some useful analytics. And we also have other examples where we use exactly the same approach, the same framework to automate processes that cross EMR, rev cycle, supply chain, such as implants billing. So I just wanted to make sure before we move on to sort of talking about bigger picture that, this was just a very, very specific use case with patient referral automations, but, obviously, the opportunities are endless. Yeah. You know, beyond that, it kind of the the the common thread is trying to move beyond all these data silos that we've created. Right? We we have done a lot to automate health care, some of it good, some of it not good. The result, though, is that we have all these crazy silos with big modes full of crocodiles, and, you know, it's very hard to kind of move data across and and, you know, do it easily and and usefully. So everything you were showing before, it has the same idea of bringing all these, different kinds of data together from different systems and building bridges across these modes so the data is more useful. You know, we know that we can't necessarily eliminate the silos. The silos are there, and they're probably gonna stay. But if we can at least let the data move around and and make the data more useful and join it, that can really deliver a lot of value both in terms of financial value, but also in terms of patient care value. Because right now, I would venture to say that most health care facilities have a lot of data that is just locked in those silos that maybe can be accessed in the context of the the silo, with some kind of reporting tool, but not in the context of everything. And if you think about, something like, bed management, you know, thinking about predicting when you're gonna need beds and when they're gonna be ready, well, yeah, you want EHR, EMR data. You want, supply chain data. You want time and attendance data to know when people are are gonna be available to, clean and set up the rooms, and you're gonna have nursing staff and so many other things. And, also, external data. You wanna know what the weather is gonna be like, and you wanna know if the CDC is predicting that there's gonna be a spike in flu in your area or any number of things. And the only way to get this done is to bring it all together with some kind of integration tool, and that is right up our alley. We've been doing that. We've been doing data integration the whole time that Oracle has been around. And now with the introduction of this health care edition of the integration tool in the Oracle Cloud, we can kind of do it all. Right? Because we can we already could do all the non health care data now being able to look at h l seven and FHIR and then also the external data sources that allows us to have this overall view that really helps, create these or generate these useful insights. Are there any features in specifically in the health care edition that, that you would like to highlight? I already we already mentioned h l seven that we use to communicate to, sort of review patient referrals back to EMR. Anything that was worth worth mentioning? What is new? The ability to not only look at HL seven and kind of fire with the subset of or or superset of HL seven, but also to do transformation. Right? To to, do things with those message and messages and send them on. So the ability to do transformation either in bulk or ad hoc is very important when you have any kind of workflow that is real time or near real time. And, you know, you have a list there, kind of trans translate versions. You know, how many h o seven versions are there? No one really knows. There are too many. Right? And fire, the same thing. You have things that work with one version that break hopelessly when you go to another version. So having that ability to do version translation is really, really important. And this is kind of the, health care, universal translator. This is something that if you're going to be doing any automation in health care, you absolutely need because this is the language that we're using globally, right, for health care. It's become the standard. You know? We we don't have that many. There's h l seven fire. There's DICOM and maybe a couple others. So it is crucially important to be able to under you know, kind of the same way that you were talking about the eFax solution. It's not just looking at something. It's understanding it. You know? It's getting some semantic meaning out of it. And so when you can look into the packets, you know, you can look into the messages and understand what's going on and, you know, do, the necessary transformations, that does a lot of the heavy lifting that otherwise people would have to create from scratch. Yeah. And then as fire is obviously nice to have. Absolutely. Carrie, we'll probably take a pause here for, any questions that we might get we might be getting from from the audience, before we get to, call to action and q and a? Tomasz, just as a reminder, you can ask a question by submitting them in the q and a engagement tool located at the bottom of your screen. And while we're waiting a few minutes for questions to come in, I did have one, that's been asked frequent frequently. What is the complexity of implementing something like this? How long do you estimate to a proof of concept here? I I can take it Esteban, but but I think, you know, this this is something that we didn't spend enough time on is the velocity. Right? The usual, implementation cycle in health care sometimes is measured in months, years. And, you know, the common pattern that we've seen is that, you know, waiting for sometimes a simple solution such as here's a PDF or hundreds of thousands of them. I would like to see summary of each and every one of them. It's a great question. So our experience implementing our CI is that it's just, it's amazing how we can stand up a meaningful proof of concept, so be able to prove that we can connect to the incoming efax, channels in a matter of weeks. To to give everyone a sense of perspective, the initial iteration for for for for the previous iteration of the efax solutions took literally weeks from standing up Oracle environments, connecting to the existing data sources, ingesting the data, and then, showing users a, you know, a way to to to interact with the data. Aswan, any thoughts here? Ease of use, speed? Well yeah. So o OCI is built for that. And, also, I wanna bring up the the security aspect. Right? The OCI security model is such that everything is, denied by default. You have to explicitly allow things, and that makes it, so that anything you do in OCI is more thoughtful because there's no way to have anything fall through the cracks. So we implement something quickly. We have, all the infrastructure and platform services that are necessary. And then on top of that, you have the, peace of mind that the way we've created the Oracle Cloud is conducive to regulated industries like health care because it's it's like, we're we're making it, very, very hard for anything to happen that you don't want to happen. I mean, there's always ways. I don't wanna say never. No one can ever say never, but we've, we've really thought long and hard about this specifically from the perspective of of regulated industries. Of course. I I have a question about the the resources. Right? So, yeah, we have CPU, GPU. We have everything available, but I think this is not a heavy solution. Right? This is a pretty lightweight solution in terms of requirements. So can you comment on that? Certainly. So, there's a very lightweight footprint behind the eFax and patient referrals. The moderate flow, which is hundreds and thousands of documents, takes literally a, autonomous data warehouse with minimal, number of, CPUs behind. So it's almost like a developer profile. There's a integration cloud component, healthcare edition, which the basic version of it takes, you know, 5,000 messages in the message box. So entry level, edition or compute profile of Oracle Integration Cloud, and some few, serverless functions, flying in the backgrounds, serverless calls to machine learning models. So it's extremely super lightweight, and ready to to deploy in a in a in a very, very impressive time frame. Great. Thank you. We do not have any questions at this time. Fantastic. Well, so I guess where when we go from here, what's the call to action? We have shirts in our, documents panel, and I'm sure it'll be available, Carrie, to everyone joining here online. Just a couple of links and a couple of, materials that's, number one, just summarize our approach, joint approach, with Oracle for for health care, summarize the solutions that we talked about today. And one thing that we would definitely like to point everyone to, back to Esteban question, you know, how how quickly can it be implemented? What's needed from, Oracle Cloud Integration resources perspective to, implement a proof of concept, of the toolset that we showed today. There's the integrated data strategy workshop for health care link in the, in the in the materials. So I would encourage everyone to, familiarize with those links and and all the materials provided with with our workshop. Data strategy workshop would be an excellent next step where, you know, for for all webinar participants who are interested, we can, spend time talking about the pain points, opportunities for automation, look, even more in-depth at any of the use cases that we talked about today. So, we would encourage everyone to, to, to to click the links and familiarize themselves with the with the content provided there. Yeah. And I'll say I I I hardly recommend that. I talk to customers all the time, and there's lots of great ideas, but usually, they run headfirst into the the hard reality that their data state is a mess. And so better kind of tackle that first and kinda look at the data state, understand what you have, what you may be missing, and and what requirements there may there may be for cleaning, transforming data, normalizing data. All of that usually is required. So it is, and and even if you don't end up doing anything else, every health care, organization should do this, should do a data strategy workshop because you're gonna be doing something in the future. And the more time you let elapse before you do something like that, the more, data debt, if you will, you're you're acquiring. So this is kind of foundational. It's the cornerstone for anything else that you do, and it's great that Argano offers it. Fantastic. And, Sivan, as always, pleasure talking to you. Thank you for joining the, webinar today. Great conversation. Once again, thanks everyone for joining our session today. We look forward to interacting with you, after the webinar, answering questions you may have. Esteban, Carrie, any closing comments before we wrap? No. Thank you so much for having me. Thank you, Esteban. And if anyone has any questions, feel free to reach out. Thanks everyone for your time, and we hope you join us for future events. Thank you. Thanks, Sergei.