Transcript
Umang Mistry (00:00) hi there. Yeah, it’s Umang, good to meet you. Likewise. How are you guys on this Friday?
Brandon Chase (00:08) Doing well, doing well. Where are you calling in from Chicago?
Nats Ewol (00:16) Okay. Nice.
Scott Everline (00:20) My favorite city in the us of a Chicago. Oh.
Umang Mistry (00:23) Really?
Scott Everline (00:24) Yeah, I love it.
Umang Mistry (00:25) What makes it so… good? It’s not.
Scott Everline (00:29) New York. So, it’s not so full of itself. No offense to anybody from New York. I just like, I like the architecture, which feels like a cliche saying that about Chicago. I like the architecture. I like the lake, maybe I just started visiting it when I was like, no, we’re going to get all emotional. I started visiting it when I was like young and just first started getting away from my hometown. So it’s like the first real proper city I saw and so just like built some connection, took my family there last winter for Christmas break and everyone’s like that’s. The craziest. Thing you could ever do is go to Chicago for Christmas vacation, but we had a wonderful time. So lots of love. I can’t afford to live there, but.
Brandon Chase (01:10) Hey, Brian. Hey, there… nats, how you doing… Brian? Is this?
Umang Mistry (01:18) The, is this?
Brandon Chase (01:19) Going to be the team from Brighton today?
Brian Ewart (01:22) I think so. I think so. Okay.
Brandon Chase (01:26) I saw, Megan had asked me to record the call. So I do have the note taker in here and I can send her. She just said, you know, send a transcript afterwards that’s fine for her. So I know she won’t be joining.
Nats Ewol (01:42) But yeah, she’s my PM by the way. What’s that she’s my project manager gotcha.
Brandon Chase (01:49) Okay. So, yeah, I guess if we’re not expecting anyone else, then it might be helpful to just start off with some quick introductions then I can kind of set the agenda and what we’d like to accomplish on the call and go from there. But yeah. So, Umang, and nats, it’s great to meet you. I’m Brandon chase and I am one of the directors of partnerships here at medallion. So you can think of me sort of as your single point of contact for all things medallion and Brighton marine. Keep things simple. You can funnel everything through me. And then I’ll figure it out on the back end and Scott, I’ll turn it over to you. Yeah.
Scott Everline (02:30) Hi. All happy Friday. So I’m the solution consultant here at medallion working closely with Brandon just to make sure all the pieces connect as expected.
Brandon Chase (02:44) Brian, do you want to kick things off on your end? We already know who you are.
Brian Ewart (02:49) Yeah, yeah. Yeah. So for anyone new, Brian, you are deputy general counsel with Brighton marine. And I’m leading the network build effort. And Nat’s, there is Stan Lowe and he’s our chief information officer.
Nats Ewol (03:06) Yeah, this is my Google stuff. Oh, Stan.
Brandon Chase (03:10) We talked to you last time. Yeah.
Nats Ewol (03:12) He did, Stan Lowe. My Google email account is ewalnats, which is Stan Lowe spelled backwards.
Brandon Chase (03:20) Oh, my gosh. That’s hilarious. Yeah.
Nats Ewol (03:23) They didn’t have Stan Lowe at the time, but later on a couple of months after I did this, a friend of mine who worked at Google called me up and said, hey, man.
Nats Ewol (03:32) This hasn’t been signed into yet you want it. I’m like, yep, which turned out to be just absolutely worthless because there’s a minister in Canada who, his name is Stan Lowe, and he was pretty pissed about that because he had initially registered it. So now he just uses it to register for every piece of spam… it’s worthless for both of us and.
Scott Everline (03:57) You said he’s a minister?
Nats Ewol (03:58) Yeah, he was at one point the minister for… police and public safety like.
Brian Ewart (04:08) A government minister, not a minister.
Nats Ewol (04:12) I don’t.
Scott Everline (04:15) know what people’s religious affiliations are, but that’s kind of rough for a minister if we’re talking about?
Nats Ewol (04:19) That.
Brian Ewart (04:20) Yeah, that’s what I was saying. I don’t know if Jesus would sign up for.
Nats Ewol (04:24) National police… dude. What are you signing up for now?
Brandon Chase (04:32) Nats?
Nats Ewol (04:33) I love it. I.
Brandon Chase (04:35) Love it. It works. My name. I don’t think would work so.
Nats Ewol (04:38) Well, no.
Scott Everline (04:40) But there is like a famous CIA operative named chase Brandon.
Nats Ewol (04:47) Oh, yeah. There would be, he’s.
Scott Everline (04:49) a podcast. He’s pretty shady.
Brian Ewart (04:51) Can’t be that good of an operative if you know his name.
Scott Everline (04:54) Yeah. Well, yeah. He’s post. I think he was disappearing a lot of people according to the podcast I was listening to. He comes up a couple times anyway, that’s all right.
Brandon Chase (05:05) All right. Umang,
Umang Mistry (05:09) hi, I’m here with Reid and we’re actually supporting bmi with the tpa transition. My role is the solutions architect. So just sort of keeping an eye on the whole system design, data flows, components, and that sort of stuff. Awesome. Nice.
Brandon Chase (05:30) Very cool. Now, we know who’s who in the zoo and we settled the nats mystery here at least for me.
Nats Ewol (05:40) What?
Brandon Chase (05:41) I propose for today. I know we talked about this on the last call but just kind of to refresh. Obviously, we want to tackle some of the things around the implementation. But with that, we’re… going to touch on data. We’ll touch on workflows, possibly… get into integrations depending on time. And of course, all that in the kind of implementation lens. And I do have a deck that I want to share just for a couple of slides to kind of orient us to, there’s a couple of different ways that we can go about doing this. And I do believe that it will definitely help kind of frame the conversation and to which direction that we want to take this. So, Scott, do you want to start on this slide or would you rather just start on the kind of the two options?
Scott Everline (06:36) No, I mean, I think I could start with this just as a primer, right? I think we talked about a little bit last week, right? Medallion is a bi directional API. So we can take data from upstream that initiates events, tasks. And then we can feed outcomes, metadata attachments, PDFS, back out. On the other side, the way a lot of customers will leverage medallion is we kind of sit in the middle of their ecosystem depending on where that data from a credentialing workflow needs to come from, as well as where it needs to go to, right? So if there’s like a contract management tool that you all are using, that might feed or initiate a credentialing request once a contract is signed, right? That can kick off via an API versus having a user manually go into the platform and submit these requests. And then depending on where credentialing fits and what tooling you all have in place or intend to build, right? Medallion can almost bolt onto the side of that versus being its own independent software platform that users go into. And so Brandon, if you want to jump in on the next slide… we typically see one of two ways that people are integrating medallion into their workflow. And we have some visuals of this too. And so one is really like a system integration where medallion really is that bolt on, right? We’re performing the primary source verifications, and then we’re sending those outcomes and the subsequent data attachments et cetera. Back into the system of record. The other one which I think is the quicker path for a lot of organizations because it’s less dependency on standing up some tooling if you don’t already have tooling in place and also doesn’t require as many integrations necessarily is where users will use the platform, right? So, I know last time we met, we kind of did a high level walkthrough of the medallion software that is kind of option number two where people are leveraging the software and then necessary data or outcomes then feed out of the platform to kick off other events, right? So whether it needs to feed data into a claim system or provider directory or wherever, right? But not necessarily managing the actual credentialing workflow internally. I know you guys are in the process or if I recall, you all are in the process of kind of looking at kind of setting up an ecosystem, a technical ecosystem for kind of managing all of this provider data contracting et cetera. Kind of curious if you are thinking of it as like a one holistic system or is it, you know, bringing together best in class tools and then finding ways to make those systems talk to each other?
Brian Ewart (09:15) Yeah. I mean, I think Stan and I are kind of thinking about this as like the, you know, keep it simple protocol. So my vision is more on the centralized workflow for this being optimal, right? So we’re we’d have everything in one place, you know, if you’re collecting all the PSV into medallion system and we can then, you know, utilize that to operationalize a committee and just kind of push into committee review from there. And then what we were seeing, I think was it last week when we last spoke where we can then also just kind of include that flag of the committee decision, right? When it’s made. That just seems like a really clean way to get to a final credentialing file from my perspective versus trying to, you know, send data to another system that we would have to at this point would have to stand up. Okay? So, so.
Scott Everline (10:22) If I hear, if I hear correctly, Brian, it’s more leveraging the medallion platform kind of as it exists today for the credentialing tool. I think that’s right? Okay.
Brandon Chase (10:31) Cool. Scott. You want me to go to that slide just to show the visual?
Scott Everline (10:36) Yeah, that.
Brandon Chase (10:38) Would be.
Scott Everline (10:39) This one, yeah. So, and this is kind of a reiteration, I think among that’s this is probably more for you, right? Because as Brian and Stan saw this last week, but essentially, as providers are coming up, it sounds like in this case, it’s not going to be new providers as much as it’s going to be recredentials, right? So looking at leveraging medallion to do the recredentialing if my notes were taken correctly. So we’ll take the recreds, you all essentially send that request to us. That could be kind of like here’s our full listing of recreds and here’s all the recred dates and then we just work off of that, right? So we’ll take the entire inventory of files or providers and then start working off of that recredit event. Then medallion will conduct all that primary source verification. Well, we pull the provider data in. So we don’t need a lot of info from you all to kick that off. We’ll extract that from caqh. We will start, the credentialing process. So conduct all the primary source verifications, do all the QA work. And then we ultimately deliver a file in platform that’s ready for an individual to review and then determine where that file needs to go from a committee perspective. And then it basically just then becomes rinse and repeat. And then in this bottom box, it’s like it’s that instance where it’s likely some of this provider data needs to go somewhere else within the ecosystem, right? It’s going to probably need a claims platform. Some of them might want to get pushed to a provider directory, whatever it might be that’s where then the LP, the apis be leveraged to use those endpoints to kind of pull that data back out and move it into downstream systems. So depending on what that is and like, of course, data translation always becomes a really fun exercise, right? So working through that with you all, whether it’s you know, the medallion team doing that mapping or whether it’s your team, and we’re just providing some insights and guidance. So on another slide later on, I kind of talk about what resources we are able to bring to the conversation, right? Whether it’s consultative as far as this is the way the data is structured, provide some guidance. I’d say, you know, architects versus builders, right? Type approach as to who’s taking on what roles in that whole translation and integration piece. Is this making sense? Brian, this is kind of aligned.
Nats Ewol (12:56) with the kind.
Scott Everline (12:57) Of the strategy that you and nats want?
Nats Ewol (12:59) To take, I’m.
Brian Ewart (13:02) going to say, I’m going to be calling him nats forever now? Yeah, he’s a.
Scott Everline (13:06) Big nationals fan is what I thought like, no.
Nats Ewol (13:09) No, I mean, games, but, yeah, it just is, I mean.
Brian Ewart (13:17) You stand about your baseball allegiance to be honest?
Nats Ewol (13:19) Yeah. Well, I mean, at least I’m not a yankees fan.
Brian Ewart (13:25) I’m glad I took the hat off because I was wearing it about an hour ago.
Scott Everline (13:29) Gotta.
Brian Ewart (13:31) go, yeah. So.
Nats Ewol (13:35) So, it makes sense to me from a flow perspective. I’m not, I’m trying to, I have to talk to spi about where we would put… the information once it’s been approved, what we would do with that, you know, it’s not necessarily.
Brian Ewart (14:02) How it works, it’s.
Nats Ewol (14:04) what happens after everything’s done? Like, I don’t I’m I haven’t even began to thought think about how a committee, a credit committee would do the review. I don’t know. They do this on the platform. Yep. Yeah. Okay. Good.
Brian Ewart (14:19) Yeah. So, I think what would be exporting out is providers that cleared?
Nats Ewol (14:26) Yeah. Just the yes or no? Like some type of.
Brian Ewart (14:29) Right. So, right. We’re going to get all the PSV and then it goes into sort of, the committee review process. And then when we go through and say committee says, yes, those providers flow downstream to wherever we need them to go. I think, for spi, that’s our claims processor. So they, they’ll need all of that information, they, you know, who’s credentialed in network, right? Stan then would that?
Nats Ewol (15:01) Come in, but,
Brian Ewart (15:02) whether it?
Nats Ewol (15:02) Comes, right, right?
Brian Ewart (15:04) So that’s the prior directory? Yeah, all that goes to provider directory, I think at in that form because you want the provider directory to, for accreditation purposes, that’s who they’re auditing us on. Yeah.
Nats Ewol (15:18) Right.
Brian Ewart (15:19) For credentialing, they’re looking at the directory and pulling names from there in my experience with those guys, that’s the rule. So, you want that to flow out of credentialing. So, you’re only sending the fully credentialed providers, right? The ones who’ve passed, that mark over into the directory. And it’s going to be the same data that we’ve got coming out of this. I’m.
Nats Ewol (15:45) going to have to make a note and I’m on make sure one of us remembers this is when we talk to these guys on Monday afternoon, that we make sure that they can ingest that feed, yeah, either through an API or some type of something. Because if they’re going to be doing a provider directory, they need to be able to get that. And then we need to be able to push that down in the to fast claims XM, right? Everybody’s calling it facet. So now it’s facet, right? Well.
Brian Ewart (16:14) I guess the thing with, so where I’m kind of working through this on the claim side is they need all of, they need this information to map who is a credential provider, right? And individual level of the mpis, because that’s probably what’s going to that’s what’s going to be on the claim, right? The billing provider, the billing entity, the mpi. But then they also need that contract information that’s going to come out of agiloft. Yeah, exactly. So, they know, how do I pay this? Like, where does this provider live under which contract?
Nats Ewol (16:47) Yeah. In my little noggin, there’s a, if you look at that bottom box, there’s a feed from the provider contracting and the provider director that goes into the claim system and the system of record is actually going to be the provider directory. And that approve of denial file goes into the provider directory and it gets flowed down that way.
Scott Everline (17:04) And that makes.
Nats Ewol (17:05) sense because that’s the way it seems like this path of least resistance and.
Scott Everline (17:10) You, I would think you would want to pull some of the data that comes out of the credentialing process because in your directory, location data is probably you’re going to want to pull from the contract. In my experience, the caqh data for locations can be a little squirrely and it’s going to be everything. It’s not necessarily where your contracted locations are. So, I think you’d want like the tin location, service level information coming from agiloft and that would feed the claims platform. So, facets or what do they call themselves now? Claimsxm sounds like a random thing.
Brian Ewart (17:42) Claimsxm is like that processor specific implementation of facets.
Scott Everline (17:47) Okay. So, like qnext, but claimsxm, yeah.
Nats Ewol (17:50) Okay.
Scott Everline (17:51) So, then you would do that, but out of the credentialing file, you’d probably want to pull their education background, their board specialty because those are things you’re also going to put into the directory. And then of course, like whether or not they.
Nats Ewol (18:05) Yeah, we’ll just have to figure out what we need out of a credentialing file to be able to service either the provider directory or the claims.
Scott Everline (18:11) Platform, yeah. So we just figure out what data is in that file. That would make sense to pull out a medallion and you probably want to feed back to agiloft. If a provider’s been declined because you then need to notify contracting to terminate the contract and, or go to writer wrap. Yeah, there would be.
Nats Ewol (18:27) A business process that says, hey, this Guy, you know, he’s a va, you know, blind heart surgeon. We don’t want to have anything to do with him that actually happened. That Guy killed like three people.
Scott Everline (18:39) A blind heart surgeon, yes.
Nats Ewol (18:41) He was a blind cardiothoracic surgeon.
Scott Everline (18:45) Whoa. And.
Nats Ewol (18:46) the va never knew. Oh, he was at the.
Brandon Chase (18:50) va the.
Nats Ewol (18:51) department of veterans affairs in Chicago, the Chicago vamc.
Brandon Chase (18:55) Okay. Well, I guess I could see that then being a veteran myself and having gone through the care at the va.
Nats Ewol (19:03) So, you know, I’m lucky Brandon in my vamc in Washington DC. I mean, I have some of the best doctors that I mean, as they.
Brian Ewart (19:18) Say, Stan, you’ve been to one va medical center, you’ve been?
Nats Ewol (19:22) To one va medical center that’s.
Brandon Chase (19:24) right. That’s.
Brian Ewart (19:25) right. Your mileage may vary for sure. Drastically.
Scott Everline (19:30) Drastically… I can build out a more like prescriptive like visio style flowchart talking about some of these ideas in a more granular capacity if you guys want me to, if you think that’d be helpful.
Nats Ewol (19:43) Yeah, it certainly would be.
Scott Everline (19:45) I’ll provide some free consulting services. I’ll build out some swim lanes and then throw that on a visio.
Nats Ewol (19:51) Because frankly, I haven’t given this part of it a lot of thought. I’ve been much more concerned with the data ingest from the previous system and stuff like that. So, yeah, that would be extraordinarily helpful, Scott, I.
Scott Everline (20:04) could do that. Scott.
Brandon Chase (20:08) Does it make sense? Now? I could use the transition there about the data to go to the next couple slides… to talk about the data part. You want to tackle that next. Yeah.
Scott Everline (20:18) We could talk about kind of the different methods, right? So there’s a couple different modals that we can use to deliver the data, ideally an API for everybody’s sake. You know, it sounds like you all will be interacting. The intention is to interact with the medallion platform, potentially, right? So there’s probably going to be a little bit of a hybrid, but like the day to day credentialing workflow would be managed within the platform. Again like contracting, azure loft could kick off a credentialing request as you’re bringing into contracting. But since we’re looking at re creds right now, it’s really working off of that existing pool of providers. So when you think about like the credentialing workflow, a lot of that’s going to be going kind of on the left hand side of the screen where that’s platform based, not a lot of technology for you all to build up. It’s really just training people how to use the system. I will say talking about managing credentialing committee specifically within the platform committee members are all over the board as far as their adoption of technology, right? You’ll get retired physicians that are like, there’s no way in hell I’m logging into anything ever. So what I have seen in those use cases is you have like a committee chair that’s running a virtual committee which I’d imagine you all are doing anyway, run the virtual committee. And the committee chair pulls up the platform and navigates the platform live like in a zoom call or Google meet or whatever your tool is, right? And then they navigate and then they can do the final vote and you just log, you record the call and then that kind of covers your, that’s the cya for the committee process. So that’s an alternative that we see quite a bit. And then when we think about like the integration back out, if we determine that like an sftp or a flat file is the best path to integrate with your current systems, we’ll just want to define what those outputs look like. And we can build out custom outputs. Typically what we do is we just pull all the data from our API and then use a like a mulesoft like tool. Forget what we’re using. Now, it’s not mulesoft but to basically map it into the format that it needs to be whether that’s a CSV or excel file or what have you or the other option is just directly pull out of the API. And then I think we would want to just kind of define what data elements. And I have some in my brain already, but like what type of data would be important to pull out of the out of the medallion database and where that would go. So when I build out the workflow, I’ll start to spell out pretty high level, what details I would think would go down to claim XM versus what would go back to agilof, which would probably be very minimal data and just kind of show you guys what that life cycle would look like as the credentialing processing takes place. Okay. Any questions on that? Anything that doesn’t track? We’ve done this a few times. Hopefully that shows, yep. All right. And then as far as resources go, I… almost got it as far as resources go. I hate this slide. Can we skip this one? Yeah?
Brandon Chase (23:28) Yeah.
Scott Everline (23:28) So, yeah. So reporting, yeah, we kind of went through that self reporting, but ultimately, we have team members that we would bring to the table that can help with the data translation, walk you through the apis. We can build the integrations, right? So if you all are saying like we don’t necessarily have the resources to actually build out all of the mapping tooling components, we would just want to sit down with you all and understand what those needs are. And then essentially like add a professional services type component to the contract to be able to work with you all to get that data moved around. And we can leave this deck with you all. So you can kind of skip through it. I don’t know if there’s more slides Brandon, I’m working with one screen today, so.
Brandon Chase (24:10) No, this is it. Yeah, I think kind of the key call out here is that I was going to say I will send our API documentation as one of the follow ups to this call.
Scott Everline (24:24) There’s actually a link in this document in the self service API that should be a hyperlink. Yeah, a hyperlink there?
Brandon Chase (24:30) So maybe I’ll just send over this deck that’d be great.
Nats Ewol (24:33) Yeah, I’ve got, you know, since this is like we’re going to be messing around in a federal system, I’m going to have to send you some security requirements. Just my guess is if you’re soc two type two, you’re iso 20, you’re going to meet them. It’s just basic. It’s the minimum acceptable fedramp stuff. So I’ll send those over there. And yeah, it’s nothing more than, you know, making sure you have this 140 does to encryption data trends and rest, you have, you know, multi factor authentication, your user access reviews, all that stuff like that. So I’ll reply to this and put that in there. We’re all like send, I guess Scott you want the email, yeah.
Scott Everline (25:09) You can send it. I mean, you can send it to both of us. I’ll.
Nats Ewol (25:12) send it to both of you and I’ll and that way we’ll have because we’ve got a record one for our cmmc certification that I, that, we did that. So. Okay, yep.
Scott Everline (25:24) So we, yeah, we’ll fill out like a security infosec assessment. Yeah.
Nats Ewol (25:28) It’s it’s fairly straightforward. It’s just I’ll send you the email and you just say, yes, yes. Yes or,, no, no or whatever or partial or what have, you know, the normal stuff. It’s not very. It’s not any more formal than that. Okay?
Scott Everline (25:42) So, like we don’t have to go through fed ramp hopefully.
Nats Ewol (25:45) God. No, no, no. That’s that’s we’re avoiding that like the plague.
Brian Ewart (25:52) That’s.
Nats Ewol (25:53) what we’re being very careful about how we bifurcate cui, so dod could give two shits about fed ramp. So we don’t have to worry about that. But the system that we’re using claims XM is in a fed ramp Ato environment. So we have to do issas and all this other stuff like that. But I don’t think you guys are going to because you’re never actually going to collect, connect directly to the claims XM system. Yeah. Okay. Yeah, we still have to do the like, hey, you know?
Scott Everline (26:21) Make sense. Anything else that you guys think would be helpful? I’ll throw together a pretty little diagram for you all to look at, but anything would be helpful sort.
Brian Ewart (26:31) Of separate and maybe related but not necessarily part of the, this technical discussion. But one question that did come up when I was talking with some other members of the team. So, for, you know, tricare credentialing requirements, we have certain data elements that we’re supposed to collect for dod, the department of war Dow now sounds like a chemical company whenever I write Dow. Okay. Anyway. And my understanding is that those things are in like the caqh application, but they’re often optional fields. Is that something that you guys can help us support in flagging to make sure that we actually get that as part of the credentialing application? I don’t know what all those fields are as of today, but I’m waiting to get them.
Scott Everline (27:23) Yeah. If you give me a list of the fields… I can, well, one I’d probably do a crosswalk to what’s actually required in caqh to find out where.
Brian Ewart (27:31) the gaps are and.
Scott Everline (27:33) Then I would take back to our operations team and see if that’s something they’re able to like proactively try to like flag. I mean, I guess my question would be a lot of the times I see those are kind of like they’re requirements, but they’re almost soft requirements. Like you’re not going to not credential provider because they don’t have a middle name on their application, right?
Brian Ewart (27:53) I don’t think it’s things like middle name, but I’ll have to, I have to see what I have to get the actual list of things. It’s it’s not, I don’t think it’s a lot but there’s a few that are on. And my understanding is they’re on the caqh application, but they’re not required. So sometimes providers just won’t will skip that for their convenience. Oh, yeah. Right. Yeah. But it’s not like necessarily middle name. It’s other items I.
Scott Everline (28:16) Say middle name because, I had a four week debate with the head of provider services of Tennessee medicaid who actually loved dearly but like we were debating over middle name for four weeks. Like what if you don’t have?
Brian Ewart (28:29) It, right? And he’s.
Scott Everline (28:30) like I need middle name. It’s a required field. I’m like anyway. So I have some PTSD.
Brian Ewart (28:35) Yeah. I mean, I hear you on that. I don’t think my grandmother had a middle name. Yeah. So like, what would she have done? Yeah, I.
Scott Everline (28:44) have like four middle.
Brian Ewart (28:45) Names just pick one up, right? What do you?
Nats Ewol (28:48) In the military, that is a required field and, you know what you have to put in there. Nmi no middle initial. Huh, good to know. All right, Amon, thanks Graham all.
Brian Ewart (29:03) Right. Yeah. So, once I get, that list, I’ll send that over and, we can chat more about it. I mean, again, it’s something that is just kind of a unique piece for us and we can deal with it at the committee level. But I would hate to be rejecting or, you know, cycling… stuff back if there’s a more efficient way to do it early.
Scott Everline (29:26) Definitely. Okay.
Brian Ewart (29:27) Yeah.
Scott Everline (29:30) Stan, are you in DC, proper? What’s that? Are you in Washington, DC, proper you in the city?
Nats Ewol (29:36) Yeah. I’m right outside fort belvoir. Okay in springfield, gotcha.
Scott Everline (29:41) I grew up in leesburg, and I lived in like northwest DC for a while before we moved. We’re in Richmond now. So, all right. Cool. I’ll.
Nats Ewol (29:49) be down through there, not next weekend, but the weekend after brand.
Scott Everline (29:52) New baseball stadium, nice and shiny. Yeah, I saw that my son was there last night. Yeah.
Nats Ewol (29:58) My twin brother lives in Newport news. So, okay.
Scott Everline (30:01) So, you drive through? Yeah, nice up.
Nats Ewol (30:04) In Richmond quite often, there’s a lot of my, there’s a lot of good restaurants in the fans. So I like running down there.
Scott Everline (30:10) Oh, yeah. Yeah. Lots of good breweries and stuff. It’s growing insanely fast. Yeah.
Nats Ewol (30:15) There’s a really good barbecue place down there, Brian. One of these times we have to go down there, we’ll go down there. I can’t remember what the name is?
Scott Everline (30:22) Zzq. Yeah.
Nats Ewol (30:23) Yeah, it’s extraordinarily expensive. I’m like Bam, this is like, you know, black’s expensive. It’s not like faint.
Brian Ewart (30:31) Yeah.
Nats Ewol (30:32) They.
Scott Everline (30:33) so, zzq and there’s a brewery right on the other side of them called ardent, they started their own. They call it easy burger, but it’s like many Z’S, easy burger and they do burgers and hot dogs like attached to the brewery almost like a food truck, but not quite, but it’s like right up into the zzq back lot. So, I.
Nats Ewol (30:53) think if we’re talking about the same place with my son and I went there to eat for lunch, and it was 100 bones.
Brian Ewart (31:00) Wow.
Nats Ewol (31:01) It was like, it was like.
Scott Everline (31:03) natural for Richmond. Richmond’s. Been notoriously cheap. Yeah.
Nats Ewol (31:07) It was, it was like black’s prices from, you know, they’re charging that.
Scott Everline (31:11) Premium.
Nats Ewol (31:12) there for a good barbecue, I mean, it was good, but it wasn’t that good. So.
Brian Ewart (31:17) My, my firm belief on barbecue is like the crappier the place looks, the better, the food usually. Yeah.
Scott Everline (31:26) And I.
Brian Ewart (31:27) I love the, if you’ve ever been out to Kansas City, like the best barbecue joint in the Kansas City area is actually in a gas station, right?
Brian Ewart (31:37) It’s like attached to a gas station, but it’s that’s like there’s other good ones too, but none of the really good. The ones that look nice out there that’s.
Nats Ewol (31:45) that’s not the best barbecue that’s in a lean to… awesome, but you have to get your ass there at like, you know, 10 30, 10, 45. Otherwise they run out of food, but, you know, one of my favorite places is actually out in Chantilly, it’s called willards. It’s over where the Chantilly expo center is or where Ikea is going to be. So.
Scott Everline (32:09) Yeah, I don’t know if you ever go out to loud and I have a good friend who.
Brandon Chase (32:12) I’m here a lot. I’ll.
Nats Ewol (32:13) be there tomorrow, okay?
Scott Everline (32:14) He opened up monks barbecue. I went to high school with them. We worked together really. Yeah, monks is supposed to be pretty legit and they own, they started a liquor company. So they do bourbon and I want to say gin. It’s like it’s not aviation. It’s not the Ryan, what’s his name. It’s another, but monks barbecue. I think it’s in Percival now is pretty legit. Okay?
Nats Ewol (32:38) I’ll be out there. I’ll have to work out to give a better world. Yeah, thanks. Getting hungry. Dang. Yeah, I haven’t it’s.
Brandon Chase (32:50) only 11 30 my time. So, I’m like.
Nats Ewol (32:52) I’m ready to go now. Now. All right? I look forward to it, Brandon, what else? Anybody else got anything else? Yeah.
Brandon Chase (33:02) I just wanted, I just wanted to confirm just next step. So, I’m gonna be sending me the deck which includes the API documentation, Brian you can send those requirements for the tricare providers. Yep.
Brian Ewart (33:13) And then,
Brandon Chase (33:14) appreciate you sending that npi file. I’m like we’re I think we’re pretty close in.
Nats Ewol (33:19) Terms of.
Brandon Chase (33:21) Directional pricing and stuff like that. But I think if you could get me the recred, dates that wouldn’t be too much.
Brian Ewart (33:27) Yeah, we’re working on that. I, I’ll have someone check on kind of when we can expect it to get that. Okay, that data hopefully rather than later, but, okay.
Brandon Chase (33:41) We’re.
Scott Everline (33:41) just keeping the rule of thirds, right? We’ll just say like we’ll assume a third of this book. Yeah, the credential.
Brandon Chase (33:48) One that’s what I did right now. So like that’s what I mean? I’m like we have directional pricing. I don’t think it’s going to change drastically. I mean, it’s it. I don’t think it’ll change the overall contract, right? If it’s like, you know, it’s we’re looking at three years, right? And it’s the number of providers is not going to change in terms of those for the regret dates. It would just be like how we’re structuring the contract in terms of what happens when, which is also to be honest, like it’s not essential because we also have skew flexibility where, you know, let’s say we divide it into thirds and you have it kind of spread equally, the volume spread equally between years one, two, right? You can borrow from the next year, you could push to the next year. It’s all going to equal out anyway.
Brian Ewart (34:37) Right? So.
Brandon Chase (34:38) Brian, if you’re like, you know what? I’d rather, just have it flat across the board. We could structure the contract like that as well. Okay?
Brian Ewart (34:46) It’s.
Brandon Chase (34:47) really, kind of, yeah.
Brian Ewart (34:48) Let me, let me check on a timeline so we can get it soon. Then obviously, that’s more helpful to get us to like, realistic. Yeah. And if not, then, you know, I think, you know, one of just kind of modeling something that’s kind of based off of thirds because mostly like that’s what I would expect is that these are not bunched up in any weird way you.
Brandon Chase (35:16) Know. Yeah. Okay. And then I guess real quick too are, where are you at with the caqh and npdb accounts?
Brian Ewart (35:25) How’s that going haven’t yet? They’ve been, they’ve been emailing me. We’ve also been talking. We, I also talked to them about their primary source verification solution. So I’m kind of like don’t want to fully engage until, you know, I’m ready to tell them that that’s not happening. Who?
Scott Everline (35:44) Are you working with over there?
Brian Ewart (35:47) Warren chang.
Scott Everline (35:49) Yeah, Warren just texted me asking me if we’re hiring. So, I like, I know Warren pretty well, but he is a dog with a bone, so, yeah, sounds like you’re catching on to that. Yeah, yeah.
Nats Ewol (36:04) Okay. At.
Brian Ewart (36:05) Least he stopped calling me three times a day. Now, he’s just been emailing me a couple times a.
Scott Everline (36:10) Week, he, I, he worked for me for a minute when I was over there and he would call people from other phone numbers because they would stop picking up his phone. Like, hey, can I borrow your cell phone? So I can follow up on this prospect? I’m like, no, no, if they’re not picking up the phone, you’ve just annoyed them like that’s. Not right? It’s gonna work very well. So, anyway.
Brian Ewart (36:35) Yeah, that.
Brandon Chase (36:37) We were, we went on site last year with one of the blues plans and that was like the first thing out of the CIO’s mouth was like, basically, do you have anything to do with Warren chang? And?
Scott Everline (36:47) We’re like,
Brian Ewart (36:49) no.
Brandon Chase (36:50) And, you know, but Scott knows him, so they kind of had a little bit of a conversation and, yeah, it, the CIO just needed to vent a little bit basically, yeah.
Nats Ewol (37:01) I’ve run across sales guys like that. I’ve worked with sales guys like that brutal dude. You need to shut the hell up more harm than good giving.
Brandon Chase (37:13) us a bad name, man. All right, guys. Well, I really appreciate it. I know it’s Friday so I’ll cut you loose but have a great weekend and we’ll look forward to talking again. I will shoot this over to you and then Brian, I’ll work with you directly sometime later next week. We’re going to be off site at our qsr next week, but I’d love to just get some directional pricing in front of you for you to react to maybe Thursday or Friday of next week, so I can send some times, yeah, if it’s just, you know, if it’s just you and I, that can want to connect that’s fine. If you want to include the broader team that’s fine too, but I’ll shoot you some options for that. Okay? All right. Appreciate it. Guys. Have a great one.
Nats Ewol (37:56) Let me know if you don’t get them perfect.
Scott Everline (38:00) Yep. I think I saw him come through.
Nats Ewol (38:02) All right. Later. Yeah, you.
Brandon Chase (38:03) guys have a,
Brian Ewart (38:04) nice weekend.