On EHRs

Vaccine rollout – it takes a village, part 2

Posted by on

Last week’s blog post on vaccine rollout took longer than expected to write as I compiled multiple resources and articles to comment on and share. With the vaccine rollout as massive an undertaking as it is and so many stories (good and bad), I decided to do part 2 this week highlighting best practices, technology challenges, and health disparities.

Best Practices

Last week, I mentioned Atrium Health and their local partnership to do mass vaccination events. It was encouraging to see their update on vaccinating over 20,000 people had a special emphasis on underserved communities.  We need more focus on underserved communities – more on that in a bit.

Another health system doing drive thru vaccination clinics at scale is Memorial Hermann in the Houston area. They are getting calls from health systems across the U.S. asking for guidance on how to design similar large-scale vaccination events and are more than willing to share their blueprint for others to replicate according to Binita Patel, Vice President of Pharmacy Services for Memorial Hermann Health System. The location (NRG Park) and staffing (700 people including many volunteers) were key to their success.

We cannot forget that there are many people leery of the vaccine, sometimes referred to as “vaccine hesitancy”. Education and public health messaging campaigns will be key as the vaccine rollout continues over the next several months. Based on the Kaiser Family Foundation’s latest COVID-19 Vaccine Monitor report, there are key messages that resonate with people. They are listed in this short article from Becker’s Health IT : “8 most convincing messages to promote COVID-19 vaccines”.

Many health IT vendors pivoted their products and services to support COVID-19 over the past year. Vaccine scheduling is the latest focus area for vendors like Kyruus which shared best practices and insights from their customers in their recent blog: “Eight Best Practices for COVID-19 Vaccine Scheduling Online: Insights From Our Health System Customers”. A great transition to the next topic.

Technology Challenges

I mentioned the Vaccine Access Management System (VAMS) in my post last week as a system provided by CDC to states and other organizations for pre-screening, registration, scheduling and tracking. Not surprisingly, a software solution developed quickly and made available for many different but similar situations and workflows has experienced problems as captured in this article from MIT Technology Review. I would hope the problems can be resolved so organizations using it do not have to switch systems midstream with vaccine rollout already in process and moving rapidly. Continue reading →

Vaccine rollout – it takes a village

Posted by on

The vaccine is top of mind for many of us and a lead news story most days. Whether we are in a prioritized group wondering when/how/where we will be able to get the vaccine or are helping a family member in one of those groups sort it out. We are disappointed to hear the supply from Pfizer and Moderna is so limited at this stage. We are frustrated and anxious not knowing when we will be able to get the vaccine.

I share all those feelings. I am anxiously waiting to learn when my state of Rhode Island will start vaccinating 65+ so I can get my husband and I an appointment. With the percent of doses administered overall in Rhode Island only 56% of what has been distributed and our state currently receiving just 14,000 new doses each week, I am not optimistic that it will be soon.

In spite of any frustration you may feel about your own state’s progress, the good news at the macro level is that in the last week, an average of 1.25 million doses per day were administered in the U.S. That is even better than the goal of 1 million per day for the first 100 days of the Biden Administration. And there is more good news regarding the supply – 200 million more doses were ordered by the Biden Administration this week with the expectation that there will be enough doses for everyone who wants the vaccine by sometime this summer.

We know that vaccine plans vary by state. How to Get a COVID-19 Vaccine: A State-by-State Guide from the Wall Street Journal provides state website links and brief description of each state’s status. States vary on how groups are prioritized, the scheduling process and systems used, and the total number of doses available. In the 65+ group, I have friends and family who have driven more than 500 miles around their state for separate husband and wife appointments that they could only make at two different locations due to the demand, a couple who was only able to register for a lottery with 8000 doses to serve 250,000 people, a couple who relatively easily made appointments at their grocery chain to receive the vaccine from the pharmacist, and a couple who relatively easily made an appointment at a local community vaccine site.

The New York Times has a vaccine calculator – Find Your Place in the Vaccine Line – that puts it into perspective. You enter a few key data points and can see where you are in line within the U.S., your state, and your county – in other words how many thousands or millions of people are ahead of you. The graphic it produces helps you understand the order of groups and their relative size.

