Thursday, March 10, 2011

What exactly is a Policy and a Procedure?

Got back from the HIMSS11 conference in Orlando. First, a few quick impressions :

  1. It was BIG. Lots of vendors, lots of people. Everyone selling you "a solution". With this many vendors, it's almost impossible to find a standard. Lots of portable toys, but no clear agreements about what's going to run on those toys. Looks like the industry has a ways to go before being mature, and HITECH has made lots of people "get into the Health IT business".
  2. No meaningful standards yet. The discussion on the PCAST report was particularly interesting, as people debated .CCR, .CCD, HL7, and other standards that either "didn't meet payor needs" or "didn't meet physician needs" or "didn't meet software needs". As the guy behind SpeakFlower.org, I can tell you nobody was addressing a standard that meets patient needs
  3. The cabs and food were expensive. Taking a cab anywhere was $30 or more. Remember this the next time you book a hotel away from the convention center.
  4. Lots of interesting people. Got into a robust debate with some tech and social media leaders about HITECH. My opinion : HITECH is going to drive small practices/hospitals to merge with larger practices/hospitals. Got into an interesting evening debate with some of those tech leaders, who seemed pretty blase and felt that was a necessary part of healthcare reform. Still, it underscores my belief that HITECH is about much more than just "let's get the docs to use computers".

Overall, definitely worth attending once, but remember - virtually everything at the conference is paid for with healthcare dollars. (If you want to save healthcare dollars, consider eating PB&J instead of a fancy dinner.) :)

Anyway, also at HIMSS, I spoke with several other informatics leaders who seemed puzzled by IT/Informatics governance, and how it relates to overall hospital governance.

To help, I thought I'd reinforce this basic informatics concept the same way I explained "What is Medicine Reconciliation, anyway?" -

So our lessons, for tonight, are "What exactly is a Policy?", "How is it different than a Procedure?", and finally, "What's the best way to make a policy / procedure?"

1. What exactly is a Policy?

A policy is a written goal of standardization for your organization. (E.g. "All patients will get low-salt meals." - The goal is to get low-salt meals to all of your patients.). It explains the who, what, when, where, and sometimes why.

A procedure is then the written steps it takes to get to that goal (E.g. "Step 1: Call kitchen  Step 2 : Order low-salt meal   Step 3 : Wait for meal to arrive") A procedure explains the how.

Both the policy and the associated procedure are generally kept on the same paper or electronic document, so that your employees can find and read those documents, and if they are written well, they will quickly understand :
    - What is the standard/goal of your organization?
    - How can he/she achieve this goal?

Writing a good policy statement is not easy. The focus has to be clarity. Short and sweet. In general, it shouldn't be more than one sentence - If it is, it's a warning sign that you may not have a clear goal.

A common mistake is to try to write several different policies into one policy - While it's tempting to do that to help avoid excessive committee discussion, putting several policies into one usually results in a policy that is unclear and ineffective.

So, some examples of unclear policy statements might be :
  1. "Acme Hospital strives to provide low-salt meals which are nutritious and served warm and only to patients who need them. This is to meet the needs of the American Heart Association guidelines and other evidence-based recommendations. All employees will reinforce this rule."
  2. "Acme hospital, to meet consumer demand, will make free parking available for any OB/GYN patients who are discharged." 
  3. "Wiping feet before entering the hospital has been shown to save floor cleaning costs. Floor mats will be used by all employees before entering the hospital."
Their corresponding improvements would be :
  1. "All CHF patients will receive low-salt meals."
  2. "All OB/GYN patients will receive free parking vouchers on discharge."
  3. "All employees will wipe their feet before entering the hospital."
Remember, the trick to writing a policy statement is clarity. To do this, you will need to know :
  1. Who/what does the standard apply to?
  2. What is the standard?
By defining both of these, you can use the following template to write a good policy statement :

                "[who/what does the standard apply to?] will [what is the standard?]"

And so you should only write a policy when :

1. You have a need to standardize something, and
2. You have the resources to enact and enforce the policy. (Just writing a good policy is not enough!)

Writing good policy requires proper balance between specificity and ambiguity. If you do it well, you will create clarity, and your policy manual will become a meaningful change management mechanism.

