Imagine a World Where Health Data Flows Freely, Securely, To the Point of Care

Healthcare on FHIR, MyHeathEData, BlueButton for 53 Million Medicare Patients, and a confirmation on the direction and actionable response from Joe Biden on these announcements. Today we are joined by my good friend Aneesh Chopra.

Please follow the show on Itunes, Google Play and Stitcher
Follow This Week in Health IT on Twitter @ThisWeekinHIT
Take a look at the website
Follow Bill Russell on LinkedIn and Twitter
Reach out to [email protected] if you want to discuss your next project.

This Week in Health IT Apple Podcast This Week in Health IT Google Play  This Week in Health IT YouTube

AI Powered Transcription

Bill Russell:                   00:04               Welcome to this week and see where we discussed the news information in emerging thought with leaders from across the healthcare industry. This is episode number 11. It’s Friday, March 25

Bill Russell:                   00:13               third. Today. We imagine a world without clipboards, a world where the patient has access to their complete medical record, a world where data is working for you while you sleep, to diagnose problems before they happen. A world that unfortunately doesn’t exist yet, but we’re closer today than we’ve ever been. Uh, today we talk about what makes that a reality. Data, liquidity and interoperability. Uh, this podcast is brought to you by health lyrics, a leader and moving healthcare to the cloud. To learn more, visit [inaudible] dot com. My name is Bill Russell, recovering healthcare cio, writer and consultant with the previously mentioned health lyrics. Today I’m joined by the preacher on fire in reference to his favorite topic and like that and the nature of the meetings that he holds a. The first time we met I was asked to be on a panel with, uh, Aaron Levie from Box Lee Shapiro, formerly all scripts, now a seven wire ventures.

Bill Russell:                   01:06               And this former cto of the federal government and the room was filled to capacity. My heart stopped for, for a good 20 seconds, but when Aneesh Chopra leads a meeting, it is a community building experience. We started on one topic and soon we were fielding questions about all things healthcare finally landing on, quite frankly, some of the same topics we’re going to be discussing today. And, uh, I’m really excited to have him. So, uh, president of care journey, former first CTO, the federal government, and my good friend and each chopper on the show. Good morning, a nice welcome to the show.

Aneesh Chopra:            01:42               Good morning, Bill. Thank you for having me and for your leadership.

Bill Russell:                   01:45               Uh, thanks. Thanks. Thanks for your leadership as well that this could end up being a love fest or one of my favorites

Aneesh Chopra:            01:51               people healthier, but we’re going to get substantive.

Bill Russell:                   01:56               We’ll get there real quick. You know, last week I had a, a heloc go on the show and he was very pragmatic about this topic. It was a lot of fun. Uh, but it was really hard to do his bio. His bio goes on for days. It’s the longest bio I’ve ever seen. Um,

Aneesh Chopra:            02:11               I just met him on a shuttle bus in 1997. We used to ride the bus together when he was a graduate student at mit and I was at the Kennedy School.

Bill Russell:                   02:20               So you guys have been really good friends for awhile.

Aneesh Chopra:            02:24               I consider him a brother.

Bill Russell:                   02:26               This’ll, this’ll be, this’ll be good. I did ask him if there was any special question I should ask you. And, and he laughed, but, um, you know, the great thing about your bio is insured. I got it from the Washington speakers bureau, a website, so a visionary technology thought leader, President Care Journey, a chief technology officer, the officer of the United States, 2009 to 12, author of innovation state. Uh, the new technologies, how new technologies can transform. The government will touch on that a little bit and it goes on to say a couple other things. You don’t, you don’t want me to embarrass you with. Actually,

Aneesh Chopra:            03:05               we’re all good. We’re all good. Let’s dive in.

Bill Russell:                   03:08               Well, you know, and I, I appreciate it. Uh, let’s see. So one of the things we do is with every, um, with every guest we ask them, is there anything you’re working on right now that you’re really excited about? And, and, uh, you know, we’re going to talk about interoperability. We’re going to talk about fire, we’re going to talk about stuff, but is there, is there anything outside of the. Talk a little bit about care journey. What are you doing there?