There are two trackers you might find interesting. The Johns Hopkins Coronavirus Resource Center tracks cases, testing and vaccines by state. You can see how your state is doing and where it ranks on vaccinations. The Bloomberg tracker shows how your state is doing by percent of doses used and number of doses administered.

There is a software system available from the CDC for states, counties and other organization to use – Vaccine Access Management System (VAMS). It handles pre-screening, registration, scheduling, and tracking. My state of Rhode Island will use PrepMod – a software solution in use by several states. Health systems appear to be using their own systems and assuming that patients can schedule through their patient portal or by phone. Some allow you to create an account if not already a patient.

I think we can all agree that front line health care workers needed to be first in line for the vaccine. But there have been stories of health systems vaccinating employees who only work from home, volunteers who aren’t coming into the hospital during the pandemic, board members and others who don’t appear to be in priority groups per the CDC guidelines. These systems have defended their actions by saying the more people vaccinated and the sooner is good for the community and that all staff are critical to the hospital’s operations. I can understand the frustration of people who are patients of those systems and in a prioritized group (such as elders or with underlying conditions) yet still waiting to learn when they will get the vaccine.

Let’s pivot to some positive stories of vaccine partnerships involving health systems to deliver shots in arms at scale. Continue reading →

Digital health has arrived

Posted by on

Every healthcare organization seems to be focusing on developing their digital health strategy these days. But do we have a common definition and understanding of what digital health means? A few months back I wrote a post called “Knocking on the digital front door” addressing what many organizations mean when they talk about digital health. Meeting patients where they are and guiding them along the right care pathway with efficient, consistent, and easy processes in the background. It was a very popular post, so I guess it resonated with many.

But digital health encompasses far more than just the digital front door. My StarBridge Advisors colleague, David Muntz, has taken on the broader issues of digital health this year in a multi-part blog series on View from the Bridge. Here is his four-part series if you are ready to go deeper on digital health:

Digital Health – Is Healthcare Ready? Are You and Your Organization Ready?

Becoming a Digital Health System

Digital Health – Governance in a Digital Health System

Digital Health – The Role of Empathy and Understanding

If you are interested in future posts in David’s digital health series, subscribe to View from the Bridge to get notifications of new posts. Our team of advisors regularly contributes posts on a wide range of topics relevant to today’s healthcare executives and IT leaders.

And if you are looking for help developing your digital health strategy and roadmap, David or I would be happy to schedule time to talk.

When healthcare becomes personal

Posted by on

When you get a call that your husband has been taken to the ER by ambulance, it is hard not to think the worst. I got that call last Wednesday. The good news is that by late Friday night Tom was OK’d for discharge from the hospital. But we still do not have the answers needed. More tests and results should help us better understand what happened and why it happened so together with his PCP and specialists we can develop a go forward plan.

I have worked in healthcare for over 35 years. Our family has dealt with various minor health issues and been able to access the best healthcare available. I have the utmost respect and gratitude for health professionals and all they do.

Through this experience I have seen healthcare through the patient and family lens in a different way. I have several takeaways worth sharing.

Emergency resources – Know when to call your PCP, go to the nearest urgent care center, call 911 or head right to the hospital ER. Minutes can matter.

Friends and family – I can’t say enough here. Tom was visiting a friend when the incident started. She took him to the closest Urgent Care, they called an ambulance fairly quickly and he was taken to the closest ER. The friend reached out to another friend thinking that person might know how to contact me. Fortunately, he did. We are setting up the Emergency Contact feature on our phones for the future. On the first call with the ED physician, I did a 3-way with my daughter who is a nurse practitioner. I wanted her in the loop from the start – to help interpret what I was being told, help educate me, and advocate for Tom.

Clinician in the family – If you are fortunate as we are to have a clinician in your family, let them help you. They are invaluable. Listen to them, loop them in on calls to ask all the right questions, and let them educate you. Our daughter spent ½ hour on the phone with the attending physician before Tom was discharged while I drove to get him. She then explained it all to me and started doing more research on her own.

Accessible and Integrated EHR – Now we are in my domain. Continue reading →

Knocking on the digital front door

Posted by on