(I recommend "Writing Effective Policies and Procedures" by Nancy J. Campbell as a reference - It's really well-written and clear and provides ample education about how to write a good policy.)

2. How is it different from a Procedure?

If the policy is the goal, then the procedure is the steps it takes to get to the goal.

So, if we use the three policy statements we improved up above :
  1. "All CHF patients will receive low-salt meals."
  2. "All OB/GYN patients will receive free parking vouchers on discharge."
  3. "All employees will wipe their feet before entering the hospital."
... then we can write clear procedures to achieve those goals :

Policy : "All CHF patients will receive low-salt meals."
Procedure :
  1. Physicians will identify all patients with a CHF diagnosis on admission.
  2. Physicians will communicate the full name/MRNO of all patients with CHF to the nurse.
  3. Nurses will send the name/MRNO of all CHF patients to the kitchen with an order for a low-sodium meal.
  4. Patients will wait for meal to arrive.

Policy : "All OB/GYN patients will receive free parking vouchers on discharge."
Procedure
  1. Discharge Planners in OB/GYN department will place a free parking voucher in all discharge packets.
  2. Nurses in OB/GYN department will review free parking voucher with all patients on discharge.
  3. Patients in OB/GYN department who have not received a free parking vouchers will be provided one on request.

Policy : "All employees will wipe their feet before entering the hospital."
Procedure :
  1. Maintenance staff will maintain a mat at the entrance to the hospital.
  2. All employees, before entering, will stand on the mat and wipe their feet for 10 seconds before entering the hospital.
  3. After wiping their feet, employees may enter the hospital.
Obviously, writing real policies will be more complicated, as you work to address the myriad of clinical, regulatory, and organizational challenges that you will face in running a modern hospital. 

The first pitfall about procedures is knowing the difference between :
  1. A procedure kept in a policy document ("How do you achieve the goal?")
  2. A procedure kept in a procedure manual (usually a nursing procedure manual, kept on most floors to help nurses review the best way to perform a particular procedure.)
If you're really fastidious, you can reference the procedure manual from your policy documents, so that you don't have to write the procedure over again (E.g. "Procedure to insert Foley : See procedure manual page 23 on 'Inserting Foleys'")

The problem with this approach is that while it may save you some time, you will still need to maintain both the procedure manual as well as your policy documents.

Another common pitfall of procedures is the "complicated procedure" where you have a bunch of complex, logical and conditional arguments, like :

Policy : Nurses will maintain blood sugars between 60 and 200 for all diabetic patients.
Procedure :
  1. Nurse will check patient's fingerstick every 2 hours
  2. If fingerstick < 60 then nurse will give 1 amp D50 IV and call physician
  3. If fingerstick = 200 - 249 then nurse will give Insulin 2 units SQ
  4. If fingerstick = 250 - 299 then nurse will give Insulin 4 units SQ
  5. If fingerstick = 300 - 349 then nurse will give Insulin 6 units SQ
  6. If patient becomes dizzy, nurse may call a rapid response.
  7. Fingersticks may be checked more often for patients who feel dizzy.
  8. If a nurse checks more than 4 fingersticks in a 2 hour period, nurses should call MD.
There are a few problems with writing this type of procedure :
  1. It doesn't have a good "trigger" that makes a nurse start to follow these instructions.
  2. It has a lot of "IF/THEN" statements. 
  3. It also has a lot of orders in it ("give Insulin 4 units IV" requires an order to be placed in your EMR.)
These are all giveaways that this is not really a procedure, but a protocol. (Remember, a protocol is a series of instructions and well-defined conditions that allow a nurse/pharmacist to start/modify/stop an order on behalf of the protocol.)

So the way to clean this up is to make a procedure that says this :
Policy : Nurses will maintain blood sugars between 60 and 200 for all diabetic patients.
Procedure :
  1. Physicians with diabetic patients will place an order for "Diabetic Protocol" in the EMR.
  2. Physicians will verbally notify the nurse that an order for "Diabetic Protocol" has been entered.
This then lets you make a Diabetic Protocol :
  1. Nurse will check patient's fingerstick every 2 hours and as needed
  2.      If fingerstick < 60 then nurse will give 1 amp D50 IV and call physician
  3.      If fingerstick = 200 - 249 then nurse will give Insulin 2 units SQ
  4.      If fingerstick = 250 - 299 then nurse will give Insulin 4 units SQ
  5.      If fingerstick = 300 - 349 then nurse will give Insulin 6 units SQ
  6.      If a nurse checks more than 4 fingersticks in a 2 hour period, nurses will page MD
  7. Nurses will check patients mentation every 2 hours
  8.      If patient becomes dizzy, nurse will dial operator to call a rapid response.

3. What's the best way to make a policy / procedure?

The funny thing is, most people aren't aware of the cognitive processes behind their daily activities. For example, you've probably sent lots of emails, right?

You probably didn't think about the steps you took to send an email :
  1. You owned the email - Your brain decided, "I need an email to accomplish a goal."
  2. You built the email - You actually typed the text of the email
  3. You tested the email - You looked at it to see whether it was fit to send
  4. You approved the email - Your brain felt the email was good enough to accomplish the goal
  5. You published the email - Your finger clicked the mouse on the "SEND" buttom
  6. You monitored the email - You waited to see the effectiveness of the email - If no response, you will probably repeat at step #2
So writing a good policy requires the same steps : Ownership, construction/building, testing, approval, publication, and monitoring. Let's just quickly review these before we wrap up for tonight :
  1. Policy Ownership - If the point of a policy is to set a goal/standard, and your leadership/directors are the ones setting and enforcing the goals/standards, then it makes sense for policies to be owned by a director/leader.
  2. Policy construction/building - This can be someone with training in building policies. (At a minimum, they should read the book I mentioned above, or attend some classes in policy writing so they can help the owner have clear and effective policies.) Informaticists are generally pretty good at understanding the construction issues, but you may choose to have someone special just to write your policies.
  3. Policy vetting / testing / reviewing - Before bringing the policy to a committee for approval, you may need to "vet" or "appraise, verify, or check for accuracy" the policy. Who you bring it to, before approval, should depend on the committee chairperson for the committee you are seeking to approve the policy.
  4. Policy Approval - This generally should be done by a committee with expertise in approving the policies. (If the policy has been properly vetted, there should be little discussion at the approval committee.) The committee chairperson should put the policy on the agenda, and at the meeting conduct a vote for approval for the policy. If the committee approves, the chairperson should sign the policy to show committee approval.
  5. Policy Publication - After approval, this generally should be done by putting the signed policy into a policy manual, and then surrounding the arrival with some education to staff about the new policy.
  6. Policy monitoring - This generally should be done by the owner, so if there is a change/update that is needed, they can go back to step #2.
It is for these reasons, then, that I put on my propeller-hat and recommend the following headings for your policy documents (these are not standard, but I would use them if I were to design a policy manual): 

ORGANIZATION NAME
POLICY TITLE
CREATION DATE

I. PURPOSE :
II. POLICY STATEMENT :
III. SCOPE :
IV. DEFINITIONS :
V. PROCEDURE :
VI. OWNER :

VII. BUILDER :
VIII. CITATIONS : (This will help keep your policy manual evidence-based!)
IX. TESTED/VETTED BY :
X. APPROVAL COMMITTEE :
XI. APPROVAL DATE : (with chairperson signature)
XII. REVISION HISTORY :


Not everyone will have these headers, but if you're at the point of actually starting a policy manual, I think this could be really helpful in getting your organization to better understand these policy development, implementation, and maintenance issues.

Remember : My advice is free, and you get what you pay for. :)