Aneesh Chopra:            03:30               Yeah. Well My, uh, I would say my passion right now is making sure that we extract as much clinically relevant insight out of the data we’re organizing for population health. So we had this kind of journey in the first chapter of population health where everybody was trying to learn the language of the insurance industry. What is my spend rate per thousand or utilization rate, how’s my spend for risk adjusted patients looking like? And physicians often have their eyes glaze over, like, oh, you kidding me. This is not a language I particularly care to learn, but the power in some of the version one of all of these population health programs is that we had access to patients longitudinal claims history. And if you use the same data asset a and reposition it for you, surround clinically relevant insights which patients should be eligible for certain care protocols that are more population based that they haven’t been, who shouldn’t be enrolled in diabetes prevention, who should get a care transition visit. These are opportunities where clinicians engage more directly because it helps them think about their patient population in a way that is more relevant to them. So my passion is just to grow an open community of algorithms and other methods to identify which patient segments should get which care protocols and to help encourage folks to deploy those and measure their impact over time. So that’s what my passion is these days.

Bill Russell:                   04:54               That’s great. That’s great. And, and uh, actually you’ve educated me somewhat on that when I was at St Joe’s, just the, the amount of data that we had access to it I really wasn’t aware of until we sat down and had that meeting. So it was really, really helpful. Uh, okay. So this last, this last week, we’re going to deviate from the show’s format. We generally have a format where we, we go back and forth on the news, we talked about leadership attack and then we close out with a, with a social media posts. Do you have a social media post or something for this week?

Aneesh Chopra:            05:31               We’ll do that.

Bill Russell:                   05:33               You could do what did he just shared his last post which works, um, if you haven’t checked them out. Uh, David Baker and I reported from the hymns floor. John Blanca and I talked last week about a machine learning the role that a cio and things from him. And uh, and this will be the last week. We just dive deep in him. So we are going to try to make sense of a lot of stuff. So my healthy data blue button, two point. Oh, $53 million Medicare patients. Uh, not a lot on [inaudible], but we’ll talk about it. Fire. We’re going to talk, we’re going to go back and forth a little bit on the smokey Joe Biden’s response. A pretty good, pretty substantive article that I’m gonna pull up here from fortune a little about that. And, uh, we’ll talk a little about, a little bit about a new role, a shepherding a on the open API initiative. So if you are ready, let’s, let’s start with a quick history lesson. And, uh, so you appeared on the daily show with Jon Stewart and you’ve now completed the, uh, the trivia question of what gas does appeared on both the daily show and this week in health it. Um, but I did, I did watch it. He grilled you on this. I’m really on this very topic on the Va. Do you remember what year that was?

Aneesh Chopra:            06:54               Uh, 2014,

Bill Russell:                   06:56               2014. All right. So, um, let’s talk about the state of things anD. Well actually let’s talk. Let’s go back to 2014. So tell us what you found in the federal government on this topic of interoperability and uh, and then I’ll talk a little bit about what I found because I came into healthcare for the first time in 2011. I’ll tell you what I found with my experience from other industries.

Aneesh Chopra:            07:20               Well, I would say there are three things to take from government. One is the initial trajectory of moving a health information exchange forward, carried beyond just the bush administration through the obama years and even now through the trump years in a matter that was harder to deviate once launched. That is to say we built a kind of an initial use case around business to business models for health information exchange and we put a lot of resources behind that model. Even though we started shifting the portfolio a bit in the obama years. The new directions didn’t have as much capital or or investment plan behind them as the initial theory of b two b exchange. So point number one is you’ll launch something in the government. It has kind of a life of its own and it carries in a big, big way. Point number two, the federal government can be both an enabler and the constraint on some of these issues and we can talk a bit about that.

