Google Cloud Next '24 | Sameer Sethi | Hackensack Meridian Health & Brian Doty | Deloitte Consulting LLP

Clips
News
More from Google Cloud Next '24

Sameer Sethi

Chief Data & Analytics Officer

Hackensack Meridian Health

Brian Doty

Principal

Deloitte Consulting LLP

Harnessing cloud power in healthcare: Hackensack Meridian Health’s journey to improving patient outcomes

In the current era of digital transformation, there’s a growing trend among healthcare organizations to shift their data to the cloud.Organizations such as Hackensack Meridian Health Inc. have successfully migrated to Google Cloud to improve patient care, operational efficiency and employee satisfaction through data analytics, AI deployment and change management, according to Sameer Sethi (pictured, left), the organization’s chief data and analytics officer. Meanwhile, the data analytic officer plays a key role in ensuring data and insights for patient care, engaging senior stakeholders and aligning incentives for technology projects in healthcare.“I function as a data analytics officer

play_circle_outline Real Organizations Leveraging Google Cloud: Partnerships, Collaboration, and Introducing Sameer Sethi and Brian Doty

play_circle_outline Overview of Hackensack Meridian Health and their data and analytics strategy

play_circle_outline Future goals include completing the migration and deploying AI applications for patient engagement

Info

Sameer Sethi | Hackensack Meridian Health & Brian Doty | Deloitte Consulting LLP

Sameer Sethi

Chief Data & Analytics Officer Hackensack Meridian Health

Brian Doty

Principal Deloitte Consulting LLP

search

>> Afternoon, everyone, and welcome back to theCube's live coverage of Google Cloud Next. We are here in smack dab in the middle of day two of the conference. I'm your host, Rebecca Knight, along with my co-host, Rob Strechay. Rob, one of the things that is just so much fun and so interesting on theCube is that we're talking to real organizations, what they're doing with their data, how they're moving their data. That's what really keeps the conversation going.

>> Absolutely. And I think, again, this should be a really fun time talking about this, because it's about how applicable all of what the announcements have been going on and how partners are really bringing this together with Google and with the customer in mind. And I think that's really what's great to pull out, because that helps other people when they're sitting at home trying to figure out, "How do I get started with these things?" Gives them ideas and

>> seeds.

>> And learnings. Exactly. Well, this is the perfect segue to introduce our next guest. They are Sameer Sethi. He's the Chief Data and Analytics Officer at Hackensack Meridian Health. Welcome.

>> Thank you for having me.And

>> Brian Doty, a principal at Deloitte Consulting. Thank you both so much for coming

>> on the

>> show.

>> Thanks for having

>> us.

>> Sameer, let's start with you. Tell us a little bit

>> about

>> Hackensack.

>> Sure. So we are a health system based out of New Jersey, 18 hospitals in total. The span all the way, starting the Hackensack up north and then spread ourselves down. It's been a very interesting ride for us, especially with Google, so really excited to have this conversation.

>> Great. Can you talk to us a little bit about your vision and your migration strategy?

>> Absolutely. So I function as a data analytics officer. My job and function is to make sure that our business units, including clinicians, have the data and the insights that they need to run their business, take care of patients. So my team focuses on bringing the data in from different source systems, normalizing the data, and then developing insights on top of that. What that to me means is that we develop the whys and the hows out of the data, versus just providing the data to folks.

>> And can you just break it down a little bit for our viewers too? What is that data, bringing it in

>> from

>> all

>> sources?

>> Yeah, so our largest data source is what we call an EMR, which is electronic medical record. This is a system that houses the patient information. So this is essentially what the doctor or the nurse or the clinician is punching in as a part of the process of a patient visiting a doctor that is our largest data source. We have other data sources. We have imaging data that we bring in. We have data related to people. We gather data from outside sources, social media. We have claims data, which is the processing of the payment, which is very rich as well for us. So we bring all that in. We try to create one record or one longitudinal view of a patient that starts to show us where the patient journey started, where it ended, what happened with them, and then we start to use it to take decisions.

>> Help us understand from a Deloitte perspective and a Google Cloud perspective, how do you get the stakeholders on board for these types of transformations and involving... Because I mean, again, there's a lot of PII, there's a lot of sensitive data, especially in healthcare. How do you really work with the

>> customers

>> on that

>> journey?

