Showing posts with label process. Show all posts
Showing posts with label process. Show all posts

Friday, July 27, 2018

Easy recipe for baking gourmet clinical #workflow changes

Hi fellow #Informatics leaders,

It's been a while since my last post, but today I thought it was finally time to write again. What inspired me was a discussion at work about a concept I'd like to describe as the "spaghetti-bowl workflow" : 

Many Informatics professionals spend time untangling these 'spaghetti-bowl' workflows, optimizing them, and making them look like the "AFTER" category above. But how exactly do they do this?

In short, it's helpful to have a solid recipe for making great, predictable, build-once "gourmet-style" clinical workflows that make everyone happy - Including patients, clinical staff, regulatory/compliance, finance, and IT. After all, good workflows are like good food - They should be healthy and nourishing, and taste (feel) great. (Both good food and good workflows are made by experienced chefs and informaticists/analysts!
If it's a cupcake you want, then it's helpful to have a good cupcake recipe.
While experienced people in #Informatics and #HealthIT might know the recipe for gourmet changes, that satisfy all the stakeholders and don't result in unexpected outcomes that need rebuilding - this recipe is not commonly written anywhere. So for clinical education purposes, I thought I would share a version of the change recipe that I think works pretty well 


This is a slight variation on my "Eight basic steps to workflow happiness" that I usually teach clinical staff, the first time I introduce the concept of following a recipe to achieve desired outcomes : 
"EIGHT BASIC STEPS TO WORKFLOW HAPPINESS"
  1. CONCEPTION / ANALYSIS / PRIORITIZATION / PROJECT APPROVAL
  2. PLANNING
  3. DRAFTING / BUILDING
  4. TESTING / "VETTING"
  5. FINAL APPROVAL
  6. EDUCATING
  7. PUBLISHING / "GO-LIVE"
  8. MONITORING / SUPPORT
While the eight steps in blue above make a good introduction - the earlier gourmet recipe fills in more details. It also highlights the importance of detailed analysis work before even scoping or planning a project. 

Sometimes, clinical staff (or clinical IT staff) can be surprised to learn the basics of project (and workflow) management. While it might at first seem daunting, it's important to remember a few things : 
  • Learning a good workflow change recipe (the basics of project scoping, planning, and execution) is vital to building solid, predictable workflows that meet all the right needs : Clinical, financial, and legal/compliance. 
  • It's not hard to learn (and is actually kind of fun once you know it!)
  • For small projects, you don't need to make elaborate efforts for each step. Just being aware of each step will help you avoid pitfalls.
  • It will make you a better informaticist, clinical project leader, and clinical workflow designer.
  • It will help you work quickly with IT analysts, to build the desired workflows you're looking for.
  • The investment in analysis and planning time will usually more than pay for itself in not having to troubleshoot or rebuild workflows after your go-live. 
  • Skipping one or more of those steps, or doing the steps out-of-order, may lead to unexpected outcomes in your desired project or performance improvement initiative. 
What these recipes do raise, however, is a common clinical informatics question : Who exactly should be responsible for each step? The IT analyst? The clinical staff? The regulatory and finance staff? The project manager? It's helpful to start with your IT and Informatics teams, look at each step, and discuss who would be the optimal person to do each step, before you bring the discussion to additional stakeholders for buy-in.

Remember - Planning, and planning ahead, are vitally important to success. These recipes can help you do that. 

Hope this generates some good discussion with you and your analyst and informatics teams, before you tackle your next project. If you have any feedback, thoughts, or favorite change recipes - Please feel free to share them in the comments section below!

Best of luck with your upcoming clinical workflow changes!

- Dirk :)  

This page is for educational purposes only. Open discussion is encouraged, education is a priority. Have any thoughts or feedback? Feel free to leave them in the comments below!

Sunday, June 29, 2014

My Open Letter to the New Physician Leader

So I've been in my current position for almost seven years now. I've learned a lot during that time, and I always enjoy sharing my lessons with other people, so maybe they won't have to spend as much time learning them as I did. So in the spirit of education, and with love and fellowship for other physician leaders, I share this blog post:

MY OPEN LETTER TO THE NEW PHYSICIAN LEADER 

To the New Physician Leader,

Welcome! You're a board-certified physician who has been honored by being asked to serve some sort of leadership position in healthcare, generally either a committee chair, department chief, or physician executive. Given all of the reform and change going on, we need good physician leadership in healthcare! We need you to bring a physician's voice to the discussion, and your hours spent in the ED, OR, ICU, floors, or clinic, will help keep you honest and patient-focused. Your experience will help answer detailed questions about how to deliver great patient care. Your clinical hours are being cut with the expectation that you will step into this new role, help coordinate with other physicians, help shape the future of healthcare, and make it great.

Unfortunately, there's no great training course for this new role. Some of you got voted into your positions, whether you wanted it or not. Some of you demonstrated your skills at many long committee meetings, and eventually earned a reputation as a physician leader. And some of you obtained MBAs, MPHs, or other advanced degrees which helped to get you started in your new role.

But I'm writing to share with you some of the lessons that I've learned in my seven years as an eternally questioning physician leader, in the hope that you will use them in any way you see fit - Hopefully, to prevent you from learning the lessons as slowly as I did.