Aneesh Chopra:            08:22               And then the last piece that I think was the lesson I wish I had learned earlier in the process was that if we found a way to get through the clutter and said, let’s go straight to the patient. If we figured that out earlier, we might have a slightly different, uh, architecture for the healthcare delivery system today. So that’s a little bit of a somewhat historical bummer that we take personal blame on a lot of it because we shepherd it a pretty significant $37 billion dollar investment because it was tied to the recovery act. We had to get the money out the door, which meant the ability to shift the allocation of those dollars down the road became more difficult. I think you would have lamp you got into some of that, which is now that we get to the final stage of meaningful use or the old meaningful use dollars left or less. But the change is hard. And so you’ve got this disconnect and we can get into all of those things. It would be useful.

Bill Russell:                   09:15               My entry into healthcare, there’s a couple things shocked me. One is the, uh, the patient really didn’t own their medical record. That kind of surprised me. The second one is the lack of a modern architecture. Know 2011, I’d come from other industries. I like to tell people, beers, beer, banks and bombs, you know. So anheuser busch, mcdonald douglas, I’ve worked for a bank of America. I’ve done a lot of consulting with various companies and all those industries. There was a open standards api, the atm network and those kinds of things. Um, and, and that didn’t exist within healthcare, but the, uh, the, it, it’s taken awhile for that to really take off. But the other thing, I didn’t really appreciate it. We’d just gone through a heavy lift. Mau was a heavy lift for a, for healthcare. Uh, I’m not sure that health care would have been digitized without smu.

Bill Russell:                   10:10               There was, there’s so many things aligned against it. It’s such a complex industry, which I didn’t appreciate when I first came in. And, and, uh, there’s, there’s just a lot of things to get right. And so it was a lot harder to get that ball rolling up the hill than I had anticipated. The good news is, I think we are a lot farther along now than we were back in 2011, 2014. So, uh, let’s, let’s hit some of these, some of these announcements. A seam of irma came to hymns to did a, my healthy data initiative. She didn’t. The blue button. Two point. Oh, initiative. Do you want to give us a little little background on the two of those and where you think they’re going to go?

Aneesh Chopra:            10:53               Well, let me begin by saying the annoUncement that she made that couldn’t have been more bipartisan, or maybe we’d call it nonpartisan. If you removed the, the voice of fema or the voice of jarret and simply read that presentation without knowledge or context as to who might’ve delivered it. You could have imagined anyone from the obama administration carrying that message forward. So this is really building on progress and really pushing it further and faster in the direction that it desperately needs to go. So that’s why you saw me applaud a great deal of the work that was done. The big message I would say is that the healthcare delivery interoperability strategy that I mentioned before, the b to b model was built on the foundation of a hipaa authorizations were you. You may share a, you’re allowed to share, but it doesn’t compel you to share.

Aneesh Chopra:            11:44               So you could put a request in as a physician, hey, I’ve got this patient could just send me the records and if they chose not to respond then you wouldn’t get data. But they were legally allowed to respond and so we had this framework of you might be able to share, but you didn’t. You didn’t hAve to. What [inaudible] saying is that the other half of hipaa, the individual right of access, it doesn’t mean you own your medical record bill, it means you’re entitled to an electronic copy and in a readily produceable format. TheSe are words that are going to come into play in the api discussion. So sima basically said, I’m going to pivot and embrace information exchange tied to that consumers. Right? And that I think is the kind of sea change that naturally is a progression of where we learned as we went and that’s the model I think that’s going to carry lowest cost, highest data liquidity because it’s a legal right to request a copy in a readily produceable form.

Aneesh Chopra:            12:39               And she built on that. That’s the my healthy data vision. The blue button two point. Oh, is I would call that dogfooding dogfooding is you’re eating your own dog food and the operations of blue button two point zero is essentially an api for a fire based explanation of benefits resource that allows a patient to connect four years of claims history and an ongoing token for weekly updates to any application of their choice. So what she’s encouraging the industry to do on its own and, and using the levers of mips and macra and all the other components she’s operationalizing within cms. And she even made the joke, it was blue button to point out meaning it was a work in progress from the obama administration and she just took it into the finish line, which is what leadership is about.