Health systems are learning many lessons during this pandemic that they will need to carry forward into the recovery and “new normal” phases. One of them may be the need for an integrated digital health strategy, and more specifically a patient focused “digital front door”. The almost overnight shift from in-person ambulatory visits to virtual visits during this pandemic highlighted the need for a more integrated approach for many health systems.

An integrated strategy for a patient centered digital front door has many components including the core website, the patient portal linked to the electronic health record, improved access and scheduling capabilities, call centers, and care delivery through virtual visits. The goal is to meet patients where they are and guide them along the right care pathway with efficient, consistent, and easy processes in the background.

However, these multiple components and functions are often led and directed in an uncoordinated manner by different senior leaders within the organization. The core website is typically owned and directed by Marketing and Communications with technical support from IT. The patient portal is often managed by the ambulatory team in IT partnering with the Chief Medical Information Officer, Ambulatory Services, and Marketing. Improved patient access and scheduling initiatives are often directed by Ambulatory Services or in an academic medical center by the Physician Practice Group leadership. The call center may be managed by Marketing or Ambulatory Services leadership. And telehealth may be provided by a specialized team either connected to or part of IT but be directed by physician leadership.

A successful patient centered digital health strategy needs to involve all these components in a coordinated, comprehensive manner. In some respects, who leads this strategic initiative does not matter. What does matter is that there is buy-in and collaboration from all leaders involved with a common overarching goal to meet patients where they are at and provide an easy, consistent experience to access services. Continue reading →

Major implementations need experienced leadership

Posted by on

What CIO hasn’t worried about a major EHR or ERP go live? Despite the years of work by your dedicated and talented team alongside your software vendor and possibly an implementation partner consulting firm, you still worry. The Go Live Readiness Assessments (GLRA) at 30-60-90 days have level set all involved on what is complete/ready, what is on track to complete, and what needs help.

It’s that last piece – what needs help or is significantly behind schedule – in bright red on the status report that requires attention. There could be many reasons it’s red, but bottom line it is red. Do you have enough of the right resources and enough time to get it done? Do you have to adjust scope? Do you have to put more money into it? You certainly don’t want to sacrifice quality. And with the scale and complexity of most major implementations, you don’t want to move the go live date. Any good project manager knows that those are the only four levers you have – scope, quality, money, and schedule.

Everyone who has done this before tells you that there will be some yellow and red areas yet at the 30-day GLRA. But they should be minimal and able to be addressed in time for the go live.

If you have a major implementation in 2020 and don’t have an implementation partner or lack full, unbiased confidence in your implementation partner, you might consider a little more help in those final 90-120 days. And not just more staff resources. As the CIO, you may need to bring in an experienced senior IT leader who can assist you by doing a quick project review and risk assessment. Someone who can identify the key areas you need to focus on and if needed bring the expertise and leadership to address them in time for a successful go live. Someone who, at a modest cost, will help you sleep better at night.

At StarBridge Advisors, we have a team of senior IT leaders serving as advisors who have significant experience leading successful implementations in all sizes and types of healthcare organizations. We know what can go wrong and how to avoid it. We know what it takes to be successful. And we will tell it to you straight. Our approach is practical, unbiased, open, and plain speaking. We offer you frank and honest opinions based on real-world experience.

If you have a major implementation in 2020 that you are worried about, let’s talk.

Related Posts:

Plans, processes, people: lessons from a successful EHR implementation

Epic Go Live – report from the field

9 Tips for Go Live support success

10 best practices for project success

10 Go Live Command Center lessons from the field

Crunch time and why IT matters

Conducting project “lessons learned” as continuous improvement

Posted by on

As I caught up on my industry reading this past weekend, I saw several implementation best practices articles – advice from experts on EHR, Telehealth, Pop Health, and Medical Device implementations. These kinds of resources are always helpful to think beyond your organization’s experience, get a different perspective, and learn from others.

At the same time, conducting lessons learned sessions internally after major projects is critical. While it’s still fresh in your mind, being able to look as a team at what worked well and what didn’t work well over the life of the project is an important step before moving on to the next project or next phase of a multi-year project. This should be done in the spirit of continuous improvement. Ask yourself, what can be learned from this project that can be applied to future projects. And be sure to document that in a way that is referenceable in the future.

