Jul 1, 2024
Join us for an insightful episode of the VRTAC-QM Manager Minute as Brittny MacIver and Sarah Clardy from the VRTAC-QM team share their expertise on case management systems. Brittny, an expert in Program and Performance within our Quality Management team, and Sarah, the Program Director for Fiscal and Resource Management, delve into best practices and the growing trend of states seeking to upgrade their systems. Learn about the nuances of state requests and the RFP process, and gain valuable knowledge to help you decide whether it's time to stay with your current system or make a move.
{Music}
Brittny: Avoid over customizing the system. There's a lot of systems out there that are already available in VR agencies, and so if it works for that VR agency, there's a good chance the majority of the processes are going to work for your agency as well.
Sarah: Silos, how do we break down silos? And this process really can be a nice segue to combining program and fiscal together. I know we've said that multiple times, and I don't think we can say it enough. This process really is an opportunity to develop relationships.
Brittny: Be curious. Your agency may have a process that you're unsure why it exists. Some may say that's how it's always been. I think it's good to be curious, figure out the reason behind it, and see if there's a way that you can streamline those processes.
Intro Voice: Manager Minute brought to you by the VRTAC for Quality Management, Conversations powered by VR, one manager at a time, one minute at a time. Here is your host Carol Pankow.
Carol: Welcome to the Manager Minute. Today I'm thrilled to have two of my esteemed colleagues, Brittny MacIver and Sarah Clardy from the VRTAC-QM, joining me in the studio today. So, Brittny, how's it going for you?
Brittny: It's going great. How about you?
Carol: Awesome. I'm better for seeing your smiling face this morning. And how about you, Miss Clardy? How are you doing?
Sarah: I'm great. Great to kick off a new week.
Carol: Excellent. So for our listeners, Brittny serves on the program and performance side of our QM team. And Sarah is the program director for the fiscal and resource management side of our QM team. And both of these ladies have extensive experience with case management systems. And during one of our regular Core QM Team meetings, I asked the team, I'm like, hey, what are some potential podcast ideas? And Brittny said, you know what? There are a lot of state voc rehab agencies on a quest right now for a new case management system. Either your state is requesting you to do another request for proposal or you're just like, hey, is there something better out there? So with lots of new players that have entered the market, your case management system is a lifeline. And if it's not functioning optimally, it can really lead to some significant issues. So we just wanted to have a conversation today that can help to guide you through this journey with open eyes. So let's dig in. So of course our listeners always like to know, like how did you people get into VR? Everybody wonders, like what's your story? So I want to hear from each of you about kind of your journey into VR. So Sarah, I'm going to kick it off with you.
Sarah: So many of you know Ron Vessell, he's a staple around VR. Ron actually hired me back in the year 2000. I was a very green government accountant just starting out, didn't know what I was getting into, and they took a chance on a new, young professional. And so I did a deep dive early in my career and never looked back.
Carol: Very nice, I love that. How about you, Britt? How did you find your way into VR? You came a little different way.
Brittny: Yeah, I think it was definitely a unique path. I actually worked in criminal justice at the prison system as a counselor for quite some time. They were privatizing the position, which meant we were kind of losing benefits. We're no longer going to be a state employee. So I started looking around for other counseling positions. And at my time at the prison, I found that there was a lot of individuals with disabilities and a lot of obstacles that we had to address and assist with while we were there. And so when I seen the position at VR, I was very interested in it interviewed. And that's where I got my start about 14 years ago.
Carol: And which state was that in? Britt.
Brittny: That was in.Indiana.
Carol: Yeah. That's cool. I think that's great. So you worked with Teresa?
Brittny: Yes.
Carol: Very good.
Brittny: I always joke and say my four years at the prison. And then I have to clarify when I was working.
Carol: I love that. In fact, we had a guest last month that also had come up through the correctional system as well. It was really fun, but that definitely having that skill set behind you coming into VR is super important, really needed. So let's talk a little bit about your work. Both of you do for the QM. Just so our listeners have a little sense. And Britt, I'm going to start with you about that. Like can you give them a little flavor kind of for what you do in this TA world?
Brittny: Yeah, as you mentioned I work on the performance team. So really all things performance. But we help agencies address performance related needs. So this can be anywhere from training on performance measures to data analysis on performance data, reviewing policy procedures, internal controls and sometimes even assessing the system impact around performance and seeing how that impacts the reporting pieces.
Carol: Yeah, I love our performance team, the stuff you guys do, and you're so good at your analysis and really looking at taking that data and really digging in deep as to what's going on. So it's a very, very important piece of what is happening out there for our VR programs as we're delivering that technical assistance. How about you, Sarah?
Sarah: I have the great pleasure of leading the financial arm of the VRTACQM, and understanding that the VR award is the probably the most complex award within the grants management world. It really covers a wide array of skills and knowledge and isn't just financial based, it's also program based. So under the QM, we help agencies sort of manage the grant from the whole life cycle perspective, making sure that all the federal requirements are met, taking a look at individual state requirements, how those two things intersect, and we spend a lot of time, probably the majority of my time is actually spent in the period of performance arena, and specifically as it relates to this topic today with case management service systems.
Carol: Excellent. So, Brittny, you had mentioned the issue of people are looking for a new case management system. And I know as of late it feels like we've had at least a half a dozen folks saying, you know, we're doing a new RFP. We either have to for the state or we're going out for a new system. What advice do you have kind of off the bat for people who are considering venturing into this new RFP process?
Brittny: Yeah, I think before writing the RFP, I think it's important for the state or the agency to do some research on what systems are out there. A lot of agencies are writing an RFP based on what their current system does, and they end up with a very similar system. The process and all the hard work of getting a new system can be really exciting. It could mean new innovative features and easier case management process, which leads to improved efficiency, improve services and outcomes. You could find a system that would help with documentation times. You can reduce that, and then that way the counselor can spend more time with their participants. So I think just seeing what's out there and what's available to help you write that RFP is huge.
Carol: Sarah, how about you? What's your perspective on making sure those fiscal pieces are addressed as they are thinking about RFPing?
Sarah: Oh goodness. There's so many perspectives to consider here. I think first and foremost states need to understand period of performance. I feel like that's a term that we make really complicated. And it's really nothing more than just looking at the funding sources that are available and understanding the timeline that agencies can obligate and expend funds. So I think, first and foremost, understanding period of performance. The second key piece really is understanding state requirements. We have a lot of states that aren't either aware of what their state requires, or there are things that are in place that they think is required by the state. And when we start doing a deep dive into what that looks like, sometimes those things really aren't state requirements. It's something that somebody put into place years ago that everybody just thought was what was required. So I think understanding those two things. And then third, I would say understanding what your end game is when you're working with a fiscal and a case management system, and we're looking at just sheer fund accounting and tracking those funds all the way through and then being able to report at the end of that cycle. And so I oftentimes will tell states, if you kind of look at the end game, look at the reporting that's required at the end, it really kind of establishes the things that are necessary along the way in terms of system adaptations, structure, configuration.
Carol: So definitely I'm going to tie you two together when a state is going out and they're looking at doing the RFP, you want to really think about your complete process so that you've got all the right team members in place from the get go, which can't just be the program side of your house. And I remember us doing this back in Minnesota as we were going through the requirements. It's like, what are those fiscal people doing here? They're all important. Like you need all the pieces together, talking through how this system is going to work, how you're going to connect to your statewide accounting system. So that becomes really important. Now, I know I was on a call, I want to say within the last three, four months and we had a state say, yeah, we're thinking about RFP for a new system to go into place January 1st. And Brittny, I want to kick this to you. What is a realistic time frame if somebody is considering a new case management system, is it really possible to do that in, uh, maybe eight months or so or not? What do you think is a good timeline?
Brittny: I think this really depends on several factors as far as a timeline when considering a new case management system, typically it could take up to six months to develop that RFP. And it's really doing some background homework, seeing what's out there, doing a business process analysis and understanding your own business processes. But typically, I'd say depending on agency size, how many years of converted data you're looking at, converting it into the new system. And I know there's federal requirements, but there's also state requirements that are sometimes even longer than the federal ones. And then also if there's any interfaces. So if you have other systems that are connecting to your current case management system, this is going to make a huge difference, because now you've got a lot of different teams having to help out with the specifications and then also test the system. So you've got to think of their timelines as well. And then lastly just that preparedness piece. So how much work did you do up front on the RFP. How much have you analyzed your business processes. And like Sarah had mentioned, are these things that somebody put into place ten years ago, or are these things that are actually a state policy or a federal policy that you're aligning with? I think the typical timeline that I typically see is around 18 to 24 months for the full implementation once you sign in that contract. But again, that could range short or longer depending on that prep work and then that agency size and things like that.
Carol: So eight months is probably a little aggressive.
Brittny: Yeah very, aggressive yeah. But optimistic I like it.
Carol: I love it. So what are some pitfalls that we want to help our listeners avoid as they're kind of tackling this process? And Sarah, I'm going to kick that to you first.
Sarah: First and foremost. And I think the listeners are probably going to see a recurring theme here, as Brittny said, not just taking current system functionality and developing that into a checklist or using that to develop the specifications. I think really sitting down and outlining what are the requirements, what are the things that we're using right now? Where did that come from? And the possibilities going into this process allows a lot of opportunity to think outside the box and think about what are the things that systems currently aren't doing, or things that are requiring a lot more work right now where we could really get creative and do some really cool things. So I think avoiding the pitfall of just not spending that time up front to understand what it is that agencies need, and then also, again, bringing fiscal and program together to understand the requirements from a physical standpoint. A lot of times that is kicked to the finance folks in the House, we're still seeing in a lot of agencies a breakdown or a gap between program and fiscal, and there's a lot of danger and not bringing those two teams together to understand on both sides of the coin, what is it that we need to do? Oftentimes within that space is where a lot of the creative ideas come out and allow greater efficiencies within the agency and more internal controls.
Carol: Very good. Britt, what do you think about pitfalls? What are some things that we could help our folks avoid?
Brittny: Yeah, I once talked to a chief technology officer and he said the two main reasons why usually a case management system implementation fails is because of fiscal and data validation. So hitting those two pieces very hard, making sure that you're not only converting the data into the system, it's almost like that toy where you've got a round circle and you've got to fit it in the round circle. The data conversion doesn't always work like that, and sometimes you're trying to fit that round circle into a square peg. And that's because the way the systems line up. So making sure that you've got individuals on the front end in different roles, looking at that data and then also testing that RSA 911 to make sure things are mapped correctly and going in correctly before you go into production. At one example I've seen of that is significance of disability. And so one system may calculate significance of disability a little bit differently than another system. And even though they've got everything mapped together, doesn't always go hand in hand and can cause some major issues. The fiscal piece, I think Sarah mentioned that quite a bit, but just making sure that you're doing heavy testing and understanding how the system will work, especially when you go into production. Working in a new system, the biggest ones are dealing with authorizations that already have partial payments on it, draft authorizations, pending payments, amending an authorization, and vendor logic. These are all pieces that may be different in that new system. So making sure you're testing every angle and you're prepared for that transition. I think a third suggestion is just my personal preference would be to avoid over customizing the system. So there's a lot of systems out there that are already available in VR agencies. And so if it works for that VR agency, there's a good chance the majority of the processes are going to work for your agency as well. And sometimes those states like to over customize that system just because they want to have what they've always had. But that ends up being sometimes pretty expensive down the road, because then you're paying for additional testing and maintenance of that customization. So I'd be open minded to changing business processes, or see if you could find your business processes met in a different way and achieving that same result.
Carol: Yeah, I like it. I remember when we had our new case management system and it was built. We went in with all our partners, our WIOA partners, and so we had this kind of groovy new system, but it was supposed to meet all these different needs. Well, it gets complicated, but we couldn't forget about our field people because a lot of those folks in the field. So while you're talking to program, you know, a lot of times it's supervisors and different folks are involved. Having those direct field staff, your VR techs and your counselors who are inputting stuff every day and they're like, hey, this weird thing over here, you know, they may not talk techie, but they can explain the stuff that isn't working so well in getting all of those ideas right from them so they can see, hey, they really can help to impact and influence the system is important.
Brittny: Definitely.
Sarah: You know, Carol, along the lines of what Brittny just shared too, I think there's a caution there in terms of customizations that are in existing systems, whether it's an off the shelf system or a homegrown system. We have a number of agencies that have their own in-house systems. Sometimes there are customizations that work for a particular state or might work for a group of states, but it's not applicable to all states. Again, because we go back to those state requirements. And then sometimes when agencies implement that, it causes some compliance issues because of their own local procurement standards. So asking the question, you know, if they're developing those specifications and not just taking everything from what they're doing or is offered to them currently, but really looking at it with a cursory eye to determine, is this something that we need or we even can use because we're seeing period of performance compliance issues from some system functionalities that are in place that worked for other states that aren't necessarily a one size fits all.
Carol: I think one thing I've noticed too, and I just noticed from the periphery, you know, it's really statewide IT systems and the IT groups have been put together. You know, we see that consolidation happening where you may have had your own IT folks that you were dealing with, and now you have a State Department of IT or something. There's some other consolidated area that has put together different processes or requirements. So I think for some folks, if you're used to maybe the old way when you were entering into this process and maybe doing an RFP and you had more control over everything, you may have a little less because you do have now these sort of statewide IT system requirements. And so it's really important to get hooked up with those folks as well, especially for listeners who may have not done this for a while. Maybe, you know, it's been a long minute since you have looked at your case management system, and you were remembering back a decade ago when it was a little easier. You could just do something a little more at the drop of a dime. But I think the benefit that having those statewide IT groups is they have so much experience. And when they're looking at how they really address putting out an RFP and they can have a lot of their expertise to bring to the table to make sure this gets put together really well. You just want to remember that you may have some other things in play that you didn't have a long time ago. Just a thought. Alright, I know Brittny, when we were talking to you, had some ideas on cool stuff and I love cool stuff. Like, you know, if you're doing your case management system, you said, well, gee, don't, don't just recreate the same old thing like you want to put cool things in place. So do you have ideas like new technology or features or things people could include in their request?
Brittny: Yeah, I've seen dashboards where there's visual dashboards and graphs or pie charts that assist the counselor and case management. So seeing how many individuals they've got enrolled in an education program and how many of those individuals have earned an MSG in the last performance year. And this allows them to check those that haven't and reach out to those participants. I've also seen a central print and mail where the state's just actually the agency put a checkbox in there, and they've got an interface with a local company and that company, they hit the checkbox and everything gets bashed up that night for a letter or anything that they want to mail. And there's a mass every night they mail out all these letters. So that way the counselor could be anywhere. They could be at the school, out in the field, anywhere, mail out a letter, and not have to worry about printing something off and stuffing that envelope. I've also seen invoice payment systems. So systems where vendors can apply to be a vendor, they can document what services agree to terms, things like that. The agency can review them and approve them in there. And then that system can work back and forth with authorizations and payments. So an authorization could be drafted in the case management system could shoot over to this invoice payment system. That vendor can view it, upload documents, invoice against it, put reports and things like that in there, and they can communicate back and forth to one another. I've also seen states exploring various ways to integrate artificial intelligence and case management systems. So I know you did a podcast on one that was kind of outside the case management system, but I'm hearing a lot of states be interested in how to integrate it in the case management system, whether it's in case notes or informed decisions across. So I'm really excited to see what states come up with and how they're able to integrate that within. But I think that's a great idea.
Carol: I love that whole area of artificial intelligence. It was super fun when we did the podcast with Washington General, because they had that really cool piece that was, you know, an add on. It was kind of outside of the system. But boy, the staff love it. But there's a lot of possibilities. I know we were kicking around on the team about ways you could use AI within VR. I mean, when you think about the development of plans, even the way you speak about things, to make it more plain language, and I still I think people are so freaked out a little bit about AI and you go, gosh, it's all over. You know, it is in our whole world. It's when you're talking to Siri or Alexa, you know, every day you go to the airport and you're getting your eyes scanned to get through, Clear whatever you may do. It's just integrated into everything we do. I think that is a really fun, developing new area that has a lot of possibility for the case management systems. Sarah, did you have any ideas too, about any cool possible groovy tools? Maybe fiscally related? I didn't mean to put you on the spot.
Sarah: No, that's okay. We haven't seen as much innovation on the fiscal side, although I think that there are a lot of opportunities. I think, again, in the AI world, I think mapping that out, looking for the possibilities, it goes back to what I said earlier, just being an innovative thinker and looking at what are the challenges and efficiencies that we're battling and what are some of those possibilities that we can use to address that. Staff recruitment retention continues to be a challenge in our VR world and especially in the fiscal arena. And as staff look to bolster their internal controls and the program at large, looking for some of those opportunities. So I don't know that I have as many cool things like Brittny shares, but I'm hoping that we'll see those on the horizon.
Carol: Yeah, me too. I think there's a lot of possibility out there now. I know Sarah, you had developed a tool that coincided with the 2023 spring CSV conference because a lot of folks were asking like, okay, what do I do with my case management system and the fiscal requirements and all of that? Can you talk a little bit about that? Because even though we felt like we widely publicized it, people are still like what? There was a tool. I don't know anything about it.
Sarah: Yeah, absolutely. And I'm still excited about it. So we developed a fiscal technology checklist for case services last year in conjunction with the period of performance training that we offered at the conference. And we found that in our technical assistance to state VR agencies around this topic, there's a gap in communication between either the CMS companies and VR, or even if an agency has their own internal program, a gap in communication between the program and fiscal and whoever those IT experts are. So we took that opportunity to map out all of the areas to consider. And so when we're working with agencies under the VRTAC-QM to analyze their processes and look at how their systems are set up, there's a linear fashion and way of looking at that. For instance, is the system set up on a state fiscal year or a federal fiscal year? There's a lot of agencies that have a system set up on a state year that really doesn't make sense for reporting, and it's causing a lot of challenges on the financial side with producing reports for the RSA 17, for example. And they thought that that's the way they had to have it set up. There's very few states that have very state specific requirements that would necessitate that. So it's not that it never would work, but it involves sort of a deep dive into why do we have our systems set up and is that necessary? The other big piece are the budgets. How are budgets set up within the system? Does it map out to the available fund sources that are available to the agency? And then there's a ton of bells and whistles that act as internal controls in the back of a case management system that really dictate how the system behaves and helps the agency navigate through period of performance. And so it's going through a whole list of considerations to make sure that the agency is well equipped to manage period of performance, manage those different fund sources and make them able to do that reporting at the end. So it's a really good list. And honestly, as states are struggling with that communication piece, particularly with the companies that they work with or through the process to develop a new case management system, it's a very nice way of considering all of those different elements that need to go into either evaluating the current system or looking at a new system to make sure that it's meeting exactly what their state requires while still taking into account those federal requirements. So we're constantly reverting folks back to that list, and hopefully agencies are taking the time to sit down as a team and combining the program and fiscal staff to walk through that, to make sure that they understand all of those elements. And if they have questions, we have a number of trainings that we offer through the VRTAC-QM to assist with that. We've even had some agencies seek out that training before they start developing those lists for their RFPs, to make sure that they both understand from a physical standpoint what all those requirements are. So anyway, it's Fiscal Technology Checklist for Case Services. It is on our website, I'm sure. Carol, you're probably going to mention that and hint, hint it is available to the public. So I know that there's been some current CMS companies that have gone out and looked at that piece also, so that they can better understand and hopefully fill in the gap for that communication gap exists so that everybody's talking the same language and on the same page.
Carol: Yes, of course, I have to make a shameless plug for our lovely website. So you will go to vRTAC-QM.org and we have a top navigation header. You can go right to resources and everything's listed under the CSAVR Spring 2023 Session Recordings and Materials. And it actually was Session Two is where you can find that checklist. But if you scroll through you can actually listen to Sarah's session recording. And then you can see the checklist there as well, as well as all of our other awesome sessions from the 2023 Spring Conference. Oh, thanks for that. So how about other words of wisdom from you fine ladies? Because I think of you both as just like, oh my gosh, such powerhouses in the case management system. Brittny, I'm going to go to you first.
Brittny: I've got a few. I think the first one is to be curious. Your agency may have a process that you're unsure why it exists. Some may say that's how it's always been. So I think it's good to be curious, figure out the reason behind it, and see if there's a way that you can streamline those processes. I would also allocate staff specifically for this project, and I think we mentioned it already a little bit earlier. But looking at those projects subject matter experts and making sure you've got the right people at the table. So this is going to be administration, IT, but also your fiscal people, your front end people. It's really important to make sure that you have some direct service or direct field staff that are knowledgeable and have a long agency history that you can integrate into that project as well, and they can provide feedback. I would also have a designated project manager that could be somebody. You within your department, or that could be somebody that you decide to contract out. But I think it's important that they have that project management experience because it is a giant project, and it is going to take quite some time to get from that RFP contract to implementation.
I'd also weave in changes as much as you can. So during the project, you'll start to have the opportunity to see the differences between the two systems, your current one and your new system. And so if there's any way that you can weave in changes early and often, this will help that transition for staff much, much easier. And then also as you're preparing or updating revising business processes, that also helps with that piece of it. I've seen states do statewide quarterly demos to kind of show staff the new system and help them kind of process that change along the way.
And lastly, I would definitely emphasize not to overlook accessibility. I'd pull in your accessibility users early to begin testing the system, and then also integrating those accessibility terms into training documents. I think one thing I learned is that using language accessibility language is huge. I couldn't imagine trying to learn a new system and somebody saying, use a dropdown box. But yet my system is calling it a combo box. So using that terminology and making this transition much easier for all staff.
Carol: Awesome points. I want to highlight a couple, that be curious. I can't emphasize that enough. There are so many agencies where I'm going to call it urban Legend. You're doing something because everybody always says, RSA said. You have to do that and RSA will come out. I've been in monitoring. They're like, we never told you that. Whatever that is in your system, you made that up like you made that happen. So I love that being curious because you want to ask questions. A lot of times you just go with the flow. You know, somebody put it in play 20 years ago and then you just keep bringing it forward. So I love that. And definitely when you talk about dedicating staff, you want to make sure you dedicate those staff, but you also want to think about all of the other roles that have been assigned to that person. You cannot put them as the project manager of this whole project, and they're still maintaining all their field services duties and doing all the other stuff, because this really is a full time job. And I know I'm going to apologize right here to Natasha Jerde. We had her as a project manager for our new case management system. At the same time, she's, you know, rewriting our policy and procedure manual and doing a million other things because I just had zero clue at how much went into this. And that was really it's really terrible. And I've actually seen some of the staff across the country burn out. We've had people retire early. They're like the case management system process killed me. So when you're dedicating staff, please do give them some time to do it. And don't expect that they're not going to work an 80 hour workweek because that is not so fabulous. But I loved your points, Brittny, those are great. How about you, Sarah? Any words of wisdom?
Sarah: Yes, thank you. I think we constantly hear from state agencies about silos. How do we break down silos? And this process really can be a nice segue to combining program and fiscal together. I know we've said that multiple times in our discussion today, but I don't think we can say it enough. This process really is an opportunity to develop relationships and I know even from the agency that I came from, the introduction that I had to the program side was through a new case management system conversion. And at first I showed up at the table. And Carol, like you said earlier, people were like, who invited her? Why is she here? Does she need to be here? People wouldn't talk and share ideas. And then as we both committed to developing that relationship and understanding one another better, not only did we end up with a quality product, but we had quality services, we had better management and leadership within the agency. So looking at it as an opportunity sort of through that lens, engage the folks in the field as well. Sometimes as leaders, we tackle these types of projects and we think the folks in the field are too busy. And really the best ideas can come from our counselors and those individuals who are supporting in those roles our field staff, our fiscal agents. And I know we have a separate training on that that we offer VR agencies, but engaging them in that process and getting their ideas on, hey, what's working and what's not working? What are the challenges that you're facing so that as you are curious to Brittny's point, you're taking into consideration maybe some of those wins that you can secure on the other side and maybe cut out some process or things while still meeting those requirements and engaging in those efficiencies.
The other thing I would offer, and we're having lots of discussions now about fiscal forecasting and spending strategies within VR agencies, as VR agencies are getting over the hump of Covid and taking a look at what their spending looks like, the case management system really is a system of record. And as we look at the statewide accounting system and in its function, we can't ignore the case management system and the role that it plays in navigating through all those fiscal requirements. And so if we think about the CMS sort of as the VR checkbook, and when we are authorizing for services and obligating funds, not only are there requirements around how to do that and how to capture that, looking at the individual sources of funds that we have available, it really is a way to capture those obligations within a checkbook so that we can take a look at any point in time from a leadership standpoint, what is our financial position? And so being able to look at how much do I have in my 23 carryover checkbook and how much do I have in 24. And plan ahead so that I can make decisions around re-allotment and I can think ahead so that we're not leaving funds on the table and lapsing funds at the back end of our of our award. It really is important that we look at how we capture all of that in the case management system in a way that allows us to continue managing our programs with a strong fiscal focus. So tying all of that in is also important at a higher level, so that we can use the data to make quality financial decisions.
Carol: Well said, well said. So in case our listeners want to get a hold of either of you, would you mind sharing your email address, Brittny?
Brittny: Yes, definitely. My email address is bMacIver So m a c I v e r@sdsu.edu. It's also available on our VRTAC website. If you go to our staff you'll see my email address there as well.
Carol: Excellent. Sarah, how about you.
Sarah: Yes thank you. It's sClardy. so, that's s c l a r d y at Sdsu.Edu.
Carol: Thanks so much I appreciate you both joining me today. Have a great one, you guys.
Brittny: Thanks.
Sarah: Thank you.
{Music}
Outro Voice: Conversations powered by VR, one manager at a time, one minute at a time, brought to you by the VR TAC for Quality Management. Catch all of our podcast episodes by subscribing on Apple Podcasts, Google Podcasts or wherever you listen to podcasts. Thanks for listening!