Google's Healthcare Data Engine - Building the Longitudinal Patient Record
Episode 1559th August 2021 • This Week Health: News • This Week Health
00:00:00 00:07:19

Transcripts

 This transcription is provided by artificial intelligence. We believe in technology but understand that even the smartest robots can sometimes get speech recognition wrong.

  Today in Health it Mayo Clinic, Google Cloud, getting together to build a healthcare data engine. My name is Bill Russ. I'm a former CIO for a 16 hospital system and creator of this week in Health IT a channel dedicated to keeping health IT staff current. I. And engaged VMware has been committed to our mission of providing relevant content to health IT professionals since the start.

They recently completed an executive study with MIT on the top Healthcare trends, shaping IT, resilience, covering how the pandemic drove unique transformation in healthcare. This is just one of many resources they have for healthcare professionals. For this and several other great content pieces, check out vmware.com/go/healthcare.

All right, here's today's story. This comes from MedCity News. Title is what Google Cloud learned about interoperability from Mayo Clinic. All right, so Google is piloting its Healthcare Data Engine, a tool intended to build longitudinal patient records and pull in data from multiple sources Early Work with Mayo Clinic, served as the foundation for the technology articles from August 2nd.

And here goes a little over a year ago, Google Cloud and Mayo Clinic struck a 10 year strategic partnership with the goal of building an assembly line of clinical AI tools. To support this, they'd need to have comprehensive and standardized data sets a rarity in healthcare, but this process of aggregating together healthcare data.

And bringing it to the cloud was time consuming, even for Mayo Clinic, which has more technical resources than most. Part of the challenge was that engineers needed to evaluate different options for cloud configurations, including best practices for networking and security. Working with Mayo Clinic through this helped Google Cloud as it was building its healthcare data engine, a cloud-based tool for healthcare companies to aggregate and standardize data.

From medical records, insurance claims, clinical trials and research, the learnings around that configuration are something that we've incorporated as well as our learnings from other large organizations like Mayo, who brought protected health information onto the cloud, said Maryanne, slight product manager for Google Cloud.

Healthcare analytics in a video interview. The platform is intended to make it easier for health systems to get real-time information to identify high risk patients, allocate resources, and other critical decisions. Before this, most health systems aggregated data manually using clinical data warehouses, which can be harder to scale and keep up to date knowing what types of data sources and formats Mayo Clinic wanted to work with.

Helped Google focus its attention on what to build as a cloud provider. Slight emphasize that Google Cloud cannot look at customer's health data or train models on that data. John Brock, Mayo Clinic's Vice Chair of Information Technology, said in a news release that the health system had been hitting a wall with its ability to innovate using on-premise software.

There are so many applications of this. For example, building a heads up display for the ICU where moments matter to help care teams direct their attention when and where it's needed most. He said, from creating better ways to care for patients remotely. Even after they leave the hospital to making it easier for patients to interact with us via mobile apps, we're working alongside Google Cloud to build a platform for healthcare transformation.

The healthcare data engine is currently available as a pilot. Some of Google's customers are looking to use it. To run projects on population health and transitions of care. Another project is focused on health equity, specifically ensuring all patients were getting follow-up screenings. Slight said, Indiana University Health, one of Google's named pilot customers is working on using the platform to improve care delivery.

Google isn't the only company working on this problem. Amazon also recently announced. Amazon Health Lake, which we talked about last week on the show, its own cloud-based system to help healthcare companies store and analyze health information. So that's enough from the story. What's the so what on this?

The next major differentiation in healthcare is gonna come from data. Creating, collecting and making meaning of data, using data to improve experience using data to treat patients more precisely. We've seen this in other industries. Knowing the customer better than the competitors is a significant advantage.

You can market just what they need almost at the right time. In medicine, it is having the right information about the person to recommend a certain course of action or prescribe a drug. That is perfect for their situation. Perhaps not entirely possible today, but well within reach. This is what Google and Amazon have perfected, collecting and making meaning out of large amounts of information.

There's a differentiation to be had, but I still worry about privacy. The health systems have collected information about us, the patients for years, and now they have. Really recognize the value and so have others. We've come to accept the surveillance economy when we assume and accept the trade-off of giving away our email for the value of whatever digital asset we are going to receive.

However, we didn't enter into that type of relationship with our health system. We never expected the information that we shared with our physician at our time of need to be used in any other way, but to care for us at that moment. A broader pact must be struck between the patient and the provider in order to maintain the trust that is required to provide great care.

If that veil is ever broken, it is almost impossible to repair. It hasn't been yet. I wanna be real clear, it hasn't been, at least that I'm aware of. This is just a preemptive warning to say it must never happen. Do you have governance set up around who and how patient information gets shared in your organization?

Do you have policies around this? This is all part of data governance. I'm just asking the question. I'm curious how many of you know the answer? That's all for today. If you know of someone that might benefit from our channel, please forward them a note. They can subscribe on our website this week, health.com, or wherever you listen to podcast Apple, Google Overcast, Spotify, Stitcher.

You get the picture. We are everywhere. We want to thank our channel sponsors who are investing in our mission to develop the next generation of health leaders, VMware Hillrom, Starbridge Advisors, McAfee and Aruba Networks. Thanks for listening. That's all for now.

Chapters