We are just over 3 weeks post go live for Wave 1 of our Epic project at the University of Vermont Health Network (UVMHN). We start a series of lessons learned/debrief sessions this week. IT managers have been asked to think about three questions and submit them in advance so they can be compiled for review and discussion:

  • What worked well?
  • What didn’t work well that we should modify?
  • What didn’t work well (or was unnecessary and we should no longer do)?

As we planned for the sessions, I suggested that we have a few guidelines – no blame, assume positive intent, and ensure everyone is heard. UVMHN has a very collaborative and team-oriented culture so that shouldn’t be difficult.

Often, it’s easy to go right to what didn’t work well. Those examples may be top of mind. But there is so much in a project of this magnitude that is done well. Capturing those points and making sure you repeat them in the future is important.

Wave 2 planning started before the Wave 1 go live. Certain lessons have already been looked at as part of that planning. But the upcoming sessions will be an opportunity to look more broadly and get the input of all areas involved. Given I’ve been interim CTO since late May, my involvement did not span the entire project but rather certain aspects in the last few months including the go live. I look forward to hearing everyone’s perspective on how we can do better and build on the successes to date.

Related posts:

10 Go Live Command Center lessons from the field

Epic Go Live – report from the field

9 Tips for Go Live support success

Plans, processes, people: lessons from a successful EHR implementation

10 Go Live Command Center lessons from the field

Posted by on

Week 2 post Epic Go Live has begun. We continue to learn and adjust. Building on my previous Epic Go Live and Command Center planning posts, there are more lessons to share.canstockphoto15204222 (1) keep calm

The last point in my most recent post was about camaraderie – defined as “mutual trust and friendship among people who spend a lot of time together”. I should add, in close quarters!

I continue to be impressed with the hardworking, dedicated IT team at the University of Vermont Health Network. I have seen many examples of teaching, helping one another and stepping up to new roles since the November 9th Go Live.

The rate of new tickets slowed down as Week 1 ended but the issues became more complex as expected. We have resolved over 65% of the tickets opened since cutover and addressed many cross cutting issues.

As promised, more lessons to share:

  • Handoffs between shifts – Ensure that key issues and work in process is reviewed and turned over to the next shift to keep things moving smoothly. Try to have people scheduled several days in a row for continuity vs on one day and off the next.
  • Seeing the “forest for the trees” – In the first few days, the focus is on closing tickets but as cross cutting issues and themes emerge, the focus needs to shift. As broad issues are defined, you need clarity on what teams and modules are involved, who is on point to lead the issue resolution, and what help is needed.
  • Escalations – It is very helpful to have highly engaged executives and operational leaders rounding and raising up the greatest pain points for users that need more focus. These escalations may come through in-person visits to the command center or email.
  • Ticket analysis – Have resources available who know the tool and can slice and dice the data to help leaders and teams see trends and where to focus.
  • Hospital daily huddle – If the organization has a daily huddle, the command center lead should attend. It’s good way to hear firsthand how all departments are doing and what their key concerns are.
  • Command center “walk-ins” – If the main command center is at the hospital you may get walk-ins – well intentioned users who want to escalate a specific ticket or issue. Command center leaders should manage this so the teams working tickets aren’t given conflicting direction on priorities.
  • Email management on steroids – Staff working tickets stay in the system and don’t watch their email. But leaders get a lot of emails and it’s hard to keep up given the pace. At the end of each command center shift, go back through your inbox to ensure that any escalations are dealt with – other email can wait.
  • Multiple locations for support – If there are a main command center and multiple other locations for support staff and triage, ensure they are well coordinated with good communication between.
  • Document management – Everyone involved needs easy online access to reference material. Dynamic information such as shift schedules need to be maintained. Having at least a few binders of printed reference information helps as well.
  • Ramp down plan – When you start adjusting command center hours, it will help to have a checklist ready on what needs to be considered and implemented (i.e. staff schedules, re-location of teams, communication to users, logistics like food and transportation, etc).

Stay tuned for more reports from the field….

Related Posts:

Epic Go Live – report from the field

9 Tips for Go Live support success

Epic Go Live – report from the field

Posted by on

