Transcript
Sami Alouani (00:00) hey, Austin. What’s going on Phil?
Philip Stefani (00:03) How are you? I’m.
Sami Alouani (00:06) good. You know, just watching all the chaos and hoping some of these deals get in?
Philip Stefani (00:12) Maybe this one?
Sami Alouani (00:14) Yeah.
Sami Alouani (00:19) Probably want to cut this part from the recording, of course, always… but yeah, we’ll be excited about this one.
Philip Stefani (00:42) Hey, garrison. Hey.
Jeff Adams (00:43) Afternoon.
Philip Stefani (00:47) All right. We got Jeff in the waiting room and we’re just waiting for Sammy.
Philip Stefani (01:09) Hey, good afternoon, Jeff. Hey, guys. How are you?
Jeff Adams (01:16) Making it?
Philip Stefani (01:18) Are you in Nashville or Atlanta this week?
Jeff Adams (01:22) I’m in Florida.
Philip Stefani (01:23) Florida. Sounds nice.
Jeff Adams (01:27) Just work… all.
Philip Stefani (01:30) Right. We’ve got Sammy Jeff, are we waiting for anybody else from your end? All right. And I know we’ve got 45 minutes on the calendar. Does that still work for you?
Jeff Adams (01:39) No, I got a hard stop at the top of the hour.
Philip Stefani (01:42) Hard stop at the top of the hour. All right. We will cover everything in that time plan for today. We got one new face from the medallion side. So want to do some quick intros there, the goal for today. So we’ve got a call with Kenya later this week to zero in on the workflow pieces for the call today. Jeff, we want to align with you on the current data architecture with modio, the plans as you move that into credstream, and then kind of talk through where medallion would enter there and kind of from a data architecture standpoint, kind of be able to recommend a course of action there and get your feedback on that. So we’ve got Sami alawani from our technical services function to help guide that. I’ll pass it over to Sami for a quick intro.
Sami Alouani (02:27) Hey, Jeff. Great to meet you. I’m Sami, like Phil said, I head up our technical solutions and implementation team. So, what that means basically is if we do end up partnering together, it’ll be me and my team that take the promise of Roi that Phil and team have shared with you to reality so that’ll be both from the technical perspective, you know, data migration, ingestion, et cetera, as well as, you know, the operational and implementation guidance to set you up for success. So, I’m looking forward to the conversation. Thanks Sami.
Philip Stefani (02:56) Perfect. So to kick us off, I think before we can kind of talk through the medallion implementation migration process, Jeff, I know we had kind of talked high level about, you know, in this move to credstream, you were looking to stand up kind of the API first ecosystem. And I think part of that was just moving your credentialing data kind of in and out of different systems you have within your ecosystem. Wondering if you can just kind of walk us through like high level, what the goals were there? So we can speak to kind of how we would fit with that piece.
Jeff Adams (03:30) I know what you’re talking about, man. I’m so sorry.
Philip Stefani (03:34) On the move to credstream, I wasn’t the.
Jeff Adams (03:39) Well, we need to leave credstream out of the whole thing. Just don’t even consider it like take it out of your slides, take it out of your information, take it out of everything. It’s going to be modio to you. There’s not going to be anything at all into credstream. So bringing their name up, even talking about how that would work is totally moot.
Philip Stefani (03:54) Okay. That’s all what I was getting at was, I thought the move to credstream was because of the API functionality and you had like specific goals around where the information was going to be moving. No, no, there weren’t.
Jeff Adams (04:07) No, just the fact they have one… just the fact they had an API that’s why I’m not buying any system without an API.
Sami Alouani (04:15) Maybe Jeff, I can kind of guide us here. So Jeff said another way like when it comes to your integration goals, right? So there’s two parts of this, right? One is going to be the transition from modio to medallion, right? We can talk about the data transformation, like what do we need extracted out of modio into medallion for the purposes of just onboarding and transition? That’s one piece, right? And then the other piece is, you know, being kind of world class when it comes to automating the touch points between medallion, now that it’s the source of truth and everything else, right? Like upstream from medallion, your HRIS systems, downstream from medallion, your, you know, your enterprise data warehouses, potentially, you know, your revcycle systems if you want to push, you know, your enrollment statuses or, you know, hospital application information, for example. So really if you could just kind of guide me to your point credstream aside, you know, a, what’s more important to you to talk about today? The cutover from modio or the API integration. And if the latter, tell me a little bit more about your goals when it comes to API integration. Because obviously you have a very robust library. I just wanted to tailor the conversation to what you need.
Jeff Adams (05:16) So I’ve been with modio for three or four years. There has never been an API or any kind of migration strategy. So there’s not currently one here. Either, it’s a one to one from modio to your system, and that potentially in the future long term, maybe next year would be an API to a data warehouse potentially and that’s about it.
Sami Alouani (05:39) Got it. Okay. Yeah, totally fair. So maybe I can just start by sharing here. I don’t know if you’ve seen our reference doc. I’ll drop it in the chat and then I can also share my screen just to give you an idea of like all of the things that we ultimately can do here. Let me know if you can see my screen.
Sami Alouani (06:02) Can you all see that I can see it? Yes. Yep. Okay. Excellent. Yeah. So, Jeff, one of the most important things you know, from your perspective here is, you know, and keep me honest. But for tjc cred and hospital applications, like talking about the tjc cred side, when you think about a data warehouse, generally, the goal is for, you know, medallion as kind of a siloed system, has the source of truth of information for, you know, like where the heck are we in the life cycle of a cred request, right? Has the provider even been brought on board? Is the provider halfway through? Has the provider’s credentialing been rejected? Or are we waiting on committee, right? Like there’s a huge life cycle of things that happen in the tjc cred process that without, you know, an integration and without access to medallion, the rest of the organization just doesn’t have visibility into, right? And so, one of the most common things that we’ll do is we’ll leverage things like our credentialing apis, or our appointments apis to give you what I like to call like a pizza tracker, right? To show you along the life cycle of credentialing, where is a given provider? And so we’ve supported dozens of organizations in building that out into their data warehouses to marry it up with other information from other systems that other people in the organization care about. So when it comes to creating that visibility that’s you know, frankly in the world of things we can do with our API, that’s one of the easier things. Do you have any questions or want to? Does that resonate? Do you want to talk a little bit more about the weeds there? Just guide me.
Jeff Adams (07:24) Here, we are not a hospital or health system sure. And so, I just want to make it clear we had no, it until five years ago. So there is not a data warehouse even there’s none of that stuff yet. We are so like we’re… just touching it. So all this looks wonderful. Amazing. Oh, great. But I have nothing to add to it. We’re just not there yet. We have no maturity in this area.
Sami Alouani (07:51) Understood. Okay. That honestly is.
Jeff Adams (07:53) Really helpful. Yeah.
Sami Alouani (07:55) Frankly, that’s exciting for me. I love partnering with groups like that where we can build together. So, yeah, heard loud and clear though that, you know, if you need a checkbox of can medallion do it, the answer is yes, when you’re ready for it, medallion will be here to help.
Jeff Adams (08:07) Yeah. I think that’s probably the thing right there is just understanding the capability as opposed to getting to the weeds of where and how. Because like I said, we just don’t have anything there. Yet. One of the things I’m hoping to do with my stack and ethos is my homegrown application is to be able to assist somehow with physicians knowing that they have. So, let me pause a second. I’m never looking at technology for technology. I’m always looking for a problem to solve always. So all the other stuff is just not necessary. It’s just noise to me. And so my problem to solve for in the future is to make sure that physicians through our doctor portal are able to know when, by alerts and alarms, when their things are due somewhere to click and somewhere to fill out. If I can get that in a future state a year from now, that would be heading down the pathway. I want to go, being able to proactively have physicians know when their things are due to them. It’s just a signature. How can they sign? Or there’s a request that comes from medallion? It’s typically an alert via email or some other communication, but it’s on my doctor portal. Instead, they log in. They say you need to click here to update your driver’s license. Click on a button that says the device is on your phone. Oh, I’m on my device. Okay. Click done. Done. Okay. Great. That’s it. Next thing, I need a signature for license in California and it pulls something from medallion and it does something that’s about the things that we’re looking to do in the future state. But at this time, I don’t even have analytics even developed yet at the company I am, so I am at the baseline of working on naturalizing… categorizing and make sure data is tagged correctly. Then we’re working towards a lake. They’ll have either inputs there, either storage and, or apis and then reporting and different tools we’ll pull from those. But once again, none of that stuff is even in place. We’re such an immature data company that has been, that is my big push. That is what I’m working on every day here. Is that kind of stuff? Got?
Sami Alouani (10:37) It, that’s thanks a ton for the reorientation there. So a couple of things I’m taking away from that one just categorically Jeff what your longer term goals are things that we do every day. So the answer is categorically and empirically yes there. And when you’re ready to talk through the details there, let me know. I’ll be your Guy and we can hash that out. Second thing is we understand the fundamentals right now are the focus and that is also something that we’ve got experience with. Frankly, I kind of get excited because, you know, you guys are you are we don’t have the problems we have with groups that are like, I’ve done this for 30 years this exact same way and we have to, you know, break the mold with change management. So we’ve got experience with all flavors there. And the stage that you’re in right now is one that we, you know, I personally actually appreciate working with more. But that said, sorry, go ahead.
Jeff Adams (11:26) No, I’m trying to eat my first time of the day, one bite of chip. So I apologize.
Sami Alouani (11:31) No, you’re good. We all got to eat. We all got to eat… but that said, you know, would it make sense at this point then to talk through, you know, like we can talk about the platform functionality that gets you there in the interim state, right? Like, you know, to your point, ideal state is we have this integration. We’ve got these, you know, the portal, talking to medallion, all that good stuff. There’s a world in the interim where our tool works out of the box to meet your needs such that you can focus your, you know, your resources elsewhere until you’re ready for advanced, you know, integration. The other, the other place we can take this conversation is I’ve got a tailored implementation plan ready for you to show, you know, if you were to move forward with medallion in the short run, what a transition from modio would look like? You know, which of those directions would be most helpful for you?
Jeff Adams (12:14) Yeah, I like the idea there kind of looking at what the things are concurrent state in your core systems and then seeing what that migration would look like from modio?
Sami Alouani (12:26) Excellent. Okay. So we can talk about the modio migration first maybe and then Hasan, have we shown Jeff a demo recently? I think focusing, you know, less on, you know, the systems communicating and more so like meeting the core needs in the interim, working directly out of medallion, you know, the tasks, the checklist, the alerts that Jeff is talking about, would, I think would benefit from a platform demo as well. Yeah.
Hassan Zahir (12:47) I think that we probably should get something on the books for. So Jeff just kind of sees where what exists today because a lot of what he was mentioning wanting to be able to do since that exists in platform, we want to make sure he’s targeting his efforts in the right place.
Hassan Zahir (13:01) So maybe we set that up as a fast follow and kind of walk through what implementation looks like. And then we can schedule some time with Jeff to follow up.
Sami Alouani (13:10) Perfect. Okay. That sounds great. So, Jeff, you on board with that? We’ll use the rest of the time today to kind of talk through this plan that I’ve put together for y’all, and then a fast follow will be, you know, the platform functionality that exists out of the box that you could benefit from while you kind of build the fundamentals you’re talking about building.
Jeff Adams (13:25) Yeah, I think so. I think it would also behoove us to have Kenya… on the call with what you’re talking about there. So the actual functions are what the things are in the box now because she and I were talking often about where we would present this, how to present it. See one of the challenges like all day long, all of us on this call, look at our emails, don’t, we… it kind of runs our day, right? Yeah, it does not doctors… and when you don’t employ the doctors, they never look at it until you make them look at it. So having emails sent to them and this, that and the other that’s not good. It just doesn’t work. So my internal application called ethos, they can’t get paid without using it. You think they’re using it? Yes, they want to get paid exactly. So if we put alerts and alarms in front of them there, they will see it… requesting doctor I need here’s. An email. I need you to do it. I need all this stuff. And then Susie comes back and Susie does it. I need all this stuff and they’re going screw you guys. Susie just asked for it yesterday. You’re asking for it today. I hadn’t seen my emails for three days. So that’s the kind of thing we need to think about is how do we make sure that whatever communications physicians need is going to be in their face in the right time, in the right place? So, I hope that kind of helps in who we are and being a little bit different than dr smith who was just hired by acme healthcare and they don’t have, they have to be on and emails and that kind of stuff.
Sami Alouani (15:12) Yeah, it’s a clear differentiator there as far as your model and we completely understand. And to your point, like there’s one thing even a successful alert, right? So, for example, one of the functions that we have out of the box today is along the lines of AI phone calls and SMS, right? Like we found that that’s a little bit more effective than emails because to your point, the last thing a doctor wants to do is check their email. But even then, to your point, the incentive lies with, hey, great. I got this notification. If I’m having to go to this system where it’s not clear that I’m going to be paid for this action where it directly impacts my bottom line, there’s a less likelihood a smaller likelihood in your business model that they’re going to engage with that. So heard you loud and clear on the distinction there and appreciate the context. And that’s one of the things by the way the AI phone call and outreach that we can provide as well as some case studies for efficacy is something we can share next time we connect with the demo. But that said, can you see my screen here?
Jeff Adams (16:08) I can. Thank you.
Sami Alouani (16:09) Yeah, of course. So yeah, this is a plan I put together for you all with a hypothetical kickoff date of may. And so just to give you the overall first glance here is we’re looking at out of the box 16 weeks and realistically based on what I’ve looked at as far as your SKU mix, the fact that you’re in the fundamental building stage actually helps us in a lot of ways move quicker here. We’ve got less processes to break and we’re more on building processes. So I’m actually even more bullish that the 16 weeks becomes closer to eight to 10 just to give you some heads up. And we move fast in general. And what we can talk about is how can we shrink these things down even further? But just wanted to lay that out. Worst case scenario. We’re talking 16 weeks, realistic scenario. Based on what I understand about your business, we’re talking probably more closely to eight to 10.
Jeff Adams (17:02) Okay. So.
Sami Alouani (17:03) Initially, what we’ll do here is we’ll obviously kick off and then these two phases of scoping and preparation. And by the way, I’m going to actually share this view with you. So you have a direct link to what I’m seeing. And if we do end up partnering together, the link I’m about to share with you would be our live project plan that my team would leverage with you when it comes to the actual execution of the project. So I just dropped that in the chat. If you want to pull it up at any time, bookmark it. What have you? Thank you. Of course. And in, by the way the scant charts is going to give you the high level. But within each of these phases, we’ve got a lot more granularity as far as exactly what it is that we ultimately need from you and your teams and who’s doing what the description of the tasks. There’s a lot of granularity here. So, you know, feel free to look at that here to answer any questions. But generally just want to give you a flavor of what the overall approach would be. So in the scoping and prep phase, really what we’re going to focus on is understanding your operational procedures today, right? Like what are your requirements for tjc? Cred? Do you have any legacy cred files that you’ve leveraged before? Do you have any policies and procedures that we need to read through? So we can figure out what verifications need to be enabled, et cetera. Right? So we just want to understand from your business needs perspective, like what are the things that at a very granular level, you need the outcome to be.
Sami Alouani (18:17) And then once we have that, you know, and for what it’s worth, again, this, we generally budget around, you know, six to seven weeks. Given again, you don’t have, you know, the longstanding processes like I could easily see us cutting that in half and doing this kind of scoping and discovery and preparation in three weeks as an example of how we can move faster but really just deep understanding not technically but more operationally, what are the needs that you need?
Sami Alouani (18:43) Such that we can in the next phase of configuration, build an instance for you that meets those needs out of the box right? Again, this is not the integration stuff. This is just like your core instance of medallion, the knobs and bells and whistles, we need to set up such that the output is operationally what you’re looking for, excuse me, and if we do a good job of this, I’m sorry. Did you have a question? No, and if we do a good job of the scoping and preparation. Again, this configuration phase can easily go from three weeks to three days. We can really squeeze out a lot here. And then this is a really important inflection point right here. So once we have configuration done, this means that you have a fully functional instance of medallion. And now we don’t have historical information. We don’t have your existing doctors yet. We don’t have your data necessarily. But the instance is ready in the sense that you have new providers that are onboarding, you need to move quickly and get those providers tjc credentialed or hospital applications submitted. This is where you’ll be able to do that for those net new providers. So this is generally where we see our customers start to unlock value is at this inflection point even though you can see there’s more of the project to complete before I move forward. Does that make sense like kind of what we’re looking for in the first half here as well as what this inflection point means? It?
Jeff Adams (20:00) Does what you’re saying, I would be cautious here though because again having an existing system with all different parts and pieces already in flight now, I’m not in that business. I don’t know anything about licensing and credentialing. I just that’s it. I’m going to take that. I’m an it Guy. But my point is that I know how much the work that continuously going back for a doctor that was well, let’s stop with that. Anytime there is a process that typically takes 150 days, we’re going to have historical data we need on day one, on day one. So I would not recommend to my staff or anyone else that they start using a system that is while intact and ready to use doesn’t have our partner data in it to use. So, is that what you’re saying? Also even though it is ready on July fifteenth, we still would not kick off anything with any kind of usage until the data was presented.
Sami Alouani (20:55) That’s an, excellent question. So there’s a nuance there, right? There is going to be some organizational core data, right? So the bare minimum data that we would need such that if dr adams joined the organization on June 20 fourth, that we have enough information about eagle in general to perform the credentialing processes. So, for example, your instance is configured with your operational standards with the outputs that you need operationally. And then we have a brand new doctor whose historical information we would pull for example from caqh, right? Like we don’t need your teams or your database’s historical info on that doctor to you. They’re new, right? We bring in their bare minimum information directly into medallion. We trigger an automatic out of the box integration import with caqh that gives us the historical information we need for that provider in order to start that request. So what I mean by historical information is really to your point, like what are those in flight things, right? Right? The doctors that the request where they joined before June and the requests are in flight, then we want to move those requests over. That’s what I refer to as historical information.
Jeff Adams (21:56) Exactly. I agree.
Sami Alouani (21:58) Awesome. And that’s thank you for saying that that’s a really important.
Jeff Adams (22:00) So, Sammy are you saying though they would work in both systems until September 10?
Sami Alouani (22:04) That’s a choice that you have to make?
Jeff Adams (22:06) Oh, yeah. I would not make that choice. I would make a hard cut over and.
Sami Alouani (22:10) We’ve seen success with both approaches. It’s you know, some groups, they have a big enough and distributed enough team such that, you know, they want to, you know, and generally, when folks migrate over to medallion, not only, of course, you know, there’s the tech platform, but operationally our outcomes are generally superior. And so groups are kind of, you know, excited to move over. And so they’ve got a big enough and distributed enough team. They say, hey, you five workout at medallion for new providers, you tend to continue working out of the old system. But again, given your state, your life cycle stage right now, totally understand the desire to do a full cutover. And that is something again, we’ve had success with as well.
Jeff Adams (22:44) And then you can do show ups at the end exactly. Okay. And it’s just, I don’t want to get too in the weeds. I don’t have a whole lot of time here, but I want to ask you’re, not going to say, hey, Jeff. Now for modio, I’m going to need a bak file because we’re going to take that out of their existing system. And now we’re going to try to shoehorn that into our SQL environment.
Sami Alouani (23:09) So, I’m not sure if I’m answering your question exactly and guide me here. So generally, we do have a structure of data that we require for tkc credentialing and hospital applications. It’s really straightforward, right? So if we’re talking payer enrollment or some of the other more complicated data structures, it’s a bigger lift. But yeah, we do generally have a template that we do require populated with that data for the historical providers. But of course, to be clear, you’ll have a technical solutions manager for my team that is a dedicated subject matter expert on that can support you in transitioning that data out of modio into medallion. Does that answer your question?
Jeff Adams (23:44) Kind of so, you know, modio, I know you guys have some familiarity with that and done some migrations for that, right? So I’m going to ask for that from them and it’s going to take them weeks to get it to me. It’s just how things work. And so I get it. If there’s any issues with it, I got to go back to them. It takes weeks. Again, any change takes weeks. It all aligns with their scrums… and with their different, well, I went blank but you know what I’m saying? Just the whole sdlc process. And so it doesn’t say, hey, I need a report and hand it to me that being said, is it going to be more of a like I’m going to have a call with you and a call with them and we’re going to come up with a mapping requirement and that mapping requirement is going to say, I need this data here in this column, this data in this column, this data in this column, this one here and they’re going to give me that report based on that. And then I’m going to give it to you for your ETL?
Sami Alouani (24:48) Nail meat hammer, the latter, yes, that’s exactly the approach. Now, I do want to be transparent with you modio. They have their standard outputs that to your point is just based on their database schema when we meet with them. And we’ve done this before as a third party to guide them on exactly what it is that we expect from them. There is a chance that they’ll charge you for that to be clear. But it is Jeff. Let my PTSD speak for us here. It is almost always worth it because to your point, any changes are very painful and the time it takes is much more costly from an opportunity cost perspective than whatever potential upfront costs they charge you for saying, hey.
Jeff Adams (25:29) Okay.
Sami Alouani (25:29) Excellent. So as long as we’re on the same page there, you’re spot on one of the first things we’ll do in implementation. And honestly, as a sign of goodwill, I’m more than happy to even meet, you know, I’ll meet myself with modio and you even before implementation starts, if we’re on a good trajectory here to get that process started because to your point, it takes time, right? So if you’re you know, after your conversations with Phil and Hasan and team, and you’re comfortable that this is the direction you want to go, let me know and we’ll hop on that call beforehand. I’m more than happy to lead it, run it. And then that way they can be working on it while for example, contractual ink is being sorted so that you can, you know, we can hit the ground running together. So, yeah. Okay.
Jeff Adams (26:10) Yeah. Then I’ll probably ask from them. I want a little test file of your output. And then I’m going to say, okay, great. That’s great. Now pause. And then I’m going to say, then I’m going to wait about three months hypothetically just a couple months and go. Now, I need the latest and greatest of that report we asked for. Yep. Okay. And then at the end, how do we do a true up for that same thing? You give.
Sami Alouani (26:32) it to us and we’ll take care of it that’s it. Okay. Got it. Okay. Yeah. So basically what will happen is and that’s what you just described Jeff is what we consider this technical implementation phase. That is exactly what the process is there. So now there is a world which I recommend where we take and I’m just going to move this hypothetically. If you can still see my screen, I suggest that we move this way back here.
Jeff Adams (26:54) Yeah, I agree.
Sami Alouani (26:55) Such that we can do that in parallel with the operational elements. And then at the end and you’ll see, I mean, you see what that does to the project timeline, it cuts it in half, right? And so then we’ll start with the modio team. Here. We’ll say, hey, modio, give us the data. It’ll take them however long it takes them. Let’s call it halfway point. Here. We’ll ingest it. And then at the end of, this phase, we’ll ask for the same exact structure. Again, they’ll just, they’ll hit run on the same script that they developed to map in the first place. And then in parallel with this training phase, while we’re preparing the operational side, we’ll do one more load of that such that at golive, we’ve gotten on the first cut, but we’ve also got that final cut data. And then you should be trued up and hopefully never have to hear from modio again. Yeah.
Jeff Adams (27:39) Great. And then from a training perspective, I like the fact that you have training way deep towards golive. I don’t believe in any training ahead of time. Interesting enough. And just as a side note, it’s strange how credentialstream… has had people be training already on a tool that’s not going to be implemented until next year like you expect them, they’re going to remember anything. And so this argument back and forth on that. So good for you for waiting.
Sami Alouani (28:07) Yeah. And at the risk of being too transparent here, there is a professional services component there more often than not. And so there’s incentives, there is a quasi incentivization to have multiple trainings because they’re getting paid for it and we don’t do that. So with our implementation package, to your point, we train when it makes sense so that there’s actual retention of that information going right into it. And we don’t charge, their training is unlimited and comes with your implementation package. So we’ll have one training. We’ll have 10 trainings, but we always recommend we do it right before go.
Jeff Adams (28:42) Live, right? Agreed. Okay. And I apologize. I do have a hard stop I’m leading this meeting at the top of the hour.
Sami Alouani (28:48) Yep. Jeff.
Garrison Goodman (28:49) Where do we stand in regards to your understanding of the technical and implementation standpoint? Do we have your buy in? What other?
Jeff Adams (28:56) Things do we need to address? No, I’m good with this. Yeah. Okay. All.
Garrison Goodman (29:00) Right. Well, we know you got to jump. We have another meeting later this week with Kenya. Sounds like we so far have a thumbs up from you. On the technical side, we’re going to make sure on the, you know, operations side that we get a thumbs up from her. And then we’re also working in parallel on the financial side as well.
Jeff Adams (29:15) Okay. Sounds great. Okay. All right, Jeff. Thanks guys. Appreciate your time.
Sami Alouani (29:18) Great to meet you, Jeff. Take care.
Jeff Adams (29:20) You too. Bye bye, cheers.