Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (11)
Destacado
Destacado (16)
Similar a 6 Requirements for Patient Hand-Off Apps
Similar a 6 Requirements for Patient Hand-Off Apps (20)
6 Requirements for Patient Hand-Off Apps
- 1. www.amia.org S42: 6 Requirements for Patient Hand-Off Application in Hospital Setting: Lesson Learned from TaskList Project Soleh Al Ayubi, PhD Innovation Group Boston Children’s Hospital
- 2. www.amia.org Disclosure • Nothing to disclose 2
- 3. www.amia.org Learning Objectives • Understand the underlying reasons to implement well-designed application to support patient hand-off processes. • Understand the 6 important user requirements of application to support patient hand-off processes. 3
- 4. www.amia.org Background • Communications are leading cause of medical errors 4 • Multi tasks • Multi patients
- 5. www.amia.org Background 5 • Unshared • Insecure • Redundant • Not-integrated • Not-live • Not mobile • Not live • Not-integrated • Insecure • Not supported
- 7. www.amia.org TaskList Pilot Pilot-1 • November 2013 • 2 Weeks - 7W Unit • Technological issues • Identified strong clinical champions • Busy periods for the unit • Complex Unit Pilot-2 • May 2014 • 2 Weeks – 9E Unit • Team engaged • Works better for a team geographically distributed • More integration with EMRs and team calendar 7
- 8. www.amia.org Six Important Requirements: Lesson Learned 8 Integrated Collaborative Secure Real Time UsableMobile
- 9. www.amia.org 6 Requirements for Patient Hand-Off Application in Hospital Setting: Lesson Learned from TaskList Project Questions Thank you! 9
Notas del editor
- After participating in this activity, the learner should be better able to
- Medical team members have many tasks, divide their attention between multiple tasks and patients, and have high demands around communication and documentation. Miscommunications among medical team members are a leading cause of medical errors.
- Paper check lists. Check lists in EMRs (often lack mobile, live-tracking components). Non-EMR check list applications (not have required security or privacy controls, may not be integrated with EMRs, and may not be supported by local institutions)