Bill Russell:                   13:27               Yeah. I mean, todd park really is the one who brought us a blue button one point. Oh, and a kind of park who’s, where’s town park these days, is he?

Aneesh Chopra:            13:35               Todd todd is running a wonderful new company called devoted health. Uh, he’s going to reimagine What life is like for seniors and medicare advantage plans. And so we’re all watching and excited about what he’ll do to make the care delivery model better.

Bill Russell:                   13:49               He was one of the people that influenced me early on. I saw a couple of his speeches of how he was going to open up data for the federal government. It really is a model for what we’re trying to do here today. so it’s exciting. So are we finally at a point where the, I mean, that’s an interesting distinction. I don’t own my medical record, but I have access to it electronically is that, does that create a new ecosystem where the apples and the googles and amazons and the others of the world can now say, hey, the patient is the center of medical record, not necessarily the health system. So now we can create a. We talked about these ecosystems and I think will arise where the cloud providers will say, hey, if you as a patient want to give us your data, we can now add value to it or we can now add other data to it and make it, enhance it and make it better. Um, and you know, pharma, we couLd, we could participate in, we can choose, we can go to our phone and say, I want to participate in this study in order to further this, uh, you know, this disease state, whatever we’re going to do around that. Are we at a point where the patient is finally the, the, the locus of, of, of this, the medical record, or we’re not there yet.

Aneesh Chopra:            15:03               We are, but what’s missing right now, bill, is that delightful application that helps my mom and my dad on medicare make the best use of that information. So we’ve got the plumbing technical standards, right? We’ve got a legal and regulatory framework that encourages it. We’ve got the cloud providers and others helping to facilitate adoption and use. But that last step, who’s going to help read my mom’s a medicare blue button file and remind her when she should get care or where if she needs care, she can choose the right provider that meets the needs that she has to have addressed. And my perSonal opinion is that this is gonna look a lot like the transition from pension plans to 401k’s where we used to have these employer, a fiduciaries that would take our money and make big judgments even if we might have wanted to do something else or someone else could have given this advice to have a better and more reliable retirement.

Aneesh Chopra:            16:04               The move to 401ks gave rise to companies that didn’t exist or if they did, they were modest vanguard and fidelity and others. So I think there’s going to be a new rise of what we’ll call a health information fiduciary who will work on the cloud platforms to do the plumbing of getting the data, but it’s going to be their last mile application. That will help make sense of that information. So I can shop smarter for supplemental plans so I can navigate the delivery system more effectively and I can access and use the preventive services to keep me healthier and whole range of other things that we’ll, we’ll see happen.

Bill Russell:                   16:38               Well, let’s, let’s talk about. So this show originally did this show for cio is to share with their staff so they can stay current. Let’s, let’s get into a little bit more of the technical aspects. So you have to hire what, what is, uh, what does the cio tell his organization or what does, um, what does the, the, the front line staff do with tepco and fire and where should they start? Where are we at?

Aneesh Chopra:            17:02               So, uh, this is a conundrum which is you can either be a supply cider, which is your job is to envision the infrastructure that you’re responsible for, modernize it, and prepare for the future. The other is a listener and responsiveness to the clinical leadership. I’m generally on the side of listened first, which is to say there’s a signal out there that you’re hearing from frontline clinicians from positions that are involved in these new value based models and they’re complaining about something about the difficulty to do their job and of course there’s general complaint, but then there’s more specific complaint. I would like to know this at this time in this way so I can make a decision without weakening my productivity, so my sense that if you start to listen as if you’re the cio and you start listening to the customer’s needs in a manner that perhaps we don’t quite do today because we make a single decision, I’ve got to make a big ehr decision and I got to maintain it.

Aneesh Chopra:            18:02               Uptime, security, that’s its own job. Now I’m listenIng and saying, well, wait a minute. I’m no longer deciding what ehr to buy. Now I’m thinking what application might write on top of the ehr that might delight my individual care teams are clinicians and patients to have a better experience, so think of it like a digital experience officer. that role, that listening function, I think is the missing link today because what their job is to figure out what it is that people need or want and then map it back to what are the underlying data assets that we have available and if you kind of do your job right, you serve up the data In a format that allows a random app developer on the street who can do the day to day app development for that doctor and not crash your secure systems or require you to allocate limited resources.