>> Yeah. Well, I think the first thing to really keep in mind is, although this is technology enablement, it is not a technology project, but the transformation, even just moving from an on-prem infrastructure into the cloud, there are changes in the way that the organization will access applications, access data, and certainly within the IT organization, there are changes in the way that people work. And so it's really important to engage senior stakeholders early in the process across the organization, set expectations around what they're trying to achieve, and ensure that everyone is aligned and that the messaging to the organization is focused on the benefits and really ensuring that it is a business-driven and IT-enabled initiative.

>> Providing access to data is not sufficient. I think what's important is to translate that into insights. That's what I think Deloitte and other organizations help us with. For the most part, providing data generally does not achieve an outcome, which is what we're looking for.

>> Okay. So where do you even begin preparing your people? I mean, Brian, you made this great point that this is not just a technology project. This is really a people project and that everyone needs to be on the same page pulling in the same direction, incentives, motivation needs to be aligned. So where do you even begin preparing your team for this?

>> Yes. I can take that. So first is customer first, whether it be the patient, for us, it's the nurse practitioners, it's the physicians, it's the hospital operators. Understanding their needs and building something around their needs is most important. So I think our approach at Hackensack and the vendors that work with us is primarily first understanding that and then building a product, a data product, around what's needed. And I think that allows us to obviously reach our outcomes. It actually increases adoption quite a bit. So I think that's what I think is what's required.

>> From a migration perspective, what was it actually that you were migrating into Google, and what was kind of the scope of

>> that?

>> So when I inherited the team, it was a very descriptive team. What that means is that we provided data and we started to show the why, but I think over time we have migrated into a mindset and an infrastructure and a technology stack that starts to do some prediction. So the migration for us has been an on-prem, very linear, let's provide the data and some insights on top of it, and now we are getting into the whys and the hows and what will happen. I think that's the migration. Google has helped us with that being on the cloud allows us to go to market with that a lot faster. When you work on-prem, you are working with obviously fixed cost, but you're also working with fix compute fix machine power versus in I think a cloud environment, what we have migrated to, you start to use the abilities to increase power, increase speed, increase processing as fast as you need it to.

>> So these projects never go maybe as smoothly as planned. I'd love for you, Sameer, to start talking a little bit about any challenges you experienced, any roadblocks or obstacles that you faced along the way. And then I'd love to get your thoughts too, Brian, about working with Hackensack through

>> these.

>> Yeah, I think for us, the struggles are really understanding the business. That's always hard. What we have generally seen is what we started off with from a concept of what was needed to what we actually ended up with is quite different.

>> Right?

>> Can you give an example though? That's

>> fascinating.

>> Yeah. So I mean, the example would be, for example, if we are in the process of optimizing our operation room usage, the OR is the most expensive asset for a health system, we generally start off by identifying where potentially we can actually fit in more procedures. But as a part of that journey, we start to realize there's things beyond that which impact, which is how do we bring in the factor of the patient being ready? How do we make sure that everything else is prepared prior to surgery? So a lot changes in that journey. So I think listening to the business units, to our customers, is really important.

>> So I'll share actually very specific sort of tactical example, going back to the discussion about this not being a technology project, but being a change to how people consume data and so forth. The simple, theoretically simple process of migrating reports from old technology to new technology in the cloud, there's both opportunity to look at the reports that you've historically been creating for an organization and rationalize that down to really make sure that you're only providing the necessary information, you're minimizing the number of reports, but in order to do that, you essentially need to redesign the reports to make sure that you're taking advantage of the capabilities of the new technologies and so forth. And in doing so, you're often changing some of the data and the way that it is being

>> presented

>> in those

>> reports. Oftentimes, because it is different than what the organization or the individuals, the end users, are used to seeing in the past, even if it is better, or even if we're able to determine that in fact some of the calculations that were historically being used were wrong and the new ones are correct, it still is jarring and there's a lot of resistance to that. So back to the change management and really setting the stage early around the benefits of this move, but recognizing that even things that may seem simple are not simple, and you have to make sure that you're engaging with the business from day one to make sure that you can streamline those processes

>> and

>> collaborate with

>> them.

