Roles and Responsibilities For Implementation of Priority Problems

Roles and Responsibilities For Implementation of Priority Problems
  1. Administrative Director /CNO
  2. Consistently communicate the vision for the Priority Problems process
  3. Participate in NLB Training Session.
  4. If scheduling permits, attend Kick off presentation for Priority Problem at staff meeting(s) or unit board(s)
  5. Participate in Tue 0730 am Conference Calls ( 4, 2, 1 week prior to go live, and 1 week post) to elicit status of pre-implementation preparation ( i.e. training targets being met, barriers etc), implementation issues, and action plans.
  6. Provide visible support for documentation & process changes by rounding at least once per week during the week prior to go live and the two weeks following implementation on each unit of responsibility.
  7. Incorporate a weekly review of one unit’sPriority Problems Reports for 2 months post implementation (alternating units reviewed each week).
  8. Create agenda item on meetings to identify problems and trends with Priority Problems process.
  9. Channel issues and concerns to QERI group for further evaluation.

  1. Unit Leadership Team(Manager, Assistance Manager(s) with Support from Administrative Director):
  2. Consistently communicate the vision for the Priority Problems process.
  3. Participate in NLB Training Session.
  4. Complete Unit-Specific Implementation Plan including(Unit Implementation Plan Tool for timelines):
  5. Staff Education Plan( in conjunction with educator)
  6. Communication Plan
  7. For Nursing Staff
  8. For Medical Staff and other key stakeholders
  9. Support Plan
  10. Identify Super Users
  11. Plan for additional resources to facilitate staff training and for support during week of implementation.
  12. Allocate resources to allow Super Users to be scheduled out of staffing or have a light assignment to allow for facilitation of training prior to go live week and support during go live week.
  13. Identify a leadership contact person for each day of the week of go live that will be responsible for addressing issues/ concerns.
  14. Ongoing monitoring and feedback Plan
  15. Jointly lead implementation with Educator/Systems Support Services Representative.
  16. Participate in Tue 0730 am Conference Calls ( 4, 2, 1 week prior to go live, and 1 week post) to provide status of pre-implementation preparation ( i.e. training targets being met, barriers etc), implementation issues, and action plans.
  17. Provides visible support for documentation & process changes by rounding at least 3 times the week prior to and daily for the two weeks following implementation.
  18. Identify barriers to success and plans to address.
  19. Identify successes and celebrate with staff.
  20. Provide input to Steering Committee in order to strengthen tools, process, or implementation going forward.
  21. After implementation week, initiate monitoring and feedback plan to hardwire change with staff. Including:
  22. Daily review of Priority Problems Reports for 2 months post implementation.
  23. Placing Priority Problem Process on Staff Meeting/Unit Board agenda 1 month prior to and 2 months post implementation.
  24. Develop a Maintenance Plan
  25. Monitor Plan of Care Report and provide feedback to staff in aggregate and individually on performance.
  26. Identify individuals who need coaching on application of new model from clinical perspective & address needs.
  27. Identify individuals who need coaching on electronic documentation with new model & address needs

  1. Educator (or identified Point Person if no Unit Educator) will:
  1. Consistently communicate the vision for the Priority Problems process.
  2. Be dedicated to Priority Problems training and support during 1 month prior to and 1-2 weeks following Go Live date.
  3. Participate in NLB Training Session.
  4. Attend Educator Priority Problem training session.
  5. Complete the unit education plan – including plans for presentation of Priority Problem Power Point as well as small group practice sessions.
  6. Identify the 10 most commonly used Pathways for the unit and place in Priority Problem Resource Manual.
  7. Customize for unit the practice exercises and review with Leadership Team, SSS Rep./CAPS to ensure internal agreement.
  8. Augment the Priority Problem resource manual to meet needs of unit specific patient population & staff.
  9. Participate in Tue 0730 am Conference Calls ( 4, 2, 1 week prior to go live, and 1 week post) to provide status update re: training and pre-implementation preparation, implementation issues, and action plans.
  10. Make arrangements to train 90% staff prior to go live date.
  11. Inform Leadership Team/SSS Rep./CAPS of any issues (i.e. staff who refused to participate in training, staff assigned to you that you have been unable to work with, questions you’ve been asked you don’t feel comfortable answering, etc.)
  12. Be an available resource to SuperUsers for questions they cannot readily answer.

  1. SuperUsers will:
  2. Consistently communicate the vision for the priority problems process.
  3. Complete practice exercise and have proficiency check off by Unit Educator/Designee before Go Live week.
  4. Be familiar with the Priority Problems resource manual including the 10 most common pathways used, most common Priority Problems, etc.
  5. Train all assigned staff prior to go live date (as assigned by educator).
  6. Serve as the clinical experts during initial orientation period, responding to questions that require clinical expertise for patient population care on your unit.
  7. Inform Unit Educator/Designee of any issues (i.e. staff who refused to participate in training, staff assigned to you that you have been unable to work with, questions you’ve been asked you don’t feel comfortable answering, etc.
  8. Provide onsite support during implementation week to assist with pathway selection, identification of priority problems, establishing short term goals and evaluating goal achievement, documentation of Nursing Summary and Plan & Priorities for next shift.
  9. Role model problem-related documentation according to new process.

  1. Systems Support Services Rep./CAPS will:
  2. Consistently communicate the vision for the priority problems process.
  3. Work closely with Unit Educator/Designee and SuperUsers to ensure understanding of:
  4. Document initiation of a new Problem in HED
  5. Document short-term goals and actual outcomes in HED
  6. Document ending a goal in HED
  7. Identify the best match Pathway in StarPanel and save to patient’s EMR.
  8. Help Staff identify available support resources during implementation period.
  9. Develop & post training aides on unit.
  10. Place Problem Log on unit to document issues/ questions.
  11. Provide onsite support during implementation week to assist with general information about identifying problems, documenting in HED, etc.
  12. Tue. – Fri. of implementation week, 9am – 5pm, usually by CAPS (or equivalent for units without assigned CAPS, on CAPS day off)
  13. Tue., - Fri. of implementation week, 9pm – 5am, shared coverage by night shift SSS person across 3-4 units. Specific two hour support time slots will be scheduled on each unit every night.