Bill Russell:                   18:51               Well, you know what I mean? I’m going to take some heat for this, but part of this is that ceos are lazy. They’ve had those listening tours. We’ve gone out and we’ve listened and we were like, oh, is so heavy. One of the. One of the benefits I had was in southern California. You can employ those docs foundatIon model. We had 100 different mrs. There was no hope. I couldn’t just say, well, we’re just going to have epic. They don’t work for us, so I couldn’t like walk into their office and say, hey, you’re all going to epic and, and, and we’ve, we’ve solved the problem. A lot of ceos have said, here’s how I’m going to solve the problem. I’m going to implement epic. I’m going to do community connect. and away we go. But the reality, as john pointed out last week is you’re still gonna have to connect to a world outside of even outside of your health system.

Bill Russell:                   19:35               Even if you do have a little ecosystem here, you’re still going to have in your community, you’re going to have rural hospitals. I have meditech. You’re gonna have, if you’re just going to have a host of different emr platforms. And so the benefit I had in California was I didn’t have the benefit of having an illusion that I could just dump this over to the emr provider and say, hey, they’re going to solve it for me. I don’t have to worry about it. Um, so, so incomes, these technologies that just make it a lot easier to do what we were trying to do in 2011 with none of this stuff in place, which was, you know, we had to build, we first we were building point to point and then we tried to build this same kind of platform where we could share the data with apis and whatnot, but we were doing that lift ourselves and literally cost us west $70,000,000 for a single health system to try to build this. So these, these thIngs are going to make it so that each health system doesn’t have to spend $70, million dollars to try to build it. There’s gonna be opportunities to do it outside of that. So, uh,

Aneesh Chopra:            20:37               well let me, let, let’s get into the cio role because there’s a really critical decision the cio has to make that could make that 70,000,700. And so let’s just kind of hit the nail on the head. The mega lift is that the data in each of those ehr systems is its own data model with its own circumstance and implementatIon plan. And all the rest, so we’ve got, and I’ve heard you talk about this before, we don’t really have interoperability. We’ve got a bunch of siloed databases that exist, happened to have different brand names in their ehr, meaningful use, three, the one that has to be turned on by one, 1:19, and that cms administrator varma said she’s not moving the date. That means each vendor to remain certified has to map their data models to a minimum common data set that has a data query capability.

Aneesh Chopra:            21:35               what that means is that heavy lift is now. Now we happen to have chosen more than half the vendors who certified today have voluntarily chosen the fire api map to the argonaut project and that was a quick cursory look at 130 or so applications that are certified for the api requirement and meaningful use. So over half the market voluntarily is mapping to a common industry standard. What that means, if I’m cio and I have an, an accountable care network with what you said, 180 hrs and I had every one of those dhrs api endpoints, all I have to do is subscribe to each of those end points, aggregate those feeds, put them in a common data warehouse, likely in the cloud, and then expose them through some api management platform. And if that happens, uh, the cost of data acquisition, normalization, exposure, security management in life will look more like the internet economics. That is to say lower cost, higher liquidity, and that’s the new information. It’s the fact that each vendor had to do the heavy lift at every provider’s site to map the data, to meet the consumer api requirements. that’s why we’re in a better place today.

Bill Russell:                   22:53               That’s great. That is a, that actually is pretty exciting stuff. I’m going to, uh, I’m going to jump to a joe biden’s response to some of this stuff because he’s, he says, hey, it’s a. Actually, he says it in the first paragraph here. I agree With this administration stated goals. It’s not a left right issue. It’s just a note we agree and his, hIs work in the, uh, in the bible, what is it? The cancer cancer initiative has really educated him on, on what’s, you know, what the current state is. So here’s a couple things. One is, um, uh, you know, he stays with the promise of electronic medical records has not materialized from what for one major reason, medical record companies and health providers have implemented systems that are not interoperable. So we know that already. It’s interesting to have this become that elevated where we’re now talking about this and you know, my parents are now talking about this.

