Transitions of Care (Handoffs) and Readback
A handoff refers to the transfer of information that takes place during transitions in the care of a patient. The purpose of a handoff is to provide complete and accurate information about a patient's clinical status, current problems and recent and/or anticipated treatment. A well-done handoff can prevent errors stemming from failure to communicate changes in the status of patient. Therefore the information communicated during a handoff must be complete and accurate.
A handoff contains verbal and/or written communication which provides information to facilitate continuity of care. Handoffs occur in a variety of transitions, including, but not limited to:
• Outpatient to Inpatient
• Shift to Shift
• Provider to Provider
• Unit to Unit
• Facility to Facility
• Inpatient to Outpatient
IT IS THE RESPONSIBILITY OF PROGRAMS TO:
• Design clinical assignments to optimize transitions in care, including their safety, frequency and structure.
• Maintain and communicate schedules of attending physicians and residents currently responsible for care.
• Ensure continuity of patient care in the event the resident may be unable to perform their patient care responsibilities due to excessive fatigue, illness, or family emergency.
• Ensure that residents and supervisors are competent in communicating with team members in the handoff process.
• In partnership with the Institution, ensure and monitor effective, structured handoff processes to facilitate continuity of care and patient safety. Additionally, programs must identify high risk transitions of care and design processes accordingly.
• Identify a designee within each department to be responsible for monitoring handoffs within the department.
• Provide an evaluation of observed handoffs to the GMEC at a frequency determined by GMEC.
IT IS THE RESPONSIBILITY OF THE INSTITUTION TO:
• Facilitate professional development for resident and faculty regarding effective transitions of care
IT IS THE RESPONSIBILITY OF INDIVIDUAL RESIDENTS AND FACULTY TO:
• Conduct each and every handoff in accordance with the standards outlined in this policy and the handoff processes established by each program or clinical service.
• When receiving a handoff:
o Thoroughly review a written handoff document and take notes on a verbal handoff
o Clarify and resolve any unclear issues with the transferring provider
ELEMENTS OF A HIGH-QUALITY HANDOFF
Within each program or clinical service, handoffs will be conducted in a consistent manner, using a standardized form or structured guideline which includes all of the elements listed below. While a single specific handoff tool or instrument is not mandated, programs are strongly encouraged to utilize a standard format (i.e. SBAR, etc.)
• Occurs in a quiet environment without interruptions
• Interactive communication which encourages questioning between the giver and the receiver of patient information
• Has a structured format
• Demonstrates accuracy and comprehension
• Has a process for verification of the received information, including readback* as appropriate
• Supervised as appropriate on a regular basis
• Face to Face whenever possible
The core content expectations for handoffs include the following:
1. Patient demographics
2. Attending Name/Responsible Team
3. Patient's Diagnosis/Problem list
4. Code Status and advance directives
5. Current Status (recent changes, critical labs, safety concerns, allergies, etc.)
5. Decision Maker Status (if not competent)
8. Pending Labs/XRay, etc.
9. Recommendation/Action Plan (If this…then do that)
10. Readback
11. Other (program or service specific)
For IP to OP/Discharge only:
12. Follow-up for each provider involved in the care of the patient (primary plus consultants)
13. Follow up with primary care provider (if different than primary service)
*A method of preventing errors in which information relayed to one person is repeated and verified in a slightly different form as a means of confirming its accuracy - for change of status, pending labs, critically ill patients, etc.
Protocol Effective: August 9, 2019