>> By the time we will be done with migration, we would've migrated approximately 17,000 assets in whole. They'll not end up being 17,000 assets, the reason that's important is our approach is not lift and shift. We are not going to bring what was already there and probably working well and then reproduce this. Instead, we will go back to the business, ask the questions again, "Do you really need it? Does this solve your problem?And " then recreate it. So lift and shift is not an approach that Hackensack has taken.And

>> by assets do you mean servers? Do you mean databases? What are you

>> considering when you say assets?When

>> I speak of assets, I speak of assets from what the user uses. It could be an alert that gets fired as a part of their workflow. It could be a dashboard, it could be a report that they're getting in their email.

>> It's really interesting. And I think, again, moving to the cloud is always, to your point, it's always a difference and it's also probably different for your team and how they actually operate and the people and how they have to kind of change some of their skilling. How have you approached that as

>> well?

>> Yeah, it is definitely an up-skilling exercise, right? How you operate in cloud, the analogy that I use is when you're on-prem, if you leave the meter on, it doesn't cost you any more for the most part. Whereas if you leave the meter on the cloud, it continues to charge you. So I think optimization of how you use cloud infrastructure is really key. And Deloitte and other organizations actually are helping us with that, we don't do it well. At the end of the day, we are healthcare organizations that caters to need of patients and their families, and I think it's important to have the right partners who can teach us how to do it.

>> Well, speaking of re-skilling and up-skilling, I want to ask Brian, about what you were talking about earlier and making sure that it's the senior stakeholders, that the message is coming from top down, that we have set expectations and that people have an understanding of what their role is and how, yes, things will change, change is hard, but we can do this and there's reasons we're doing this. Can you talk a little bit about how you help leaders understand role and the importance of what they're doing and making sure that that messaging is getting through to Hackensack's leaders as

>> well as

>> throughout other

>> organizations too?

>> Yeah. And what you're really talking about is change management and not technical change management, but organizational change management. And we spend a lot of time up front in conversations with the client, really emphasizing the importance of that change management and really discussing the role that every leader in the organization plays in both setting the foundation for that change and frankly, giving folks permission to think about things in new ways, and also to ask questions and challenge both the way that things are being done and really just continuing the conversation there. I think the tone needs to be set from the top, but it is going to be implemented by the teams and that empowerment and the clarity around decision making and decision rights is a big part of that. We're not going to second guess every decision that the team makes, but we want to make sure that the decisions are being made with a consistent understanding of the end goal. And that's what change management really is, is establishing the foundation, building the case for change, and then empowering teams to really take the organization through that journey.

>> How did you decide to go down this journey? How did it all begin?

>> So I think two things. One is we are a very large Google partner. We started our journey with Google around five years ago, which is when we moved to work our workspace tools into GCP. And I think over time, we have seen how being on Cloud has helped us through that relationship with Google, we got introduced to what Cloud can do, and for us what that means is being able to go to market as fast as we can. There aren't any limits for us today, at least from a hospital perspective,- on finding the servers and the machines that we need to process data and make the insights available. So I think the decision for us was around being able to find the capability that allows us to

>> go to

>> market

>> fast. That's been the journey for us. That was a decision point for us, is we no longer wanted to limit ourselves to purchasing servers, managing servers. Instead, we'd rather work with organizations that do it much better than us and are able to provide those resources to us by swipe of a credit card. So we go online and there's a platform. We say we need this machine, this size, this memory, this storage, and it gets available to us instantly. That helps us quite a bit, because that's one problem that's gone. There are other problems obviously that we have to solve for, but at least that's something that we don't have to worry about.

>> And it also gives you a professional development opportunity for your teams. You're taking some of the more sort of rote activities off of their and allowing them to focus on the up-skilling and moving into the future, which I think is a really important retention and training tool as

>> well.It's making their jobs more interesting for them,

>> and

>> we're

>> satisfying too.

>> They get to focus on really the higher order activities, the more strategically important things as opposed to having to do the keep the lights on sort of activities that can be.

>> Well, just to piggyback on that, my question's for you is what has the response been both for the team and as well as the patients?

