HEALTHTECH: What kind of technology and governance foundation is needed to deploy edge-to-cloud AI? Do most healthcare organizations already have this foundation in place?
NIEWOLNY: New software applications are driving this need in many cases. Some healthcare organizations have bits and pieces of that infrastructure and governance today, but you’re looking at a foundation of accelerated compute. You need data center and edge in addition to size for the workload. You need reliable networking, storage, standardized containers, application programming interfaces, identity access, device management and monitoring. There are a lot of pieces that a standard healthcare IT system should have in place.
However, when you start bringing in mission-critical applications, you now need a governance system that connects the clinical with IT, security, privacy, legal and the development teams that may be building and deploying AI.
Governance models are being developed, and some of this is being outlined by regulatory agencies. This is true especially in terms of what they’re expecting from device manufacturers and software providers, such as predetermined control-change plans and ensuring they can maintain and update the software on a regular basis.
HEALTHTECH: How can hospitals balance the need to keep data local with the benefits of a centralized AI model?
NIEWOLNY: That’s tricky, and I’d say they should definitely err on the side of caution. Most people don’t want raw patient data to leave the site. In that case, you want models that can be deployed locally at the edge. Then the organizations end up choosing only to centralize what they deem is appropriate, such as approved model artifacts, de-identified data, aggregated telemetry data or performance metrics. That’s the type of data that can be managed off-prem in a cloud or data center.
In many cases, we’re working with organizations to minimize some of their data. For some of the larger healthcare organizations we’re looking at building federated data approaches and creating synthetic data on-prem to make sure they have that data in place. Centralization comes into play when you start talking about large-scale governance, reproducibility, fleet health, learning across multiple sites and anything involving a lot of patient data within the confines of a healthcare organization.
RELATED: Enable faster clinical decisions at the point of care with real-time analytics at the edge.
HEALTHTECH: What advice do you have for organizations interested in deploying edge-to-cloud AI?
NIEWOLNY: Health systems looking at edge-to-cloud deployments are often buyers of technology, not necessarily builders, so they’re going to have to understand the different AI applications they plan on running. Some med tech and health tech may provide their own infrastructure as part of an end-to-end solution due to the complexity of working within a health organization’s IT system. However, some of them may require the organization to have their own edge infrastructure in place.
Ask how edge compute is being delivered for the AI applications and software you’re leveraging. Is that being delivered with the solution, similar to a medical device, or is this something that is truly being deployed as software? We are working with different healthcare organizations to help them build a true infrastructure from the ground up that allows them to provide edge-to-cloud capabilities within the hospital — essentially, at the time of build or retrofit.
NVIDIA is working with a lot of these companies to democratize edge technology, which can reduce costs. Providing edge architecture based on the software you’re using and the workloads you need, you can ensure your hospital is future-proofed with edge-to-cloud applications that are true software applications running on your IT infrastructure.
