Transcript
Nick Scallion (00:00) hey, folks. Good morning. How’s everyone doing today? Pretty good. Yeah… the Aaron joining and… josh from my team is joined. All right. So we’ve got four on the usap side. Justin. Let me know if you think you’re looking complete on your end or if we’re waiting for anybody else.
Jocelyn Kopchak (00:33) I did invite one other person but we can go ahead and get started. I invited Rosanne but it looks like she is currently away so… you can go ahead and dive in.
Nick Scallion (00:49) No sweat and we will record the demo. So if you want to send that to Rosanne following, she can like speed it up to two X speed and skip around or you folks can do that as well. So no sweat. So for the new faces, I’ll Nick on our sales and partnerships team and I’m joined by josh levitin on our solutions consultancy organization. Josh will lead the demonstration today. So I had a couple great chats with Jocelyn and Aaron and goal today is just to provide an overview of how we try to operationalize usap workflows with onboarding, credentialing, payer, enrollment the hospital mso applications that you’re sending to your partner facilities and trying to cram that into, let’s say 45 50 Ish minutes, please pepper in some Q a throughout, but we’ll also try to leave a little buffer at the end as well. Let me know if I missed anything on the agenda, folks, but otherwise, I’ll let josh load up his screen and we can try to get started here.
Joshua Levitan (01:54) Yeah, pleasure to meet some new people and see some old faces as well.
Nick Scallion (02:01) And Ivonne and Tiffany just fill me in just for intros. Where do you folks sit within usap just so we make sure we’re tackling all the items that you folks want to hear about today?
Tiffany Jolley (02:14) This is Tiffany. I’m over credentialing for half the United States for the hospital credentialing, and then I’m also nationally over all of payer enrollment.
Nick Scallion (02:24) Perfect. Okay, great to meet you, Tiffany. This.
Ivonne Oladunni (02:27) is Ivonne, I am over the other half of the country for credentialing. So the onboarding reappointment facility the.
Jocelyn Kopchak (02:35) Whole nine.
Ivonne Oladunni (02:36) Yards.
Nick Scallion (02:38) perfect. That sounds great. We’ll make sure we try to touch on everything and Aaron and Jocelyn will tell you josh doesn’t mind being interrupted because you’ll probably forget what question you had. So just feel free to interrupt him. Sorry, josh, but I’ll let you get started. We’ll go from there. Yeah.
Joshua Levitan (02:57) No, I’ll say it. Okay, great.
Nick Scallion (02:59) So,
Joshua Levitan (03:00) we’ll get into the demo here in a sec, quick preamble we’re going to look at the demo in sort of three parts. Again, lots of covers. I’m a long winded individual and I’m sure you’re all going to have some great questions. So might not get to all of it today. But the way that we’ll walk through this is first by talking about like sort of onboarding, so getting and storing data, we’ll take a look at this as if we were a provider who was joining usap, the process that they would go through to actually get their data into the system like from their perspective. And then the second part of this sort of intro will be storing… and managing the data and how your team would see all of the information on providers across the org or an individual provider. So that’s sort of like our foundational element, right? We need that in order to be able to do anything downstream, the next section of the demonstration will also be multi part and that’s doing something with the data. So the different parts of this will be credentialing payer, enrollment, sending out applications to hospitals, like how do we actually take that data and then achieve business outcomes with it?
Nick Scallion (04:14) When.
Joshua Levitan (04:15) we get to that point, we’ll probably start with credentialing, then move to PE, and then move to hospital apps because I think that would probably represent your flow. Excuse… me best as it is right now, but we can be flexible there in what matters the most for you all to see the last part of the data of the demo which we most certainly won’t get to. But we can touch on as needed either with a video we can send as a follow up or an additional session would be more about reporting and analytics. How do we view the information from like a business intelligence dashboarding perspective on everything we’ve collected so that we can sort of track where everything is in the process at a organization wide or management type level? Does that sound like a good plan for everyone?
Tiffany Jolley (05:02) Sure. Sounds good. Awesome. All right.
Joshua Levitan (05:05) So starting off here… again, I’m now impersonating a provider. And so let’s say this provider just joined your organization. We’re going to reach out to them. This will be part of their onboarding flow, right? Like they need to give us all sorts of information to be able to pay them. And whatnot part of that also is for credentialing. So they’re going to get an email invitation to medallion. We’re going to take this email. We’re going to co, brand it, right? So we’re going to have your logo up here. We can collaborate with you on language. But basically what we’re saying to the provider is like, hey, we need details from you. This is a safe and secure platform. Your organization uses this platform to achieve these very important business outcomes to make sure that you can actually get placed and start seeing patients. And when they hit get started, they’re gonna be brought into medallion and we’re gonna begin the flow of them creating a profile. Now, when we are creating this profile, the most efficient way to do this to get data from them is gonna be leveraging caqh. Most providers already have this, it’s usually updated to some degree of confidence, might not be 100 percent accurate, might not be updated yesterday, but maybe it was updated nine months ago or six months ago. So we’re gonna ask them to link their caqh profile. There are other options here that we’ll talk about if a provider doesn’t have a caqh profile because they’re like right out of med school or something, or if it is really out of date. But for most providers, we want to leverage medallion’s native integration with caqh to start building out their profile. Now, we are also gonna talk down the road about then updating caqh to make sure that it’s fully complete and attested. So, there are two sides to the caqh workflow. But right now, we’re just using this as like, hey, if data already exists there, let’s grab it so that we don’t have to type in a bunch of fields manually. Any questions about the caqh ingestion piece right now, taking data from caqh and putting it in medallion to help build these profiles.
Tiffany Jolley (07:16) Well, we need the reasoning power to get that data imported?
Joshua Levitan (07:20) Sorry, what was that?
Tiffany Jolley (07:22) We need the provider’s caqh passwords and information to have that imported in. Yeah.
Joshua Levitan (07:31) Great question. And the answer is no, and this is a big differentiator between medallion and other tools. We are a participating organization with caqh, which means we’re the only credentialing vendor with that status. We have the ability to pull in their profile just with their caqh id. We do not need their password at this point in time. Okay? So again, you’re asking because I’m sure it’s something you think about right where we see that question come into being important is like they don’t have to remember to reset their password or like ask us why they have to share something. So it makes their life a little bit easier as long as they have this id. And then, you know, two other basic fields here to try and get this process moving as quickly as possible. I have.
Erin.Sanchez (08:18) A question for you there too. So if the provider doesn’t know their caqh id number, is there a way for them to quickly and easily look that up? Because I know there is like on the caqh website, there’s a way to look that up.
Joshua Levitan (08:31) Yeah, they would.
Erin.Sanchez (08:31) Just do that on the caqh.
Joshua Levitan (08:34) Website. Are.
Erin.Sanchez (08:35) there instructions here to show them how to do that?
Joshua Levitan (08:39) Yeah. We can, that’s something we would put into like that welcome email or into like communications with them. Okay. Yeah. So it’s a really interesting point. We have other ways of doing that like in bulk and querying it, right? So like you could give us 4,000 of your providers and we could tell you who has caqh profiles and last time they were updated. But providing that lookup like self service is very hard because caqh doesn’t have the most modern architecture for us to like query something like that in real time. Okay. So yeah. What it does have the architecture for us to be able to do is if we have the id pull in all of the corresponding information. Okay? So we’re going to confirm and link the profile. And then again, we’re just providing, you know, for them here, some additional information on what they still probably will need to give us if it’s not in caqh and sort of how they go through this process. And once they’ve linked caqh, they go to their profile. Now, the goal of this is to be very self service, right? Like we recognize that not all providers will use this portal to… the best of its ability. There might be providers who are more tech savvy who fly through this and understand how to use this. There might be some that need a little bit more hand holding and that is the reality of this. But what we want to do is use modern technology like this to make it as easy as possible and decrease the amount of questions that you get from providers or the amount of time that you need to sort of hand hold providers. This profile now that we are in exists in perpetuity, it is the provider’s portal. Like it is just their information in here. You can see. All right, like if caqh is really good, they might not need to take any other actions besides, you know, filling out their disclosure questions and signing some agreements. If their caqh is not the most updated, then they can come in here and change fields and manually save those. They could, you know, add professional history, they can upload documents, whatever. It might be. One thing I do want to call out for providers that have either a very outdated profile or no profile at all. Is that this adding documents function becomes the next easiest way to reduce the amount of time that they spend doing manual data entry. What do I mean by that? If we’re in documents and we hit upload by photo? It’s April right now. So it’s tax season. So this is incredibly relevant. I just did my taxes this weekend and when I needed to upload a form, right? Turbotax said scan this QR Code. I scanned that QR Code on my phone. You’re.
Nick Scallion (11:35) cutting your taxes pretty close, but I guess this is pretty timely for provider onboarding. Is going to be cutting it close every time too. So it’s a good analogy here.
Tiffany Jolley (11:43) Well, I’m glad you brought that up because you just reminded me I need to do it there.
Nick Scallion (11:47) You go.
Joshua Levitan (11:48) Two more weekends… but basically like it pulls up it like uses the camera on your phone, right? And then you take a picture of the document that could be sitting on your desk or maybe it’s saved in like your icloud if it’s your resume or something like that. And when medallion, like when the picture of the document is uploaded to medallion in this way like turbotax, not only does the document just like paste it as a PDF back here, but we actually read the document and we extract the text from the document and put that in corresponding fields. So if a provider uses this for their resume or their CV, we’re going to read the information from that resume and CV and put it directly into the professional history section. If the professional history section was blank. So that becomes again a really powerful tool. You can also just, you know, upload from your computer. I don’t know if you can see the little like downloads thing that popped up, right? But just how you would normally upload a document or you can do the photo upload using the mobile capability.
Joshua Levitan (12:58) And ultimately go ahead.
Tiffany Jolley (13:02) How does the, how does the system know what it’s reading on those documents? So, how does it know it’s a Texas state license or Dea or a diploma?
Joshua Levitan (13:11) Yeah… part of the answer is the magic of technology, right? So this uses technology called optical character recognition which has been around for a while but is certainly enhanced by… AI and the, you know, newest and greatest stuff out there. So essentially, the technology is trained not only to parse the text but to understand the context of it. Okay? So, part of our automation special sauce here, OCR… has been around for a while like just the ability for, you know, a computer to read text. What has gotten really good in the last six to 12 months is the ability to understand the context of that text and then do something with it. In this case, put it in the right place in medallion.
Tiffany Jolley (13:55) Okay. Thanks.
Joshua Levitan (13:58) Yeah, great question. Now, in the overview here, Naomi is a star student. She gets an a, her caqh was super up to date and there’s nothing that she has left to do, but this is where gap identification happens. And this is our call to action to providers if there is something they need to do. So, while this process is happening of them uploading documents of them, filling out information of us, connecting caqh medallion is essentially constantly going to compare what’s in Naomi’s profile right here to what would be considered like a golden record with all of the information that’s needed. And when there are gaps in that process, they’re going to show up right here in this tasks module. It might be like, hey upload your two by two passport photo or like, hey, there’s a six month work history gap. Do you need to add an employer? What was the reason for that? It could also be something like, hey, we just need you to sign your attestation. So, a lot of different things that come in here. It’s great that they’re in tasks in this portal, want to be clear as well. We’re also going to take that one step further in terms of letting the providers know that there are things that they need to do. This happens automatically. You don’t have to like do anything here. But every time there’s a task, the provider is going to get an email. And with some of our customers, they choose to also use our agent capabilities to send text messages or have phone calls made to the providers about these tasks as well. So essentially, we want to be the squeaky wheel, but, you know, we’re not going to call them every 10 minutes, but we want to make sure that we are guiding providers in the right direction to complete gaps and get the information in as quickly as possible. It has huge time flow as, you know, right? Like the quicker we have all the data, the quicker we can move on to the next steps. But what’s important is your team doesn’t have to identify those gaps. Your team doesn’t have to chase down providers. It’s all done through technology. And we’re trying to even limit the amount of tasking that happens in the first place because of the caqh integration, the document scanner and other methods like that.
Joshua Levitan (16:13) Any questions about this portal?
Ivonne Oladunni (16:20) No questions. But you probably saw emojis early on. My keyboard was stuck. So, just a disclaimer there. I think emojis were flying all over the place. I like.
Joshua Levitan (16:31) Emojis boosting my self confidence for a Monday morning, seeing the thumbs up. Okay? And then the last piece, last point on, this is also optimized for mobile. So there’s no Nick’s having fun with the emojis. Now, the provider can come to medallion’s website on their phone and they can see all of the same things like nicely formatted. They could even for example, like add a signature with their finger directly on their phone to sign their attestations. And I mentioned attestations a couple of times here. So I should note we ask providers to attest to the information in medallion. And this kind of relates back to the question too about like, well, how does the, you know, if we scan a document, how do we have the context to know like what it is, right? And we gave the answer about technology being really good at that. But what we want the provider to do, they could do it here on the computer as well. With attestations. Is like there is an expectation that they will look through this and review it and make sure that everything is up to date and offer their attestation in medallion as the last step. But there’s added benefit in this, we talked before about caqh being a place where we start to look for data. But as we know later in the workflow, caqh also needs to be updated for payers to reference it as part of credentialing. And there becomes a dynamic where medallion ends up having more accurate information than caqh and what you’re I believe you’re doing right now what a lot of customers do is then it’s someone’s job, either the provider or someone on your team to go into caqh every quarter, make sure the information is accurate if it’s changed and then attest, and that represents a huge manual burden. And if you don’t do that, you could risk missing like a reval or not having a successful outcome of a new pay or enrollment. So with medallion, we handle that for you, that becomes the second part of the caqh conversation which is in addition to pulling that data in medallion’s automation automatically. Then once the provider has attested to medallion goes and updates caqh on your behalf on the provider’s behalf. And we do those attestations for you. So the provider normally has to attest four times a year. I believe in caqh. With medallion, they attest once a year in medallion. And then we do all of the caqh attestations for them. In addition, we’re going to make sure that the data is updated more than once a year, right? So anytime that a pay or enrollment request is submitted or… data is changed in medallion, those are the two triggers that will trigger our automation to go in that backwards direction to caqh and make sure that caqh matches the information as it exists in medallion from a source of truth perspective.
Tiffany Jolley (19:40) And so I have a question. So if there isn’t changes, let’s say things just steady eddy, and it’s time for them to attest, and they’re recorded a test. Do y’all get the notifications or does your system know that they’re due on a certain date to know to attest to it?
Joshua Levitan (19:54) We track the dates and we track the notifications. Yeah. So it’s on autopilot, or maybe we should use the staples easy button analogy. Yeah, we’re tracking all of that. And one thing I think is, I just said this, but I think it’s really important and it’s getting ahead a little bit to the PE part of the conversation. But there are scheduled cadences for this, right? Like that. We just talked about where we’ll make sure caqh is up to date and do the attestation. But we’re also gonna off schedule. Make sure that anytime we submit a payr enrollment application to a payr, like right before we submit it, we make sure that caqh is up to date reflecting the information of medallion because we don’t want the information that we submit on a payr enrollment application to be different from caqh when the payr goes to pull it, and therefore lead to an unfavorable outcome. So we’re sort of catching all of the normal changes just by doing, the quarterly attestations and updates at that time. And then we’re taking it one step further and we’re saying what is the most important time in the workflow for caqh off cycle to be updated based on like what we know is happening with the business and let’s do it then, is there as well? So like nothing ever slips through the cracks?
Joshua Levitan (21:16) Does that make sense? Any questions about that?
Tiffany Jolley (21:20) Well, the provider just has to test once a year, correct? Yep.
Joshua Levitan (21:24) Every.
Tiffany Jolley (21:24) year they would attest, correct? Yep.
Joshua Levitan (21:26) Every year they come into medallion and attest, and they come into this portal to do that. We’ll remind them, right? So there would be a task saying like attest to your medallion profile and obviously like they’re going to see it in here, but we’re going to email them as well and potentially call or text them if you choose as well to make sure they know to go and do that in medallion. And that’s a great segue I’m now transitioning from the provider view to your team’s view of medallion. So this is like the administrative or the operator view, right? And coming out like in line with that conversation about tasks you’ll see like the first screen that you get brought to when you log into medallion is the task screen and these are tasks that are being sent to the providers, but your team has visibility into them. So anytime we are asking something of the provider, you know exactly what it is and, you know, if the provider’s done it or not.
Joshua Levitan (22:34) So I can’t promise that 100 percent of the time that providers are going to do everything based on our calls and emails, right? Like we want to use our technology to make that as likely as possible. But as we said providers have, you know, different levels of compliance and technical sophistication. So like there are some instances you can see in the demo environment here, we leave a bunch that are 30 days old.
Joshua Levitan (22:53) So they pop up in red. There are instances where we’ve asked the provider to do something if it’s 30 days old in medallion, that means medallion has at a minimum emailed them 10 times. And in addition, probably called or texted them a number of times as well depending on if you’re using those services. So there might be, you know, a case for you or for someone in like a regional office, whatever your structure is, someone on your team to like take this the next step further and like help reinforce the message that this needs to be done. But you’re only getting involved to take that manual action after medallion has made as much effort as is, you know, as is sort of like possible to get the provider to do whatever it is that they need to do.
Tiffany Jolley (23:40) So, do we have, do we have the ability to set up the frequency of what their, when… notifications go out? Because then I want like hca, right? That portal that our providers get inundated with that and it gets… you know, annoying to them. And then it just becomes then they just start ignoring it. So, is this something where we would identify the items that we want them reminded for? And then the frequency that they get reminded?
Joshua Levitan (24:09) Yes, absolutely. We think about that concept a lot. And so we have tried to fine tune this with, you know, all of our 400 plus customers and 100 plus 1,100 1,000 plus providers to think about that exact question, like what is the right level of squeaky wheel? You can take that one step further if you don’t agree with like our default preferences.
Tiffany Jolley (24:31) But we’re.
Joshua Levitan (24:32) constantly trying to think about that balance itself. And if it needs to be adjusted, we can actually work with you on that on either the timeline or in some cases, the actual messaging itself. Yeah.
Tiffany Jolley (24:44) Because I mean, these are clinicians, you know, they’re our customers. So when they get annoyed with it, right? And then, you know, it’s going to be hard to get them to adjust to something new and we want to make that as pleasant as possible for them, yeah.
Joshua Levitan (24:58) Okay. Thanks. Okay. So continuing with your view of the world here, right? You can see all the tasks that are assigned to providers. There are also sometimes tasks assigned to administrators. The best example of this would be like if you need us to update the Coi at a group level, you can also track all expirables in one place. Now, we’ll talk a little bit about like specifically license expiration in a sec, which is related to this but a little bit different. This includes even more broadly like the passport picture that they uploaded is expiring… or, you know, oftentimes like board certs, so anything that can expire and does expire is tracked in here. It’s sorted. You can filter this really easily. So you have that sort of view into the world at a high level like right off the bat in your sort of like home screen hub here as well. But the bulk of the data like the calls to action live in tasks, the bulk of the data lives within the provider’s profile themselves. So I switched to my provider’s screen here. We can see all of the providers. Again. We can sort and filter. We can change these views a little bit to show us the most helpful information. We also get a quick sense of where their data is at, right? So we want green check marks. That means we have all their data and they’re good to go. If we see red or yellow, that means that, you know, there’s still information that’s missing that they might need. But let’s click into Naomi here. This is the same provider who I was showing you from her side of the screen. And what you’ll notice is like when I click into her profile, you see the exact same thing that she did. And you can also edit data and change data on her behalf, or edit and change documents. Again. Like this is the least efficient option, but it’s nice to know. I would imagine for you that as a fallback if your provider is not, you know, filling out or like updating the information or like you could even link caqh for them directly in here. So you have the same levels of control that we do. Now, obviously that might not be your whole team, we might restrict access to this to certain members of your team and from an audit and compliance standpoint, like we are tracking every change that made and that was made and the user that made it. So we know, like did a provider update their address or did you? But right off the bat, you have this full ability with the exception of answering disclosure questions and agreements to edit the profile as needed.
Tiffany Jolley (27:29) And then we start to real quick. Every time that we do let’s say, fill data in for the clinicians because that’s what they’re going to want us to do on a lot of them. Do they have to attest to each change?
Joshua Levitan (27:45) Yes, but we’re not going to send them attestation notifications after each change. Like we’re going to wait until like everything is like in a green status and then ask them to attest, okay, like if you change one field, we don’t want that to trigger a new attestation, right?
Joshua Levitan (28:01) Right? But if you do a bunch of work… I should also mention like with the portal that we just looked at, we see an average. And again, like I’m trying to be realistic here, an average means that more than 50 percent or less. But we see an average of two days for a provider to complete their profile and attest in terms of getting data into the system, right? There are outliers, right? There are older school providers like we’re not going to sugarcoat this, who are less technologically advanced, who are going to email you things and want you to come in here and do it on their behalf. And those are outliers. But on average, if we look at a really large sample size of 100,000 plus providers that use medallion every year, it takes about two days from when they get the invite email and login to when their profile is complete and attested to.
Joshua Levitan (28:51) Okay, but… expanding on this, you have like a lot more information in here now that can help you do very specific things on their behalf. And you can see all of this in one pane of glass. So you have their profile. But then we can begin to look at verifications. So medallions and ncqa certified cvo, we are going to verify primary sources. We are going to stick those in packets and help support committee workflows in line with your current structure on how you do that and what needs to happen there. And apologies, this is a demo environment here. So this is a fake person. And we’re actually trying to the technology is actually trying to verify her license that does not exist because we made up her name, but you will see in here in verifications, all of the primary source verifications that meet ncqa standards in addition to some, that sort of bridge the gap more into the hospital world like peer references. In one place. We are going to first run these primary source verifications using technology and automation for ncqa purposes. If we need to be to ncqa standards for you and your organization, then we will have a human review all of these that is still dictated by mcqa that a human reviews all verifications. But from an ongoing monitoring perspective, and just to get a baseline on this provider, it takes seconds for most of these automations to come back and… be verified by our tool. Is.
Tiffany Jolley (30:35) that automatic with… the system or is that where we would purchase the software and then we would have the verification like a different module that y’all part of the package? Is it all inclusive or can we like choose if we want y’all to do the verifications or not? Yeah.
Joshua Levitan (30:55) It’s not a buffet. It’s a la carte because there are some organizations that only do payer enrollment and don’t really care.
Tiffany Jolley (31:01) about credentialing.
Joshua Levitan (31:03) There are some like yourself who need, you know, the hospital applications who need credentialing, who need PE, so we can get into all that stuff later. It’s a little bit more next to me. But yeah, it’s all a la carte. But I think what’s important is while the pricing is all a la carte because you get value out of these different services in different ways. It’s from a data and usage perspective and how you use the tool, like your payer enrollment, your hospital privileging, your licensing and your credentialing are all in one single location. Okay? So you’re not like flipping back between, you know, like some part of a tool or system that runs the CDO to some part of a tool or system that runs payer enrollment to some part of a tool or system that manages hospital privileging. Okay. So we have our verifications, we have licenses, we can get new state licenses that’s one of the services we offer is actually automating that process.
Joshua Levitan (31:59) You would see those in requests. And then you’ll also see existing licenses, right? We’re going to verify these as well. So, are they active when’s the expiration date? Is it part of a compact? Have we verified this on your behalf? So you have that piece in here. We’re going to notify 90 days before license expiration. If you’re using our service for license renewal, we’ll just go ahead and actually automatically renew the license. If you’re putting that onus on the provider or you’re doing it yourself, then we’ll just notify you, hey the license is expiring and 90 days you need to take action?
Joshua Levitan (32:37) In here, we also tie providers to practice locations.
Joshua Levitan (32:42) And then we get into the pay enrollment piece of this so we can come in for the provider. We can see the payers that they’re currently enrolled with. And we can as well see enrollment requests. Now, we’ll talk about this in a little bit more detail in one sec here, but this is where medallion is automatically going to like let’s say blue cross blue shield, Arizona’s evalid portal, using the information that’s in your profile that’s in the provider’s profile and submitting that application to evalid. Again, we’ll put a pin on that and come back to that in one sec. But we can view all of that here as well as make requests in here. Same thing. I don’t know if Naomi has any privileging requests. Oh, yeah, she does in the privileging request portal, as well as where we would request that Naomi get enrolled with a specific hospital and then use our technology to populate and then sort of move the process of filling out that hospital’s intake process for privileges and appointments from there. And I.
Nick Scallion (33:50) think Jocelyn, you’d made a comment that this was a little bit harder to navigate with your current setup. So again, this is kind of more of the micro level view that you can have into individual providers. But this same information if you want to see who is privileged at all of the northeast region, southwest, location, teams, or locations, right? So micro visibility as well as macro like idea being here, just kind of showcasing how readily available this data is for you folks.
Tiffany Jolley (34:18) So I do have a question on the privileging part. So since we’re in, you know, we’re in six or seven different hospitals nationally and obviously each one has their own applications. They use a different software.
Joshua Levitan (34:29) Most.
Tiffany Jolley (34:30) are online and stuff. Does this interact with the online portals? Yeah, absolutely. I mean, how, I mean that’s is it just a couple y’all, have access to or is it a good chunk of them just trying to see how?
Joshua Levitan (34:45) So I’m going to answer your question in two parts. Okay. On the privileging piece… yes, we will interact with the way that the hospital does this. If we love it. It’s a portal because that’s easy for us to automate against. On the hospital side, there is more setup in implementation that’s required where we basically say what are your lists of the hospitals? And then we go and research or if you already have it documented like their process. It’s a paper app. It’s a portal. This is what’s needed. But then we build automation that runs that. So, you know, it takes us two or three days to build all of that out. The payer side. We’re doing the same thing. I’m actually going to switch to my payer module here. We’re doing the same thing, right? Where we’re taking the information but using technology to get that information out the door as quick as possible and as accurately as possible. But for payers, there’s a much more finite number of payers in the country than there are hospitals. So we actually pre log all of the payers’ processes for 1,100 different payers in the country. So if you want to get a provider enrolled in a new payer, you’re going to come up here. And this is the same screen that you saw in Naomi’s profile. You can see Naomi right here. But this is for everyone, all of the providers including like facilities or groups. You’re going to go ahead and make a request. In this case, just for an example, we’ll do a provider enrollment request, but again, you have the group and facility option there too. We’ll say we want to enroll Naomi. We know the groups of the tins that she’s part of. We know the states that she’s licensed in. And then we’ll select payers. Now, we actually know every group contract that community health center has. So we can select all here. We’re going to select lines of business… for each of these different payers… we’re going to then move on to practice locations. I’m just going to select all for this for purposes of the demo. We want this to show up in the payers public facing directory. We want to request such and such effective date, any notes. And then we hit submit. And so keep in mind, right? That the legwork that’s done before this is medallion has mapped the payer enrollment process for every combination and permutation of provider type, state and payer for over 1,100 payers in the country. And when you hit submit what medallion does is trigger a process on the back end where it takes all of Naomi’s information, gets that into a portal or a paper like or maps it onto a PDF that needs to be mailed or a roster, whatever it is. And then just executes that process on your behalf. I can quickly show you here. What that looks like. This is a recording of our tool doing this for blue cross blue shield of Arizona.
Joshua Levitan (37:48) Let’s see if my demo platform wants to load the video. Here we go. So this is literally like a screen recording of that bot, right? Logging in to blue cross blue shield. So taking a while to load, I’m sorry, I don’t know. I must be freaking out here, but you can literally see the bot just work through this process as a human would. But this is not a person, right? This is automation that is freeing up the manual data entry that your team used to do as we showed in the last step, right? We’re not presuming necessarily like we’re not going to do this automatically on your behalf in the sense that like you still need to direct medallion to say, this provider needs to be enrolled with these payers and tell us the specific payers, but then we handle the time repetitive manual data entry that happens after this.
Ivonne Oladunni (38:42) So, josh, quick question. Going back to the hospital side. So if we have hospital a that uses MDF, and then we bring on additional hospitals after the fact since you already mapped MDF, would you have to do it again? Like is it specific to that hospital?
Joshua Levitan (38:59) It is specific to the hospital. Yep. So basically, the way that would work, like there’s a team of three people that support our customers, long term. They help with various things. We can get into this like later in terms of those three people and their roles. But one of them is like your guru on like all things like industry and technical. So you would basically just email that person and say, hey, we just signed a contract with a new hospital, can medallion map their process. And the outcome of the mapping is exactly like what I showed you with azblue. Obviously, it’s the hospital’s portal. And that’s why I answered Tiffany’s question originally here with two answers, right? Cause it is a little bit easier in the payers cause we know that there’s a finite number of payers with hospitals a lot more, right? So, imagine like I would say, assume one business week. So five business days lag between the time that you tell us. Hey, we’re working with a brand new hospital that we haven’t told you about to, when you can actually go and submit applications against it. But what I also want to note there is we own that process. We’re not asking your team to go ahead and like build workflows or use some sort of something, right? Like we own that work and that responsibility of doing the mapping and then training our automation to execute that mapping.
Tiffany Jolley (40:20) And if I obviously have other customers and clients, so if they also already set up for a specific hospital, and since we’re the anesthesia group for that, y’all, would already pretty much have it mapped with maybe just a couple tweaks for anesthesia, right? Yeah.
Joshua Levitan (40:35) I was going to say there’s probably some provider type based tweaks there.
Tiffany Jolley (40:38) Yeah. Okay. But y’all, wouldn’t have to start from scratch, correct? We would not have to start from scratch. Yeah. Okay. All right. We also.
Joshua Levitan (40:48) Have the flexibility there too, like if you’re I mean, you guys are huge, right? So you carry a lot of weight, like if there’s a process that is specific to you, that a smaller organization that is staffing in a hospital might not have, but you have worked out with the mso team, there something some process that helps you move quicker or submit information in a different way. Like we can accommodate that as well, right? So, this is really bespoke to, especially for, you know, organizations like with your size and prowess that if you have these relationships like we can accommodate that as well. Like we’re going to treat you and your instance as something that we build against that might be different than, you know, a much smaller group that’s like not operating in the same way because they don’t have as much relationship or sway with an mso team at a big hospital.
Tiffany Jolley (41:38) Yeah. We’ll definitely have that on the payr site because some of them just let us, we don’t do the full application. It’s just a.
Joshua Levitan (41:43) Roster a roster. Yep. Exactly everything I said there about the hospitals, right? That relates to the payr piece as well. And again, we already probably have the normal process we do for 1,100 payrs, have the normal process for that payr mapped out there. What we would do is during implementation, when we’re setting all of this up, we would say, okay, do you have processes like that for a specific payr with a roster that deviate from the normal process? And then there’d be like a training like the automation would be trained specific to you for that process. Now with both the hospital apps and the payr piece, what I also want to mention then is you have a ton of visibility here once we’ve actually submitted this. So first and foremost, we’re committing to service level agreements to contractual hard guarantees on the amount of time it takes us to do things in medallion’s control. And you can see that right here. So, you know, that we are hitting our benchmarks that we’ve agreed to contractually with. Then on top of that, from more of like the operations standpoint, you can see for any of these enrollments, like where are we at in the process, right? So I affectionately call this the domino’s pizza tracker of where is this at a high level? But then we can get more detailed. So you can see like, are there dependents now? I’m talking more on the parent enrollment side here with these dependencies, right? But like does someone need to be enrolled with medicare, sorry, with medicaid before they can enroll with an mco. Those would be considered dependent enrollments that you could view right here. You can view the tasks that medallion is taking. We’re managing follow up for you, right? So we’re gonna call and email the… payers or scan their portals and like scrape their portals for information about the enrollments that we’ve submitted. And then we’re gonna take next best action on that. And that might look different from pair to pair. We know that we might know like with Aetna in a specific state, we get really good results if we reach out to Aetna five times in the first 10 days of submitting the application, but we might know with blue cross blue shield in that state, like they don’t even have record of it until day seven.
Joshua Levitan (43:54) So we’re gonna make the first contact, reach out to day seven. So we have this follow up protocol that we’ve like fine tuned and tested and it executes on your behalf. But you can click into this in detail and see what medallion is doing.
Tiffany Jolley (44:08) So, what kind of, so when y’all reach out to payr’s, follow up? What are y’all reaching out to find out if they’ve received the application, if they’re enrolled yet? What’s what is the purpose of? Yeah?
Joshua Levitan (44:20) So, I mean, the first step is to make sure that they received it. The second piece is to say like did they notice any errors early on? And like that we need to adjust. And then we’re basically just going to follow up on the status, hey, where’s this at, where’s this at, where’s this at? Okay. And so you can see in my example right here, like there’s a screenshot. This was probably this was done by a portal scraper from an email. So we got an email back here saying that the application submitted was confirmed. And so we’re going to post that as like evidence here for you. We’re using email to follow up. We’re also increasingly using AI phone calling bots. They’re scary good. They don’t sound like AI and it allows us to make thousands of calls a day and follow up super rigorously.
Joshua Levitan (45:10) So, we’re using that a lot with payers. And then again, there’s this portal scraping element where we can like log into the portal, a bot can and just like grab the information on the website to see like, is there something flagged? Is there, was it accepted? What status is it in? And then the perhaps most important part of this is whenever there’s confirmation of enrollment, let’s say that’s like a welcome packet. We’re going to post that right here for you in this note section. So that if for some reason, you got a denial down the road like for provider not network, but, you know, that they were enrolled like you have the packet, the information right here to go and adjudicate that claim as appropriate. We’re actually going to show you as well in here. Like literally the emails, there’s no examples in this one. But literally the emails we are sending to and receiving from the payer? Yeah, also do the follow.
Tiffany Jolley (46:02) up emails to the hospital credentialing as well. Or is it just on the payer side? Yeah.
Joshua Levitan (46:08) Great question. So, we absolutely can, I think we take a little bit more of a bespoke approach there and it depends on the relationship that like we don’t want to, we don’t want you to give up your relationship with that mso entirely like there’s other reasons why your team still needs to be tightly aligned with them, right? And so we can, right? Like we have all these tools built out, we have all the automation and if you want us to like, absolutely, we will go and do all of that follow up for you. But that is a conversation we want to have and be strategic about on the hospital side again different than the payer side because like if there already is some sort of workflow where you’re working with your mso contacts and some sort of cadence to review certain things we don’t want to like interrupt that and start sending mso a bunch of emails, correct? When?
Tiffany Jolley (46:58) You meet with them. Yeah, that would annoy them. But it would be nice if we could find some we’re in the workflow to where applications complete after a certain timeframe, maybe that’s a follow up email goes just, you know, is your file complete? I don’t know we have to talk about that as a team, but just curious, yeah.
Joshua Levitan (47:16) It’s a great point that’s one of the type of things that we’re definitely going to like that, you know, if we’re lucky enough to run your business, we would really get into during the implementation process with your engagement manager and come up with the right approach there. I think you’re hearing me give all these answers for both the payer side and the hospital side. And it’s like the themes are what I think is helpful to take away is that the themes are basically the same and the technology is basically the same. We’re submitting information to someone. And then we’re basically annoying them to give us an answer. Where the nuance is that like payers are big beasts and we can treat them in a way that requires, you know, a little bit of a different approach versus like, you know, your hospitals are your customers. And so everything we do on the hospital side is a little bit more bespoke and a lot more thought out from a strategy standpoint just because of the nature of the relationship that you have and how important that is with the hospital partners.
Tiffany Jolley (48:14) But from a.
Joshua Levitan (48:15) tech perspective, right? Like it’s all the same, okay. And,
Ivonne Oladunni (48:21) josh, on this page here, this is considered the coordinator’s workflow, like what they’ll come into the system used to kind of guide their day to day. Yeah. Okay.
Joshua Levitan (48:34) Yep. It’s this like it’s coming in and making these requests. I would argue part of their workflow is also probably using this tasks piece to like figure out what is tardy and what they need to follow up on, right? And in the home screen as well. There’s I’ll just quickly pop into this like we actually try… and like make this a little bit more like workflow action oriented. But yes, yes.
Joshua Levitan (49:05) Just doing a quick time check here. We have about 10 minutes left. We’ve gone through a lot of the information on the pay enrollment side. And on the hospital side, we haven’t talked a ton about credentialing like… sort of just the basic psvs and any sort of ncqa piece. Do we want to touch on that or are there more questions or other areas we want to dig into in what we’ve already seen?
Tiffany Jolley (49:29) I think the psvs that’s pretty self explanatory, if y’all are performing them on y’all’s end, they’re there for us fantastic, I think understanding.
Tiffany Jolley (49:45) Probably just, yeah. Like Ivonne was saying, like the workflows that employees would use, how do those get set up? I mean, do we customize it when we customize it? Does it break the reporting dashboards that y’all have canned in the system already?
Joshua Levitan (50:02) Yeah. Let’s address that piece. So there’s no element of your team customizing a workflow, right? Like with the payor side, the workflows are already in there if they need to be adjusted because you do a roster and everyone else is a portal. We do that. On the hospital side, the workflows are all built by us. Our specialty as a healthcare software company, right? Is building those workflows. We want to own that because we don’t want it to like it’s just, it’s not something that is needed from you like you are the source of information and truth and action, but we can build the workflows in a way that is like really maintained so that they don’t break and to your point, like, so they don’t break reporting or something like that. So if there’s and we sort of gave this example before, right? Like if you add a new hospital, technically, there’s a new workflow, right? Which is the process of filling out that hospital application that’s an email to us or brought up with us in our weekly meeting with you. And then we own it and then we just show it to you and teach you how to use it. And it looks the same. It’s just request payrollment or like in privileging, like just request a new appointment, right? This looks the same as what we saw before… in analytics and reporting. There are a couple different options here on how you want to view this information. And some of them are just pre built by us. Some you do have control over, but there’s never anything that’s going to like break, right? So what’s built for you is these dashboards you can tell us like what you want to see in these, and we’ll change these a little bit to meet your needs. Specifically. I just have some examples in here… but these are like, you know, enrollments completed time intake. We could go into the credentialing one. We could go into the privileging one and see this type of information for all of them with visuals with like these widgets, right? And we have flexibility in what you want here. Your team then has the ability to make custom reports on the fly without us for any specific piece of information that you might need at any given time. So you can come in here and hit like provider, just kind of put in a bunch of random fields, right? But we could, you know, think about an example that would make sense for you here. I’m gonna put in the provider, we’re gonna put in their profile completion status, we’re gonna put in their start date… we can put in their licenses… their board certs, their, work history is gonna make this report look weird and long. But you get the sense we click off things here. We hit this little arrow. They show up in the report and the report exists below. We can sort and filter this as well. And then we could save this and have it emailed to anyone on your team. So like you guys were explaining, you kind of like break up half the country, right? So like we could sort this based on specific states and for each of you or people on your team and then have it just sent to them automatically. And there are different types in here, right? So we have the payment enrollments, the credentialing, the providers, my demo environment doesn’t have one, but there’d be another one here for like the hospital privileging as well where you could see like all the statuses… and this is what you need. Like what you can use for self service data action. Like someone asks you a question in the business and you need to pull something or you have someone that like doesn’t want to log into medallion and go to a dashboard. They prefer to get a report via email that’s where the report builder is used to fill that gap. But again, no matter what you’re doing anywhere else in the tool, like there’s nothing that there’s no gotchas. There’s no, like we changed the data field and it breaks anything like we have strict guardrails in place to make sure that you’re… focusing on moving this process along and getting business outcomes. And we’re focusing on managing fields and workflows, and bots, and AI, phone calls, and that type of stuff.
Jocelyn Kopchak (54:05) So, I think where Tiffany is coming from is not necessarily, you know, we change a field and y’all, don’t allow it to break like if we customized the medallion to match our business needs… that might entail you know, renaming or moving or adding things, you know, in a different manner than we’re seeing them right now? One, is that a possibility? And two, if we do make changes like that, you know, if we are capable to make a change like that, are these dashboards still accessible… to where we can add those changes into a dashboard like this?
Joshua Levitan (54:53) Yes, and yes. So the dashboarding piece, yes, very simple to do again, we would do that for you. And then it would just be posted here. The first part of the question is sort of like changing fields. We’d want to really dive into like what the specific use cases are. Quite frankly, this does not come up a lot because… the like we’ve sort of built everything in here. So while other tools that have been on the market like require you to do a lot of like coming up with your own data schemas, we’ve taken the approach of like learning this industry and the pain points like inside and out and covering it all. That does mean that for some customers like they actually might not use half the fields in medallion, but those fields are there and exist for the customers like you that might need them. If there is something that you need that is not already built into here. Yes, we can absolutely work with you on that and figure out the best way to approach that and partner on making sure that capability is there. But it’s going to be done in a controlled way. Yeah. Right. So that there’s no, because like, you know, there are other tools, right? Like this is somewhat of a basic example. But like let’s say you needed to add a date field for something. And three years ago, one person added start date, right? And then two years later someone adds a different field that’s begin date and they mean the same thing, right?
Tiffany Jolley (56:18) No, we agree with that, Rosanne. Yeah.
Joshua Levitan (56:21) Yeah, no.
Tiffany Jolley (56:22) We understand the duplication and.
Joshua Levitan (56:25) It just.
Tiffany Jolley (56:26) Trash in trash out one of.
Tiffany Jolley (56:35) the things just off the hand I’m thinking with facilities, hospital credentials. You want to see everyone credentialed at. We have to be able to identify ones that are credentialed at a usap facility versus just their active privileges where they’re working somewhere else for another group. It’s those nuances that usually dirty up the system.
Joshua Levitan (56:55) I think we’re all saying the same thing. I think in some ways we give you less control than other platforms or I should say we insert ourselves into the control that you have. But we do that because of your point about good data in and good data out… changes that need to be made often involve our team. You’re not going to make them. And I’m talking about in the data schemas, not in the report builder. They involve our team, but they involve our team because we know that a lot of these tools on the market where you do things self service. You have this data sprawl issue and it ends up causing more harm than good even though in the moment, it feels like I can just add this field. It took me three seconds. Great. But then six months a year, five years later, the data is slop that can’t really be used.
Tiffany Jolley (57:52) Correct. I.
Joshua Levitan (57:53) Almost hesitate to say we give you less control, but I do think that’s an accurate statement. But we give you less control because we want to be methodical partners for the long term and not just say yes to everything in the moment without thinking about the implications from a workflow industry company or data perspective. You know, the implications three months from now and five years from now, right? Is that fair? Do you understand no?
Tiffany Jolley (58:25) We understand exactly. And I actually kind of like that because right now, you know, me, Jasmine and Ivonne, we are the controllers of data. So we do need to create a field and we have a new item. We have to track, we get together and we have to try to vet out every possible scenario if we repurpose a field or whatever how it’s going to impact? And is there automation behind that field that’s going to mess something up? And we have to do that. And that’s not our jobs. You know, it’s become our jobs over the past, you know, seven years, five years, and that’s just not what we do but we’ve been doing it the best we can. So I do welcome that. I just need to make sure that like the system when we get into the nuts and bolts of it that it’s able to track our data the way we need it tracked and reported on.
Joshua Levitan (59:17) Yeah, no, absolutely. Hear you on your concerns. I both on medallion and just broader with how your last five years have played out and look like this is the first time that some of us are meeting, right? Like this is a conversation, right? So playing these out, right? Like this is what we do, right? Like we bring in people from our data team that can talk to how this works when your it team has questions like you and I can work together on getting super specific and detailed. We want to be consultative and helpful in this process and not just like show you a tool and be like, here we go, right? So there’s a lot of this that we can continue to dig into if you have like very specific questions that we need to vet out now, two weeks from now, four weeks from now, whenever it might be.
Ivonne Oladunni (60:07) Josh, can you hover over to the provider onboarding real quick? I know we’re probably at time, but I’m curious on how the dashboard already? Yeah.
Joshua Levitan (60:15) I’m actually not sure. I have this one provisioned in my demo account. Let’s see.
Tiffany Jolley (60:20) I also have a question for you, Ivonne before we, I just wanted to put that out there before we end.
Joshua Levitan (60:24) I just added this into my demo account and it’s kind of like half built.
Ivonne Oladunni (60:28) Okay. But if.
Joshua Levitan (60:30) you are thinking of something here that we want to talk about, what it would look like. I… can come up with a more bespoke example. Is there like something you were looking to see specifically in the provider onboarding reporting?
Ivonne Oladunni (60:47) Oh, well, turnaround time, so that’s great. Yeah. But yeah, we have other items and such, but we can get to the granular.
Joshua Levitan (60:54) Yeah. And I think the other interesting thing is like if you have dashboards that you rely on every day in an hour now, like if you screenshot those and send them to me like that’s a really valuable exercise just for like me to record but also for me to either like mock up or share with like the implementation and the teams that actually like do this. All right?
Joshua Levitan (61:26) There are about 700 different reports that can be placed in any number of these dashboards. And certain customers have way more dashboards off to the left here. Those are 700 that we’ve already built, right? So we sort of choose from those when we go and set this up for you or build specific ones for you if it’s not covered in those 700. And when I say report, I mean, like this is one report like widgets or like things, right? So we stack these together in a way, that makes the most sense or we just build one specific for you. I mean, building this report takes like four minutes for someone on our team.
Joshua Levitan (62:10) I know there was one other question. I also want to be conscious of time here.
Erin.Sanchez (62:14) Yeah. I have one question about enrollment. We have different… processes. So like for some payers, they want us to submit providers like on a roster and some payers, want us to submit stuff, you know, providers, one by one, you know, online through a web app… and I know that you had like you’re showing us their follow ups that your team is doing and there’s you know, proof of the follow ups and so specifically about our insurances. Like I’m just going to give an example. So, for like our Texas group with Aetna, they want the submissions done via a roster once a month and they’re really specific about it.
Joshua Levitan (63:01) So,
Erin.Sanchez (63:01) those follow ups, they really would be upset if.
Tiffany Jolley (63:06) there were multiple.
Erin.Sanchez (63:08) Follow ups done for each individual provider. Could you specify to do one follow up once a month on all of the providers that were submitted that month? Absolutely. Okay. So, okay, I just want to that’s like a customizable thing that can be done, yep, for each insurance for each group or state or whatever. Yep. Yeah.
Joshua Levitan (63:30) I think even broader than that, like anything that deviates from what our norm is we can do, and then we track for you, right? So like we call it a project plan, it’s just the name for it internally. But like that’s something that we would in implementation. Like we will go through all of your payers and like for one payer, it might just be, hey, they have an availability portal, but we submit via roster for the next payer, like in your example, it might be, we submit via roster and we need a specific follow up cadence, right? That we’ve pre determined with them. And that information is then like logged in our system and the automation is trained off of it.
Erin.Sanchez (64:05) Okay. Or?
Joshua Levitan (64:07) Like we also, we’ve talked a lot about automation on this call. Like I also don’t want to, I don’t want to not mention that like in, there are humans involved in this process when needed as backstop as quality control, and like that sort of oversight to the automation. So like we have a team of honestly like people with resumes like you, right? That used to do what you did, but now work for medallion doing the same thing that are in the loop for like this is healthcare. We can’t automate everything. And like there’s a lot of edge cases and there’s a lot of compliance concerns. So, like there would be someone that would be like specifically responsible for that, and making sure like with your account that like, the, with, your project plan, exactly what the parameters are. It’s very well documented and it either executes via automation with those parameters or one of our team members just handles that because it’s like a, very, hyper specific sensitive situation.
Tiffany Jolley (65:13) Okay. I have one last question that’s it. So we deal with bots in our own company, not in our area for the most part, but how dependable are your bots? Because you.
Erin.Sanchez (65:26) know, when our.
Tiffany Jolley (65:27) bots go down claim billing, it comes to a screeching halt and it’s a big.
Joshua Levitan (65:31) deal.
Tiffany Jolley (65:33) So, how, I mean, how frequently just we just want to have like the right expectation because, you, know, we know bots are going to have their quirks and things like that from time to time, but how frequently does that happen that we can kind of expect that?
Joshua Levitan (65:47) Yeah, phenomenal question. And really related to my last answer, right? Which is this is all backstopped by humans. So we’re contractually committing to a lot of this work in specific timelines like if our technology is being updated or tweaked or has issues, like we’re still responsible for that, and we’re just going to have our team jump in and then do it manually for like, you know, the couple hours that we’re tweaking something. So that’s the first piece, right? Like what you get is guaranteed outcomes written to a contract. We want to tell you how we do that and create all these efficiencies but like we are able to adjust how we do that in specific circumstances if needed. There’s also, you know, certain like medicates that have different protocols. Whatever the technical answer is from a building of technology perspective, there’s approaches to how to do this. One approach is like what you see on like social media which is like AI can do this. All you just say AI go and do this and it does everything that’s not how this works. That does not produce good outcomes when we build these bots and technologies and automations, what we will do is look at a process and break that process into every single step and sub process. So let’s say that’s like submitting an enrollment somewhere and that has 50 sub processes as part of it. And then we will build the automation or the bots or whatever. There’s a number of different types of automation that we use for each one of those 50 different sub steps. And then we will orchestrate them together. And why that’s really important from like a technical strategy standpoint, is there’s no single point of failure if any one of those and maybe like of those 50 steps, two actually can’t be automated based on technical limitations or whatever, right? So, maybe there’s 48 steps that are automated and two that tag a human in as some sort of escalation protocol. But if any one of those go down, it’s not like the whole system goes down. And that is the architecture approach that has enabled us to do this and do it with higher quality. You know, obviously there’s it’s not 100 percent perfect, but we get better results quite frankly than humans because humans can call out sick and can type the wrong button. So there are trade offs there, but that’s yeah, I’m getting long winded because I would love to talk about this for the next 30 minutes about like the architecture and the strategy behind it.
Joshua Levitan (68:17) But that’s the overall ethos to make sure that everything performs in the way you can rely on and gives you value. Okay? Yeah.
Jocelyn Kopchak (68:35) Great. I think so… next steps I’ll you know, go back and talk with Tiffany and Ivonne Erin, and I think Rosanne ended up joining and I’m not sure how much she listened in because she is on pto today, but I will… get back to josh and Nick on next steps and that’ll probably be like we talked about before with the it team. Yeah. So we can walk through the back end the questions that they might have, but we, I will be in touch after I group together with this group on our side. Yeah.
Nick Scallion (69:19) That’s that’s perfect. Jocelyn. Let’s do whatever makes the most sense from your perspective and probably won’t be perfect the first go round. But I can also start working with you on ballpark investment figures, and we can also start looking at those, you know, kind of contractual performance improvements. So we can kind of look at a first iteration of our return on investment analysis. So you all already stayed fill out an extra minute. So I’ll let you run and Jocelyn. Yeah, we’d just love to hear back from you sometime this week to connect the dots on next steps. But thank you everyone for starting your Mondays with josh and I and really excited to continue the conversations. Thanks everyone. Thank.
Jocelyn Kopchak (69:53) You. Bye bye.