>> It's been amazing for us. I'll speak to this from a perspective of hiring and retaining talent, I think having the right technology in place keeps our workforce engaged, and the folks that we generally work with get very excited over technology. So having the leading edge technology through Google, I think has helped us retain amazing talent. As you can imagine, these folks that work for us have a choice. They could go across the river and work for the technology companies, but if you make that technology available for us, there's a bigger mission, which is they have the technology platforms to work on and they're helping save lives, help people live better, sometimes die better. So there's an advantage to that. So I think that that's been pretty huge for us. From a patient perspective, I think the digitization of data or availability of data or insights has been a lot easier as a result of everything that's happening here. That's been a huge advantage usually in the past, that was a very large blocker. It took us really a really long time for us to put things in place, and I think that through a cloud journey, and I think these technology company's taken a big part in making and enabling that need, I think go-to market has improved.

>> So we're here in 2024. What do you see as kind of your goals or where you hope to be next year when you're here at Google next and hopefully on theCUBE with us?

>> For me, I am hoping that we are not going to have a migration conversation. That would've been done and dusted with. I think with Deloitte's help, I mean these guys have been really awesome in telling us how to do it and create a factory around it. So I'm excited about that. The second would be, I think AI, that's the theme here. I think at Hackensack we tend to divide our AI use cases in three buckets. Operational efficiency, decision support, and patient experience. I think we are making some major moves around operational efficiency and decision support. What we haven't done a whole lot is make moves or make AI available that is more patient-facing. So I think next year, I would love to be in a position to say that we have actually deployed some use cases in production where we feel that there's safe AI in place that interacts with patients directly. We will have to create some sort of way by which there's human in the loop that's absolutely needed. Healthcare is a very human-centric business, but I think what I'm excited about. Next year for us is all about creating AI applications that are patient-facing.

>> Do you have any advice for other..?

>> Well, I think that the first piece of advice, particularly related to data and the migration of data is take a look at current processes. I think that this presents a real opportunity to improve upon the legacy data assets that you already have in-house. It is very, very important as you move into the world of AI and more advanced uses of this data, that the data is trustworthy, that it is clean, that it is well-governed. So take a step back and make sure that you have the foundational processes in place, and if not, to design those processes, so when this migration from on-prem legacy technologies into the new world of cloud occurs, you're ready to make sure that you are appropriately maintaining that new asset and that you won't have to deal with issues of trust and issues of quality as you really take on the

>> next order

>> opportunities.

>> And we're taking full advantage of that, by the way. As a part of our migration journey, we are looking at ways by which we can do automation instead of doing manual ways by which we were bringing the data in, so I think absolutely. And obviously governance is a big piece for us as well. This is an opportunity, true opportunity for us to look at what we didn't do well in the past and as we built in these new assets or rebuild these assets that we factor all those things in.

>> Wow. Wow. That's powerful.

>> Yeah.

>> Incredible. Well, Sameer and Brian, thank you both so much for coming on

theCUBE. This has >> been

>> a great

>> conversation.

>> Thank

>> .you very much for having us.I'm

>> Rebecca Knight for Rob Strechay, stay tuned for more of theCUBE's live coverage of Google Cloud Next, you are watching theCUBE, the leading source for enterprise tech news.

Sameer Sethi | Hackensack Meridian Health & Brian Doty | Deloitte Consulting LLP

search

>> Afternoon, everyone, and welcome back to theCube's live coverage of Google Cloud Next. We are here in smack dab in the middle of day two of the conference. I'm your host, Rebecca Knight, along with my co-host, Rob Strechay. Rob, one of the things that is just so much fun and so interesting on theCube is that we're talking to real organizations, what they're doing with their data, how they're moving their data. That's what really keeps the conversation going.

>> Absolutely. And I think, again, this should be a really fun time talking about this, because it's about how applicable all of what the announcements have been going on and how partners are really bringing this together with Google and with the customer in mind. And I think that's really what's great to pull out, because that helps other people when they're sitting at home trying to figure out, "How do I get started with these things?" Gives them ideas and

>> seeds.

>> And learnings. Exactly. Well, this is the perfect segue to introduce our next guest. They are Sameer Sethi. He's the Chief Data and Analytics Officer at Hackensack Meridian Health. Welcome.

>> Thank you for having me.And

>> Brian Doty, a principal at Deloitte Consulting. Thank you both so much for coming

>> on the

>> show.

>> Thanks for having

>> us.

>> Sameer, let's start with you. Tell us a little bit

>> about

>> Hackensack.

>> Sure. So we are a health system based out of New Jersey, 18 hospitals in total. The span all the way, starting the Hackensack up north and then spread ourselves down. It's been a very interesting ride for us, especially with Google, so really excited to have this conversation.

