Transcript
Jocelyn Kopchak (00:00) good morning, hey, Erin. Hey.
Nick Scallion (00:03) Jocelyn. How are you all doing? Hello?
Jocelyn Kopchak (00:04) Good. How are you?
Nick Scallion (00:06) I’m good. How was your trip? Didn’t you say you were out of the country?
Jocelyn Kopchak (00:10) Yeah, I was, it was great. It was probably top three of our trips. We’ve done a lot of traveling and… I.
Erin.Sanchez (00:19) feel like that’s an understatement Jocelyn. We’ve done a lot of traveling.
Jocelyn Kopchak (00:24) Where?
Nick Scallion (00:24) Was this to?
Jocelyn Kopchak (00:26) So, this one, we did like two days in Ecuador and then flew out to the galapagos islands, and then we were there for seven days and then we did 11 days in Peru. So we did machu picchu and all that fun stuff epic.
Nick Scallion (00:47) Well, that’s awesome. Just a small trip. Yeah, just a small trip that’s like a combination of way cooler trips than I’ve ever been on. It’s. Amazing. Okay. Stop. Let me just message my colleague josh. I’m sure you’ve been underwater, when did you get back? When did you get?
Jocelyn Kopchak (01:08) Back? I technically got back at the end of last week, but I check my emails and keep in touch every day that I’m gone just because if not, I’d come back to insanity. And then it’s like what’s the point of going away probably.
Nick Scallion (01:26) Better for the five or 10 minute check in than coming back and being underwater. Makes sense. Yeah.
Jocelyn Kopchak (01:32) Yeah. This was the first trip we’ve taken in a long time, that was in the same time zone as Texas. So it was a little weird. Usually, I’m used to waking up and everyone is going to sleep in the states and I can check my email. And then I don’t get any more and I’ve got to worry about it. But this one, we were in the same time zone. I didn’t fully realize that I feel.
Nick Scallion (01:54) like South America like a lot of the trips down there are getting a lot more popular. I feel like, you know, Europe got kind of like a lot of Europe travelers like the last decade or so and now I’m seeing a lot more people go down south and that’s cool.
Jocelyn Kopchak (02:06) Yeah.
Nick Scallion (02:08) Well, cool. I saw josh just joined. I think it’s been a while folks. I think like the last session, we did have that initial demonstration. I think we looked sort of at the platform itself and kind of both sides of the coin, how we’re helping accelerate the onboarding process with our caqh integration… and just kind of having like a modernized UI for both the providers on web and mobile, right? So just the idea of getting this documentation a little bit faster and then obviously being able to act on that. So we looked at the payer enrollment function, right? So how we can submit applications via different mechanisms and try to close the gap on getting responses from the payers, and we talked a little bit about also the inverse of the caqh integration, not just getting data to complete profiles but also how we can push updates to caqh and help with the attestation. So I think where we missed out on the last session, the purpose of today was to kind of look at okay, not just the payer side but also the credentialing, and then also getting privileges admitted to the facilities that you folks are conducting care in is also equally as important. And then we didn’t get really any look into the reporting and analytics that I think are also really important. So that’s what we were planning to share today. But you folks tell us if we need to dive back into anything payer enrollment related or anything else you’re hoping to see out of the demo or chat through today?
Jocelyn Kopchak (03:25) No, as far as I… know, I think that’s good. I think the plan unless Erin there’s anything you want to go back over, but I.
Erin.Sanchez (03:38) don’t know… cool.
Nick Scallion (03:41) Well, I think we should be able to cruise through that with the time that we have. So let’s start there.
Nick Scallion (03:46) And then if there’s anything that comes to top of mind, just feel free to interrupt josh and I and we can try to get it answered. I think it.
Joshua Levitan (03:54) Might be helpful to nothing that you wanted to sort of redo from last time. But I’d love to just we checked it a little bit at the end of last time, but just to structure the conversation today, sort of just get like your overall thoughts and impressions at the highest level about what you saw last time.
Joshua Levitan (04:10) I know it’s a status quo shift, right? So how are we feeling about if that is a worthwhile impact, if it makes sense? If it doesn’t.
Erin.Sanchez (04:22) yeah, I mean, sorry.
Jocelyn Kopchak (04:23) Go ahead. No, go ahead, no.
Erin.Sanchez (04:26) I mean, yeah, things last time, I really liked the way that the dashboard and everything worked… the way that y’all have everything streamlined. The way that the forms are updated automatically is pretty life changing for me personally… that’s a thing that I struggle with for my… team. Just the forms constantly updating is one thing that’s really hard for me to keep up with, but.
Joshua Levitan (04:57) Yeah. You mean the payr forms, like they’re.
Nick Scallion (04:58) just.
Joshua Levitan (04:59) changing all the time without them wanting to tell anyone or give anyone a?
Erin.Sanchez (05:05) Heads up. Yeah, they don’t notify you. And then, yeah. So that’s a really big pain point for me. Yeah.
Nick Scallion (05:14) All right.
Joshua Levitan (05:15) Jocelyn from your side, I.
Jocelyn Kopchak (05:17) would have to, I know I talked to Erin after we met and I know anything that can alleviate her pain points. We are on board with. So, yeah… having those updated and having like someone on the back end to be monitoring that and taking care of it and that’s it might sound small, but it’s definitely, a big thing on our side. Okay? Awesome.
Nick Scallion (05:46) Well, yeah. At your scale like frankly, like, you know, you folks have a pretty large group, right? So, so, yeah, small nuance with thousands of providers and onboarding tons, right? Like, that matters. So, yeah.
Jocelyn Kopchak (06:00) Good.
Nick Scallion (06:01) Call. Cool. Okay?
Joshua Levitan (06:03) We’ll get into it today. I think I’ll start with the hospital application process. If that works, we need to cover hospital applications, we’ll do the reporting and analytics at the end. And then we need to talk a little bit more about credentialing as well.
Nick Scallion (06:18) To.
Joshua Levitan (06:18) level set on the credentialing before I get into the hospital application piece? So, are… you, is there anything beyond? And forgive me if I already asked, is there anything beyond the ncqa standard verifications that you’re doing when you’re doing your own internal credentialing… peer reviews, case logs.
Jocelyn Kopchak (06:37) Yes. So, we do peer reviews and like fppe and oppe, that is maintained by our risk management department.
Joshua Levitan (06:50) Okay.
Jocelyn Kopchak (06:51) And then case logs, we do run for our clinicians and we run them out of Power BI, that’s tied to our billing system.
Joshua Levitan (07:02) Okay.
Jocelyn Kopchak (07:03) So, they’re updated on a daily basis so we can go in and pull them for a two year span. I’m trying to think if there’s any, oh, go ahead, the.
Joshua Levitan (07:12) Fppe, or fppe. Oppe. So I hear both terms. I like fppe. It sounds more.
Jocelyn Kopchak (07:17) Fun. Yeah, I haven’t heard that before that’s way more fun.
Joshua Levitan (07:19) Is that run out of the emr? Like where is the system of record for storing and tracking that?
Jocelyn Kopchak (07:27) That’s a really great question. I have no idea. I’m usually not involved in which sounds weird for a credentialing person to say they’re not involved in that, but anything or any time that our facilities need any type of quality data that comes directly from our risk management, they have their own platform that they utilize. All right?
Joshua Levitan (07:49) Honestly, I think that’s actually for the better here, we get a lot of requests to incorporate that into credentialing. But while it’s possible, I actually think it’s sometimes better suited to be in systems that are much more used to dealing with quality data and compliance than hipaa specifically like safe harbor act. We’re trying to minimize the amount of hipaa data we have in our system. It’s in everyone’s best interest to do that. So I digress, but I actually think that’s a beneficial scenario to be in and I think it allows you as well as us to focus on bread and butter type stuff. Yeah.
Jocelyn Kopchak (08:25) Okay.
Joshua Levitan (08:26) So we’ll talk about hospital applications first or should we dive into the credentialing piece first? Maybe I’ll turn that around as a question. What do you think is more valuable? Or maybe I’ll re, ask that, which do you tend to have more issues with in your current state?
Jocelyn Kopchak (08:43) Probably the credentialing piece, the hospital apps… they’re both kind of a pain just depends on the hospital, right? But let’s go with the credentialing piece first. Okay. They got mine.
Joshua Levitan (09:08) Demonstration set up here. And also, I apologize if I’m a little quick on the trigger today, I’m in the kitchen instead of in my office because my puppy was just neutered and so I’m keeping an eye on him in the crate, he has figured out how to get around his cone. Oh yeah.
Jocelyn Kopchak (09:23) And.
Joshua Levitan (09:23) lick, and I have to bring him to the vet later today to make sure that we are all good. So he’s over there in the corner. I’m just on my laptop. I’m really missing my nice 36 inch ultra wide monitor and my special ergonomic mouse. But you got to do what you got to do for the little ones. Yeah.
Nick Scallion (09:44) But Brucie runs the levitan house. We know.
Jocelyn Kopchak (09:47) This, we know.
Joshua Levitan (09:48) This, Nick knows, yeah, he, I digress, he chewed through the plastic cone that they gave us. Yeah.
Jocelyn Kopchak (09:56) I have one of those.
Joshua Levitan (09:57) Yep, like the hard plastic. And so we got a soft one but he’s now figured out if he jams his head against something, the soft one like bends back and then he can still lick. So I.
Nick Scallion (10:10) we could get off this topic. But the last comment is if you have to go through this again, they do make these onesies for the dogs. And so the cone was an issue for us. And so we did the onesie which looks ridiculous, but the onesie was actually really effective for that and better for them, you know?
Joshua Levitan (10:24) What I think the issue is Nick, they did not give us any trazodone or cabernet sauvignon. Oh no.
Jocelyn Kopchak (10:31) They.
Joshua Levitan (10:31) said they handed us back to them and they said we did the easy part. Now, you have the hard part, no running or jumping. I said, excuse me, mr and mrs vet. He is an American working bread hunting dog who lives in the city and.
Jocelyn Kopchak (10:46) is.
Joshua Levitan (10:47) only well behaved if we start our day with 45 minutes of fetch and a walk and they’re like, well, you can walk and I’m like great walking doesn’t do it the way that the fetch does, no.
Jocelyn Kopchak (10:58) And then we.
Joshua Levitan (10:59) were talking to our friends who went to a vet right down the street and they’re like, yeah, we got a 10 day supply of trazodone to make sure that he was just cool.
Joshua Levitan (11:06) And I’m like, okay, well, I could talk about this for two hours, but we have other things. All right. So, credentialing… the process is pretty simple. We want to do as much as we can for you. We’re an ncqa certified cvo. If there were requirements beyond the basic ncqa certifications, we are regularly working with organizations meeting tjc, aaahc, CMS, you name it, whatever the standard is. The goal here is for us to use automation as much as possible to pull primary sources. But to be compliant with ncqa, we then need humans to review it. I’m going to go ahead and say that my guess is right now you are probably having people on your side review psvs once you pull them either… before a committee or for a quality review, but let’s just double click into that. How’s that working currently?
Jocelyn Kopchak (12:02) Our credentialing specialists pull all primary source pull and review the primary source verifications for their assigned clinicians both at initial and reappointment. Okay. Not well, reappointment. It depends on the site but definitely at initial. Sorry. Okay. So.
Joshua Levitan (12:21) They pull the primary sources. They build the packet I’m presuming in some way shape or form, and then that gets delivered to somehow pass along to committee.
Jocelyn Kopchak (12:32) We don’t have any credentials committees here. So, any internal credentialing that’s completed is just, we follow a checklist and it gets audited by our auditing team once a month. You know, they do random polls to make sure we’re doing what we’re supposed to be doing, but there’s no committee approval. Once they’re approved at the hospital, they go through our process in tandem with the hospital process. Once all of that is completed, they’re covered by our medmal, then they’re able to start working okay?
Joshua Levitan (13:13) And because they’re going through the hospital process, we know there’s obviously a committee that’s rigorously checking on that side. Yes. Is that a factor? Like would you consider that not really a PSV but something on the checklist that you’re collecting like at least having one hospital application be included favorably?
Jocelyn Kopchak (13:33) Yes, we usually wait for the first privilege to grant, and then we’re like, okay, you’ve completed the usap credentialing checklist. You’ve clearly completed the hospital credentialing checklist. And then we continue to monitor for any privilege granted after that initial first privilege. But they’re technically able to work if they’ve cleared, you know, background check, drug screen, medmal, all that stuff. Okay.
Joshua Levitan (13:59) So some of what I’m about to show you here might in this demo environment actually be a little overkill, but that’s okay. It can be parsed down sort of in the real, there’s flexibility here in how this works, but I’ll walk through it just so we get a sense of like the full capability. And then we’ll talk about how that might be parsed down… super simple. When you want to credential someone. Again, you can see do the recred or the initial cred here. We’re going to use a new provider or sorry, an existing provider existing here means that they’re already in our system… new provider would mean like we literally just started, we haven’t even added them to medallion yet. So all we do is literally click their name and we can do multiple here. And then we hit submit request… that’s the work that your team does to initiate this process. You’ll then see that individual show up in the requests section and you can actually see the packet start to be built out. As this is happening. Again, this is right now, what’s in my demo environment is literally just like the standard ncqa primary sources. We’re again gonna use automation as much as possible to grab these primary sources, but then have a human on our side review them to be ncqa compliant.
Joshua Levitan (15:11) And our SLA here is that we will return a credentialing packet in three days, but we average less than 24 hours. So from the time you hit that blue request button, to the time that it moves from request to ready, SLA, three days average. I think it’s like 23 point two hours. Last time. I checked little bit of a delay there, right? Because there are some psvs that we can’t automate. So about five percent of those we have to grab manually and we need a human to review them all anyway as a quality control measure based on ncqa that’s why it can’t be instant but pretty darn quick. How long does that take you right now as a comparison point there in terms of either like hours worked or time from when you make the request to when it gets to the queue? So.
Jocelyn Kopchak (15:57) Because we have the privileging piece, if we had a clinician that came on that was already credentialed with usap but needed to go through facility credentialing. Depends on the facility, could take 30 days, could take 90 days. If we have someone that comes on new to usap but is already privileged at the facility, we can probably PSV… wise, you know, most of that you can do within 24 to 48 hours, okay? But we are then waiting typically for the background and the drug screen, which is three to five business days and that’s done through our HR team. Okay? So, I think.
Joshua Levitan (16:36) that’s the comparison point, right? Which is like let’s say they already were privileged somewhere else coming in just apples to apples. You said 24 to 48. We’re right in that, you know, average of 24 but guaranteed three days… ready is like a placeholder here. So you’ll see also by the way you can see all of our SLA tracking in the app really transparently, this is a demo environment.
Joshua Levitan (16:57) So we have things that miss the SLA because these are all fake people that just sit in my demo environment. But I think it’s really important for customers to know that like you’re constantly being able to check our performance against our contract. We’re not hiding that. It’s really easy for you to pull that information. Ready. Here is a bucket that’s sort of like a container for… you to then make any sort of changes additions, review that you need. So what you would likely do at this point is actually go into the credentialing packet and add attachments of whatever you needed that we could not pull directly. So something like the drug screen, we could talk about if there was a way to like ingest that information programmatically. But like basic, if we don’t ingest that programmatically from some sort of system, like you would upload something like the talk screen right here as like an additional form of the PSV hospital apps could work the same way. We’ve done this in a couple of different ways, the hospital privileges, right? Because we are, we would potentially be running those for you. So they are in our system, but we need to move them over here. I would expect like what you were talking about where there’s sort of that delay then for getting those, the hospital credentials like your ready bucket is actually probably going to be pretty lengthy because you’re going to be waiting like the psvs, the basic psvs are done. But now you’re waiting for those other things to happen and sort of get situated and ready. What I want to note is important here is you can see high level status. If there is anything that’s flagged, this will turn into like a yellow exclamation point. And then anyone who has the proper access and there are different.
Jocelyn Kopchak (18:35) Roles and.
Joshua Levitan (18:36) You know, we might not want everyone to see this but everyone who has the proper access can actually come in and view the entire packet. And if we go into things like here, you’re going to see everything you know, in detail, screenshots who… was reviewed by, you know, all of this great information. And you can also add in notes things that you might like. If your team is reviewing and see something that’s of concern. You can note that directly in here and everyone can see that. So it’s pretty transparent. Some people prefer to look at this information in PDF. If you have anyone like that, you hit download here, this downloads as like a traditional credentialing packet. You know, a bunch of 20 pages of PDF, but I think a lot of teams really enjoy being able to view this in this format with the note taking piece right here, as opposed to having to like manage a bunch of PDFS via email and print everything off or, you know, annotate a PDF with comments and then figure out how to get that back to their peers when evaluating this. And from there, there’s then a gate sort of between ready and committee. Now committee here, we can use as a loose term. You’re not running a formal committee right now, but you said there are some like quality reviews. Is there a medical director or anyone that has to sign off? No. Okay. So it’s just that.
Jocelyn Kopchak (19:54) The process?
Joshua Levitan (19:55) You were describing of like the quality like spot checks?
Jocelyn Kopchak (19:59) Yeah. And that’s done by a different department entirely and we don’t know who they select until they’ve done their reviews. Okay?
Joshua Levitan (20:09) So what we would do there if we’re… generating delegated rosters, like we need the custom, we medallion need the customer to like delegate some form of approval. That means that like you had eyes on this, Or we’re going to stick it on a roster and like that’s so, a lot of times that is a formal committee, but it doesn’t have to be. What we would actually do here is just add your team as the committee. And we’re still going to ask like it might seem like a repetitive step, but we just for like legal reasons need to make sure that you gave something a check before we put it on a roster. Yeah. So your team would basically just come in here, do your final check again like review everything as it is. Okay. Open the packet if you need. And then you can hit approve. You can set this up where there could be 100 people on the committee and it gets like passed through if just one of those 100 like it’s not an all or nothing with the committee piece.
Jocelyn Kopchak (21:01) Okay. Yeah, that sounds like something. We have a manager.
Joshua Levitan (21:07) When a file.
Jocelyn Kopchak (21:07) Gets to a certain point, it sends our system will send an email to the manager assigned to say, hey, you know, can you do a quick manager review to make sure we’ve completed X y and Z? So this is,
Joshua Levitan (21:19) that’s that, yep. Yeah, perfect. And then from there, you can also see like timestamps and date stamps on this, right? So if there are compliance reasons down the road, your team wants to go and check all of the information is in here, like who approved it? And then it goes to closed. That’s pretty much the bulk of the workflow here. We’ll denote a re, credentialing date and we will schedule those for you ahead of time. Usually it’s three years, but if it’s not for you, that’s okay, we can change that. So we have our closed here. You can see who was approved. You can see, you know, all of the information. You can always go back and reference the packet if you need, right? So for anything downstream. And I believe I did show you last time we spoke that all of the psvs are listed out not in a packet form but actually in the system in the provider profile.
Jocelyn Kopchak (22:05) Excuse.
Joshua Levitan (22:07) Me. Sorry, over here, and we’re going to monitor, you know, all of those sources that are required for you, Sam, oig, ofx mpdv monthly. So in reality, we don’t see people pulling these credentialing packets after the fact, unless there’s an audit. Yeah, but we do want to make these available for audit purposes for quality purposes, and then use the verification section of the provider profile for that more sort of ongoing monitoring check on any of these sources. Okay?
Jocelyn Kopchak (22:40) Actually, that answered my question because we do get every once in a while, you know, you get risk management, yep, a subpoena comes in from the medical board, and we need every document from the medical board. And you’re like my gosh.
Joshua Levitan (22:54) Yep. And with payer audits specifically, is it often that you get audited by your payer? Okay?
Jocelyn Kopchak (23:00) We don’t get audited by payers that I’m aware of because we are hospital based. Okay? Aaron, I don’t know if you’ve had any recent, yeah. Okay.
Joshua Levitan (23:11) I was going to say we offer audit support which in our language is usually from payers, but I think we can talk to our teams about like it’s the same process, whether it’s what you were just talking about or whether it’s a payer auditing. You. There’s a request of you to pull a bunch of documents. We very likely can just make that like for the audits that you do have. Like we’ll just pull the data for you and stick it in like a zip file so that you don’t have to come in here and hit a bunch of downloads. Again, technically, the SKU is meant for payer audits, but it’s the same process. It’s you email us and say what data do we need from what on who? And what time frame? And we just do a bulk upload from the back of the system and provide that to you in a way that’s easy for an auditor to review it. Auditors could come directly in here. There actually is a, okay, you can add an auditor function so they have access but in a limited way to medallion, but usually people prefer to give them that information. Yeah. In other ways. Okay. So that’s pretty much the credentialing process. Again, most important things, we can change what’s in here to meet your what’s in the actual psvs, if you did want to include things like the case logs or peer reviews, if you’re handling it separately, that’s great too. But there’s a little bit of flexibility. And then we can use that notes to add things like the talk screen and all of the other pieces. So we’re encompassing your process as is we don’t want to change your process. You have sops, it works. We just want to use this tool to basically automate the psvs that are federal databases, those coming back as super quick as possible and then just try and help move the process along using sort of like the basic task management piece here from a visual and sort of user interface perspective. Sounds good. I’ll pause, Erin, I’ll call on you. What do you think? I mean?
Erin.Sanchez (24:57) This is more Jocelyn’s purview. Yeah, I don’t really handle the credentialing side, but this looks really cool. I.
Jocelyn Kopchak (25:05) Do have a question?
Joshua Levitan (25:10) With verifications?
Jocelyn Kopchak (25:12) That require a release or that are not automated? Is that something… the medallion team is working on the back end or is that something that would be maintained within our credentialing team? How does that work? Sometimes?
Joshua Levitan (25:28) Give me an example. So.
Jocelyn Kopchak (25:30) Education, sometimes education, you know, you have to call the school because it’s older. Same with some hospitals, it’s faxme, or rookfax faxme?
Joshua Levitan (25:40) Or relief yep.
Jocelyn Kopchak (25:41) Not work history. We don’t really worry too much about verification of work history that’s done on our background check, but we verify all hospital privileges, current and prior. Okay. So sometimes you get smaller facilities that, you know, you actually have to call and scan in a release and then they fill out a document and send it back to you.
Joshua Levitan (26:05) So, there’s a little bit of a double answer here. Some of these things we are doing the legwork we see this really commonly for like our tjc SKUs for our Tj SKU products, right? Like where we are powering the hospital mso. So for them, like we are verifying work history by calling providers, we are reaching out to peer references and collecting the peer references ourselves. We are in some cases reaching out to the former employer for case logs at their last organization. But we do like to take these things as a little bit of a case by case basis because there isn’t like an industry standard we’ve found on like how this is done, right? So like sometimes case logs are actually collected by HR or sometimes like you said, fipi is from the credentialing department versus the quality department, I’m sort of spitballing here. So what we would do is say during like the later stages of this, like I’d ask you basically for an anonymized copy of your packet or your checklist, and like we’d talk through each line and we’d say, how do you get this right now? And I’d bring that to our ops team and say, like we have here humans that can do this work and do this work. But does it actually make sense? And a lot of times is, when it falls in the process, right? So, like when do you need it? And if you’re getting it before you get to credentialing because there’s some sort of like HR activity upstream that needs the same information. It might not actually make sense for us to take it on because we’re going to then slow you down. But if it is truly like housed within just the credentialing process and it doesn’t need to be grabbed like earlier from when you literally make this request right here, then in a lot of circumstances, we can actually do the legwork of contacting whoever it is via phone, email, fax, you name it. There are sometimes effects on the SLA there, right? Like if we have to rely on a different party to give us information, we’re not going to necessarily be able to hold to the same, you know, three day SLA, but we would talk through that in detail again, okay? Usually at a later step. So. Okay.
Jocelyn Kopchak (28:08) Sounds good.
Joshua Levitan (28:09) A bit rambly there, but there’s not a clear yes or no. We like to really be prescriptive and understand your process when we’re working through those issues or those opportunities. I should say… okay, cool. Should we move on here to hospital applications?
Jocelyn Kopchak (28:29) Yeah. Go ahead.
Joshua Levitan (28:30) Okay. The hospital application process, I think like if you think about what powers payer, enrollment, it’s the same thing in many ways, right? It’s there is something out there that is a form could be paper, could be a portal that we need to set information in it that we need to submit. And then we need to follow up. So the backend infrastructure that we use is essentially the same thing. It’s the same type of like bots and form mapping tools and PDF fill. User experience looks a little bit different. But essentially, what you’re gonna do is request a new initial appointment or reappointment you’re gonna select the provider and then you’re gonna select the entities. And so you can see like these are all random examples of organizations that you might want your providers to have privileges with. This is not, I think the difference between this and PE, right? Is for PE, we have 1,100 providers mapped in the system and we have their process already mapped. Lot harder to do that here. So this is all done during implementation where you’re gonna say, here are the 300 hospitals that we work with here’s. Like we’re actually gonna say like what do you know about their process right now if you know nothing which obviously, you know a lot because you’re working it right now, but like we can go and do that research but it’s usually quicker for you to say like here’s an example of what the dop forms look like or the information needed in their portal. From what our process is. We’re gonna take that and use that to train our automation in our process so that we can still execute on your behalf but be informed by the legwork that you’ve already done because you’re already working with these hospitals and institutions and ascs. Then it comes down to just selecting a bunch of them. So you can select multiple or… just one. There are some times where we’ll actually upload the dop form in here depending on if we can programmatically ingest it. And you’ll actually select privileges that you’re applying for here. There are some times based on how the hospital’s dop form is structured that we actually do that after the fact, and we send a task to the provider and say fill it out then or to you depending on if you want that task to go to you or the provider on which privileges they want. But ultimately, we need that step at some part in the process, there’s a little bit of variation on how it, where it shows up based on the capabilities of the other hospital. But then you hit submit similar to PE, submits, the magic button, we have cataloged the process. We have the information we need. If there’s something that we are missing, it will generate a task. That task will be sent to the provider, to your team with reminders, all that great stuff that we talked about with tasks and sort of like the data collection and outreach. And then we go ahead and we execute the process. Our SLA here is 10 days. We average less than that, but we are committing that in no circumstance, will it take more than 10 days from when you request this to when we actually get the application out to the medstaff office of that hospital. We will follow up with those medstaff offices as well. On the status. We do recommend that you still obviously have like a close relationship with your partner institutions like it is a little bit different than the payr world where we can really manage that follow up and that relationship in a much more entirety. So, I think, you know, while we can do a lot of the follow up for you, like you should still be having whatever your cadence of like sort of like leadership to leadership like monthly or whatever meetings. And I’m sure there’s contractual talks that come up with that. But at the mso level, we would still recommend that you have like a strategic coordination with them and we handle just sort of the mundane elements of all of this. Okay?
Jocelyn Kopchak (32:22) So, how does that work with portal applications? Or because?
Joshua Levitan (32:28) A lot.
Jocelyn Kopchak (32:28) of our apps are going online, going through a portal, you know, needing some type of delegated form that allows access, you know, allows our team to have access, how does that those types of applications work here? Yeah.
Joshua Levitan (32:44) So, if there’s paperwork that allows your team to access the provider’s portals, we would use that same paperwork to allow our team to access it. There are certain types of applications where we would actually just use the provider’s own login. And we would ask them for a task to say, hey, provide like if they create their own profile within that system, we’ve seen that as well give us your username and login. There are certain times where we can create one. If there isn’t one that already exists. So, a wide variety of approach, but I think similar to the payr landscape, we’ve kind of seen it all here. And sometimes there’s paperwork to make this, you know, to get this set up properly. Sometimes like we are just impersonating the provider essentially, and the system usually doesn’t really care. I’m curious right now, when you’re doing this, are you ever using provider logins themselves or do you always try and figure out a way to set up your own login?
Jocelyn Kopchak (33:44) I would say 98 percent of the time we have separate logins?
Joshua Levitan (33:49) Because we.
Jocelyn Kopchak (33:51) don’t want to have any access whatsoever to dops… to… your questions, we don’t want to have the ability to submit that needs to maintain and stay with the clinician.
Joshua Levitan (34:06) So,
Jocelyn Kopchak (34:06) there are a few facilities that don’t allow that, or they have a system. I think symplr might be one of the systems that doesn’t allow a delegated portal, but… people are moving away from those types of.
Joshua Levitan (34:25) Applications to.
Jocelyn Kopchak (34:27) Allow some type of delegation.
Joshua Levitan (34:30) That’s very consistent with what we’ve seen as well. Good gut check for me and hopefully good gut check for you. That’s definitely the trend. And then I guess like process tracking, once we get this in here, you will see it in committee, which means it’s with the med staff committee of the hospital. And then you will see it go to closed. I don’t know why my demo environment isn’t loading right now. Perhaps my WI fi in the kitchen is a little gimmicky. But then you will see it go to closed… which is it obviously closed recently. We’re going to denote the date we’re going to make sure we have all the paperwork that came back from the hospital logged within here. And then in existing, you can look… up the privileges and we’re actually about to restructure so that you don’t have to hit that little button to see the specific privileges and make this just a little bit more visually friendly. But you can run reports on here. This sort of becomes your privileging portal… to view what exists out there amongst your provider base. Okay?
Jocelyn Kopchak (35:39) And you obtain the board certification letter and everything or not the board certification letter, the board approval letter?
Joshua Levitan (35:45) Yes. Yep. And we want to document that as well. It’ll be in the provider’s documents… as well as saved like in line here.
Joshua Levitan (36:04) Okay. Just taking a pause here for one sec. I’m sorry, I need to go and adjust… his cone. It’s doing pretty good thus far though.
Joshua Levitan (36:21) Okay. We’re good. Yeah, he has been doing pretty good. Okay. I’ve been talking a lot and I’m drinking a diet coke. So I’m all nice and chatty over here. We want to go through the reporting and analytics piece and we have a little bit of time left, but just want to do a gut check. How are we doing on anything? Major questions, major red flags things we need conversation for.
Jocelyn Kopchak (36:43) Not off the top of my head,
Jocelyn Kopchak (36:51) No, no. I think we’re good for right now, okay? Nick?
Joshua Levitan (36:54) Anything from yours? No, I have a couple questions, but I don’t want to, I don’t want to stop with progress. Let’s do the reporting analytics and see if we have time before we wrap. Yep. This is a pretty quick session, but there’s a lot of power behind it. Obviously, this being a demo environment, it’s not exactly how this is going to look for you. Reporting analytics and analytics that we’ve seen built in, right? Like you could see for example, in the payers tab, your current enrollments, right? And you can sort and filter here and download to CSV here. This is reporting, but it’s detailed reporting. What we want to provide in analytics is a little bit more of an overview, the type of thing you would use in like a monthly team meeting or a presentation to leadership, that’s often focused on like speed and volume as well as sort of tracking trends by time. I will say there’s about 400 different reports that we have that we can dump into these dashboards based on what you need that are already pre built. And this is just a selection of a few of them. So, I would think, of viewing these in this demo environment more as a flavor of like what dashboards look like from a look and feel. And we can have a conversation about like you tell me if there’s a monthly powerpoint that you have to build Jocelyn and present to executives, like what’s in that powerpoint, can we recreate that here? So you never have to build that powerpoint again and it’s updated live.
Erin.Sanchez (38:13) Right, non stop. But, you know?
Joshua Levitan (38:16) For examples on my payroll piece here, we’re sort of tracking by trends. We’re tracking statuses.
Erin.Sanchez (38:23) We’re.
Joshua Levitan (38:23) tracking sort of time in each stage. Obviously, who was, who went par most recently?
Erin.Sanchez (38:31) There’s a lot.
Joshua Levitan (38:32) Here, we can get down to like summarizing tasks?
Erin.Sanchez (38:36) In,
Joshua Levitan (38:36) a different way.
Erin.Sanchez (38:38) Than we.
Joshua Levitan (38:38) Saw before, so.
Erin.Sanchez (38:40) Actual.
Joshua Levitan (38:41) Outstanding tasks like average time?
Erin.Sanchez (38:44) Get really?
Joshua Levitan (38:45) Detailed from this perspective, historical performance of tasks. Are there bottlenecks in who needs to answer what?
Erin.Sanchez (38:53) We.
Joshua Levitan (38:53) can we, there’s the whole privileging section of here as well. I’ll pop into cred, I’m actually going to pop into licensing after that, cause it’s a little bit more colorful.
Erin.Sanchez (39:01) But you can see the,
Joshua Levitan (39:02) same type of thing here, right? Like volume of initials versus recreds by month? How long is it taking us, you know, in that like committee for you, but like how long is it taking in each phase?
Erin.Sanchez (39:15) All sorts?
Joshua Levitan (39:16) Of good stuff.
Erin.Sanchez (39:18) There’s an element of.
Joshua Levitan (39:18) This, that’s also often like what, what’s coming up that’s expirables, there’s a whole expirable tracking dashboard that’s a part of ongoing monitoring. And then we’re also sort of nesting a lot of this in specific dashboards as well. All of these reports you can download right from here.
Erin.Sanchez (39:35) I like showing licensing.
Joshua Levitan (39:37) Even if we’re not doing licensing for you, cause we can get like a little bit more of a colorful visual.
Erin.Sanchez (39:42) And we’re balancing, you know, sort of like.
Joshua Levitan (39:45) Empirical charts with actionable information.
Erin.Sanchez (39:49) All in one place. So that’s.
Joshua Levitan (39:52) analytics, again, I think the best example is to think about the powerpoint that you have to give to someone or the weekly email that you have to send or whatever someone’s asking for you and we just try and recreate it.
Erin.Sanchez (40:01) I’ll move on to report.
Joshua Levitan (40:02) Builder next. But any questions from either of you about analytics and the dashboard and capability?
Erin.Sanchez (40:10) I don’t think so. Not off the top of my head, but that’s really cool. There’s already a lot of already pre built reports in there. Yeah, all of ours are.
Jocelyn Kopchak (40:22) Built from scratch.
Joshua Levitan (40:24) Now, to the logic, we used to do that too, but we’re like if we’re having customers cause you can’t actually build these yourself. And so, we’re like if customer B is asking us for this report, why don’t we just catalog that and we can change the data to customer C’s data, but we already did the legwork of building it, right? It’s great for all of you. It’s also like less work. We have to do like, it’s kind of just a good scenario. Obviously, the data is specific to you and this is hosted in your environment, but like the, you know, put this in the bar chart? Like that logic really easy to just move that from one report to another.
Erin.Sanchez (40:55) So, if.
Jocelyn Kopchak (40:56) we needed something built, how?
Erin.Sanchez (41:00) Do we do it like?
Jocelyn Kopchak (41:00) If it wasn’t already predetermined?
Joshua Levitan (41:04) In your system, yep, we have a team that does that. We’re powered by a bi tool that’s similar to like Power BI, it’s called sigma which is what we use in the backend.
Erin.Sanchez (41:13) Takes a couple.
Joshua Levitan (41:14) Minutes to spin those up depending on like if it’s already something we built, we’re just going to do it for you and dump it in here. We want to handle as much of this in implementation as possible. If there is something that’s like really sort of like.
Erin.Sanchez (41:27) People ask.
Joshua Levitan (41:27) us before about like mapping things on like a map of the U. S and like things that take a little bit more. There might be a cost component to cover the time of our resources that had to do that.
Erin.Sanchez (41:38) But again, that’s.
Joshua Levitan (41:39) just within dashboarding. I think the other answer to your question is report builder, which you can build anything in the tool yourself. This is the other part of reporting here. So you.
Jocelyn Kopchak (41:51) just you just select.
Joshua Levitan (41:52) Fields in here, right? I’ll show you this in a sec, and you can then send anything you build in this report builder to someone on any sort of cadence via email. You can see them in your saved reports here.
Erin.Sanchez (42:04) We see something examples.
Joshua Levitan (42:05) Of this where you’re building a report and sending it to people on a cadence on a sequence to like a specific region or like a specific group practice that needs a subset of information. And they prefer to get that in email, you know, every Monday as opposed to logging into medallion with limited privileges. So that’s a good use case here. A couple of different categories, like some of these are based on the open requests?
Erin.Sanchez (42:27) And then some of this is.
Joshua Levitan (42:28) Just based on general provider data, I’ll just build a quick fake report here to show you how easy this is. So we want to look at like providers we want to look at is their profile complete? Do we have all their data? When do they start?
Erin.Sanchez (42:46) What is?
Joshua Levitan (42:48) Their primary specialty, their primary taxonomy, their?
Erin.Sanchez (42:52) Primary state?
Joshua Levitan (42:55) There’s tons of stuff in here. What else would make sense in this report? Maybe the practice locations that they’re tied to and,
Erin.Sanchez (43:04) hospital.
Joshua Levitan (43:05) affiliations.
Erin.Sanchez (43:07) Select these.
Joshua Levitan (43:08) Right. Hit this little magic button. Right here. We can now see what’s in our report?
Erin.Sanchez (43:13) We now have that report? Let’s say, oops. Hit my back button, oh.
Jocelyn Kopchak (43:24) Use my mouse to.
Joshua Levitan (43:25) Slide and hit my back button, but I was going to say, let’s say you didn’t like something in here. I’m just going to select some random ones.
Erin.Sanchez (43:32) You didn’t like something in.
Joshua Levitan (43:33) Here like, okay, delete it. It leaves the report below. Let’s say you want to filter on something you can filter.
Erin.Sanchez (43:40) And then.
Joshua Levitan (43:40) what you’re left with is what you can either export or save and send on a cadence to select members of the team?
Jocelyn Kopchak (43:52) It doesn’t it doesn’t is there a way to that? It’s just auto like we built this report. And every week it sends to these people. Okay? Because we have a lot.
Joshua Levitan (44:02) of those, yep. Yep.
Jocelyn Kopchak (44:05) Lots of those, yeah, lots of those and some of them look very the same but they’re not.
Joshua Levitan (44:12) Yeah. So, do you want to schedule this to run automatically? Yeah, yes, report, cadence. And then you would just make a grouping of people which is usually going to be tied to groupings you already have like team managers of like the east team or the west team or the Chicago practice or whatever it is.
Jocelyn Kopchak (44:29) Okay. And then.
Joshua Levitan (44:30) run automatically, cadence daily, monthly, weekly start on this day and do the email. It’s going to send us an excel or a CSV?
Jocelyn Kopchak (44:40) Perfect. Yeah. Okay.
Nick Scallion (44:44) Oh, well, I had you folks reserved until 1,215. Do you want to, maybe, do you have like two or three minutes just to kind of see where we go from here?
Jocelyn Kopchak (44:52) Yeah.
Nick Scallion (44:53) Okay. Well, cool. I know like somebody still asked me like Jocelyn, I looked at some of my notes just before our call from our last conversation. I jotted down like you said you’d seen just about every demonstration of every platform on the marketplace and you hadn’t found one that really checked the boxes you were looking for. So, I’m just trying to get a sense… like kind of where you think medallion falls under that? And if there are like areas where I’m not really sure we’re checking a box, like if we could try to address that in follow ups. So just general feel for where you think medallion is landing for what a good solution might look like for usap, long term, knowing this isn’t like an imminent change, but just trying to understand, you know, where you think we’ve landed?
Jocelyn Kopchak (45:33) Great question. I think that… other than the fact that we can track or have the capability of seeing where… clinicians are within what facility, what I didn’t see and it could just be, I’m not remembering it, is actually tracking each application per… day. So like, and that might be a build thing down the line. And again, I apologize if this is something we did talk about. And I’m just not remembering correctly, but if they’re going to five different hospitals, what is the detail of each five hospital? Has the application been sent? You know, I know that there’s an overall this person is going to committee, but, you know, how does that work with a cvo where they might be getting approved for one facility? And then we go ahead and add another. And we still have to wait for that committee process to go… through, you know, even though they’re a part of a larger cvo… that’s always my, I hold up is being able to really drill down on every single hospital and know exactly where they are with each hospital. Because the amount of reports and dashboards we have built off, that is significant, they want to know, you know, how long did it, how long did it take for usap to complete the application? How long did it take for offshore to complete the application? How long did it sit at the hospital? How long did it get through approvals? So they want to know all… that information down to the super minute detail and that’s where I and that’s where I struggle with a lot of databases. They’re mainly made for hospitals and not practices such as usap. But you have a lot more functionality than some of the other databases where, you know, your dashboards are a little more… customizable, and the report building is a little more customizable. Where some of it, it’s kind of you get what you get and if you want to do something different, you know, it takes a week or more to get something back and sometimes we don’t have the luxury of time.
Nick Scallion (48:01) Go ahead josh.
Joshua Levitan (48:02) Click into this real quick. And maybe I didn’t do a great job of showing this. But in the privileging, so I just searched for one provider so you can see both the different hospitals. So any different hospital is going to show us just a completely different line item.
Jocelyn Kopchak (48:17) What I think and then.
Joshua Levitan (48:18) there’s an element of status that’s sort of controlled up at the top like in progress versus it’s in the hospitals committee versus it’s closed in here. You can see like requested app complete. And then in the committee workflow, there’s a different date which is like the date we get it back… to your point where you can see the different hospitals here, what we’re not, and we’re showing the dates. What we’re not showing is the time elapsed between date a to date B, that’s where we would use an analytics dashboard. Okay. Just basically take everything we’re seeing right here, but like group it by provider because if I take out my filter here, this is just based in like the request order. So even though I have, Noah Allen, or, Jen, and Jen, it’s grouped the wrong way. So we would just in the analytics dashboard, recreate this filter, it by provider and then take the date columns that we already have and just generate like a delta three days between step a and step B, four days between step B and step C.
Jocelyn Kopchak (49:20) Okay.
Joshua Levitan (49:21) Is that the type of thing that you’re looking for with the?
Jocelyn Kopchak (49:23) Yeah. We have that yep. And then we also have where, you know, we want to be able to see. And then my, that we haven’t experienced an expirables person that works all expiring except for hospital privileges. Yeah, expiring hospital privileges is worked by the clinician that again is assigned to that provider. But we have dashboards that do countdowns and turn colors. And our leadership teams look at that every single day to see, you know, how many in what state for what facility do we have expiring within 30 days or 45 days? So as long as we have a way to capture that information, it’s definitely worth having the larger team, you know, go through a demo and see what their thoughts are.
Joshua Levitan (50:11) Okay. And the business value of that is you need to make sure that you have coverage on all of your contracts essentially for each hospital and.
Jocelyn Kopchak (50:19) Yes, and make sure we have, because… it feeds into the scheduling system, right? So we need to make sure that no one’s being scheduled if they have an upcoming reappointment, and then if not every hospital gives you an answer right away, if their committee’s the last day of the month, our system might look like it’s still expired, but really it’s not. So we found out, we found a way to designate that. So it keeps them green on our dashboard so they know that they are approved. But we’re just waiting for the letter. So we really have done some creative customization to satisfy our internal partners, which is, you know, the billing department, the scheduling department, HR it, you know, they all have access to our system for various reasons to complete their own job functions that.
Joshua Levitan (51:11) Context makes a ton of sense. Look, I think honestly like there’s some rebuild that we would have to do in our analytics. I don’t know if we have those exact reports, but I think like with our approach, all that rebuild will be done during implementation. So by the time you go live with us, you’re going to have everything you need with all of those different things and, you know, I think that’s definitely.
Erin.Sanchez (51:28) A.
Joshua Levitan (51:30) common thing. But we’d want to make sure that it was really tailored. I mean we can literally copy the reports you have right now in visual aspects or if you actually want improvements on those reports and to use this as an opportunity to tailor them like that’s great too.
Jocelyn Kopchak (51:43) Awesome. Yeah.
Joshua Levitan (51:45) I’d say maybe we’re talking about also adding like two weeks to the implementation timeline like it’s not a huge lift, right? So, there is a time factor here that I want to be transparent about, but it’s not, we’re.
Jocelyn Kopchak (51:54) not, we’re not really in a hurry. We’d rather it be done, you know, take the time and get it done, right? Is there a testing environment as well? Just, is it something where we would launch, you know, and test, make sure everything looks good and then launch in production or how does that work when it comes to implementation? Yeah.
Joshua Levitan (52:13) We would, we can do both. It depends the testing environment we’re usually only going to spin up if your team is doing integration work?
Jocelyn Kopchak (52:20) Okay.
Joshua Levitan (52:22) With integration work, sometimes customers want our teams to do that. We have a whole professional services team built out. We probably actually not too long from now. If there’s good interest here, we want to introduce you to Sammy who runs both the implementation team and like the technical team that handles custom reporting, custom integration. So, if your team is building those integrations, then yes, we’re going to give you a testing instance so that you can do that.
Nick Scallion (52:46) What we would likely do if.
Joshua Levitan (52:47) we were building integrations or if there were no integrations and we’re really only testing things like reports, is we’re just going to build that in a live environment. But before we transfer data in and just like use some mock data just to give you a sense of what it looks like. Okay? So, yeah.
Jocelyn Kopchak (53:02) Okay.
Nick Scallion (53:03) Yeah. I mean, I think just to add on to that like, yes, we have set up sandboxes before Jocelyn, it’s like a little non standard as part of our evaluation process. I think as long as we could just like define the purpose, the timing and like as long as we can map that out, I think that’s something josh, you know, I could easily advocate on your behalf for it’s like no problem.
Erin.Sanchez (53:22) On the timing.
Nick Scallion (53:23) Piece, I know like you had said, like you were just probably going to start looking at you?
Erin.Sanchez (53:29) Know what else?
Nick Scallion (53:29) Is out there, where do we kind of go from here in terms of what you’re thinking after you get caught up from vacation, like what’s kind of next?
Jocelyn Kopchak (53:37) Yeah. So next steps would be probably going through a similar… demo, maybe not two different.
Erin.Sanchez (53:51) Meetings.
Jocelyn Kopchak (53:52) Long, but for.
Jocelyn Kopchak (53:59) Example, if you’re going to be doing something that’s going to be a little bit different than what you’re thinking, then you’re going to have to go through a similar demo, maybe not two different meetings long. But for example, if you’re going to be doing something that’s going to be a little bit different than what you’re thinking, then you’re… going to have to go through a similar demo, maybe not two different meetings long. But for example, if you’re going to be doing something that’s going to be a little bit different than what you’re thinking, then you’re going to have to go through a similar demo, maybe not two different meetings long. But for example, if you’re going to be doing something that’s going to be a little bit different than what you’re thinking, then you’re going to have to go through a similar demo, maybe not two different meetings long. But for example, if you’re going to be doing something that’s.
Erin.Sanchez (54:27) going to be a little bit different than what you’re thinking, then you’re going to have to go through.
Jocelyn Kopchak (54:29) a similar demo, maybe not two different meetings long. But for example, if you’re going to be doing something that’s going to be a little bit different than what you’re thinking, then you’re going to have to go through a similar demo, maybe not two different meetings long. But for example.
Erin.Sanchez (54:35) If you’re going to be doing something that?
Jocelyn Kopchak (54:38) Is probably going to be that larger audience.
Nick Scallion (54:40) Oh, makes sense. And I met Ben almost exactly two years ago. It was actually shortly after I joined medallion and probably couldn’t really speak nearly as well about what we actually do and the problems we solve as we do. So it’ll be good to have a second chance eventually. So that sounds good in terms of timing. Jocelyn, are you thinking maybe like April Ish, for the larger audience demo, you tell me and we don’t need like it doesn’t need to be written in blood right now, but just trying to get an idea of when josh and I will try to get with you folks next?
Jocelyn Kopchak (55:11) Yeah, probably.
Erin.Sanchez (55:15) I.
Jocelyn Kopchak (55:15) mean, oh, Yvonne’s out next week. Okay? So yeah, it will be probably the week of the thirtieth through the third. It looks like one of our directors is on pto next week. So, and she will be critical to have on the call. So I will, I can send you some times, but it looks like Tuesday, the 30 first, Thursday, the second and Friday the third are pretty.
Erin.Sanchez (55:42) open.
Jocelyn Kopchak (55:43) For me, cool. Let’s do an.
Nick Scallion (55:45) hour block so I can send like our scheduling link as well so we can determine which one’s best for you. Let’s do an hour block. And then josh and I can make sure that we try to like make sure that we, it’s not a two session because it’s going to be hard to get all these folks together for two sessions.
Nick Scallion (55:56) So we can try to abbreviate, and then really, you know, focus on what you and Aaron had asked about in sessions and just, really kind of stick there.
Jocelyn Kopchak (56:05) Sounds good. Now, would you prefer if the… it individuals on a separate call or is it okay to include them? I know they may have different questions than what the credentialing leadership team might ask. So, what’s the preference?
Nick Scallion (56:22) We just had one of these calls Jocelyn. It was actually with a different solutions consultant than josh, but the it folks kind of dominated and this is a personality thing.
Jocelyn Kopchak (56:31) That’s what I’m asking. Yeah.
Nick Scallion (56:32) They kind of dominated the last conversation. And like the clinical and operational folks didn’t really understand like we didn’t get through the demonstration for payr and all that. It was mainly like, you know, integrations and like really valid questions that need to come up. So I would argue that maybe those are separate conversations or at least maybe set the stage with the it person. Hey, if you want to like sit in on this demonstration, then we have the technical session. I do recommend separating them.
Jocelyn Kopchak (56:58) Though. Okay. That’s why I asked. I have a, just a suspicion that we would be the same where it’s you know, taking over the call.
Nick Scallion (57:07) It’s all good. It’s just really.
Joshua Levitan (57:09) Different, Nick. Let’s bring in Sammy for that. Who’s the gentleman I was just talking about, who leads those teams?
Erin.Sanchez (57:16) Yeah, yeah, yeah, perfect.
Nick Scallion (57:17) That’s it. All right, folks. Thanks so much for staying extra with us, Jocelyn. Great.
Jocelyn Kopchak (57:21) To see you guys again. Thank you. Appreciate it likewise.
Nick Scallion (57:24) Let me get an email over to you and we’ll work on locking something in the thirtieth, we’ll talk soon. Thanks again for the.
Jocelyn Kopchak (57:29) Time. Sounds good. Thank you all.
Nick Scallion (57:31) Right. Bye bye.