So with that, I humbly offer you these ten lessons that either I've learned myself, or that were shared with me from other physician leaders :
  1. Don't think being a doctor prepares you for this leadership role. Medical school teaches us a lot about anatomy, physiology, pathology, and histology. Residency teaches us a lot about medicine, surgery, OB-GYN, pediatrics. Fellowship teaches us a lot about pulmonary/critical care, neurosurgery, and cardiology. Experience may teach us how to do our job, or lead a clinical team to a successful surgery. That education and experience will serve you well in this new role, but there is still much to learn. Leading a clinical team through a surgery is very different than leading a whole department or a clinical service. Always be humble and thankful for the people who teach you new things. In my opinion, as physicians, we should always strive to be both teachers and students for the rest of our lives.
  2. Set high standards for yourself. You have one shot at this. Don't just be "good enough." Be "good enough for your children." Attention to detail can be the difference between success and failure, and we need you to be successful in your new role. Don't just aim to succeed - Distinguish yourself by aiming to succeed and wow. Don't just try to meet legal standards, try to meet ethical standards.
  3. Learn some basic parliamentary procedure. Buy yourself a copy of "Roberts' Rules of Order" and read it. Keep your copy in your new office. Knowing how to run a good meeting is a critical skill that not everyone has. When the opportunity arises, being able to correctly discuss the difference between a primary motion and a secondary motion is very impressive. You will also need to know this if you have to make any big changes, which will invariably involve politics and governance.
  4. Know how to write a really good committee charter, meeting agenda, and minutes. These tools are so essential to success, and still many physician leaders don't pay much attention to them. If you really care about these documents, you will be empowered by knowing how to run really good meetings where people show up and things get done.
  5. Control your documents, don't let them control you. Simply put, documentation matters. First, make sure you read your organizational chart, bylaws, rules and regulations, and policies (at least once), and make sure you understand what they all do. Physician leaders sometimes fail because they don't know or understand their governing and operational documents. Next, make sure you know how to develop a really good document - Starting from your idea, to your regulatory/policy/literature search, to your stakeholder list, to your well-designed template, to your first DRAFT, to your stakeholder review, to your final draft, to your FINAL document approval, to your document publication and monitoring - Every step is essential to making a good document. It doesn't matter how good and well-planned your idea is - If it's not properly developed and documented, then it's likely to fail. Finally, keep all of your computer documents somewhere where other people can find them. If you keep all of your tools on your local C: drive, or your email, then nobody else can see them, read them, or collaborate on them. And if you get sick or leave - They may be lost forever! A much better place to keep them is an internal, secure, shared network drive that many people in your organization have access to - It facilitates collaboration, and someone else can find things if you're sick!
  6. "Workflow" is everything. While this term is often used when trying to implement an EMR, everyone should know what it means and why it's important. Workflow is actually deceptively simple. It's a procedure. The success (or failure) of your projects and departments will depend on having good, clear, well-designed, cost-effective workflows that build best-practices into your daily routines. To document your current and future workflows, some people try to make elaborate Visio diagrams or flowcharts, but it doesn't need to be that complex, and sometimes the complex diagrams can leave out important details. You may still need expert help when trying to fix workflows, but as a start, try studying food recipes to see how easy it can be to write good procedures. By design, food recipes/procedures/workflows are generally very 'lean' (in process, not necessarily nutrition - Sorry, no pun intended!) You may still need expert help when trying to fix workflows, but you can start writing a good procedure/workflow, line-by-line, using the general format [ WHO ] will [ WHAT ] [ how ] [ when ] [ where ] [ why ], where the bold parts are mandatory and the italic parts are optional (and only used when needed.) Once you have your current state workflows documented in this manner, you'll quickly see where it can be streamlined to develop your future state.
  7. Don't just make the future good, make it excellent. It's easy to get lost in trying to preserve the past. Sure, there are some things you'll want to keep (like good patient care, compassion, and continuity), but some of healthcare was broken. Make sure you're not trying to preserve the stuff that was broken. (This is especially important when trying to go electronic - You do not want to build bad workflows into your new electronic system!) Remember - Doctors will still be doctors after healthcare reform. We may look a little different, work a little different, and even get paid a little different, but patients will still need us to help them. Plan to make the future excellent for both patients and caregivers.
  8. Finance matters. Through medical school, residency, and fellowship, most doctors don't pay much attention to financial issues (other than student debt!), but at the end of the day, clinical decisions need to make financial sense, and many hospitals close because of insufficient funds. Every penny counts. To make sure everything you do has value, and your projects are well-planned and financially sound, always include someone from finance/accounting early in your clinical discussions. Doctors have as much to learn from finance as finance has to learn from doctors. 
  9. Prepare for shared governance. Let's face it - In the old days, doctors 'ruled' the hospital, while nurses actually kept it alive and functioning. That model doesn't work anymore - You were hired because the nurses can't do it alone. Some people mourn the passing of those days. Personally, I don't. In the future, doctors, nurses, pharmacists, quality, regulatory, legal, and financial people will work together to break down silos, answer questions and collaborate on decisions. I love working collaboratively because I learn so much from these other team members. Working together, we reduce costs, avoid workflow problems, and make better decisions. 
  10. Always let the patient guide your compass to True North. I was once given this advice by another physician leader when I asked him, "How do you always know what to do?". He basically told me, "As long as you always think about the right thing for the patient, you'll always know what to do." I've spent seven years validating his advice, and I can say that so far it has served me very well.
We desperately need you to help shape the future of healthcare, and shepherd other physicians and advanced practice clinicians (PAs, NPs, etc.) through this transition process. To help our patients, we are counting on you to be both happy and successful in your new position! Good luck, share your lessons with other people, and always remember why you applied to medical school in the first place - to help people.

Humbly submitted,

- Dirk
(fellow student, teacher, and eternally questioning physician leader)


Remember - This blog is for educational purposes only, so I always welcome opinions and feedback! Do you have any lessons you would share for a new physician leader? Leave them in the comments below!