>> Great. Can you talk to us a little bit about your vision and your migration strategy?

>> Absolutely. So I function as a data analytics officer. My job and function is to make sure that our business units, including clinicians, have the data and the insights that they need to run their business, take care of patients. So my team focuses on bringing the data in from different source systems, normalizing the data, and then developing insights on top of that. What that to me means is that we develop the whys and the hows out of the data, versus just providing the data to folks.

>> And can you just break it down a little bit for our viewers too? What is that data, bringing it in

>> from

>> all

>> sources?

>> Yeah, so our largest data source is what we call an EMR, which is electronic medical record. This is a system that houses the patient information. So this is essentially what the doctor or the nurse or the clinician is punching in as a part of the process of a patient visiting a doctor that is our largest data source. We have other data sources. We have imaging data that we bring in. We have data related to people. We gather data from outside sources, social media. We have claims data, which is the processing of the payment, which is very rich as well for us. So we bring all that in. We try to create one record or one longitudinal view of a patient that starts to show us where the patient journey started, where it ended, what happened with them, and then we start to use it to take decisions.

>> Help us understand from a Deloitte perspective and a Google Cloud perspective, how do you get the stakeholders on board for these types of transformations and involving... Because I mean, again, there's a lot of PII, there's a lot of sensitive data, especially in healthcare. How do you really work with the

>> customers

>> on that

>> journey?

>> Yeah. Well, I think the first thing to really keep in mind is, although this is technology enablement, it is not a technology project, but the transformation, even just moving from an on-prem infrastructure into the cloud, there are changes in the way that the organization will access applications, access data, and certainly within the IT organization, there are changes in the way that people work. And so it's really important to engage senior stakeholders early in the process across the organization, set expectations around what they're trying to achieve, and ensure that everyone is aligned and that the messaging to the organization is focused on the benefits and really ensuring that it is a business-driven and IT-enabled initiative.

>> Providing access to data is not sufficient. I think what's important is to translate that into insights. That's what I think Deloitte and other organizations help us with. For the most part, providing data generally does not achieve an outcome, which is what we're looking for.

>> Okay. So where do you even begin preparing your people? I mean, Brian, you made this great point that this is not just a technology project. This is really a people project and that everyone needs to be on the same page pulling in the same direction, incentives, motivation needs to be aligned. So where do you even begin preparing your team for this?

>> Yes. I can take that. So first is customer first, whether it be the patient, for us, it's the nurse practitioners, it's the physicians, it's the hospital operators. Understanding their needs and building something around their needs is most important. So I think our approach at Hackensack and the vendors that work with us is primarily first understanding that and then building a product, a data product, around what's needed. And I think that allows us to obviously reach our outcomes. It actually increases adoption quite a bit. So I think that's what I think is what's required.

>> From a migration perspective, what was it actually that you were migrating into Google, and what was kind of the scope of

>> that?

>> So when I inherited the team, it was a very descriptive team. What that means is that we provided data and we started to show the why, but I think over time we have migrated into a mindset and an infrastructure and a technology stack that starts to do some prediction. So the migration for us has been an on-prem, very linear, let's provide the data and some insights on top of it, and now we are getting into the whys and the hows and what will happen. I think that's the migration. Google has helped us with that being on the cloud allows us to go to market with that a lot faster. When you work on-prem, you are working with obviously fixed cost, but you're also working with fix compute fix machine power versus in I think a cloud environment, what we have migrated to, you start to use the abilities to increase power, increase speed, increase processing as fast as you need it to.

>> So these projects never go maybe as smoothly as planned. I'd love for you, Sameer, to start talking a little bit about any challenges you experienced, any roadblocks or obstacles that you faced along the way. And then I'd love to get your thoughts too, Brian, about working with Hackensack through

>> these.

>> Yeah, I think for us, the struggles are really understanding the business. That's always hard. What we have generally seen is what we started off with from a concept of what was needed to what we actually ended up with is quite different.

>> Right?

>> Can you give an example though? That's

>> fascinating.

>> Yeah. So I mean, the example would be, for example, if we are in the process of optimizing our operation room usage, the OR is the most expensive asset for a health system, we generally start off by identifying where potentially we can actually fit in more procedures. But as a part of that journey, we start to realize there's things beyond that which impact, which is how do we bring in the factor of the patient being ready? How do we make sure that everything else is prepared prior to surgery? So a lot changes in that journey. So I think listening to the business units, to our customers, is really important.

