What really makes or breaks an electronic medical record (EMR) implementation? It's not the tech - it's the culture and process behind it. In this episode of MasterMined, Mark Scrivner, Jeff Skillen, and Lee Pepper sit down with Shawn Manis, former CIO of North Point Recovery and Meadows Behavioral Health. Known as a "culture-driven operator and financial waste assassin," Shawn shares practical strategies for evaluating, selecting, and integrating EMRs without torching your team's morale. If you're leading a behavioral health organization - or planning your next tech investment - this episode unpacks the real-world lessons CIOs rarely share: why "plug and play" is a myth, how culture eats technology for breakfast, and what leaders must measure to see true ROI. What You'll Learn: Why processes - not platforms - determine EMR success The hidden costs of "plug and play" thinking How to get buy-in across departments (and why clinical teams can't be left out) The 6-month ROI window and key indicators to track How AI and automation are shaping the future of health IT Don't miss this deep dive into the intersection of culture, process, and technology. Subscribe to MasterMined today for more candid conversations on scaling behavioral health businesses. Learn More & Connect: Snapshot Interactive: https://snapshotinteractive.com Connect with the Hosts: Mark Scrivner on LinkedIn Jeff Skillen on LinkedIn Lee Pepper on LinkedIn Guest: Shawn Manis on LinkedIn Subscribe to the MasterMined YouTube Playlist Join the MasterMined Newsletter: Sign up here
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
Welcome to Mastermind, the behavioral health business Podcast. We go beyond the clinical to explore what it really takes to build, grow and lead a successful behavioral health organization. Each episode features candid, practical conversations with industry leaders, offering strategies to scale your business while staying true to your mission. From branding and marketing to leadership, culture, and compliance, we cover the tools you need to balance care and commerce with confidence. Mastermind is brought to you by snapshot, a digital agency on a mission to serve
with heart, execute with excellence, and build something bigger together. And now. Welcome to mastermind. Hey, everyone, welcome back to mastermind. I'm here with my co-host, Jeff Skilling, founder of Skill Set Enterprise. Hey, Mark. Great to be here. Thanks. And also Lee Pepper, author of the new book, Never Outmatched. Mark, once again, thank you for having me. Great. Well, today we're also joined by Sean Mannus, a culture driven operator
and financial waste assassin who has led tech strategy as the CIO for both North Point Recovery and Meadows Behavioral Health Care. On this episode, we're digging into the realities of electronic medical record systems. How to pick the right one, why plug and play is a myth, and what it really takes to integrate tech without torching your team. Let's get started.
Lee, take it away. Thank you so much, Mark and Sean, I'm so honored to have you here as our guest on mastermind today. And I think one of the things that I wanted to start off with, my first question was just telling just a little quick story. You know, I had just been hired as the CIO, at Foundations Recovery Network, and I met Sean Mannus, who at the time was our tier electronic health records administrator. And I knew from the first week that I was there that Sean just had a really bright future because we were trying to figure out our phone system, and it wasn't even Sean's responsibility.
And we were working late into the evening trying to figure out how to get the display set up. And he was just right there. Step and I and I knew this is the person that will figure it out. He will never be outmatched. Just put another plug in for my, that was very simple. And I think that that is I think that's one of the things that I was so honored to have him on today, because there are so many things changing in our world. And whether it's, you know, tech or whether it's digital marketing, and you have to have somebody like Sean who is going to always figure things out.
And so, Sean, welcome. Thank you. I appreciate it. And I remember that night. I think it was a Tuesday night. Yeah. Sounds close Tuesday Wednesday Thursday. Well, listen, one of the first questions that we had was that when you're thinking about the behavior health space, did you, when you were younger and going through your education and then your first couple of jobs, did you have in your plan on your bingo card, so to speak, that you wanted to be a CIO? It was actually my time at foundations, with you and Rob and Richard.
Seeing such young sea levels, I was like, oh, I always expected sea levels to be, you know, in their 60s and, you know, tanned suits. And here we are with a bunch of, you know, late 30s, early 40s kind of trailblazers who are really impressive and what they've accomplished. And I told myself in that moment I wanted to be a sea by 40. Excellent, excellent. Well, you made it. I did, by three months, thanks to you. I actually, you know, this is the first time we've actually had an assassin on this show. And, and so, I mean, part of what I'm really curious about is, like, based upon.
I mean, so now we put you in the ninja assassin category and get it done. Category. As you look, as you look back at your sort of experiences, like, what's a personal lesson that you've learned on this trajectory that either you feel like you'd like to share with us or you'd like to share with our listeners out there that that we could all take away from. I mean, maybe it's cliche, but no, as much as you can. I think, you know, knowing your tech stack even outside of it. Right. What is your marketing team using? What is your biz dev team using? What is your, you know, clinical team using HR and so on.
You need to know all of the tools in their ecosystems, predominantly just for, scalability purposes. Right? There's a lot of crossover and tools and you'll have redundant tools, redundant solutions. So you've got more money going out the door. You know, you've got disparate data in different systems that may even conflict with each other. So you don't have a single source of truth. So I think that's probably the biggest thing that I've picked up on. And that financial waste is actually, you know, sass and perspective is not just the financial piece, but the data consolidation and scalability piece.
Do you mind if I follow up on that just a little bit, because you've actually brought a perspective that I wasn't expecting. So a lot of times CIOs, what they when they look at something is they have an idea of how they would like to build their tech stack and what I heard you say was that you're actually starting with what people are already using and how to make that work. I mean, that's let's talk about the difference in perspective there. Yeah. I think, you know, they're the experts, right? They're the leaders of their department or their vertical. And so they've even if they don't have a technical background, they can tell what works for them. And so to come in, you know, guns blazing, ready to make every tool,
your preferred tool could backfire, right? Maybe it works for integration purposes. Maybe it's good for reporting purposes. And those are important. But you got to get the data in first and you got to have a happy culture. You got to have a happy staff. At the end of the day, if they can't use it or won't use it, you know, the domino effect of those problems, you know, is untold. I think that is really sort of a very underappreciated aspect in terms of is like, we're going to create this great data utopia, and then we're going
to force people to use the tools that we want them to use. I think that perspective is really refreshing. Yeah. I mean, Sean, you've worked with some really impressive companies and really impressive teams over the years. Like, I'd be interested to know, like, what do you love the most about this profession? And like, you know, and again, the cliche answer everyone will say, but you know, I, I to deviate for a second. Grew up in a helper family. My dad was a fireman. My mom was a nurse. My sister actually is, a master's level social worker.
She currently works for the VA as the Chief Experience officer in North Carolina. So granted, I did not go into the clinical or medical side, but I kind of chose a helping profession, just maybe by default. And then getting that call to come into the behavioral health care world, it was a nonprofit, government funded in South Florida. You know, sadly, a very, very hard population to work with. And, I kind of saw two ends of the spectrum, having grown up where I did versus where I ended up getting my first job in this industry,
it was very eye opening. And to see people getting help that needed it and understanding that there is nothing wrong with them, that, you know, they've made choices or that choices have been made for them by outside factors. We've still chosen, you know, as a society to put the resources out there for them to get the help they need. And it, you know, spending 25 years in that role was, life changing. Yeah. And, Sean, if I could just do one follow up question to like, you know, being a CIO or in technology in any company is sometimes a thankless job,
like you, you know, when things go right, sometimes can be you can be the it's sort of like operations. But, you know, when things go right, you're the hero. But, you know, when things go wrong, it's definitely, big spotlight on you have how have you dealt with that stuff, that kind of pressure over the years? I think I got very lucky in my first IT role. You know, my job was at that time, bottom of the totem pole. I was literally making Ethernet cable at a startup for, you know, the 200 people
we had just hired, you know, plugging old school phone box systems in and so on. And so one of the things that my, supervisor at the time told me was, it is a thankless job. Everything's an emergency, even when it's not. And it's a lot like being a firefighter, which my father was. So I say it with respect. I know it's a little less than that. But, you know, the bell goes off and you have five minutes to fix that kind of thing. And a lot of times you are blamed for things outside of your control. When Microsoft goes down
or when you know your internet service providers having issues. Right. It's like it, fix it. I think you have to have a thick skin in that regard. And also be a good educator. You know, you don't have to browbeat people with tech speak. You don't have to belittle them for not knowing what's going on. You want to look them in the eye and say, here is what we're experiencing. Here is why we cannot help at this time. But the second it is back up and running, we will let you know and just, you know, communicating to the point where they feel like, you know,
you have enough to offer them that they're not just sitting in the dark waiting for the magic wand to happen. Yeah, man, that's refreshing to hear you say that. That's a great approach to so thank you. You know, Sean, we're going to get into, you know, how to select an EMR in EHR. But one of the comments that I wanted to get you to respond to before I asked that question on, on those specifics, is that I think that technology can solve a lot of problems, but sometimes from an IT perspective, as a CIO, we you know, we
we have to be careful that we don't come in and just say, oh, yeah, this platform is going to solve all your problems. And I think that's one of the things I've witnessed you personally. And certainly the way that I operate is that we have to understand what the business need is first. And so it's to me, it always starts with the process. Like we can implement anything, but if your process is broken, it's not going to solve it. And I think that as we get into talking about EHR and EMR, I would love your your perspective on why so many implementations seem to go poorly. Yeah, I mean, the short
answer, since I know we'll get to it later is exactly what you said. Process comes first, you know, I think it's a process people tech sort of order. Digitizing your real world processes really only makes them worse. My favorite adage or metaphor for this is if you take a piece of paper, you can write in the margins, you can flip it over and write on the back. You can't do that with technology, the fields or the fields, the systems, the system. So that's where you run into trouble. If you have bad processes, how are those going to translate to a world where you're locked in to the actual workflow that was designed?
And you know, Sean, you know, you and I, we worked, when we sold foundations, and we were traveling around looking, you know, you know, working now with some new sister companies. And that was a common refrain that they hated the system. They had kind of been dropped on them and they weren't able to. And that's where it kind of really resonates with. That's probably why a lot of owner founders wonder, like, well, I just implemented this tech solution. You know, I talk to all these different groups and they said, this is going to solve my problem. When that wasn't their problem. The problem was understanding like, what is their process first?
Right. Yeah. The culture will eat technology all day long. Boy I love that quote. That's a great quote. Yeah, I was going to stick with the, the the process people tech. It's like I mean that's bumper sticker worthy. Yeah. I think it's like, yeah, it'd be really nice if people could actually boil it, boil it down because as not to be overly reductive, but that's really the way it works. And we often see this thing inverted like that. I do want to jump into the EMR thing because, I mean, you've got a lot of experience. And I've also rarely have I worked with a company where people love their EMR.
Rarely, if I worked with a company where they feel like everything is working very smoothly and is like it becomes the thing that everyone sort of rallies around hating so is like, if you were to be, you know, parachute into an organization and say, we really don't like our EMR, we know that we need to make a change. How do you prepare people for that? And it's like, what's what's the approach before we even get to tactics? It was just like, how do you prepare people for that? And then what's your what's your sort of angle? Yeah. Especially if I'm truly parachuted in. You know, I'll be asking some historical culture questions.
Right. How does this organization respond to change how much changes have gone through in the last 12 to 18 months? You could put in the best EMR in the world, but if they just went through ten changes over the last 12 months, they're probably not ready for it. You know, there is a true breakdown of knowledge that you can take in all at once for all humans, right? We can only absorb so much before we say, okay, I think I'm full. And even though this new thing is great, I don't know if I'm ready for it. So the hesitation becomes, you know, bad processes inside of the system.
That is great, but people don't adapt. And then how do you factor in, I mean, the EMR, you know, is so systemic in terms of it touches on almost every aspect an organization. But yet that is not their full time job. Their full time job is not to learn an EMR. It's not to make it work better. So how does it set up sort of a facilitating role as opposed to just an all consuming role? I think, the documentation piece, a lot of times it is what it is. Right? You're, I hate to say saddled, but you've got your governing bodies,
that state, you know, this is what you have to collect. You've got your payer systems who say, we want this exact information or you're not going to get paid in this order. Yeah. Right. Yeah. And then, you know, and then there's the clinical delivery itself, right. Let's call it what it is. Everyone in this industry is in it for a reason. They want to help other people. They want to facilitate good service delivery. And when systems hold them back, they'll find ways around it. Right. At the end of the day, if you've got something that at least again to say it this way they can tolerate and it flows
smoothly, you will find that they adopt it even if they don't love it. But, you know, ultimately it comes down to having a system that everyone had buy in on. A lot of times there are teams left out in the selection process. Organizations will bring in your compliance department, the tech department, the ops department. And believe it or not, sometimes, if not often, the clinical team is who's kind of left in the dark because we're meeting our regulatory requirements. You know, we've hit all of those, you know, key markers or metrics
that were expected to have once it's launched. But no one brought in the clinical team to talk about the actual flow and the clicks and what it takes to get from, you know, A to L or A from A to P, because some forms are just long. There's nothing you can do about it, right? Yeah. Sean, you, you get the teams all together, you get all the buy in from everybody. Now we've got an investment we're making. We invest in the tech, we invest in the implementation. We invest in all the ongoing training that happens. Like, how have you seen working with your CFO or accounting departments?
Like how have you seen, you measure like return on investment of this implementation? Yeah, I think speed of documentation improvements is a big one. Right. Are you getting your notes in on time? Are you able to do your group notes? You know, are we getting our discharge summaries locked in before, you know, the patient leaves? I've seen a lot of organizations, you know, through peers or even admitting some of my own experience where, you know, we had to tweak, not get documentation and when it was really do. So I think the improvement in documentation times is one.
Certainly, you know, you've got to look at your, your billing returns, right? Are your are your payers happy with what you're with, what you're submitting? You could be Medicaid, right? You could be private pay. You could be insurance based. And, you know, at some point you're sending someone a bill asking for money, and it's got to meet their needs. I think, you know, one of the key factors when it comes to developing the EHR for those purposes isn't to be blindsided by that only, though, because it's not just about getting paid. It is the service delivery piece. It is admittedly internal KPIs and metrics.
And so, you know, it's a it's a complex issue that you're sort of compounding, those elements into one larger goal, which is just the overall improvement of everyone's experience. So from the call center having the right fields to document. And so they collect a good history, right, which oftentimes comes from your referral sources. They're you know, people who are sent over are people who've called in due to your, you know, your online presence. They don't know what they're going to be asked. They just know they need help. And so it's up to us to get good documentation.
Same thing goes for the clinical and the compliance. And you know you can extrapolate from there. But I think a big piece for organizations going into the selection phase is to focus on what they can get into the system so they can get good data out, which is, you know, a tired phrase, good data and good data out. But it's tried and true. Yeah. Let's say that, you know, everything goes perfectly with the implementation training. Everybody's ready to go, and I'm on the executive team. What do you typically say is like, we should start seeing the return on investment in this time frame?
I think, you know, I'd say six months is a good marker that you've seen the needle move. Right. You're going to have the first three months where people are still getting used to it, no matter how good they are at their jobs. And again, they wouldn't be in this industry if they didn't want to be. So they're probably good at the service delivery side, but they're adjusting to a new solution. So I think you're looking at a six month time frame, you know, where you could say, hey, you know, we're getting our documentation and faster our payers or, you know, not kicking back any of our, you know, claims,
I think you also see that your compliance rates go up. You know, that's a big piece, of course, because we're all beholden to somebody. And the compliance side is, you know, that's hard and fast rules. There's no way around those. And I think you'll find that when you start to actually report out on, you know, meeting those expectations and rules of, of of our governing bodies, that those all improve within the first six months, a year, you might be doing something wrong. I don't even want to say that you need another six months to get it right. And I was going to add that into that, you know, being a former CIO, too,
there are these things called error reports. And so if you will document as you're going into your implementation, what are the reports that you and your team are going to be looking at and sharing those with the team, especially clinical team. And then when you're getting into these months after the implementation, like you're expecting to see those er report logs go down. Right. And that's what we're going to measure. As long as everybody knows kind of where what are these key indicators that we're going to look at. I think that then gives the clinical team like because we can't sit there
and do the group notes properly, we can't sit there and fill in all the fields like they have to do that. And if you'll communicate what it is, the 2 or 3 things you want to look at generally they will make sure their teams are well trained and that's what they're focused on. But I think a lot of times we just implement things and we go, problem solved, we have a new HR, problem solved. And then like, no, yeah, that was the easy part. Was signing. Yeah I mean wonderful. Box check. Box check. Check. Written box check.
You know but what's what's interesting and I think what we're highlighting here and Shawn would love to get your take on this. This is an enterprise decision. This is not an IT decision or or a technology decision. Therefore, the enterprise needs to decide what we're going to measure and how we're going to decide whether it's it's successful as opposed to the CIO needs to come in at six months and just say, guys, look at all the things we've done. Look at your problem, we've fixed all your problems. Right. And so then it's like that sets that sets you up on a six month clock to then, you know, basically pull a rabbit out of your hat
when the reality of it is this is an enterprise decision, this is an enterprise rollout, and this is an enterprise opportunity. So how do you take that framing and then put in your lived experience? Yeah, I think it's a good question because I think you got to back up to the beginning. Right. The joke of like, you know, you start writing the check is the easy part, right? The selection process, you know, these are a couple of, you know, cheesy phrases that I use with my team, but, like, you know, you got to slow down to speed up, right? Don't do something twice. You can fix it the first time around. Right?
So when you are in that phase of saying, what tool are we looking for? You're kind of backing up to the biggest level. What kind of organization are you? Right? Are you? Outpatient, inpatient, telehealth a combination are you for profit nonprofit. Right. Are you being, you know, built, you know, for the long haul? Are you being built to sell? Are you privately funded? And, you know, there's maybe no necessarily future decided at that point? You've got to pick a tool that works for your organization for the next 5 to 7 years, right?
Three is too short. You never know where you're going to be in ten. And unless you're and fall into one of those very obvious categories of, hey, we are absolutely going to be around for 30 years and no one is going to touch us. Or we could potentially be, you know, exited by year five, year seven, year ten. Who's buying you? That's the next question. You can't know that. But what systems do they have. And are you going to have to adopt their technology. And it is all cooks in the kitchen. Responsibility. I think you can have too many people in meetings sometimes
I think this is one of those times that that's not true. I think death by meeting is very real. I decline a fair amount of meetings so that I can do my job. But this is one where it is all hands on deck, and you want everyone who's going to have a piece of that pie in the room. No one left out helping to, you know, drive the ultimate decision, and then you're launching. Even without a perfect tool, you're launching with full organizational buy in. You're all rowing the same direction. You've all said this is the one.
And then, you know, from there it's, tweaking. And they all work that way, right? Oh, they all work that way. Yeah. Every organization, every tool, they're all perfect. So I want I want to ask a specific question about, obviously you're very knowledgeable about what platforms are and what tools are available in the market. You know, as as are we. And there does seem to be sort of a put it all in one box category. And then there is sort of the, you know, internal plumbing, multiple tools. Do you have a preference
one way or the other in terms of what drives, you know, a better outcome? I hate to say it, but a lot of times it comes down to money, right. How much money do you have to go? Best of breed. Because you could, if you've got the resources to go. Best of breed. I don't know that there's anything wrong with that. It is more expensive and it is more complex. Most organizations do not operate that way. So I do believe the you know, kind of the opposite is the best approach is what tool can we get that will meet our needs at the 80 to 90%? Right?
I think we've all got enough experience in business to know that 8020 gets the job done. And if the 80 is the, you know, the the confidence of going in and all your needs are met, the 20% is the exception to the rule. It is the third party integration. It is maybe a smaller, cheaper, best of breed solution. But ultimately I think you've got to look at, you know, the tools that are available in this industry are admittedly kind of behind tech in the rest of the world, right? Yeah. There are some great EMAs out there, don't get me wrong. But, you know, it's not like they're playing with the same,
you know, deck of cards or, you know, the same piggy bank that you know, Silicon Valley is playing with. Yeah, I was going to say there is, there was a and and I think you guys have heard me refer to this bit back, you know, when I was at Pro Systems, I was in Nashville at a project management professionals meeting. And you know, ladies, if you're ever looking for, you know, single guys, you know, you can go to a project manager professionals, me. But I was there, and, Mercedes Olivares was the project manager for the skimmer horn Symphony Hall build. And of course, she's doing this great presentation.
And of course, you know, somebody asked a question, you know. Well, tell me exactly what tool you use to manage, you know, your this big project. And she goes, you ever heard of Microsoft Excel? And, it was it was great because I'm like, sometimes we get so worried with the shiny tools. And I think about, you know, Sean and I worked, on a project where we were coming into a new company, and they had purchased Salesforce.com, and for two years they didn't implement it. And Sean and I, we had to go through and we had to make the recommendation that you just you need to kill it because it wasn't going to solve their problem.
It's like it's like when people get online banking and they still are wondering, well, why don't I have any revenue coming in? Well, because online banking doesn't get you a job. It doesn't get it doesn't. It just processes things. And that's where I think people. And so one of the questions I had for you, Sean, is that, you know, when I was at foundations and you were working, on our tier product, I mean, you were the subject matter expert, you could do the customizations. So do sometimes we suffer from over customizing or and it kind of gets a little bit to Jeff's question, you know,
should we just take things out of the box, or should we be looking for a platform that does allow us to, to, to do all these customizations? Yeah, that's a that's a tough one because as you know, you were kind enough to give me a whole year to rewrite R from scratch. That is true story. We spent five years on the out of the box version, and we realized we were outgrowing it. And it was either go spend, you know, a million or more on something new or put my head down, rebuild our EMR from scratch, specific to foundations, workflows.
And at the time, I think it was a huge benefit. And, you know, when we were, sold to us and many years later, just from staying in touch with some of my, you know, my old friends at the org, they were still using it. And, you know, I admittedly self-conscious adulatory pat on the back, but but it matched. Our workflow can work. You do have to have a subject matter expert of your business, not even necessarily the technical. So I was very lucky by no means my a clinician or a nurse, but or an intake coordinator.
But I knew our business inside now from having supported the organization and built smaller custom, you know, objects in the original off the shelf version. I think buying something off the shelf fully never works either with no configuration or customizations. Because most organizations have unique workflows. We all sort of do the same thing, right? But we've got our passion projects, in this industry, people who are focused on, you know, the mental health or the substance abuse
or eating disorders, you know, other process addictions. Right? And they came from a certain school of thought. They came from a certain mentorship line. And so they're going to want to see things they're familiar with that they know work from a clinical delivery perspective. So unless you are opening your doors tomorrow and have no clinical model decided, I don't think an off the shelf product works right away. But that's not to say that you can't. Again, full circle, go 8020. Most tools will provide the basics of what you need to document for compliance
reasons, regulatory your own clinical delivery, and then hopefully the product offers, you know, some customization so that you can tweak it. That last 20% is you tweaking to the things that are special to you and your people and your your delivery model. Well, and I just wanted to add just quickly to I think it, it shows that an organization, no matter their size, they have to have an internal champion, an internal expert. That was one of the problems with the sales force is that they bought it. But then who inside the organization
and I think their response was it. Right. Well, it doesn't know specifically. You know, they were handling their networks, their printers, their helpdesk. They were not Salesforce experts. And so you have to add that into your budget is that you're going to need to have somebody identified to do all the training to stay up with everything and potentially be the administrator. Yeah, I'd love to touch on that for a second, because I do know of a resource, who is on its ninth certification with Salesforce. But he has a behavioral health care background. You know, he's 15 years in, he knows best
of, the intake call center admissions process. And, you know, he's over Reebok's now. And it's not to say he doesn't know the rest of the workflows. He learned the business, but that's rare, right? Someone who is a Salesforce expert and specifically that tool, you know, it's a complex product to develop and you do not get your first certification easily, much less your second, third and so on. So he's a world class guy. And at the end of the day, I think he is a rarity that if you find them and you want Salesforce specifically, great, go for it.
But teams can invest. They can't because I know who you're talking about, you know. And I you know and Dorian started at Foundation. Yep. And he was able to get the training and the support internally to go on. And that's where I think a lot of organizations, they get people and then they forget to, oh, you need to send it to a conference where you need to pay for their training, you need to pay for their certification, and they'll stick with you. And then they'll and they'll become really valuable assets to you. Well, I mean, that sets up the question that I was actually going to ask because, I mean, Shawn, we've talked a lot about, how you've gotten to the position that you're in.
But now let's talk about the position that you're in, how do you make sure that the team that works with you has that same understanding of a business and then understands, because I'm, I'm hearing very thoroughly that it's like you need to understand the business. And then before you make a decision. Right. So how do you make sure you instill that in the team that you currently have? I think it's communication on things you wouldn't usually include your subordinates and which, you know, hopefully I don't scare any of my peers, but I think it's okay to share information.
You know, that's not, you know, private to the C-suite or, you know, the board, right? Where is the organization going? What do we struggle with? What do we do? Well, right. And, the vision that I bring to the team is only part and parcel to what the organization's vision is, not only by department vertical, but an entire organization as a whole. And so, you know, especially with my time at the Meadows, it was, you know, kind of a five year education, things that I admittedly
had learned from Lee and learned from you, things that I had learned from my, my, you know, supervisor at the time, George Meany, you know, mentors that I'd had in the past, Stephen Townsend is one that, you know, people taught me to look at the, you know, the organization holistically and not just how is it supporting, how is it facilitating, but what does the decision we make in the tool we put in? How does it impact the organization down the line, not just from a revenue perspective, but a culture perspective, you know, from a data perspective.
And so I think it is is, you know, you know, as maybe black and white as it sounds, it is just educating your staff on how the organization operates every chance you get. I take a chance to do it in teams. It's one sentence we move on. I, you know, pull them aside and say, hey, the reason we made this decision is X and here's how it's going to impact the organization down the line. You know us not making this decision has this effect. Well let me just follow up if you don't mind. So I hear that and I agree with that. I mean but let me get a little bit more granular.
I mean, do you actually have staff shadow that clinician, shadow that admissions team and just see how they're actually touching the technology or I mean, because because I really think it's one thing to say we made a decision based upon X. It's another thing to say, hey, I actually sat next to this person and I saw what they deal with. Yeah, I won't even take credit for it. I'll give, you know, foundations, the credit for kind of planting that seed is that, you know, we had, you know, kind of an employee placement shadowing program. We sent our staff into the call center to sit and listen to calls.
We sent them to sit with marketing. We sent them to sit with ops. We sent them to sit with clinical. If anything, we did a, you know, a faux admission, you know, walked through the entire process of being admitted, going through that first, you know, condensed. But 72 hour intake process and then sitting in a group, shadowing a group, sitting in graduation, right. Going and sitting with the RCM team and seeing what they deal with. And I think that education is important, honestly, regardless of industry, I think knowing how your business operates, and I do have a bit owning
the blinders in a positive way that I did that naturally, being in the role that I was in, it was, you know, wasn't Sean's idea. It was sort of forced upon me by being the administrator. Hey, we're having a problem with the admissions, you know, function. Okay, let me get in there. Oh, hey, you know, my my nursing assessment is, you know, causing errors when I hit, say, okay, let me get in there. And you, you're the rest of your team really should have an opportunity to do that. And I would say that goes every direction that your admissions folks on the clinical side take your red cycle people and, you know, put them with it for a day.
Right. It's you know, you can't send everybody everywhere every day long or no business will get done, so to speak. But I do find there's a lot of value in that education piece. From any angle, you can offer it without hurting your business, you know, you also have the benefit of having superb people skills and not everybody that follow, you know, that that goes into this level of work had that sort of emotional intelligence or the ability to gain trust from people in that environment. Do you is that something you work on with them, or do you actually make that
as a hiring decision so that you bring people in who not only have the knowledge base, but also have more of an EQ aspect? To bring to it? Well, I appreciate the compliment. First of all, I don't know that I was always that way, you know, typical IT guy thinks in ones and zeros or, you know, sort of just sees a problem and wants to execute the completion, you know, of fixing it. I do find that you have to work being very specific to it. No offense to anyone else.
That's common. They're not people. People? Yeah. I actually had an IT person one one time refer to people skills as user interface. You know, not surprising. If you're given a team, if you inherit a team. I've had guys that were never going to be people. People, but they were excellent at what they did and they worked with other IT people. Well, and it's, you know, maybe, silly as this sounds, you sort of hide them from the organization, right? Let them be in the basement, be, you know, with the cockroach spray and dark, you know, tinted windows because that's what they like.
They don't want to talk to people. And I'm picking songs that I was I was picturing Milton. Yeah. Jeff always goes dark. Yeah, yeah. Super dark. But, you know, there are those people who sort of ride the line of being technical with being able to talk to people. And then there are people, you know, admittedly, like me to, to your point, who just are you know, gregarious and outgoing and sort of not afraid of the conversation. And, I'll slip up on my words. You know, I may misspeak. We're all human. I think it's a matter of how do you respond in the moment.
And admittedly, a lot of people and it tend to tense up when they make a mistake because they, in their own mind, say, I have to be infallible. I am the robot IT guy who never makes mistakes because computers never make mistakes in quotes. Yeah, yeah. You know, Sean, you mentioned, just a minute ago, a great resource that you had. Dorian, does the sales force, is he a consultant? Dorian is a full time employee at Karen Foundation. Oh, he is, a former employee of mine during our foundation's days.
And, just, you know, stayed in touch with him over the years. He's here in Nashville, lives down in Spring Hill with his beautiful family. And, he just continues to educate himself and, you know, really find a niche with, with sales force and health care specifically. And he's gone from being an admin to being, you know, a rev ops and BD expert. Yeah. Well, we've I was going to say we drop his, contact information for that. He know that Karen would appreciate that. I don't know Karen like it. But, you know, we'll we'll slip you a great they got a great person there.
Yeah. But yeah, but hey, just with all of these that you've implemented, like, I know there's, typically some most important things that you have to have, and then maybe, like, what do you see? Like, what do you see from like, features and workflows that you have to have. And then what do you see from like the gaps that maybe some of these bigger ones are even missing today? Yeah, I think, you know, I hear the word bigger and immediately my break goes epic, right. Which most organizations are not going to have. It is predominantly medical focus to begin with.
It's also extremely expensive. I work for an organization at one point where we reached out to epic and they literally replied, you're too small to work with, right? I'm paraphrasing, but yeah, you're just, you know, you're not really in our sphere. I think a lot of the tools that are out there, especially in the last few years, tools I had seen ten years ago, five years ago, even they have come a long way. They have really taken the reins of modernizing their products, not just, oh, we're in the cloud, but thinking about third party integrations where it's necessary, being available to APIs.
You know, for getting the data out or getting new data and, being friendly with CRM, if there isn't going to cut the mustard, they all sell them. And some are good, right? Some might meet the, you know, the quotable 8020. But, I think the data that that you get out of there, everyone's got a data warehouse. And if they don't, they should. So that's become an absolute must. So many of these were closed ecosystems. They weren't really thinking about how they were going to get the data out for you, or you were going to get it out for yourself.
And if you did, it was ugly. And there was a lot of transformation and cleanup around that. I think, you know, I like to see systems that have already built in labs, if it's not custom code, but are already working with those third parties, you know, that that kind of run our world, billing is obviously a big one, you know? Right? Wrong or indifferent, you got to have you got to have revenue, right? It pays the bills whether you're a nonprofit or for profit. We all want our paychecks. We all want to keep the lights on. And I think, you know, those are probably the big three to me
that matter most is, you know, your, your, your third party integrations, getting data out into your data warehouse, then being data centric, knowing that you need those for metrics and, you know, and the like, reporting is the last big one. And then billing, where are we today in the behavioral health space with these EMR and billing? Are there, tools that are doing a great job of handling the billing internally? Or are most, organizations using third party billers?
I've seen most using third party Billers. I think there's a couple tools out there. You know, I don't necessarily want to endorse anyone specifically, but at the same time, I think there's definitely a few of the if you Google them, they're on the first page players. Right. They're doing a pretty good job. You know, it might be that you need to supplement with some automations. It might be that, you know, you've got a little more of that, export and re-import to get the data just how you want it. But nothing that's such a heavy lift. It's not possible to overcome most, I think, go with the third parties who really excel, and that's where they focus.
And that's why, you know, you kind of full circle the best of breed. There's a time and a place for it, and maybe your big three are you have a CRM, you have any idea and you haven't RCM solution. Right. And if those three are separate, are they the best at what they do? And do you need the best in that moment, or should you kind of keep it simple and go with, you know, an all in one solution depending on your size and your goals? You know, as an organization for the, you know, near and long term from a from your perspective as a CIO, is it less headache
to have it all three of those integrated, or is it less headache to have the the best individually it's two sides of the same coin, which is a B.S. answer, but kind of true when it's all integrated. The data that goes in at the beginning impacts whether it works on the end. Yeah, right. If you don't have good checks, do you. Yeah. If you don't have a lot of if you don't have good PII going in good demographics that down the line data when it gets to the rev cycle kills your first pass yield.
You're not sending claims out that first time around and then in a meaningful way you're probably getting rejected, right. So you pro is that it's all in one solution and you are in control. Right. And the data set is all the same. You know, as far as the database is concerned and the framing that they put it in, how they modeled it, how you're going to get the data out, or if it's got the built in reports that you don't have to go and custom build. Best of breed has the other side is the integration piece, right. Integration is finicky.
It can be built, it can work great. And then one small thing can change on any one of those systems. And you see a failure at 2 a.m., you start seeing the errors roll in. I think if I had to pick truly just down to like, you know, on the spot decision, I would go all in one for this industry. Right. Most organization options are not US sized, right. They're not HCA size. So they'd benefit from an all in one system.
It's simpler to manage one or to administrators. Max, the data is all in one place. You know, if they did pick the right tool, they still have some opportunity for integration with outside solutions. But, you know, those, those kind of three separate products that are all integrated. The only benefit there is if you've, you know, you've really built a solid integration and can react to it in real time so that you don't lose business data. Don't lose, you know, time to, billing. You know, anything that falls into where your integration fails
biz dev to the call center and then the EHR into the RCM tool. Do you anticipate the, innovation curve actually picking up in the space? I mean, you mentioned you mentioned earlier that we tend to lag some of the bigger developments that are that are happening in software in general. And I think that's true. Even the move to a more open architecture like we're talking about, I mean, it's years behind what we're seeing elsewhere. I mean, so looking at the crystal ball and it's like, what is the innovation curve look like for us? I do think it picks up a few of the, the, you know,
EMR that I've referred to without naming names. I know they're CTOs. You know, I've, I've had conversations with their CEOs and, you know, they have made huge strides in what they're offering built in telehealth, you know, proprietary, video code. Right? You're not plugging in zoom, which is just another third party tool that you have to pay for. You know, built in custom labs, right? They may dump that data out to an actual lab company, but you're not having to do a broken interface where it's just push this button and now you're a window into lab core or a window into quest.
Right? Right. And I think, you know, it's obviously not a buzzword, but I'll say the buzz word of AI, you know, what impact does that have going forward? I don't even know if anyone can predict that it is moving so fast at this point. And what is AI versus what is automation? That's the other side of it. I'll be the first to say, even as the tech guy, I do not think I should be doing clinical documentation. I think that is a human function. Can it synthesize information that you've written in there
and it get reviewed and then approved? Sure, that'll speed things up. But to say that it is just flat out creating notes is not something I'm really for. But then there's the other areas of the business, right? RPA that robotic process automation. I click this button which results in this task, which results in this data, which results in this button being clicked right down the line. That stuff you can automate. And I think we should be automating those things because then everybody benefits. Multiple departments no longer have to feel like they're the one going from button one to button 17.
But I think it's going to move fast. I love what you just said about is it automation because I, I sense that with, with one of my clients is now using the ability for what they're calling a, to listen in and then give the clinician the notes that they have to approve. But I'm thinking, is that anything different than what what you and I were working with years ago? What was it, Dragon speak. Right. I mean, we've always had the ability. This is going back 15 years ago, right? When we had Dragon speak and we were trying. And then the. And the more those little pads, Sean, that we had to like the Topaz thing.
I mean, so is is it AI or is it automation? It is. It's a great question. Yeah. You know, Dragon is a good example of that. You know, natural language processing to your point, has existed for 15, 20 years. And certainly it's gotten better over time. I think where the AI piece comes in is, is, it is still just NLP, the natural language processing, but it's cutting out the ambient noise in the background. It's being able to define who is speaking and what their role is in that, you know, particular situation. You know, are they the clinician?
Are they, you know, a group facilitator? Is it a nurse that popped her head in real quick to say, like, you forgot to take your meds, right. We shouldn't that shouldn't be in the progress note, so to speak. I think understanding that that's where it sort of separates from the old school to the new school, but it's still valid to say what is which. I mean, I'm picking up on a distinction and I think it's fair. It's, you know, the creation of data and then the synthesis of data. Right? It's like synthesis of data. It's like, okay, that makes that makes a lot of sense, but a bit in terms of the creation, it just goes back into good data in, you know, good data.
And yeah, and all of those models, including the big players, right. ChatGPT and Claude and everyone that's out there that we've all seen a thousand stories on, they only are able to provide their synthesize they genetic data that they do because of the data they've received. Right. And we all know they hallucinate and that they can create, you know, poor information results. They're amazingly cool. And they have a real, you know, impact on our future in a positive way. But they're just good data and good data out right now.
You know, scooters are cool, scooters are cool, scooters are cool. And and it's like. But, I mean, not everybody in metro areas, like, yeah, I'll admit, I move the ones that end up in the front of my house to someone else's yard. You know, Sean, you, just stay in on the AI for just a second. You know, in clients that we have in this industry or others, you know, you ask them, you know, how are you using AI? Oh, yeah, we use AI like we use ChatGPT. And, that's a typical response. Like, are there tools out there that you're playing around with and testing out today
from an AI standpoint that you go, I'm seeing some, you know, great benefit here. And we don't want the varnished answer. We want the like, you know, the real deep down. Yeah. True story. Answer. Please stop using ChatGPT in the clinical world. Unless it is your own private instance, because that is not HIPAA compliant. Right. If we're going to talk data security and data safety, you absolutely want to avoid now you can use Copilot, which is built into your Microsoft 365. You've got the VA. You've got. Yeah. Yeah. You're fully protected in that sense.
As long as you are within your, you know, oh 365 ecosystem and it's ChatGPT back. So you're essentially getting the same answers. As far as like individual tools, you know, right now there is a focus on the RCM side of the house. So, you know, tools that, focus on insurance verification, you know, tools that focus on claims, you know, it's going to reduce head count, it's going to reduce processing time, it's going to increase accuracy. And, you know, that's I think a key area where every organization, almost regardless of industry, again, it's it's the automation of is this correct check error.
How can we go get the right data correct. Submit receive rejection. What do we need to correct. Go get the data. Rinse, repeat. A lot of that is going to pay huge dividends. Yeah. There you we talked a little bit about security features and with just ChatGPT, are there other things that like you have to really strongly focus on with the EMR as the year round, like just HIPAA compliant? And you do you actually audit the enterprise to make sure that you're not vulnerable?
Yeah, I will say, you know, I'll, I'll credit where it's due to, you know, former employee of mine, Donovan. Sanchez. Brilliant security expert, someone that I still look at in a way, as my own mentor in that world. And, you know, so much to the point that I promoted him into my role when I departed from the Meadows. Because he's a brilliant man, and he's very good at what he does. And he taught me, a wealth about security in areas I didn't even really want to know. But when it comes to data, when it comes to EMR is right.
Is the data secure at rest and is it secure in transit? That's kind of number one because the data is going to go in regardless. Or is it secure sitting in whatever table or database. Has it been masked? You know, is it encrypted? Is it okay if someone sadly broke in but couldn't see anything? The other piece that I would say from a data security perspective is our, you know, this world is all HIPAA compliant. But, you know, sometimes we forget about soc2. And why not both? You know, Soc2 is a little more flexible and allows you to kind of adapt, whereas HIPAA has prescriptive rules.
Again, why not both? You know, throw in zero trust while you're at it, which, you know, these are words. Maybe not everyone listening understands, but Google look into it, talk to your IT team about what those really mean. If you can if you can nail those three, I think you're in good shape to say that your your data, your EMR, where it goes is also safe, not only on its way, but people trying to get in, people wanting to do anything nefarious with it. It's going to be a lot harder, sadly to tangent for two seconds, but the famous word is or famous phrase.
It's not if it's win, right. Your goal is to minimize the impact of a breach because it will happen one way or another. Not to be doomsday, but it's just the world we live in. Technology move so fast and hackers are smart. That's a great point. Yeah, I guess, you know, just staying. We touched on it a little bit about like reporting. But like what is the most important reporting that you get out of these tools for like the leadership team when you're going in meetings?
You know, I think we touched on it earlier. Right. I'll go back to first past yield is, is, you know, an important metric. You know, I think our, you know, our compliance pieces, you know, are we meeting regulatory compliance? You know, you've got your incident reports. Those are big. And then, you know, I think organizational metrics vary, right? Based on what they're offering is what service lines they're focused on. You know, if you're telehealth, it may be about attendance, right.
It's not to say attendance doesn't matter in the physical, but they may put more of an emphasis on seeing the individual progress notes from private therapy sessions, and being able to sort of, you know, map that out and dashboard format where it's like, you know, we've got 80 patients in 79 of them every day, you know, on a consistent trend or are doing their private therapy. You look at the group notes and you're like, well, wait a second, why are only 40 of our 80 patients going to group right now? Right. And you start to dig into those? And I think drilling down is a big piece in that regard.
Right. Why is the 40 only 40 instead of 80? So it also goes back to the right tool, are using, you know, a power BI or using a Tableau or using reports directly out of the air. Most of those are not going to be that robust on just straight out of the HR side. They're going to be kind of static information. What you want that is, you know, cross-pollination, bringing, you know, your, hours worked, you know, employee days to to patient counts, employee patient ratio, days to employees. Right.
I think those are key for our team. We, you know, review them, weekly, if not monthly. Yeah. Well, Sean, it is so clear that you were like a leading expert in this field. And I really appreciate you being on the show. Is there anything that, like, maybe that we forgot to ask or maybe that you'd want to share before we wrap it up? I don't know if you forgot to ask anything. We touched on a little bit of everything. I'd probably circle back and say, I think one of the most important pieces of making this larger decision of what? EMR.
You want to repeat it one more time is having the cooks in the kitchen. You've got to have the whole team in there. You've got to be earnest. And who wants what and why? Be willing to make some sacrifices, but also understand that decisions you make impact others, not just in that room, but the staff in those verticals. And then ultimately your, you know, your reporting and your, your revenue. And so I think it's important, you know, to make sure that you take the time upfront. I've seen a lot of organizations say we want a new EHR.
We want it in six months. That is not enough time. So you've got to do the diligence upfront, right? Slow down to speed up. If you take your time and do it right at the beginning, picking the tool, making sure it is culturally aligned, you know, with your organization that it has those feature sets that are going to make you better as a team, as an org. And, and then, you know, some of those bells and whistles which today are commonplace, but good integration, great reporting. At the end of the day, I think you will find that
those are the things that matter most when it comes to making the selection is sitting in the room and doing it as a group, slowly, surely, competently, and then saying, we're ready. We've got a tool that works, and we can iterate from the 80 to the 90 to the 95. Because let's be honest, you'll never get to 100 governing bodies. Payers will all be making sure that you're constantly having to change the things that you collect. So, I mean, Mark, one of the big takeaways that I'm getting and Seana be curious you want to respond to this.
To go from a good team to a great team. It sounds like the good team is responsive to issues. The great team knows the business and anticipates those issues. And and you're already ahead of the ahead of the curve in terms of what people want to see and how you want to respond and how you want to integrate. So that's a big takeaway that I'm getting from you. And it's really refreshing to hear that because I'm I'm so used to the responsive and the finger pointing. So what are your thoughts around that? Yeah, I think, you know, it's very well said.
And it's not me. Right. I think it's, it's I've learned from some great leaders that taught me to see three and five years ahead. And I didn't used to I'll own I was like six months down the road, one year max guy. I think we're all there at some point in our career. We just don't quite have the experience or, you know, we haven't been mentored in a way that allows us to see this decision has an impact and this kind of domino effect. But it's very well said, Jeff, because I think, you know, truly what ultimately decides business success is seeing the future.
And that's not easy for everyone to do. And it is both very reactive because we respond to incidents. But, you know, being a little nerdy here, if you go with the classic I tell practices, incidents in multiple are problems and problems need change management. Right. So you can see 50 of the same thing. You got a problem. Let's go fix that problem which results in change. And that is the stepping stone to saying well what problems might we have. And let's get ahead of that by engineering processes, systems or automations
to, you know, keep them at bay or from happening at all? Yeah. Great insight Sean Lee. Jeff, man, it's always an honor to share this show with you guys. You just always bring it and great questions. Really appreciate you. Today, A huge thanks to Sean Mannus for his willingness to share his CIO knowledge with us. From me and the entire mastermind team. Thanks for listening. Be sure to subscribe, rate, and review, and let us know your thoughts on the intersection of technology and behavioral health.
Until next time, mastermind. Signing off That wraps up this episode of mastermind. Thank you so much for joining us. And remember. Mastermind is not just a podcast. It's a community. So don't forget to comment, subscribe and review us. Your feedback helps us continue to bring you content that's relevant and relatable. Thanks again to our sponsor, snapshot, a digital media marketing agency. And thank you for joining us on mastermind. Your behavioral health playbook.
What happens when a fast-moving digital mental health company joins one of the largest hospital systems in the country? Erin Boyd, Chief Growth Officer at Talkspace, a Universal Health Services company, joins Mark...
When someone finally works up the courage to call for help, who answers? In part two of this MasterMined OG series on the behavioral health technology stack, host Mark Scrivner and co-host Lee Pepper move from the...
What does your EHR actually cost once you add implementation, data migration, and your clinical team’s time? Most operators find out after they sign. In this OG episode of MasterMined, host Mark Scrivner sits down with...
What happens to the person who calls your treatment center at 11 PM and gets a voicemail? For most organizations, that person is gone for good. Geoff Nudd, CEO and Co-Founder of Anonymous Health, joins Mark Scrivner and...
What happens when the seal that signals legitimacy becomes easy to fake? And who holds the certifier accountable? Mark Scrivner and Jeff Skillen sit down with Naomi Moono, Director of Strategy (Certification) at...