Transcript
Bradley Eral (00:00) hey, Ryan. Hey, Sean got Brad here with medallion. How are you guys doing today?
Sean Behan (00:09) Just trying to get off of mute in order to do anything.
Sami Alouani (00:13) Yep. I’ve been there one of those days.
Bradley Eral (00:18) No kidding. How’s everything been on your end, Sean?
Sami Alouani (00:23) We’re good. We’re thinking.
Sean Behan (00:25) Everything’s going to be all right. We’re pretty much on track. So we need this meeting to go through, just get an idea of how we’re going to make it happen essentially, but I think on the contract side, we’re just about ready to sign off once we get those final numbers.
Bradley Eral (00:45) Nice.
Sean Behan (00:46) No.
Bradley Eral (00:47) That’s awesome to hear.
Sean Behan (00:51) Brad will be away, so we might not get until next week just to give you the heads up.
Bradley Eral (00:56) Yeah, we’ll.
Sean Behan (00:57) be off on a flight in a couple hours. So I don’t think we’re going to nail it down in, you know, two hours, but makes sense. Probably Tuesday something like that when he.
Bradley Eral (01:05) Gets back. Yeah, no, absolutely. Yeah. Next week’s all the same from our side, and.
Sami Alouani (01:11) we’ll hear.
Bradley Eral (01:12) where you’re coming from? Where’s Brad off to? Beats me. I know he’s got a completely different office anywhere but work, right?
Sean Behan (01:20) Right. But,
Bradley Eral (01:22) I will take your lead. Sean. I know we’ve got a full house, so we’ll take your lead when we have quorum and we can jump right in.
Sean Behan (01:30) Sure. I think we’ve got Nick. We’ve got Ryan, just not seeing. All right, cool. This is probably enough to kick it off on our side just so we can respect everyone’s time. So we have a pretty solid mix on our end product managers, product owners, it infrastructure architects, dev managers. So they’re senior devs there’s a pretty good spread here. Amazing a lot of people haven’t seen it. Everybody’s had access to the API docs. So just kind of walking through what it is and what you do.
Bradley Eral (02:08) Perfect. Well, I appreciate that. And really guys, the goal today is discuss the implementation process. So we come away aligned on who owns, what to expect from a timing perspective, resourcing perspective, integrations, perspective. And then also discuss, hey, long term, what does support look like as we kick off the partnership, right? So, with that said, from our side, you and myself, Brad E roll, director of strategic partnerships here, we have Sammy who’s head of implementations from our side. And then josh is one of our solutions consultants. Sammy will be running point. This is your time team. So interject with questions. But ultimately, the output of this will be a detailed sow that we can put into practice. So with that said, Sammy, the floor is yours.
Sami Alouani (02:51) Awesome. Thanks, Brad. And to Brad’s point, this is definitely meant to be conversational. So please feel free to interrupt and yeah, looking forward to the conversation. But yeah, so as far as implementation is concerned, there’s really a phased approach that we’ve seen success with here. So the most important thing is for our smaller provider groups where we are kind of taking this self serve onboarding process. We really need to get our fundamentals set technically… from the get go. And so the first thing that we ultimately need to do is find a process where you all have decided, you know, hey here’s the subset of organizations that we want, you know, in the sphere of what medallion is going to be ultimately, you know, working for or working on rather. And so that could be, you know, hey, we’ve got, you know, this promotional definition from the marketing perspective where we want to send new customers or, hey, we’ve got this subset of existing customers that are like five providers or less that don’t have an admin, you know, whatever that ultimately is, you know, step one is for you all to kind of define in business logic, what it is that you all are going to be, you know, sending to medallion. And so once we have that, I’m actually going to share my screen here. And just to give a visual here, the first step on the medallion side is, you know, you all are going to ultimately deliver to us this context of who the organization is and some basic information about the organization and the providers, so that we can ultimately automate the creation of an instance in medallion and that’s like kind of, you know, step zero if you will, is identify who we want to send to medallion, programmatically deliver medallion, some information, medallion creates this organization and that’s kind of a recurring process as we, you know, continue to onboard providers. But before we get into kind of like what exactly it is that we need from you all. And of course, you know, we’ll send this out after the fact. Any questions so far about, you know, the approach from day one instead of, you know, which it’s a little non traditional in the sense that we’re not focusing on onboarding individual organizations but rather building a process such that we can automate the onboarding of organizations at scale. So I’ll pause there and see if there’s any questions so far?
Bill C (04:58) I guess that was a question. Your product’s not available individually to providers. It.
Sami Alouani (05:05) Absolutely, is we just need to create individual organizations, right? And so that’s more of a data segregation thing. So, the result of this process is we will create an instance for that provider organization, and then we’ll send the individual providers invites to said instance. But this is really more of a segregation activity than anything. Okay? That’s a great question bill any others before we get into the details of what we expect to be sent?
Ben Newton (05:34) Yeah. I have a quick question just to make sure I’m aligned on definitions. So… essentially therapynotes, just from reading the API documentation, we’re going to be in there with our enterprise key and there will be multiple organizations underneath us. The organization is going to represent what we would call a provider in our system or I’m sorry, a practice in our system. And then that can be associated with many different people, I guess that are looking to get credentialed.
Sami Alouani (06:09) That’s exactly right? That’s the hierarchy for sure. The one key there Ben, that’s not super obvious is that, you know, I don’t know by the way, it makes my heart happy that you guys have already looked at and parsed the API docs that’s great to hear. But the key difference here is before you’re able to leverage the enterprise API key to do all the things and the integrations that we’re going to talk about here in a bit. This process is necessary first because as of today, there’s not this concept of you all like initiating and creating your own organizations via API, though that is something that we’re ultimately working towards. What I’m talking about here is just you all sending us some bare minimum information via sftp from day one to get that org created at which point we’re going to send you back some information about, that org id, that then you can leverage subsequently with the apis that are in the API document and you’re exactly right, hierarchically that you’ll have this enterprise API key and it’ll be mapped and you’ll have like these child orgs that are mapped underneath that. And then within the child organization, you’ll have of course, your individuals, your individual providers. Okay? Awesome. Thanks. Yeah. That’s a great question.
Nikhil Oza (07:17) Yeah. And just from my benefit and I don’t know about others is there and if it’s coming, let me know if possible, we’d like to see some kind of demo, technical implementation demo, walk through the screens and stuff like that, like how it’s going to look and how the data is going to flow. I think at least that will help us tie the API with the workflow and see what makes more sense from the implementation standpoint. And that would also help you know, we have folks from it to understand from the security standpoint, what is going to look like and stuff like that.
Sami Alouani (07:49) Perfect. Yeah. And so if I’m understanding correctly, what you were looking for kind of is like a, process flow diagram that shows the technical flow of the onboarding that we’re kind of voicing over today.
Nikhil Oza (08:01) That would be helpful. Yeah.
Sami Alouani (08:03) Absolutely. So we do have that. Generally, what I like to do is have these conversations so that we, because, you know, it’s not one size fits all, right? And so like through the course of this conversation, I guarantee you there are going to be things that I’m going to need to tweak in our standard process flow. But as a follow up to this call, everything we’re talking about will be memorialized in a flow that we’ll send over. And of course would also be included in, you know, any sort of an sow we put up. Awesome. No, it’s a great call Nikhil. Okay. So really quickly just to kind of cement the type of information here. This is, very high level info. So like this will be like the legal name of the organization, a slug to separate the organization from others. You know, the email suffix that we want to leverage for, you know, for automated outreach. And then the email addresses of the admins. And there’s this is a kind of a somewhat important distinction when we say corporate admin email versus provider email or admin email. What we mean here is if you all, and this kind of ties into the support conversation we’ll hopefully close out the call with. But if you all have, you know, a support organization or a user that you want associated with all of the child organizations, that such that, you know, that person can log in to a given child organization to help, you know, whether it’s troubleshooting or to audit or what have you. This is more of a therapynotes level administrator that would be associated with all organizations. So like generally, we would see, you know, a static email be sent here. Whereas this provider admin email is going to be from the provider group themselves. Like which of the providers are we considering the admin for that organization? That would be able to for example, invite additional providers and the likes, does that distinction make sense? It’s not the most, the best naming convention. But… yeah, I think we got that. Awesome. Okay. Great. So then, you know, so some high level info, the provider admin role, the license type. Are you a do MD, pa, et cetera, npi and caqh number kind of conditional depending on if we want to, you know, trigger automation, automatic import of information from caqh for those providers. And then everything else really very optional. And generally we’ll figure this out during implementation would almost always have some static values based on how we decide, you know, the core kind of mold for an organization would look like under the therapynotes model… that’s it really high level info. And then the expectation. Is, you know, from step one, you guys identify who should be in this spreadsheet as far as organizations and medallion needs to create, you send us the spreadsheet in nftp, we ingest it orgs are created. Providers are invited that’s the highest level kind of flow for the first part. Any questions before we move on to… what happens next? Okay. Sounds good. So, from here, you know, at this point, providers are in platform there’s you know, of course, there’s the enablement elements that, you know, kind of walk them through what they need to do for their enrollments, et cetera. But generally what we’ve seen success with in, you know, in similar groups that we’ve worked with is the concept of deeper integration as we continue to phase into the partnership and so that’s where obviously the endpoints come into play. And so there’s a number of approaches we can take here. A very simple one is, you know, step one, when we have our organization create endpoint, like you all can automate this sftp process, right? That’s kind of a very basic element. Another approach is, you know, you all can start the population of provider profile information, right? So when a provider is in medallion, they have to fill out some information like they have to fill out their name and they have to fill out, you know, their social security number for the purposes of certain payer enrollments. And so, you know, you all can start collecting more and more of that upfront. Such that when they, you know, ultimately enter medallion, there’s more populated. There’s less they do in medallion and more they do in therapy notes. And then that’s generally the theme as we talk about continuing to phase out the approach with the end goal being, you know, the majority if not all of the providers interaction happens in therapynotes. And medallion ultimately becomes kind of a background service where the operational work is done and providers are really living, you know, in therapynotes for their purposes, for the things that we need from them. I’m happy to dive in as much as you all would like here. I just, I think if I had a takeaway, it’s that, you know, we have, you know, the end points to support more and more of that phased integration. And more and more of the workflow being built into therapynotes. It’s a process we’ll work through together throughout the implementation phase. But yeah, I’ll pause. There are there any questions about, you know, or things that you all want to accomplish that you want to, you know, validate as possible floor is yours here as far as information I can provide here.
Sean Behan (13:09) So if our provider go.
Sami Alouani (13:11) Ahead.
Sean Behan (13:16) I just want to make sure. So when our providers sign up, right? We start the whole process, kick it off, set up their, what we would call practice, right? Can we iframe the medallion piece and use a single sign on to just show it within our application?
Sami Alouani (13:34) Not today. So iframe is not something that’s supported. We do have on the roadmap, the concept of single sign on such that, you know, when a provider or if you all like again, we’re kind of just hypothetical here. But if you all had a button in therapynotes that said click here to log into medallion. We do have on the roadmap, the concept of that single sign on that would jump them directly into their profile medallion. So they wouldn’t have to log in again, for example. But the concept of iframing for a number of reasons is not currently supported. And so that’s where the API based integration approach is really is king, right? So that you all would ultimately build, you know, your own front end that is tailored to your provider population within therapynotes, that is powered by the medallion backend.
Bradley Eral (14:23) Yeah. And worth noting. We see like all different variations of this between, you know, kind of the less integrated model to the fully integrated experience, and all the way in between where there’s certain tasks that are best fit in medallion, some of our customers deem, but they have updates within their application to drive high value activity within obviously this case therapynotes. So there’s not one true fits all if you will.
Sean Behan (14:47) I’m just a little surprised that we’re here and we’re hearing that now because when we talked the very beginning, right? We had said that our intent was always going to be, I frame the medallion within the application. They click a button and they can see what’s going on without having to leave therapynotes. Yeah.
Sami Alouani (15:06) And to be clear, I think that might be a terminology thing. So like that is definitely possible, right? Like the concept of them being able to make an enrollment request, them being able to see the status of that enrollment request. And those are all things that absolutely can be done within therapynotes. To be clear, I think the concept of iframing is just maybe just a technical terminology. What’s not going to happen is we’re not going to take all of medallion and just plop it into therapynotes. It’s more so like we have to build the individual activities that need to happen within therapynotes. So that’s maybe just it we.
Sean Behan (15:40) Were pretty clear. It’s the dashboard that somebody would log into medallion to see just living with inside therapynotes like that was our expectation from the beginning. Like not building out a whole set of API calls, getting the response back, building out a UI to display the same stuff that’s available within that dashboard. But as the quick and dirty initial implementation, it was, we’ll build a process to send all of the provider and practice information to you.
Sami Alouani (16:14) And then with.
Sean Behan (16:17) that enrollment here’s your dashboard of tasks to do but not leaving the therapynotes application to find that thing. Yeah.
Sami Alouani (16:28) Understood. And I mean, that’s absolutely something we can explore. I mean, the truth, the true reality on the ground is that the iframe like as of today is not a supported approach, but Brad, if you have any other context there?
Bradley Eral (16:41) Yeah. Just as far as, you know, the way to get there like you will still have the ability, for example, all our HR customers have the dash like a dashboard that shows the, you know, the dominoes piece tracker of here’s. The enrollment status here’s. The existing enrollments. It’s just to Sammy’s point, the mechanism to get there. It’s not a straight iframe model. It’s API based or some of our customers prefer to like have, you know, hyperlinks as like kind of that phase one of like check your enrollment status here as like the crawl if you will before the walk and run.
Sean Behan (17:17) Now, that’s not what our expectations were in any way shape or form, right? Because even when we were talking to josh earlier, that was what we had said was we don’t want to have to leave the application because when somebody leaves the application, they’re going to time out on the back end, come back in, they’re going to lose any work that they had been doing, right? Like the idea was hold them in a single environment… and we were going to have to rebuild an entire UI to make that happen. Because what you’re saying to get that to happen right now is we just have to go straight to run there’s. No crawl walk there’s. No other option than to do a full tight integration is what I’m hearing? Am I wrong on that perspective?
Sami Alouani (18:11) That is technically accurate. I think as far as the concept of if you want the entirety of the workflow to happen within therapynotes, you would theoretically have to jump to the run, but I guess maybe worth digging into a little bit at least for an initial phase, what is your aversion? I guess to… there is a pretty clean cut as far as work being done in therapynotes versus, you know, the work that needs to be done in medallion today. So, you know, if there was a seamless way to jump to medallion at least again, you know, in the interim, what are the concerns with that? Given there shouldn’t hopefully be any overlap. Well there tangibly isn’t really overlap in the work that’s being done. So curious to hear more about the concern of jumping to medallion at least.
Sean Behan (19:00) To start… I’m not worried about the work, right? Like we’re perfectly fine letting the work happen in medallion. In the first part because you guys built a tool, it’s a fantastic tool that can do a lot of things that’s really awesome. And we’d love to leverage that. We never integrate anybody where you leave our platform that’s a standing rule, right? Like when you come to therapynotes, it’s because we are an all in one team platform. When you have to send a claim to a clearinghouse, you don’t leave therapynotes, go to availity and upload your claim. You click a button and your claim’s done, right? That ease of use and that seamless user experience is our hallmark, right? So the idea of a… button, a link, whatever of, hey, there’s something that you can do… to go somewhere else entirely. What do you need therapynotes for at that point? Just go to medallion.
Sami Alouani (20:07) Got it. Okay. So, but to be clear, like from a user experience perspective, let’s say hypothetically we could iframe in it would still be a completely different user experience just like in the therapynotes page. So like, I guess what is the core of the rule there? Is it that the experience needs to feel like a singular experience or it’s that like a new tab doesn’t need to be opened and a new login doesn’t need to happen?
Sean Behan (20:29) The latter, we’re fine. We have dr first as an example, right? The regulations around E prescribing are significant, especially around UI controls UX pieces. We don’t want to rebuild that. They have it certified already. So, you enroll through therapynotes, you literally click a button that says, I want to prescribe, you never leave therapynotes. You stay within our product the entire time you complete the enrollment process, you get certified with surescripts. And then there’s a little new tab on the page that says E prescribe. And it is the dr first sure it is not a perfect therapynotes match for the UI. The UX is definitely different.
Sami Alouani (21:12) But they’re.
Sean Behan (21:13) staying within the context of the patient that they’re prescribing for. They’re never leaving that therapynotes world to do all of it even if it doesn’t look exactly the same. Totally fine with that. But the fact that you’re leaving the therapynotes world entirely and you’re going to any other page, it’s not just a medallion.
Bradley Eral (21:36) That’s yeah. And ultimately… we do get to that fully integrated model, right? We have customers who have that fully integrated experience where it looks and feels like their application never leaving the application. Again. It’s just an apa based model to get there. And then josh, I’ll have you speak to some of the near term white labeling aspects. We see that I think Sean align well with the end vision here. But I consider lower lift items for this initial launch if you will, yeah.
Joshua Levitan (22:09) First of all, apologies, everyone for being on mute and off camera. I’m dealing with some personal medical stuff and was waiting on a callback from a doctor. But yeah, I think Sean, I mean, quite frankly some of this might have been on miscommunication that started with me here. What I recall from the original conversation was we talked about the phased approach. We talked about using a series of white labeling right out of the gate, adding in your logo, adding in changes to, you know, customizing the emails that providers get as the initial phase. And I bel, I believe in that what we had shared is like with other similar organizations to you. We get a lot of benefit from moving through this model. I think at the time a couple months ago when we first talked, I think you had asked about white labeling and the answer or sorry, I should say iframing and, the answer that we give is we were exploring it, but that there were a bunch of other ways that we would usually build up to give the same end user experience of everything being in medallion and the way that we are doing that right now with the best success, that is the best approach we’ve determined on, is with this API based integration, there is obviously a, you know, some, a little bit of work on your side to enable that which is different than the iframe. But we have a lot of market data from experience with other customers. That, that is the approach that is not only best for the end user, but best, for both of our parties. Again, apologize if what I presented as something that was a potential option in the future that we could look into as a one path. It, was misperceived based on my communication as something that was a definite but that’s sort of where we are right now. Truthfully. And that’s been, you know, proven out, by the market, with other organizations we’re doing this with right now, the end goal? Is there the intent? Is there, the, I think we’re talking about the same end division, just a slightly different way to get there. And, and we’re more proposing that we get there methodically and slowly so that we get it right the first time and all learn and collaborate along the way, but also allow you to get into market quickly by leveraging a phased approach that can be stood up in much… shorter timeline.
Bradley Eral (25:01) Yeah. And I guess question for the team, I’ll make sure we’re aligned to this when we say like the goal of iframe in the dashboard, take an iframe out of it. But the dashboard itself, what are the data points that you’d want visible with that iframe?
Sean Behan (25:19) I mean, again, without having the dashboard sitting in front of me, I couldn’t tell you all the pieces to it because again, you guys built a pretty awesome complex tool that can do a whole lot of things, right? There was that left menu that gave you a lot of different screens that you could go through. You could see a lot of different statuses, manage new things, create new enrollments, right? There was again a significant complete product in that dashboard. So if we’re saying that we have to essentially skin an entire product from scratch where we’re just calling apis in the back end that’s not a quick lightweight integration that’s, a full on UX problem to get through, right? Especially if we’re gonna end up making like serial API calls because we have to figure out what’s going on. We have to manage errors on those and downtime like it’s not just a flip a switch kind of thing. So, there’s you know, I think given that we have four minutes, I think we can just stop here and we’ll go back and have some internal discussions to see if we’re going to move forward or not. Yeah.
Bradley Eral (26:29) No, that sounds good. And then Sean, I’ll coordinate a follow up session where we can talk in a little more detail around what this would look like. And, you know, what we see with many of your peers as the approach I’ll.
Sean Behan (26:40) tell you, telling Brad what many of our peers does doesn’t matter to him, right? We, we are therapynotes, we are not all of our peers, no.
Bradley Eral (26:51) That’s, that’s fair. But yeah, I’ll coordinate the follow up session. We can work from there. We, we appreciate everyone’s time today. I think, you know, obviously have a good idea of the implementation itself with the integration piece being the one outstanding item here. So we’ll coordinate that, but appreciate the time guys. Thank.
Sean Behan (27:10) You. Bye have a good one. Thanks all.