>> So I'll share actually very specific sort of tactical example, going back to the discussion about this not being a technology project, but being a change to how people consume data and so forth. The simple, theoretically simple process of migrating reports from old technology to new technology in the cloud, there's both opportunity to look at the reports that you've historically been creating for an organization and rationalize that down to really make sure that you're only providing the necessary information, you're minimizing the number of reports, but in order to do that, you essentially need to redesign the reports to make sure that you're taking advantage of the capabilities of the new technologies and so forth. And in doing so, you're often changing some of the data and the way that it is being

>> presented

>> in those

>> reports. Oftentimes, because it is different than what the organization or the individuals, the end users, are used to seeing in the past, even if it is better, or even if we're able to determine that in fact some of the calculations that were historically being used were wrong and the new ones are correct, it still is jarring and there's a lot of resistance to that. So back to the change management and really setting the stage early around the benefits of this move, but recognizing that even things that may seem simple are not simple, and you have to make sure that you're engaging with the business from day one to make sure that you can streamline those processes

>> and

>> collaborate with

>> them.

>> By the time we will be done with migration, we would've migrated approximately 17,000 assets in whole. They'll not end up being 17,000 assets, the reason that's important is our approach is not lift and shift. We are not going to bring what was already there and probably working well and then reproduce this. Instead, we will go back to the business, ask the questions again, "Do you really need it? Does this solve your problem?And " then recreate it. So lift and shift is not an approach that Hackensack has taken.And

>> by assets do you mean servers? Do you mean databases? What are you

>> considering when you say assets?When

>> I speak of assets, I speak of assets from what the user uses. It could be an alert that gets fired as a part of their workflow. It could be a dashboard, it could be a report that they're getting in their email.

>> It's really interesting. And I think, again, moving to the cloud is always, to your point, it's always a difference and it's also probably different for your team and how they actually operate and the people and how they have to kind of change some of their skilling. How have you approached that as

>> well?

>> Yeah, it is definitely an up-skilling exercise, right? How you operate in cloud, the analogy that I use is when you're on-prem, if you leave the meter on, it doesn't cost you any more for the most part. Whereas if you leave the meter on the cloud, it continues to charge you. So I think optimization of how you use cloud infrastructure is really key. And Deloitte and other organizations actually are helping us with that, we don't do it well. At the end of the day, we are healthcare organizations that caters to need of patients and their families, and I think it's important to have the right partners who can teach us how to do it.

>> Well, speaking of re-skilling and up-skilling, I want to ask Brian, about what you were talking about earlier and making sure that it's the senior stakeholders, that the message is coming from top down, that we have set expectations and that people have an understanding of what their role is and how, yes, things will change, change is hard, but we can do this and there's reasons we're doing this. Can you talk a little bit about how you help leaders understand role and the importance of what they're doing and making sure that that messaging is getting through to Hackensack's leaders as

>> well as

>> throughout other

>> organizations too?

>> Yeah. And what you're really talking about is change management and not technical change management, but organizational change management. And we spend a lot of time up front in conversations with the client, really emphasizing the importance of that change management and really discussing the role that every leader in the organization plays in both setting the foundation for that change and frankly, giving folks permission to think about things in new ways, and also to ask questions and challenge both the way that things are being done and really just continuing the conversation there. I think the tone needs to be set from the top, but it is going to be implemented by the teams and that empowerment and the clarity around decision making and decision rights is a big part of that. We're not going to second guess every decision that the team makes, but we want to make sure that the decisions are being made with a consistent understanding of the end goal. And that's what change management really is, is establishing the foundation, building the case for change, and then empowering teams to really take the organization through that journey.

>> How did you decide to go down this journey? How did it all begin?

>> So I think two things. One is we are a very large Google partner. We started our journey with Google around five years ago, which is when we moved to work our workspace tools into GCP. And I think over time, we have seen how being on Cloud has helped us through that relationship with Google, we got introduced to what Cloud can do, and for us what that means is being able to go to market as fast as we can. There aren't any limits for us today, at least from a hospital perspective,- on finding the servers and the machines that we need to process data and make the insights available. So I think the decision for us was around being able to find the capability that allows us to