Many of you have been through a major EHR implementation and go live. I’ve been through them before as well. The teamwork of a go live is like nothing else I’ve ever experienced.canstockphoto16071239 (1) teamwork

There is the overnight cutover period that was practiced numerous times as “cutover dry runs” with the goal of making sure it goes smooth and can be done in the shortest time possible. After all, you are asking a hospital to go to downtime procedures until you can bring up the new system.

There is the excitement as others gather for the proverbial “flip the switch” moment. The applause and high fives for people who have been working hard towards this moment for many months. The appreciation from operations leaders on hand.

There is the wait for the first user calls and tickets to roll in. The wondering if all the planning for the command center and support structure was on target.

There is the settling in as ticket volume increases, teams start working them, and tickets start getting resolved.

There are the periodic reports from operational leaders who are rounding on the floors. They report on the pulse of staff who are dealing with a new system while trying to care for patients. They report on the issues that seem most problematic.

There is the dashboard monitoring to see which teams are getting the most tickets and whether adjustments in staffing need to be made. There is the ongoing review of tickets to ensure they are prioritized appropriately. Continue reading →

9 Tips for Go Live support success

Posted by on

My first blog post published back in 2014 was called “Three Days and Counting…” written as we approached a major Epic go live at Michigan Medicine. This week’s post could be called “Five days and canstockphoto15204222 (1) keep calmcounting….” as we approach our Wave 1 Epic go live at University of Vermont Health Network on Saturday 11/9.

We were originally scheduled for a 11/1 go live. But in mid-October after much deliberation with operations and IT leadership, our CEO, Dr. John Brumsted, made the decision to move the go live back one week. As he said in his communication to the entire organization, “This decision is in the best interests of our patients, our people and our Network. It gives us the time we need to get to a place where we are confident to go live and it allows users additional opportunities to prepare”.

Planning for the two-week 24/7 command center and support structure started a few months ago. With just five days to go, the plan is pretty much finalized. Highlights and some tips to share based on our game plan:

  • Physical setup/location – Where your command center is located will depend on space available but ideally it will be in the hospital. We are fortunate to have primary and secondary locations at the University of Vermont Medical Center where we’ll have approximately 80 people. We will also have a triage team (to review and route the tickets entered online) and trainers (to answer “how to” questions) co-located offsite. In addition, we’ll have local support centers at each of the hospitals involved in Wave 1.
  • Overall call flow and phone setup – We have a documented decision tree/call flow starting with the super users reporting issues they can’t address. Phones are programmed to route calls to the appropriate support staff depending on user role and/or application involved.
  • Reporting issues – When you are dealing with thousands of issues, you need to use a common tool and standard process. We use ServiceNow and all tickets will be entered and tracked through this tool. Dashboards have been created for leaders to monitor ticket volume and trends.
  • Staffing – A command center operating 24 hours a day for two weeks means people are scheduled for 12.5 hour shifts including time for handoff to the next shift.
  • Leadership roles – Multiple leadership roles have been defined and scheduled for these same shifts. Roles include a physician and nurse leader from IT, someone to monitor ServiceNow tickets and trends, and someone to be overall command center leader.
  • Huddles – There are huddles scheduled throughout the day for each operational area to review broad issues and trends that will then role up to the executive huddle at the end of the day.
  • Communications – This is a critical function to embed in any command center. As high impact issues are resolved and trends are identified, communications staff will work closely with command center leadership to push out daily updates and specific tip sheets.
  • Reference documentation for support staff – Wwith the intensity and pace of a major go live like this, you can’t rely on personal knowledge. Documentation will be available to all support staff and will be reviewed in advance to ensure everyone is comfortable with the plan and what is expected of them.
  • Logistics – And last, but not least, don’t forget about food, parking and transportation arrangements.

Our command center and support plans for go live are well defined. They may not be perfect, but a lot of thought and preparation has gone into them. The key is to be flexible and adaptive as the days go by.

As I always tell my IT teams, we are part of the extended care team. While we don’t touch patients directly, the staff who do depend on the systems and support services we provide. This is never truer than at go live time!

Related Posts: 

Crunch time and why IT matters

IT takes a village

Three Days and Counting…

Plans, processes, people: lessons from a successful EHR implementation