Bill Russell:                   23:46               It’s really there. They’re 80 years old and they’re saying, hey, why, uh, you know it because they are going from one system to another. And they’re saying, why? Why does my medical record now following? So this, this is, you know, he’s acknowledging something that’s top of mind even for our 80 and 85 year old parents. Um, and he goes on to say, we now have a need. We, we have nOw had nearly a decade to examine the consequences of how electronic health record systems have been deployed. The industry has had ample opportunity to voluntarily addressed the issues of interoperability and putting data in patients’ hands and they have not done so. Now. It is time for something about do something about the data silos they’ve created to improve health and extended lives. Now is he proposing something different than some of these announcements or as he is, is he envisioning more of a government hand in this to sort of force ehr providers hands? I’m curious.

Aneesh Chopra:            24:41               No, let me let disclosed on the biden cancer advisory committee, so just to. I’m on team biden, so just to be cleared in disclosure for my bias of what he’s really saying is here’s some specific steps that are that are entirely consistent with the policy statements made by sema and jarett and he just went a step further to say, here are the explicit government actions that I would recommend, and by the way, I’m fairly competent. Some of those ideas are likely to be adopted on their own within the trump administration. So it’s not about bigger government, smaller government, its implementation guidance and a lot of feedback people are hearing about a vice president for vice president’s remarks that he was remarkably pragmatic because the suggestions are not massive new, a bureaucracy expansions, but just tweaks a instead of a 30 day requirement to give me a copy of my data, make it 24 hours, not unreasonable in today’s digital environment of directing the nci, the national cancer institute, to kind of build a research data trust and a commons so that you can facilitate the sharing from consumers to researchers, not an unreasonable.

Aneesh Chopra:            25:49               And then the one that I’m most excited about, he notes that the medicare innovation center, which was created by the affordable care act, has the legal authority to experiment with new models to engage patients for purposes of getting better value care. So I actually think on all three of those things they can be achieved within existing law. Maybe not the 24 hours. That may be an interpretation. Maybe it’s regulation, maybe it’s an adjustment to the law, but it’s very achievable and pragmatic. And that’s. I think that the tone with which he took his, uh, his piece.

Bill Russell:                   26:20               Yeah, and the fortune article is great because it lists these four principles which you’ve had four principals in four action steps and I agree with you. It could easily have come out of any administration and I’m, I’m really glad that this thing is getting the kind of traction that it’s, that it’s getting, what do you say to the, to the physician. So every now and then you and I post out on social media and we get the, the, the physicians who come back and say, you know, enough, you’ve made my life so hard, you know, for, for so long. What do you say to them? I mean, are we, are we close enough that they’re going to start to see benefit and value? Or is it because some of them are essentially saying, let’s throw in the towel. Let’s go back to paper. I was much more efficient. I could actually look at the patient in the eye. I’m a, I mean that’s clearly not going to happen, but what would you, what do you say to the physician anyway?

Aneesh Chopra:            27:10               What I would say to them right now is by this next phase of moving data through open apis to consumers and hopefully repurposing them as well for clinicians inside the enterprise that might mean an app developer they learn about could help them do all of their job without ever having to separately log into the ehr. Again, I envision a read write api model that in the not too distant future, physicians can do their joB simply with support from ai and machine learning to help prepopulate advise, encourage so less of their time is spent dictating and typing, looking into a screen and more naturally engaging patients and having the systems work for them. That’s the big mistake. Bill. If I were to characterize this in an economics perspective, we’ve, this is the first time and I would argue most industries were a massive investment in technology, weakened productivity, and that has a lot to do with all the issues, usability, uh, the transitiOn from fee for service to value, which means you’re now doing two jobs, not one.

