Originally posted on Medcurity Podcast
Host: Mel (Medcurity Podcast)
Guest: Ghazenfer Mansoor (CEO, Technology Rivers)
In this episode of The Medcurity Podcast, host Mel interviews Ghazenfer Mansoor, the CEO and
founder of the software development company Technology Rivers. Ghazenfer explains that his
company specializes in health tech, helping healthcare organizations with product development,
improving operations, and rescuing failing software projects. A significant portion of their work involves assisting physician entrepreneurs and healthcare service businesses like home care and assisted living facilities. They focus on bringing ideas to life and improving efficiency through custom software, mobile apps, and AI-driven automation.
The Medcurity Podcast explores the intersection of healthcare technology and HIPAA compliance, featuring expert insights on securing patient data and implementing AI solutions in healthcare organizations.
[00:00:00] Mel: Hi, everyone. Welcome to the Medcurity Podcast. This is Mel. I am your host for this episode. I have a very special guest with me today. His name is Ghazenfer Mansoor. He's the CEO and founder of Technology Rivers. Ghazenfer, welcome to the show.
[00:00:14] Ghazenfer Mansoor: Thanks for having me.
[00:00:15] Mel: So why don't we start off, why don't you tell us a little bit about Technology Rivers and your background and what inspired you to start the company?
[00:00:24] Ghazenfer Mansoor: Okay. So yeah, my name is Ghazenfer Mansoor. I run the software development company Technology Rivers. We started as a mobile app development company. Gradually moved to healthcare. Our second customer was a health tech company. That's how we got into more and more health tech. Before starting this, I was the early engineer in two startups and then later on built a recruitment software startup. And then in 2015 I started this business helping businesses in product development, and then gradually focused, moved to more and more building health tech applications, helping healthcare organizations in product development, improving their operation, bringing ideas to life.
[00:01:11] Mel: I see. And so as far as your software development, you're, you're creating new products and helping people fix issues with any existing mobile apps as well? That. Am I correct?
[00:01:25] Ghazenfer Mansoor: That is true. A big amount of our work is, we call it, like, fixing broken projects. Customers come to us after having bad experiences with either other vendors or in building internally, taking projects, taking longer time to build. So we come in, rescue those projects, help them get back on track. So a lot of things we have to do, and obviously we can talk more on that now or at some stage, but that's a bigger part of. But a good amount of work also where people have ideas, we help them bring those ideas to life building. A lot of our customers are physician entrepreneurs, interestingly, and they have ideas, so we help them create those ideas. And this is where we work with many of those product people and really that's our sweet spot. And the third area where we work with healthcare services businesses like home care, assisted living, autism care, those companies, helping them improve their operations through AI and technology. That's where we build internal tools to automate their processes and bring efficiency into them. So for us it's, it's, it's not really just efficiency, but it's unlocking the growth. Because as you are building these tools, you are making more time available to take care of your core business.
[00:02:54] Mel: So would you say that your driving force behind your company and just what you're doing with AI and everything is just improving healthcare and allowing providers and just enabling them to have more time with patients, what really inspired you to do the work that you do?
[00:03:13] Ghazenfer Mansoor: So I think the key part is the. I believe in technology being a service to people rather than we're building a technology. We're, we're using it as the technology's built. No. So the focus is building really intuitive, friendly applications that solve the problem. Every problem that we solve reduces some workload from the people, and doctors can spend more time caring for those patients, caregivers can spend more time. Because rather than worrying about a lot of those processes, if a lot of your processes are automated, it allows you to do more business.
[00:04:01] Mel: So when you're, when you're adopting or increasing or helping healthcare and health organizations adopt new technology and things like that, what challenges do you see them having? Or do they usually come to you or say, "Oh, hey I'm looking for help with this." What are their specific challenges, or the most common threads that you're seeing these days?
[00:04:26] Ghazenfer Mansoor: It's a combination. I think a lot of that comes with, I would say, a misconception. Because a lot of time, nowadays everybody wants AI. So whether it's needed or not. You don't have data but you want AI. Yes, AI could be part of the roadmap down the road, but the misconception is mostly like, okay, a lot of people think it, AI is plug and play. So it's not the case. Then, you have to have data, you have to have your flows. The bigger part is how do you really take what you have and build it? So AI is not gonna solve your problems if you don't have the right workflows. So if I mean, it could be a weakness. You could, you could build. It could fail your project. It would open up more failures for you. So AI is not just about. It will just expose you. So, in computer science, we study like garbage in, garbage out. So
[00:05:23] Mel: Yeah.
[00:05:23] Ghazenfer Mansoor: If you don't have the right flows, if you don't have your processes documented, if you don't have the right data, if you don't have audit logging, you, well, you will not have the AI result. AI is like a mirror. AI is gonna reflect what you are putting into it. It's gonna reflect your people. It's gonna reflect your processes. It's gonna reflect everything that you have in your business, it's just that now it's gonna do more intelligently for you. It's gonna save time for you, but AI is not gonna just produce something that you don't have.
[00:05:57] Mel: So for the organizations that are just starting or getting started with automation AI what's a good risk project they can start with, or where should they begin essentially as far as like readiness or do you have steps that you ask people to take care of, or do you coach them through it, or what do you suggest for anyone who's wanting to implement AI and just new tools?
[00:06:22] Ghazenfer Mansoor: Yeah. So I think the very first thing we talk about is the data. The second part is your workflow. Mapping your data. So you need to have your data, you need to map, you need to have your right processes. That's the only way you can have the right. We do have a checklist that we go through in terms to make sure these are HIPAA compliant, but now we have an AI version of it as well. So you need to make sure you have all of those things in place before you can be sure. So it's one of the common challenges we have seen, like if your people or you cannot explain your processes, if these are not documented, you're not gonna be able to build them right.
[00:07:09] Mel: As far as the healthcare experience and how AI and these efficiency tools are just in general improving workflows, like what areas of healthcare do you see it transforming the most and for a patient, for the patient experience and in general, like what are you seeing as far as improving for the everyday person?
[00:07:32] Ghazenfer Mansoor: It varies. So we work, we go, we work pretty broad. So a lot of our focus is on health tech, and that's where a lot of different types of applications are being built. Like, so remote patient monitoring I would say is probably the most that we see adapted because that's really still a pretty new thing. So remote care, that's doctors communication, that improved significantly. And it could improve more. Scheduling. A lot of those things are making a difference. So it's, in our case, we also work with autism care home care, assisted living. Again, that's a totally different world compared to the one that you see in the, at the provider's practices. So, but it's all over. I wouldn't say there's only one area that's helping more. But remote care is definitely the one that I would say across the board on both sides.
[00:08:33] Mel: I see. When you think of more and more technology and the interconnectedness and the different health apps and devices that people are using it's increasing the like the attack surface I guess you could call it for healthcare organizations and patients just in general. So when they're, when you're working with people and they're implementing new solutions they're thinking of their security risks. And so what would you say for compliance officers or healthcare organizations to prioritize when they're implementing new software, especially with the based solutions and AI, or I guess keep in mind when they're doing that in terms of security?
[00:09:20] Ghazenfer Mansoor: Yeah. So I'll bring the checklist forward again. And that's where we talk a lot. So make sure you are following certain things. So but the foremost is definitely the clarity on your data once what data. And then there are steps that you can take to validate if it's really HIPAA compliant. That includes audit logging, that's really important. Encryption, that's considered by default, but really still making sure encryption at rest, encryption in transit when you're sending the data. Authentication and authorization, making sure you have access control. Who has access to what data? Who looked at data, what time, how long? That stuff. And those things do change as you move to mobile, as you move to AI. Because now let's say on a software side, whether it's a web or mobile, certain things you can view, let's say maybe a list of patient data. It may not have 100% of the PHI data, but once somebody clicks on the patient and then goes look at their prescriptions and any other data that the patient had, the visit, the medications, everything, now that's a lot more detailed, right? So tracking all of that up to that level makes a difference because that helps make those decisions, especially if there are any incidents happening. Who has access to your database? That's at the infrastructure level, not necessarily at the software level, things like that. On a phone, you have the phone left on somebody's table, or you're outside, you lost the phone, and if you have PHI data, how do you make sure? Can you remotely erase it? Can. So those things need to be seen by the security officer as they are reviewing. Again, it's a big list of things. I can't talk all in this, but
[00:11:09] Mel: Yeah. Understood. Yeah. These
[00:11:10] Ghazenfer Mansoor: Are some of the top ones to remember. And I think yeah, one last thing I just realized, like, the analytics part. So for example, if you are integrating with any third party, so our software is communicating with whether it's Google Analytics, Mixpanel, whatever other different tools, what data are you passing? If you're passing any PHI data, is that also HIPAA compliant? So sometimes you will see the companies are building software, that software itself is HIPAA compliant, but the tools it's using other than the cloud are not. So you have to make sure everything is addressed.
[00:11:49] Mel: Yeah. So as far as the when you think of, like, the healthcare organizations, they're struggling with their, they're managing that third party, and they're looking for a third party vendor and/or a new tech vendor, what should they look for when they're trying - when they're comparing and they're trying to think of someone who can come up with an innovative solution while also keeping in mind those security and privacy issues? What would you tell them to look for?
[00:12:18] Ghazenfer Mansoor: Yeah. So I think you have to look at their policies. Like, do they sign BAA? If - especially if they are if they're accessing the real data, PHI data. Do they have separate environments? So for example, during the dev or staging environment, you may not have real data. Those are probably anonymized data. Do they have a process to anonymize data? How does the data touch from one to another? So what is their data deletion policy once something happens? Or even if the patient record is deleted in HIPAA, we don't - we consider, like, nothing is deleted. Yeah. Unless that company is out of business and you say, "I wanna shut down." That's a different discussion. Unless that is the case, you don't delete. Every data still stays. It's just that now it's deleted, marked as deleted. But in
[00:13:13] Mel: Yeah.
[00:13:13] Ghazenfer Mansoor: In reality, that is available somewhere because that data was looked at by somebody at some stage. It is not your current data, but it is still. So a lot of these things, how. I always look at the processes for these companies. How are they building? What are these things they're doing in order to make sure those applications are compliant? I think, again, I'll share the HIPAA checklist that has listed pretty much all of these things.
[00:13:41] Mel: So speaking of the things that healthcare workers have to look out for and those third party vendor vetting and all of that, what are some pitfalls that you see when they're adopting new tech and have you come in to help somebody who maybe worked with a different vendor and they had a problem, and then you're coming in to fix it? Are you seeing anything, any common threads there as far as, like, what problems people are having with their software?
[00:14:13] Ghazenfer Mansoor: Yeah. I think the bigger part is the knowledge of HIPAA, knowledge of PHI. So many times applications are built with the assumption that just encrypting is enough for HIPAA. That's not. And then a lot of time people come in and they would, for example, they would ask for compliance, and they would say, "We want to automate that." But you can't automate the compliance. You can only automate after compliance is embedded in your process. So again, as I said, like, somebody. If your software has all those rules but then your database access is open, anybody can get in. Then there's no point. It's like you have a computer and anybody can come in and access that computer or the files in your office. So the. So that process is important for compliance. The automation really comes after the After the process. If you don't have the process, then automation would create more chaos. It will open up those problems.
[00:15:19] Mel: As far as any other challenges or concerns, I know an AI is a big buzzword, and along with that people have had some issues or concerns about things like bias or not using it for the right reasons or correctly. What would you suggest organizations can do to address that, or how it can be fixed as far as using AI if there's, if you have any ideas on that?
[00:15:44] Ghazenfer Mansoor: Yeah. So bias data is depending on what you put in your system. Garbage in, garbage out. So AI can be unethical, AI can be biased depending on what you put in. But yes, on an ethical part, so the - you have to, again, have certain processes, certain flows what data you allow. That's the only way, otherwise there's no limit.
[00:16:10] Mel: Yeah. So in your experience, you've rescued a lot of healthcare software projects that have failed and so if you think of - let me come to you, what's the, what's the red flag that you spot early on when you're helping?
[00:16:23] Ghazenfer Mansoor: So the bigger one is the clarity of the flow. So really what you are building. Many times the focus may be on one or two use cases. Many times people are talking about one specific solution, but is it tied in a whole workflow? So clarity of the workflow, how the system works, like for each of the users, what the patients will do from A to Z, what the home care role is sorry, the caregiver role is. What is the role of the admin staff? Like, whatever are the different people who will be accessing the software, what are their use cases? What are their stories? What are their flows? If you're clear on that, then you can build the right product. Secondly, the pattern is most of the time those techs are built by generalists. They don't understand healthcare. If you don't understand healthcare, if you don't understand HIPAA. Like even knowing what PHI is, you'll be surprised. Yes. Yeah. Is the date of birth or is your name like, part of the HIPAA? Is that PHI or not? So even just the basic knowledge sometime, and you could quickly see that from by quickly looking at it. Like, oh, you log in and you realize, oh, the application is logged in for two days.
[00:17:44] Mel: Yeah.
[00:17:45] Ghazenfer Mansoor: So I used to work at the Veterans Health Administration. So we, every year we do those privacy policy training. So part of those, they ask you those questions in terms of like, what if you have something on your computer you left. You just go to the bathroom or pick up the coffee. Yeah. Somebody can come in and hover on your screen and see the data. That's a violation. So even those basic things. So if your software is not implementing any of those, then you are in violation.
[00:18:19] Mel: Yeah.
[00:18:19] Ghazenfer Mansoor: So for these products, like obviously the clarity of the workflow, the generalist not understanding the healthcare, and then not one person responsible for that whole process. So they are different. Everybody is like, you may have seen though where companies would look for just a developer to build. So
[00:18:41] Ghazenfer Mansoor: It's not just the developer. Being a developer is one part of the process. There are many others. Somebody has to drive that, and that makes a huge difference.
[00:18:50] Mel: Yeah, and I think that makes it also easier for your security doing your HIPAA security risk analysis when you're aware of everyone who has access, your, what data you're collecting, where it's going, how things are set up. It just, I think that makes it a lot easier, and I think being that we're focused on, or MedSecurty, we do the HIPAA compliance and focus on the security risk analysis, and a lot of companies will hire a maybe an I a or, sorry, an IT vendor, but they'll, they'll do the security risk analysis focused on the technical aspect, but miss the rest. And so just I think, when you have that Full overlooking of every little piece and having that plan. -
[00:19:34] Ghazenfer Mansoor: Yeah, I think ownership is key here. So obviously just like when an organization have the HIPAA compliance security compliance officer, similarly you need to have a product owner for this side to make sure who owns it, who really drive those projects.
[00:19:52] Mel: Yeah. So if you, a healthcare organization, want to be able. They wanna check and see if their party tools that they're using are HIPAA compliant. Is there something that they can do quickly and easily to look at it or?
[00:20:10] Ghazenfer Mansoor: yeah, I briefly touched on it before. So they have to look at, like, the audit logging, let's say. And you could do a quick test. Okay, you did a certain thing, and then as part of the verification process you can see, is everything being tracked? Who logged in? What time? You have to see how they're handling PHI in practice, like their process of developing, their process of like the environment. If they're touching the production data, then obviously they have to sign the BAA. So those things are done or not. If that was not even there, so that just is tell, so maybe there is something fishy. How do they handle the data deletion process? Then the third party tools integration, how the integration is done. All, are all those tools compliant? Which cloud hosting is being used? Are you following that process? They also need to sign the BAA.
[00:21:05] Mel: As far as PHI goes, how do you, how do you trust AI with PHI?
[00:21:10] Ghazenfer Mansoor: So you put in AI whatever you give. So you. It's like what do you put on your social media? Whatever you trusted will. So you usually can't.
[00:21:23] Mel: So
[00:21:23] Ghazenfer Mansoor: You can't trust AI just by putting everything in. You have to make sure the data is anonymized. So let's say if there are, say in your. Like if it's healthcare, and you can either anonymize or you can make the data change in a way so that it's generic, so it has reasonable information. So for example women of this age range from this background, something like that, has these symptoms. So now you're not sharing any specific data. So as long as that, the data is generic, you are okay with it. So yeah. Then you can also have internal processes. You can use AI internally where the data is not used to train AI. So -. And again, that's where you have to have those contracts with, whether it's ChatGPT or any other tool that they are using. They do provide those enterprise versions where your data stays within your organization. It is not used to train.
[00:22:27] Mel: Yeah. Yeah, and I imagine with the AI when you're working with it that if you have those guardrails set up, and there's those 18, they call it the 18 safe harbor identifiers. If you're, if you're setting it up so that all of those are removed, then you're, you're making the. Or essentially making it the Yeah. So that it can't be traced back to people. -
[00:22:52] Ghazenfer Mansoor: Yeah, so there's this saying we say, like, if you wouldn't trust your temp hire with your patient data, why would you trust your data?
[00:23:04] Mel: Yeah. So when you were saying, speaking earlier before, you were saying how the AI doesn't fix problems and it helps to reveal them. Can you explain that, what that means and what healthcare organizations can do before they dive into automation?
[00:23:19] Ghazenfer Mansoor: Yeah, I touched on this briefly before. So it goes back to the process and the data. If you don't have a right. So let's say you use AI to create your scheduling process, and if your people if you don't have that process and the AI is just suggesting, you cannot just because you cannot map your current data with the AI. Suddenly you got something that just doesn't work. It's great for somebody. It's like picking up any of those tools that are great, but is it gonna fit well within your organization? And I always say that any tool is as good as the data in it. Whether you are using any CRM, whether you are using any telehealth software, any patient care software, anything, if there is no right data, that data is not gonna help you. So the tool is not gonna help you. So that's very true in healthcare as well. You have to have the right flows. You have to have your data mapping. You have to have your defined processes, and then you use AI to improve those processes through AI.
[00:24:32] Mel: So when we're speaking of AI and preparing for it, and we see more and more companies adopting it, we can see that it's becoming increasingly critical to prepare and learn and be aware. So as far as when healthcare organizations are diving into it or wanting to dive in it, they do their checklist and take all those steps. But what else beyond that checklist and that can they do? Maybe training or what other ideas do you have?
[00:25:08] Ghazenfer Mansoor: Yeah, awareness is important. Training is important. A and I think another part is the comfort, the trust part. So you can start small with automating certain things that do not have PHI data. You may just start your, with your, let's say, operations or any other flows. It could be your scheduling, it could be your patient intake or anything that is not critical. So, obviously patient intake does have a PHI, but there are a lot of other things in your business that are PHI. So you can start with the simple flows and automate. Once people start to see the efficiency, they're more comfortable. Now they're gonna take it big. They can start to have those ideas, "Oh, this is possible." Even today, up till today, most people are using AI just for their content. "Oh, I have those, that Jasper plugin into my email." You right click and it will improve your writing. Or, so I mean, so that's a very basic minimum anybody can use, but there is a world beyond that as well. So there's a lot more you can do. So, but one step at a time. So the organization can start small with automating some critical and then gradually expand. Because the key is you also need to learn how all of this works, what data you need to provide. So even with the content, for example, if you just ask ChatGPT to generate, let's say, certain content, whether it's a blog or anything It doesn't know about your business. It will just create a generic one. So
[00:26:51] Mel: Yeah.
[00:26:52] Ghazenfer Mansoor: You have to coach your AI Train based on your content. So you have to give all that data that you have internal, and that would give you more specific information. So we created those internal GPTs. We. There's, like, an internal document system where, internal knowledge base. So your ChatGPT, your AI, can only answer based on the data that you have. Then you're getting more accurate. So once people start seeing, oh, these are the possibilities, they will start having more and more ideas. But yeah training is important. As I said earlier, in a traditional, obviously, in a. You have the HIPAA in your office environment. There are physical regulations. Then the web came, certain more restrictions, more openness. The phone made it more open. Now AI is a lot more. Everybody has access to those AI tools. What if people start putting in ChatGPT or Gemini or other tools and start asking questions without even. But that's where your HIPAA training comes in, the privacy policy. What are the things they can do or cannot do? So
[00:28:09] Ghazenfer Mansoor: And then having a process to enforce that, and, like, maybe not giving them access to certain things that are considered those. So Could be a more private version of the GPTs where you only have access to the data, or it could only be stayed internally and not used for the general training.
[00:28:32] Mel: Yeah. Yeah. That's - Those are all good points and everyone has a different level of comfortability and knowledge and I think as we're speaking of training, I imagine thinking, making sure everyone has that base knowledge and understanding how the AI works. I think even if it's helpful just people have some thoughts on security and privacy and all those things, how it comes together. But yeah. Looking ahead when you're seeing the AI changing and trends and things like that, what are your thoughts on how it will change going forward in the next couple years? Like, what direction do you hypothetically go?
[00:29:19] Ghazenfer Mansoor: Well it's a pretty big topic. I don't think I'll do it justice in answering that, but I can tell what I know. Obviously, there are a lot more experts that can probably answer more. So for me, it's more the context of AI assistance, just like as we were talking a few minutes ago, having your own knowledge base so that any responses you get based on your own. So I think this is becoming more and more having more AI agents where that's gonna be. And those things are already happening, but those are now becoming more and more specific to your workflows, your organization. So more internal aware, predictive, and personalized care models. That's gonna be more and more. That's what, again, that's what my guess is. Things will change. We never know. And then the growing use of AI in compliance automation. So right now, there's still a reluctance.. A small percentage of companies are open to AI in the healthcare space, and that's gonna grow more and more. Because as there is more compliance automation, you will have ways of flagging potential HIPAA violations, monitoring access patterns, things like that. So for example, in a system you're uploading a picture, and suddenly that's somebody's face picture. Even though you may be showing a scar to another doctor, that's a HIPAA violation. So it can flag those things. So, but yeah, I think a lot of these things will come into play, and we don't know which direction. We'll see how it's changing. This is the current direction, at least in my perspective.
[00:31:06] Mel: Yeah. Just out of curiosity, how are you using AI tools? Or like what are, what are your favorite tools to use, or how are you using them just to make your life easier on a daily basis?
[00:31:18] Ghazenfer Mansoor: Yeah. So Tools. Yeah, no, so a ton of tools. So I personally use Jasper and ChatGPT. ChatGPT is my favorite among all. But our team uses tons of different tools. So we're adapting AI in our development processes. So we like to use vibe coding. We use tools like Bolt, Lovable, Builder. We can generate the code from Figma. We can quickly create the POC. So if you have, let's say, any problem you tell me, and literally we can create a quick POC with a lot of screens in just a few hours timeframe. So, we have done those, like home care application, remote patient monitoring. Not those are right away in production ready, but close to production ready. Then there's a human touch part of it, and that's another part that I didn't get a chance to talk about. Like it's not that AI will do everything for you. There's a human, you have to create. There's a human involvement part as part of your process gradually because somebody still needs to review certain things and tweak it, right?
[00:32:24] Mel:. So we use that a lot. So in our processes, our goal is that everybody in our company is 10X from where it used to be. So yeah.
[00:32:34] Ghazenfer Mansoor: we all. I mean, the tools are there. You need to be productive - Yeah. As much as possible. A and that' Yeah. That's how the world is moving, so.
[00:32:47] Mel: Yeah. Yeah. And you I think you mentioned the human element isn't lost, you're still. It's, it's. The tools assisting? They're not replaced. And yeah, I was looking through your different projects that you've done, and I saw the golf. There was a golf app, and that was the one that stood out to me the most. It was. That was really neat. But it was a golf ball or something that could determine
[00:33:12] Ghazenfer Mansoor: Yeah. Golf ball scanning app. Yeah. That's healthcare, but that's where Yeah. We created a traditional model training it because every ball to detect the playability, detect the damage, different things.
[00:33:24] Mel: Yeah. It's just neat to see all the different applications of it that you can. That you're building. That's cool.
[00:33:30] Ghazenfer Mansoor: There are a lot of other applications, even in the healthcare side, we're building that has, AI involved. So. Yeah. A and that's, that's going to be the direction people are going. So more and more healthcare companies are willing to use AI in their projects. Everybody wants to use it, not everybody's ready for it.
[00:33:52] Mel: Yeah. That's a great point.
[00:33:54] Ghazenfer Mansoor: And I tell people, like, technology doesn't fix broken thinking. It amplifies it, so you have to have those things ready. You have to have your right processes. Then the technology will help you.
[00:34:06] Mel: Yeah. So as far as future plans, do you have any news or new things that you're doing at Technology Rivers? Anything exciting that you wanna share? Or last comments or things that you wanna say to our audience before we wrap up here?
[00:34:26] Ghazenfer Mansoor: Yeah. So I think I already shared in my previous comment that everybody in our company, we're trying to do 10X productivity. Every role doesn't matter whether you're an ops person, whether you're a QA, everybody is adapting AI to be more productive. So that's the main thing. And we started doing that. Like, we get a requirement, and we create a quick POC before our calls. So that's something we started doing because we can do that now with technology. So that's definitely one of the main things that I'll probably be talking about more and more in the coming days. Because that's a big achievement.
[00:35:10] Mel: Yeah. Well, thanks so much for joining me for this episode and it was really nice chatting with you and sharing all your insight.
[00:35:18] Ghazenfer Mansoor: Thanks for having me. It was great chatting.
[00:35:21] Mel: And thanks everyone for tuning into this episode of the Medcurity Podcast.
July 9, 2025