(In all seriousness, this is how I might set up my policy headers and development process, but your mileage may vary.)

Would love to hear your thoughts/opinions! Please comment or ask questions - I would love to discuss other healthcare informatics issues! :)

2 comments:

Andrew said...

I absolutely agree with the philosophy behind governance and the value behind a policy manual. The key challenge that all organizations, whether corporate or health-care related, is how to disseminate, educate, and enforce the policies among staff. In many cases, the policy manual is generally only referred to when there is a dispute or a disciplinary action.

Yes, if you have an active, engaged committee that is reviewing policies, it can disseminate new or changed policies to staff. Of course, this could be accomplished (most likely unsuccessfully) by just copying and pasting the text of the policy to all individuals who are affected by the policy.

It would be interesting for you to post your thoughts policy dissemination. And, also, how to bring new employees, whether medical or staff, aware of policies in place.

Dirk Stanley, MD, MPH said...

Policy dissemination, education, and implementation is not a one-step process. Like anything worth it, it requires time.
1. On hiring an employee - The policy manual should be given to all new employees to review during training. All employees should know where they can read and find clinical policies.
2. On all educational opportunities - Directors should reinforce that the clinical policy manual can be helpful at figuring out how to do something
3. On all performance evaluations - Directors should reinforce behaviors
4. On all policy approvals - Directors should disseminate policies to their constituents.
5. Occasional posters, screen savers, and emails should remind employees of the existence, location, importance, and relevance of clinical and administrative policies.
There are probably other avenues to reinforce good policy awareness and culture...