>> go to

>> market

>> fast. That's been the journey for us. That was a decision point for us, is we no longer wanted to limit ourselves to purchasing servers, managing servers. Instead, we'd rather work with organizations that do it much better than us and are able to provide those resources to us by swipe of a credit card. So we go online and there's a platform. We say we need this machine, this size, this memory, this storage, and it gets available to us instantly. That helps us quite a bit, because that's one problem that's gone. There are other problems obviously that we have to solve for, but at least that's something that we don't have to worry about.

>> And it also gives you a professional development opportunity for your teams. You're taking some of the more sort of rote activities off of their and allowing them to focus on the up-skilling and moving into the future, which I think is a really important retention and training tool as

>> well.It's making their jobs more interesting for them,

>> and

>> we're

>> satisfying too.

>> They get to focus on really the higher order activities, the more strategically important things as opposed to having to do the keep the lights on sort of activities that can be.

>> Well, just to piggyback on that, my question's for you is what has the response been both for the team and as well as the patients?

>> It's been amazing for us. I'll speak to this from a perspective of hiring and retaining talent, I think having the right technology in place keeps our workforce engaged, and the folks that we generally work with get very excited over technology. So having the leading edge technology through Google, I think has helped us retain amazing talent. As you can imagine, these folks that work for us have a choice. They could go across the river and work for the technology companies, but if you make that technology available for us, there's a bigger mission, which is they have the technology platforms to work on and they're helping save lives, help people live better, sometimes die better. So there's an advantage to that. So I think that that's been pretty huge for us. From a patient perspective, I think the digitization of data or availability of data or insights has been a lot easier as a result of everything that's happening here. That's been a huge advantage usually in the past, that was a very large blocker. It took us really a really long time for us to put things in place, and I think that through a cloud journey, and I think these technology company's taken a big part in making and enabling that need, I think go-to market has improved.

>> So we're here in 2024. What do you see as kind of your goals or where you hope to be next year when you're here at Google next and hopefully on theCUBE with us?

>> For me, I am hoping that we are not going to have a migration conversation. That would've been done and dusted with. I think with Deloitte's help, I mean these guys have been really awesome in telling us how to do it and create a factory around it. So I'm excited about that. The second would be, I think AI, that's the theme here. I think at Hackensack we tend to divide our AI use cases in three buckets. Operational efficiency, decision support, and patient experience. I think we are making some major moves around operational efficiency and decision support. What we haven't done a whole lot is make moves or make AI available that is more patient-facing. So I think next year, I would love to be in a position to say that we have actually deployed some use cases in production where we feel that there's safe AI in place that interacts with patients directly. We will have to create some sort of way by which there's human in the loop that's absolutely needed. Healthcare is a very human-centric business, but I think what I'm excited about. Next year for us is all about creating AI applications that are patient-facing.

>> Do you have any advice for other..?

>> Well, I think that the first piece of advice, particularly related to data and the migration of data is take a look at current processes. I think that this presents a real opportunity to improve upon the legacy data assets that you already have in-house. It is very, very important as you move into the world of AI and more advanced uses of this data, that the data is trustworthy, that it is clean, that it is well-governed. So take a step back and make sure that you have the foundational processes in place, and if not, to design those processes, so when this migration from on-prem legacy technologies into the new world of cloud occurs, you're ready to make sure that you are appropriately maintaining that new asset and that you won't have to deal with issues of trust and issues of quality as you really take on the

>> next order

>> opportunities.

>> And we're taking full advantage of that, by the way. As a part of our migration journey, we are looking at ways by which we can do automation instead of doing manual ways by which we were bringing the data in, so I think absolutely. And obviously governance is a big piece for us as well. This is an opportunity, true opportunity for us to look at what we didn't do well in the past and as we built in these new assets or rebuild these assets that we factor all those things in.

>> Wow. Wow. That's powerful.

>> Yeah.

>> Incredible. Well, Sameer and Brian, thank you both so much for coming on

theCUBE. This has >> been

>> a great

>> conversation.

>> Thank

>> .you very much for having us.I'm

>> Rebecca Knight for Rob Strechay, stay tuned for more of theCUBE's live coverage of Google Cloud Next, you are watching theCUBE, the leading source for enterprise tech news.