Transcript
Rae Tompkins (00:00) good afternoon, hi, Alyssa. How?
Alyssa Lawler (00:02) Are you? I’m well, how are you? Good?
Rae Tompkins (00:12) I think Falesha is still connecting to audio.
Alyssa Lawler (00:17) Hello? I’m here, Felicia. How are you? Good. How are you guys? Good?
Rae Tompkins (00:27) I did not have much to review today, but Nico is here to help us figure out the best way of splitting the Json for the partial packets. And then our next calls will start our bi weekly schedule but wanted to keep this one so that we can kind of scope out that process and then go from there.
Alyssa Lawler (00:48) Fantastic. Thank you.
Rae Tompkins (00:50) And before Nico, I have an update on the files that you requested. Falesha. I’m going to send this over via email. It looks like a lot of them are pending just caqh attestations or, you know, other items needed in order to prevent the file from being moved forward, but I can definitely provide that via email. Our team just completed the audit of the requested files.
Alyssa Lawler (01:13) Okay. Thank you. And if we’re I can quickly add on to that, Falesha and I were discussing this yesterday, and I noticed there were, as part of this list, there were a couple that show that they were completed and we cannot find where they were sent to us. Is there like some kind of checklist or something that maybe is already available that I just don’t know about that we could use to verify what was completed this week and should have been sent versus what we actually received? Is there a way to manage that? So?
Rae Tompkins (01:54) When you say completed, do you mean they were in the ready queue or they were marked?
Alyssa Lawler (01:59) App… complete? So like the one that we looked at was sent on January 26 and it showed app completed January 26. So, I would have thought we would have received it like the next week but we have not received it at all as of yesterday. And,
Niko Byron (02:22) you mean when you say received, do you mean via the Json file? Yes. Okay. And,
Alyssa Lawler (02:30) I was thinking maybe it was one that was archived or closed or whatever. There was an issue with it, but it wasn’t that wasn’t the case. So, yeah, Falesha, if you will send that one over.
Niko Byron (02:43) Yeah, we’ll take a look and see why it’s not, and,
Alyssa Lawler (02:45) adjust.
Niko Byron (02:46) Anything we need, to solve that.
Alyssa Lawler (02:50) Yeah. Previously, when we were working with caqh verified, they would send us a list as part of the packet. The part of, this sftp drop that showed, you know, what we should have and that way we could compare it. So I’m just trying to make sure that we’re not missing anything on our end as part of the process.
Rae Tompkins (03:15) Yeah, absolutely. If you’ll if you don’t mind sending me that name, and then any files that you may be missing and we can take a look to kind of better understand. Obviously the expectation being anything in the ready queue with that ready on date is kind of that checklist you’re referring to. That should be when you receive the file. So we can definitely investigate this internally if you can provide us those names just to make sure that no other providers are falling into that same category?
Alyssa Lawler (03:43) Absolutely. Thank you.
Rae Tompkins (03:49) Was there any other ops related business before we kind of switch to, the Json? I wanted.
Alyssa Lawler (03:57) to follow up with you very quickly and just make sure that our protocol was updated for the Dea requirements. I know we had talked about that briefly. Yes.
Rae Tompkins (04:08) That was submitted to our tech team. I just followed up this afternoon to ensure that was turned on. I will definitely shoot over an email once I get that completely configured in platform, but I do have that list and our team is referencing it currently to ensure that we’re not holding up any additional files?
Alyssa Lawler (04:26) Awesome. And then I know you were still waiting on some feedback about the CMS automation about the CMS verification. So, yeah, I assume we’re still pending that.
Rae Tompkins (04:36) Yes, I sent a little nudge this afternoon and we’ll obviously follow up as soon as possible.
Alyssa Lawler (04:43) Fantastic. Yeah. Then that’s all I had just the partial packet stuff.
Rae Tompkins (04:48) Okay, perfect. Yeah… Nico, was there anything that we needed from the viva team to kind of start?
Niko Byron (04:54) Yeah. Well, I’m not sure if this was the meeting we wanted to discuss it, but I know there was talk about investigating whether we wanted to split the Json into two different files for archive versus clean. Is that something we should save for a wider group or is that a conversation we want to have now?
Alyssa Lawler (05:09) Yeah, we can go ahead and have now on our end that would be great.
Niko Byron (05:14) Yeah. So I guess I’m curious… what, the like the benefit would be? Because right now the Json each Json entry should have the ability to tell if it’s an archived or clean file versus like separating them out into two files. It’s something we can definitely do if we want to. But I just want to make sure that like if the current integration has like maybe has the functionality that you’re looking for and like it’s a huge payload. So I understand that like it’s not easy to find these things and I can maybe advise on how to use it to fulfill what you’re trying to get to without that split potentially?
Alyssa Lawler (05:53) Yeah, absolutely. So our current process is when we have the Json come across and it automatically splits it up into the PDFS for us through the process we go through. And we save those PDFS to a folder for each provider. And that’s what we work out of when we work the application… just from working, that there… is not an easy way for us to see. Will these three are partial packets because for one reason or another, the application was not able to be completed. So what we’re doing now is going back to the dashboard and pulling back information… sorting it by closed… archived, whatever it may be, and then taking that and utilizing that. However, what we’ve run across is, of course, this is an ongoing list. It’s not like the old ones just disappear. So then we’re having to sort through and we’re looking at dates and that kind of thing. So if there was an easy way for us to identify as they came over, which ones were those partial packets? Then we could sort those out at the beginning. And that goes back to, I guess with that checklist that we were talking about… we were used with caqh, verified that was denoted on that checklist. So we sort of had a heads up when we got that. Yeah. So.
Niko Byron (07:22) When, you say it automatically splits the files like into smaller files because they’re too large in some cases. Is that what you mean it?
Alyssa Lawler (07:29) Pulls out. It takes that Json and pulls out a PDF, the packet as a PDF. Yeah, and drops all the PDFS from each week into a folder and we take each provider’s PDF and put it in an individual folder that we work out of. Yeah.
Niko Byron (07:44) So, and so is, would the integration team be like doing something different? Like they’d have two of these two or I guess the tech team on your end, the it team, they have two, these two, they would have two Json files. Sorry, I’m repeating myself a 1,000,000 times and they would put them in like different directories or something or different buckets depending on which Json file it comes from.
Alyssa Lawler (08:07) Yeah, that was sort of my thing. If we had two separate Json drops, one being just what we’re already getting normal clean files and then one that was just partial packets. We could do same day, different day. You know, we could figure that part out. Sure, just as long as they were separated out, that might be helpful for us.
Niko Byron (08:27) Yeah. Well, I’m just wondering if like the end goal is to have them is to like read one file and put it in one directory, read another file, put it in another directory. I think that, are there any of the it stakeholders on this call right now?
Alyssa Lawler (08:42) There are not, no, we would have to get them.
Niko Byron (08:44) Yeah. I wonder if we should have a conversation with them because we might be able to just use the data within the larger current Json file to be able to like put those files in the correct spot depending like they should be able to identify if they’re a partial packet the way it is now from the major Json file. Again, like if it’s not super easy, we can definitely do two files, but I just wonder if it might even be easier to keep it the way it is and just use some of the data that’s already in that Json file? And I can advise the it team on where to look for that. So, I think, is there a meeting that we have with the it team on scheduled? Or maybe we can just pull them into the next meeting or something? Yeah, this.
Rae Tompkins (09:24) One was just to kind of scope and get an idea, but we can definitely try to include them in our next one.
Alyssa Lawler (09:30) Yeah, I’ll see if I can get them someone available from their team to join on our next bi weekly. Awesome. Once again, this is not a huge issue. It’s just more of a convenient thing on our end 100 percent.
Niko Byron (09:44) And we want to make that, you know, as convenient as possible. So I just want to make sure we got the right, the best solution going forward and we’re you know, we’re not opposed to doing what you suggested as two files, but it might even be easier for both teams not to. So just would like to hear what they think about that idea. But, yeah, thanks so much for also identifying that missing provider and sending that over. And we’ll be sure to investigate that and improve the automation on our end to make sure those don’t fall out.
Alyssa Lawler (10:15) Fantastic. Thank you so much.
Rae Tompkins (10:16) And I did confirm that the Dea configuration was set. So we’re all good, there, there should be no additional fallouts, it’s configured in platform based on the list Falesha, provided.
Alyssa Lawler (10:29) Thanks so much, Ray and I appreciate you being so flexible and helping us out with that. Yeah.
Rae Tompkins (10:34) Absolutely. So we’ll start our bi weekly. I’ll be out of the office Friday. We’ll be back on Tuesday, but obviously, if anything comes up between that time, I will get back to you as soon as possible, and then our next call will be April the tenth. So if we want to explore the opportunity of adding some it members to the call, we can definitely kind of continue the conversations on the Json while we have Nico available.
Alyssa Lawler (11:01) Yes, I will go ahead and reach out to them and I will give you a heads up on that.
Rae Tompkins (11:05) Perfect. Thank you so much. Thank you.
Alyssa Lawler (11:08) All have a good afternoon, you too. Bye.