For the 113th episode of the CIO podcast hosted by Healthcare IT Today, we are joined by Nitin Agarwal, Chief Information Officer at Wayne Memorial Hospital, to talk about balancing hospital operational needs with technology and innovation! We kick this episode off with one of the biggest technologies in healthcare right now – AI. Agarwal shares where and how he sees AI currently benefiting his organization. Then we discuss how to approach AI as it evolves so quickly. Next, we take a look at Agarwal’s approach with implementation to learn more about how he chooses what to implement. With hundreds of solutions out there, how does he decide among them, and why not go with just one nice AI platform?
We then transition over to innovation by discussing whether Agarwal views his EMR and ERP platforms as an approach to innovation or a challenge to innovation. Next, we get Agarwal’s perspective on healthcare interoperability. We dive deep to see where interoperability is helping his organization and what areas it should be in that it’s not. Next, we get into the big question of the episode – how do CIOs balance hospital operational needs with technology and innovation? Then we learn more about the challenges Agarwal is facing, that aren’t getting enough acknowledgment. We then conclude this episode with Agarwal passing along the best piece of advice he’s been given in his career.
Now, without further ado, we’re excited to share with you the next episode of the CIO Podcast by Healthcare IT Today.
We release a new CIO Podcast every ~2 weeks. You can also subscribe to the Healthcare IT Today podcast on any of the following platforms:
Thanks for listening to the CIO Podcast on Healthcare IT Today and if you enjoy the content we’re sharing, please rate the podcast on your favorite podcasting platform.
We’d love to hear what you think of the podcast and if there are other healthcare CIO you’d like to see us have on the program. Feel free to share your thoughts and perspectives in the comments of this post with @techguy on Twitter, or privately on our Contact Us page.