Aneesh Chopra:            28:16               and the challenge right now is for a physician who’s in, who’s angry about his or her job is as much about what is their job because that itself is fundamentally changing and we want to have an agile, nimble it infrastructure. So as the job changes, the data can follow. I’ll just give you one small example. I know we’re running low on time, but million hearts, almost every clinician I know has endorsed the cms, the centers for disease control, million hearts campaign. You know, if we just do four things, keep people on aspirin, lower their manager blood pressure, their cholesterol, and get them to stop smoking. We can produce a million heart attacks. Almost every physician that I know raised their hand and said, sign me up. They need five pieces of information. What is the current blood pressure has changed? Patients’ cholesterol levels changed. These are very discreet, normalized values that sit in all the disparate silo dhrs.

Aneesh Chopra:            29:11               Imagine a small little app that a physician has that could go with consumer consent, update all that information and alert them if there’s been a change. That simple idea they can’t do today because we don’t have that api layer, we don’t have that app structure so that physician can only do app development on when they see the patient, which maybe once every few, maybe three or four months when the patient may be going to the walmart and getting their blood pressure read at the local station or at a minute clinic or at a primary care doctor’s office down the street. That is what’s frustrating. They want to do the right thing clinically, but the it isn’t working. We have to get there in the open api strategy will make it easier.

Bill Russell:                   29:51               I wanted to talk about apple. I wanT to talk about the va and hopefully you’ll come back on, but one thing I do want to get to, if you give me another minute or so is can you highlight some of the people, some of the. Some of the heroes of this movement who have really moved it forward. I’d love to just give them a shout out for the work they’ve done over the last couple of years.

Aneesh Chopra:            30:13               Well, I would say dr shafiq, rob, who was at hackensack and now at rush, has personally invested a lot of effort to map his ehr to fire and to be an early testbed for app developers. Not in words, but in operations and so I’ll give him a big shout out. Dr. William Morris at the cleveland clinic, allister skin at geisinger. Stephanie real at hopkins. There’s a portfolio of cio’s who basically looked at this issue and said lead or follow, and they’re kind of in the lead camp, whether they’re in the lead camp on the engineering like shafique or alster. Someone where they’ve actually built code or lead in the form of convincing their peers and colleagues to move in a certain direction or to negotiate with where the industry should go. Like stephanie, this is the opportunity and ross zoo is right at the top of that list as a kind of a convener and chief, which is why he was natural for the va to tap him who sits on top of a cerner ecosystem and an epic ecosystem in a relationship with many stakeholders to bring us together to move forward. And so there are a lot of heroes. I’m missing a bunch, but I would say those are the cio in the, in the community who have been driving very hard and fast.

Bill Russell:                   31:23               Yeah. And there’s also, there’s also obviously people in the, in the federal government who have really pushed things forward as well as uh, uh, as well as the people at apple and google and others that, you know, just

Aneesh Chopra:            31:36               oh, full litany of it. We’re going to get to dozens of people all equally deserving of an incredible amount of work. And I might even obviously shout out to atlanta and others who’ve just been incredible in their thought leadership. So I don’t want to ignore anybody in the shout outs. Uh, everyone’s done a great job but, but it’s, uh, it’s really a collaborative effort. There is no one king or queen of this movement. It’s a totally democratized collaboration model as it should be.

Bill Russell:                   32:02               Absolutely. Well, that’s all for now. Thanks for being on the show. How can people follow you or stay up to date on things you’re working on?

Aneesh Chopra:            32:11               Sure. my twitter handle is at aneesh chopra and I do post a great deal of the work that I do, our company care journey. I’ve got a blog that has some historical [email protected] and uh, I’ve written that book innovative state, so I’ve got a website, innovative if people want to stay with my policy interests on open labor market data or other topics, so happy to. Happy to stay engaged.

Bill Russell:                   32:32               Sounds good. Awesome. You can, uh, you can follow me on twitter at the patient cio, my writing on the healthier website or health system cio, uh, and don’t forget to follow the show on twitter this week and hit and check out our new website this week in health it. Uh, if you like the show, please take a few seconds, give us a review on itunes or google play and please come back every friday for news commentary and information from a industry in Florida.

Speaker 4:                    32:57               That’s all for now.



Leave a Reply