Transcript
Jordan Tantleff (00:11) how’s it going Chris?
Chris Teixeira (00:14) I’m good, Jordan. How are you?
Jordan Tantleff (00:17) No complaints. How was your weekend?
Chris Teixeira (00:20) Not too bad. Got a young kid. So did all the fun Easter stuff. How about you? Fun?
Jordan Tantleff (00:28) It was good. I’m from New Jersey. So I was actually down the jersey shore area at my aunt and uncle’s place. No more like super young kids in our family. So I didn’t get to do like the Easter egg hunt and those things, but I’m sure some grandkids will be around the corner for my grandparents for those to pick up back up again, but it was good R, R and family time. It was just nice.
Chris Teixeira (00:55) Is it still a little chilly down by the shore? That’s got to be right?
Jordan Tantleff (01:00) It’s actually finally warming up a bit. It was like mid sixties, which is quite different from like two days ago. It was like in the forties so I can actually enjoy going outside. Let’s go, Scott, hello.
Chris Teixeira (01:19) Chris Scott. How are you? Your?
Scott Everline (01:23) Name looks familiar for some reason.
Chris Teixeira (01:27) Hopefully, not a bad one.
Scott Everline (01:28) No, no, no. I’ve been around this space for a long time and it just, it rings a bell, but my memory is aging like my beard and hair. So.
Chris Teixeira (01:38) Yeah. Well, with a camera on you’d, see a lot of great things. It happens.
Jordan Tantleff (01:45) How’s it going? Erica?
Erica Sagastizado (01:46) How’s it going?
Jordan Tantleff (01:48) It’s going. Well, appreciate you all taking the time to hop on here. I know this is all our first time meeting. So I thought we could start with some intros. And then Erica, I’d like to kind of quickly recap your conversation with fletcher.
Jordan Tantleff (02:01) And then we have just a few kind of questions regarding the current process which will kind of inform how Scott runs the demo here. But just to quickly introduce myself, my name is Jordan. I’m one of the account executives here at medallion coming up on almost three years here. So I’ll be kind of the main point of contact as you guys evaluate medallion and kind of align on next steps throughout this evaluation. But I’ll kick it over to Scott for an intro here as well.
Scott Everline (02:31) Hi all. So I’m Jordan’s kind of partner in crime. My role is technically the solutions consultant here at medallion or one of so work closely in the credentialing space, provider, data space, working closely with our payer customers. Prior to medallion, I was at caqh for nine years and then prior to that working with some other vendors and spent a little bit of time on the payer side as well. So here just to kind of run you all through the demo, make sure everything’s kind of aligning with your expectations and make sure we really understand kind of the problems you all are looking to solve.
Jordan Tantleff (03:03) Great. Thank.
Erica Sagastizado (03:04) You. Okay. So I’ll just introduce myself. My name is Erica. I’ve been with provider partners for three years now. I’m the credentialing manager. I’m super excited to see what you guys are going to show us and see if it’s a good fit for us. Awesome. And I’ll let valer and then Chris introduce themselves hey.
Valair Valentin (03:30) Guys, valer, Valentine, I’m with our network development team. So working with contracting credentialing teams, data management. So just kind of jumping in to support wherever I.
Scott Everline (03:42) Can today?
Jordan Tantleff (03:44) Nice to meet you, valer. And.
Chris Teixeira (03:46) Chris tuxera, I’m the Salesforce database administrator for provider partners. So kind of try to keep all of their stuff straight and work with third party vendors if there’s an integration on that side.
Jordan Tantleff (03:59) Awesome. It’s nice to meet you all. And like I was saying, just to kind of quickly recap and just make sure we’re aligned on Erica, your previous conversation with fletcher. It sounds like today you guys are using verifiable alongside Salesforce, where verifiable is handling the primary source verification and then, but it sounds like your internal team is still doing some of the heavy lifting around, you know, building credentialing packets and processing files. The network sounds like about 35,000 directly credentialed providers with 4,300 facilities plus a significant delegated network population as well. All that being handled by an eight person team handling that workload today. From what I understood things are working. But the biggest driver for exploring alternatives right now is cost both on the vendor cost side with verifiable and potentially, you know, internal overhead kind of required to support that process. So it sounds like this evaluation is really about an understanding if there’s a way to reduce those total costs while also kind of taking work off your team without disrupting the, you know, Salesforce driven workflow that’s in place today. Sounds like you’re also evaluating some vendors throughout these next few weeks looking to kind of make a decision on the partner by end of April, aiming for implementation in August that’s correct? Hopefully I captured that accurately. Yes.
Erica Sagastizado (05:29) He did okay.
Jordan Tantleff (05:31) Perfect. And to start and this will kind of help Scott orient on the demo here. We’d love to kind of understand your workflow a bit deeper so we can kind of mirror that in the demo. So if you, could you walk me through kind of end to end workflow today? From when a provider is identified to when they’re fully credentialed, you know, where does verifiable stop? And your team take over any kind of context there would be helpful?
Erica Sagastizado (05:57) Okay. So our providers, we have a team that loads the providers in Salesforce. Those providers are loaded in Salesforce, which then triggers a credentialing event via verifiable is the system that we use for processing all of our providers. So once those credit events are created, those providers are assigned to an individual coordinator, who then takes that credit event, starts performing the psvs screening apps. And, you know, basically the beginning to end of that credentialing file… and ultimately it goes to our CMO for approval and everything is housed in verifiable. Now, we also, they also include ongoing monitoring via mpdb so that’s included as well. So that is part of the enrollment. So we don’t actually go to any external sites for mpdb that is all automatically populated into mpdb since verifiable is an agent of ours. So that takes a lot of work off. And then ceqh is automatically imported into verifiable as well. Data elements that are required to be in our system. We actually get that imported directly by verifiable into Salesforce. So that is also there, the issue with that is since my team, they’re performing the psvs when we have a large volume, of course, it’s sometimes hard to meet… turnaround times under 30 days, right? Because of large volumes, especially with reprints. There are some months that are higher than others because, you know, due to maybe expansions or maybe, you know, network, you know, network expansions and so many other factors, right? Sometimes there’s network adequacy, whatever’s needed. But so.
Scott Everline (08:00) My.
Erica Sagastizado (08:01) concern is making sure that when we get those files processed within certain time frames, of course, within the three years when they’re up for re, creds, not going over the three year mark and just being in compliance.
Jordan Tantleff (08:18) Absolutely makes a lot of sense. And then on the ongoing monitoring piece, we’ve had some conversations with health plans where they’re also doing this ongoing monitoring work for their delegated network as well. Is that the case for you all or you?
Erica Sagastizado (08:32) Guys, no, we delegate ongoing monitoring to the delegated health systems.
Jordan Tantleff (08:35) Okay. Got it.
Scott Everline (08:39) Erica, on the PSV side, I thought verifiable was a cvo and they’re doing psvs. Why is your team doing psvs as well? No, so.
Erica Sagastizado (08:48) We don’t contract with them for their cvo side. Okay. We only use them for their platform system. So they have like those web crawlers already in the verifiable system and they’re just a click away.
Scott Everline (09:08) Okay. So essentially your team members are going in and kind of initiating automated psvs, verifiable’s platform is doing the web crawling, but your team is then bringing everything back in packaging it, getting it ready for committee. Yeah. But like a license verification won’t happen unless somebody on your team is kind of pushing the button to get that initiated.
Erica Sagastizado (09:30) Some of them aren’t like some of those are already initiated automatically. The only thing that they actually do run might be maybe an education verification, mpdb but licenses are usually already ran. Okay.
Scott Everline (09:47) And so it sounds like the full credentialing workflow then is happening in verifiable you’re not taking the results of the psvs and then tracking and managing the credentialing process in Salesforce.
Erica Sagastizado (10:01) No. So it’s actually in verifiable, okay. Okay. That tracks.
Jordan Tantleff (10:10) I guess is like in these evaluations, is that kind of the relationship you’re looking for between a vendor and your team?
Erica Sagastizado (10:17) No. So right now, we’re looking for a cbo, a true cbo option, right? Not where the team is still processing.
Jordan Tantleff (10:28) Absolutely. Okay. So we’re aligned then. So medallion is an ncqa certified cbo. So we would handle the end to end credentialing for you all in platform. We’re averaging turnaround times once we have all that provider data imported from caqh, averaging a turnaround time of, you know, point eight days. On average. We would contract to turn around those ncqa compliant cred files in five days. I’m sure this will make you know, more sense how the workflow works within the process. Once Scott flips over to the demo here. But one thing I’d also like you to understand is, you know, after the demo, I guess what does the kind of decision process look like typically on your side? Are there other stakeholders that are going to be looped in at any point that we should be aware of and kind of game planning ahead with you all, so.
Erica Sagastizado (11:16) Right now we’re assessing, so that’s why valer and Chris are on the call. So we’re assessing and we are going to review other vendors as well. There’s a few things that we want to look at internally just to make sure that it works for provider partners.
Jordan Tantleff (11:33) Makes sense. And the useful next step if we need, typically, we loop in like our head of technical solutions, if we need to start kind of scoping out what integration would look like, whether that’s you know, via API or, you know, to Salesforce in this case, so we can start those conversations as well whenever you guys are ready to kind of kick that off. But Scott, any other questions I guess you have before going into the demo side here?
Scott Everline (11:58) Just on the delegates… as far as the delegated roster piece goes, is that something verifiable is touching from a platform perspective or that’s going?
Erica Sagastizado (12:08) Directly into Salesforce. So, we actually have a team that handles that. That is, we actually have a provider data team that they basically handle all the roster loads.
Scott Everline (12:22) And that goes directly into Salesforce. Yes. And.
Erica Sagastizado (12:26) that goes via mass import. Okay?
Scott Everline (12:32) Perfect. The stars are aligning.
Erica Sagastizado (12:37) And you guys offer facility credentialing as well as part of the cbo?
Scott Everline (12:42) We do, yeah. On the facility piece… are you all like what’s that look like from like application gathering to like, because there’s not a caqh equivalent, right? For facilities. So, what’s that process?
Erica Sagastizado (12:58) Look like we have a pphp facility app that we use there. We have different requirements based on different facility types, right? So that would always be different. We do run mpdbs license verifications. We do a lot of the basic sources. We do verify insurance, WNI, so those things we do require that during the processing of the application, N, pes verification. And so there we have a list. So if it comes down that we are moving forward, there are a list of things that we would require by facility type.
Scott Everline (13:44) We’ve seen those grids multiple times.
Erica Sagastizado (13:46) Right. Okay. Yeah, that’s.
Scott Everline (13:47) exactly. Yeah. Like an ambulatory surgical center needs these following requirements, right? And here’s the standards like they need a site visit, if they don’t have a certification or a license or, yeah, and,
Erica Sagastizado (13:57) all of our facilities are CMS certified, they have to be. So that would of course, waive the site visit requirement. Perfect.
Scott Everline (14:07) Yeah.
Erica Sagastizado (14:07) It.
Scott Everline (14:08) makes life a bit easier for everybody. Yeah. So, is verifiable doing anything with the facility credentialing today? No. Okay. So that’s all on your team? Yes. Okay. Cool. I’m happy to run us through a demo. If you all want to go through that, you can ask me lots of questions as we do it.
Erica Sagastizado (14:31) Yes, of course. Okay.
Scott Everline (14:33) Anything else you wanted to toss out there, Jordan before we?
Jordan Tantleff (14:36) No, I think this is a good starting point, okay? Cool.
Scott Everline (14:41) So, I’m going to speak in some theories a little bit, right? So this is actually the live platform. So before I even start talking about theories, but I’m going to visualize what I would think like a world with Salesforce understanding that you all are starting with providers getting loaded into Salesforce and then that kind of triggering events downstream, and then data coming back into Salesforce at the tail end. So think of Salesforce as kind of the bookends if you will, right? So the medallion platform is bi directionally API enabled. So we could take data coming from Salesforce. So thinking like Salesforce initiating a request for a credentialing event through an API, right? So not somebody coming in and manually loading a file just to give you a little bit of a visualization of what that would require is for the API call, we need to know the provider’s caqh id, the provider’s npi and then their first and last name. So that would allow us to initiate a credentialing event within the platform. If you have a specific email that you want us to reach out to, or a provider contact for credentialing contact, we can take those in as well. A lot of organizations say, just use what’s in caqh. Some people say, hey, we have a very specific contract person at this practice. We want you to reach out to them either. Or if you give us this, we will use it. If you don’t we’ll leverage what’s in the caqh profile.
Erica Sagastizado (16:02) And this would be directly extracted like from an extract file directly in Salesforce that you guys would just pull? Or how would that work it?
Scott Everline (16:10) Could be an API. So we could actually call directly so no one’s picking up a file and formatting things, right? If you wanted to get your hands on it. I know some orgs want to have control, right? Because moving over to a cvo, you’re relinquishing a little bit more control. So you’re going to be comfortable with us, you could get this and load it as a file. But a lot of customers that are leveraging tools like Salesforce, we’ll just initiate an API call to say, hey, here are the providers we need credentialed. So it’s flexible, right? You could even literally come into the platform and just start the request process on a one by one basis. From that point, we’re actually going to call caqh, we’ll get your caqh instance. Probably not that different from what you’re seeing with verifiable, right? You gave them privileges or they’re calling caqh on your account rostering provider. So essentially, that file will initiate a caqh rostering event. And then we will hit the caqh API and check on the provider status. So we check on like whether or not we’re authorized or you’re authorized to view that provider profile, whether or not they’re attested, if there’s any missing information, right? So if there’s like a gap in work history or we’re missing a Dea certificate, we’ll call all that out as we’re kind of initiating that import, all that’s visible here within the platform, right? So you’ll be able to see what imports have failed, what fields are a result of the fail? You’ll be able to see like I don’t have any here. But like if action’s required, you’ll be able to see the communications that go out to those providers. So that’s all visible here within the platform. And then we’ll store that provider record. Yep. Okay.
Erica Sagastizado (17:47) Question. So, do you guys roster the providers or is that something that my team will still have to do we?
Scott Everline (17:54) Roster the providers on your behalf, we do not de roster though. So if you want to remove that provider from your roster, you would need to take care of that?
Erica Sagastizado (18:02) Okay. And then you guys don’t offset the caqh fees, right? So.
Scott Everline (18:07) Caqh has put in a transaction toll around apis. So you have the provider fees that you pay. And then all of us cvos in the industry now pay caqh a privilege fee of being able to call their apis on your behalf. Okay? So that’s just included in like the standard pass through fee kind of packaging?
Erica Sagastizado (18:33) How much is that?
Scott Everline (18:35) It’s a dollar. It’s a dollar 85.
Erica Sagastizado (18:37) Okay. And,
Scott Everline (18:40) that’s not per API transaction that’s per provider per year. So, if we end up pulling that provider off the roster, we’re not going to pay for that API transaction. So just, I don’t know if you all manage your caqh roster today, like you’re putting providers on and off based on cred cycle, we do.
Erica Sagastizado (18:56) Oh, no, we keep them on and we keep them on. And then we only remove them if we’re terminating them from the network, okay?
Scott Everline (19:05) Are you using their data for other use cases in between those events?
Erica Sagastizado (19:09) No, okay.
Scott Everline (19:11) So you could de roster and save yourself some money.
Erica Sagastizado (19:16) That’s a lot of manual work. Yeah.
Scott Everline (19:18) I could teach you how to do it pretty quick, yeah, I mean, there is an API to de, roster anyway. So basically… as long as they’re on your roster, that dollar 85 would continue to hit on top of the five. I think they’re 555 now… yeah. But that’s like,
Erica Sagastizado (19:36) something.
Scott Everline (19:37) Chris and I could figure out like every six months you’re de, rostering any provider that’s not currently in credentialing, that could be something you do and that would clean up and save you guys a chunk of money anyway. So we’ll store the provider profile here within the platform. So you’ll be able to see the individual provider’s profile, kind of all those key criteria that you’re going to want to be able to see info licenses, et cetera. So kind of like a provider profile that’s coming in off of that caqh import. You can also, so this isn’t the cvo tooling, but you can also see specifically if you ever need to go back and look at verifications that have taken place, you’re able to come in here and see all those existing verifications. So if I want to actually look at the evidence, I could pull up the evidence and look at that information again, not the actual cvo package, but this data is here. So if you ever have a question and you need to go back and look at verifications that have taken place, you’re able to see those here within the platform.
Erica Sagastizado (20:37) Okay.
Scott Everline (20:40) That’s the profile. Like I understand you’re probably not going to do a lot day to day with the profile… any questions or things you would think about as far as like I’m kind of curious from your perspective, how much is your team interacting with the profile on verifiable today?
Erica Sagastizado (20:57) So, I mean they’re very involved. I mean, they’re traditionally processing files. So what your team does is what my team is basically doing in essence, right? Yep. So they screen the apps, they review the apps, you know, and if there’s something that’s missing, they conduct the outreach, you know, and they do all those good faith attempts if anything is outstanding. The way I see this working with the cbo is you guys would only get it if the provider is ready to reprocess, so they would still do screening before it’s sent over. Okay? So.
Scott Everline (21:38) That way you’re not paying for the cbo to work a file, exactly?
Erica Sagastizado (21:42) Yep.
Scott Everline (21:43) Okay. So in that case, ultimately, right? You’re going to be submitting those credentialing requests again through that import template or kind of through a Salesforce initiation, right? Where that’s an API call that generates that. And then this is really like you wouldn’t see a lot of this stuff. This is a kind of a master account. So some of this will be truncated down for individual users, but you’ll be able to see within credentialing… files that are in process. So files that have been requested that we’re conducting the primary source verification stuff on this is an API queryable field. So if you want to be able to like feed back to like a provider portal, the status, you can again, as Jordan said, our typical turnaround time is less than a day. Contractually, it’s five days. So files don’t tend to sit here long enough for providers to be nagging you about where is my file at, right? But if need be, you can come into the platform. You can see exactly where the status is of those files. Not really anything for your team to do here. You’re just kind of seeing what’s in flight, right? Once files are completed, we’re going to move them into the ready status and that’s when those files have been, all the primary source verifications have taken place, all the outreach, although you all would have taken care of that. Say we run into something where there’s additional outreach. We would conduct that. And then we actually do like a final QA. So we have a final team member that reviews those packets, make sure that everything matches, make sure that the sources align with the data that’s being primary source verified, right? Just kind of putting that final bow on the package of the credentialing packet. This is where your team would be able to like look at the files themselves and then ultimately determine which direction they need to go to, from a credentialing committee perspective, whether it’s like a clean file that goes to the CMO or whether that’s a file that needs to go to the credentialing committee to be reviewed?
Erica Sagastizado (23:32) Okay. And when that file is actually completed, how, how’s that credit report sent back? Is it directly? Is it sent back through?
Scott Everline (23:43) Do.
Erica Sagastizado (23:44) you guys like load that into Salesforce? How does that work?
Scott Everline (23:48) So we could, right? So like thinking about how you use verifiable today, essentially, medallion would be doing all the primary source verification. And then we would package up that here directly within the platform. Now, if you want to use Salesforce as your credentialing workflow tool, we can send that packet back directly to Salesforce. And then you’re not interacting with the medallion interface at all. Yeah. And.
Erica Sagastizado (24:14) that’s probably the route that I would want. Okay?
Scott Everline (24:18) So to give you the visual of what it looks like when we return something, right? Essentially, it comes back with a PSV report, just whether or not it came back without any issues or maybe a file came back with some issues. And then you’re going to get the credentialing packet. So you’ll get a summary of all the verifications that took place, the verification date, the status, and then you’re going to be able to, if you’re working in platform, be able to look at each one of these individual components, right? So we need to look at a provider license. I could see a copy of their license. I would see the source, the URL, et cetera. So a lot of the stuff that it sounds like your team is plugging into the packets today, pretty much come back like fully baked, managed in this packet on the platform, they could make notes. So again, if you want to leverage the medallion platform, they could make notes here directly within the file. I can even mention medallion users. So if I saw that Allison was processing something, I could say, hey add Allison, like the verification evidence isn’t clear to me, right? Can you rescan the image or whatever it might be? Typically caught in the QA process, but nobody’s perfect. Right? And so being able to make those notes directly back to the medallion team, I can add additional documents. So some teams have things that they throw in that aren’t PSV related, like customer complaints, right? They’ll include that for the credentialing committee. You’re able to attach those. You can add links to other reports or fields that you want to bring in. So that can all live here within the packet. You don’t want it to be included in future audits. So say you’re audited later. It’s just communication between two cred team members. You can just make sure that it’s a private note. And then that wouldn’t show up on like an ncqa audit process.
Erica Sagastizado (25:56) Okay. I.
Scott Everline (25:57) can also download the file. So I can download a PDF. So if you’re going to do like what you were talking about with Salesforce, we’d essentially send over the metadata. It’s all the information, the verifications, the evidence, et cetera. And then most organizations that do that want to see a PDF of the application itself as well, right? That full end to end. And you want that record in there. The one thing this packet is missing and it’s more for brevity and sanity is we actually include the full caqh application in the packet… as you probably know, those can be pretty lengthy. So we pulled it out of this demo instance. But here, I’m able to kind of jump hyperlink to specific sections of the application. Again. So if I want to jump into evidence which I actually think is pretty cool from the PDF perspective because if you’re managing committee and there’s something that needs review, just be like, hey, we need to go look at a license, not scroll through 350 pages to get to the section that you care about, right? So if there’s an mpdb query, right? We just jump in there and let’s look at it… so that you would potentially export directly into Salesforce as an API feed into the Salesforce instance. But again, you could live and breathe this process on medallion. So there’s kind of two different workflows and we would probably want to spend some time if you guys like what you see today really figuring out what that would want to look like, right? Whether it’s your team does this work in medallion, which is perfectly fine. We have a lot of customers that manage that or whether you want to just take the outcomes and feed them into Salesforce, and then manage the rest of the process through Salesforce. We are indifferent to it. We support both capacity, both workflows. It’s just whatever works best for you all.
Erica Sagastizado (27:40) Okay. Go ahead… for the pass through fees. I saw that there was like the national student clearinghouse, are those fees that provider partners that we will have to pay for? Or is that something that medallion pays for?
Scott Everline (28:02) So, the pass through fees come through to you all, we only use national student clearinghouse. So we defer to proxy credentialing by proxy. So ncqa will allow us to credential like if ama does license verifications or a board does license or education verifications, we will leverage those versus going to the fee for service type pass through fee vendors. So we will use national student clearinghouse when proxy is not eligible or available, and that would be a pass through fee, same thing with mpdb. But that’s a little more standard. Yeah. And there are some boards like, I don’t know if you all board verify your nurses, nurse practitioners. Yeah?
Erica Sagastizado (28:49) So we have a large volume of mid levels. Okay? So yeah, those MP boards, I mean, we have to verify that.
Scott Everline (28:56) Okay. And so you all okay, because those are costly boards as well, right?
Erica Sagastizado (28:59) They’re like 50?
Scott Everline (29:01) Yeah. For whatever reason, I’m not sure why, but, yeah. So those would all come through as kind of part of like the invoicing essentially. Okay? But I wouldn’t expect it to be any different than what you all pay from a pass through fee today. It’s just not a pass through today for you. All right? You’re being invoiced directly whereas it would come through medallion and fed through to you. All. Okay? And then I don’t know if like, for it sounds like you all are doing this because you’re setting verifiable up for ogm or ongoing monitoring, but it sounds like you’re we use continuous query for mpdb. So when we get a provider, we set them up for continuous query. So that supports a lot of the ongoing monitoring aspects as well. Yeah.
Erica Sagastizado (29:49) So all of our providers are on ongoing monitoring through mpdb. Okay.
Scott Everline (29:54) Yeah. So from here, if you’re leveraging the platform, users can then send these files to committees, right? So depending on how many committees you want, we can set up committees within the platform, and then users are able to send files directly to the committee, and then committee members are able to view files within the platform.
Erica Sagastizado (30:16) Yeah, but that’s if we’re using the platform exactly. So with the team, I would want them to work directly from Salesforce. Okay?
Scott Everline (30:23) Yeah. So we would skip this step, ultimately, right? So what would happen is we would deliver the file, the PDF, the metadata that would feed into Salesforce committee would happen off platform. And then ultimately, we would want you all to tell us what the outcomes were because we’re going to store those decisions here within medallion. And then ultimately, that dictates your re, credentialing volumes, right? So we’re then going to know, hey, here are the providers that are scheduled for re, cred for re, credentialing. We start 120 days prior to the deadline with… a goal of delivering or a guarantee of delivering files 60 days prior to that credentialing deadline because there are some, in some communities there’s kind of the outreach requirement around like if you all are doing medicare advantage business, you have to notify members. I think it’s 45 days in advance if a provider terminates from the network. So make sure you have enough time to review those files and get those communications out. There is some flexibility there though. I mean if you’re really like we want them 90 days, we want them 30 days, there is some flexibility, but it seems like most orgs are kind of comfortable landing on that 60 day window.
Erica Sagastizado (31:37) Okay. Got it. Okay. I don’t have any questions, Chris valer. Do you guys have any questions?
Chris Teixeira (31:52) No, I’m good. Seems pretty straightforward. Obviously, it’ll be a little more intensive if we get into it, but don’t want to get too into the weeds right now until we need to.
Scott Everline (32:03) Yeah. I mean, Chris, if it makes you feel more comfortable, we built out a full end to end integration with… optum behavioral health with our Salesforce instance kind of managing all the things we talked about, right? So moving everything from the credentialing workflow from start to when files are delivered to feeding data back out of Salesforce into medallion to receive kind of the final decision making process. So it would not be our first rodeo building out integrations with Salesforce and kind of connecting that. I know verifiable has a particularly interesting relationship with Salesforce. We’re a little bit different, but fully capable of kind of making those connections work.
Erica Sagastizado (32:44) So, I know that other, I know that other cbos they’re able to import when they do the import of the file, they’re able to import the file directly into provider records, whenever those, you know, files are done, right? Is that how it would work with medallion as well?
Scott Everline (33:03) When you say import files directly into provider?
Erica Sagastizado (33:05) Records. Yeah. So basically, like when that credentialing package is done and you guys are like sending that over to Salesforce right? During that through that feed, it’s directly then, or is that like a configuration that Chris would have to do where it’s directly linked into those individual provider records? Yeah.
Scott Everline (33:25) No, it would link to the provider record in Salesforce. So we would link the packet and the evidence, right? Like the metadata, like all the information behind it. And then the actual packet itself, we would link directly to the provider record and what we would use to identify that in most cases like an mpi or a caqh or a combination just to make sure we have unique identifiers. So we’re not like landing on a name issue, right? Like if we had John and we had Jonathan in the packet, God forbid, that would throw something off. So we try to use unique identifiers to make those linkages. Yeah.
Chris Teixeira (33:56) Erica, we probably would be doing something similar in structure to what we’re doing. Now, it would help us have a different workflow, but we would want to keep the individualized events that are being sent over to them as a separate record related to the provider. And so it’s going to look structurally similar from what I’m understanding Scott, but it’s going to be just, you know, obviously no work on your side, it would just be data syncing back.
Jordan Tantleff (34:20) And forth. Okay?
Erica Sagastizado (34:25) All right.
Erica Sagastizado (34:33) I think that is everything so far right now that I can think of. Okay. Yeah.
Jordan Tantleff (34:41) If anything comes up like any other like must have kind of capabilities that we might not have covered today, definitely shoot us an email and we can see if we’re kind of aligned on the expectations of what that would look like. I imagine you guys are having kind of a bunch of these conversations throughout the weeks. So kind of defer to you all on what makes sense for next steps. And when I’m not sure if we want to put on like a, you know, check in like mid April type thing. We.
Erica Sagastizado (35:08) Can and I’m just to confirm you guys said that for data elements, you guys can import data elements into Salesforce. Because if we of course, move away from verifiable, we will no longer have that information, right? So we want to make sure that those data elements are mapped into Salesforce. And of course, we would create those fields, but then we would want, that data imported from caqh. Okay. Yeah.
Scott Everline (35:37) And we even like we’ll use and I don’t know Chris, if you’re leveraging anything like a mulesoft tooling or anything, but we, it becomes like a migration conversation just to make sure that we’re using like the same terminology for boards or the same acronyms for licenses and things like that. Because if there’s a miss, it can cause failure. So we just want to make sure it’s a process to map like our data into the data that you all have and whether we do that mapping before we send it or whether you do the mapping. Once we send it, we want to just make sure that we’re all looking at the information the same way, but it’s definitely something we manage and support today.
Erica Sagastizado (36:10) Okay.
Jordan Tantleff (36:17) Erica, is it okay if I put on like a tentative time on like April seventeenth and we can move that around as needed?
Erica Sagastizado (36:26) April seventeenth. Let’s see.
Jordan Tantleff (36:30) Friday.
Erica Sagastizado (36:36) Okay. Does two 30 work for everyone? Two 30?
Jordan Tantleff (36:45) Are you all Eastern Time? Yes. So I do have a conflict then I’m free at three PM Eastern Time or one P. M Eastern Time, if either of those work.
Erica Sagastizado (36:58) Okay. One P. M Eastern Time works? Okay, great.
Jordan Tantleff (37:04) And, I do imagine obviously pricing is going to have, well.
Erica Sagastizado (37:07) It works for me, valer, Chris, does it work for you guys? Sorry?
Chris Teixeira (37:15) I have a conflict but I don’t know that I need to be on that one. I think that’s more next steps for you guys, you know, when we get some more of the technical stuff, you can, I’ll live back in, okay?
Valair Valentin (37:26) I’m good for that time. Thank.
Erica Sagastizado (37:29) You.
Jordan Tantleff (37:32) I’ll send that out. And as I was saying, I do imagine obviously pricing is going to be an important factor in all this, and I mean, if we want to use that time at that point, if, you know, medallion is kind of one of, the vendor of choices and moving forward, we can kind of scope out what kind of volumes we might be looking at year over year and start working, on pricing at that point. I’m happy to send over like a mutual NDA to get ahead of that and get that in order if we start having those conversations as well. Okay?
Erica Sagastizado (38:10) If you can send that over, that would be great. And then also… a quote of what the pricing would look. Did you send that over by chance? Not sure if we did.
Jordan Tantleff (38:24) I do not believe anything was sent. I know I did, I don’t think fletcher did either I.
Erica Sagastizado (38:31) Know he just, we went over pricing and he did go over numbers, but if we can have something in writing because I do need something to present to our exact team so they can review that as well.
Jordan Tantleff (38:45) Understood. And we’re talking about. So 35,000 providers, do you want to just simply divide by three to estimate? Yeah.
Erica Sagastizado (38:53) Okay. Are you?
Jordan Tantleff (38:56) Guys onboarding a specific amount of providers each year to the network?
Erica Sagastizado (39:01) Right. For initials?
Jordan Tantleff (39:03) That’s what?
Erica Sagastizado (39:03) The layer question right now, the layer, when are we looking at any expansion soon?
Valair Valentin (39:10) We are expanding in two markets, but I don’t have a hard provider account off the top, of my head. We’re still kind of in the early phases, of getting those counties approved. So, okay, we can,
Jordan Tantleff (39:24) we can start scoping out just, the current network as is. And if we need to kind of adjust based on what initials may look like over the next few years, we can certainly do so. Okay. But I’ll start working on that pricing. I’ll get the mda over Erica, and then we can, I’ll send out, the tentative calendar invite for the seventeenth as well. But if anything comes up between now, and then definitely don’t hesitate to shoot us a quick email and we can kind of answer anything async, if necessary, okay?
Erica Sagastizado (39:56) Sounds good.
Jordan Tantleff (39:59) Appreciate you all taking the time today.
Erica Sagastizado (40:01) Thank you.