# Seeking Feasibility Feedback Clinical Task Handover & Shift Continuity Idea
**URL:** https://talk.openmrs.org/t/seeking-feasibility-feedback-clinical-task-handover-shift-continuity-idea/48121
**Category:** Community
**Tags:** developers-forum, o3
**Created:** [January 26, 2026, 7:26pm UTC](https://talk.openmrs.org/t/seeking-feasibility-feedback-clinical-task-handover-shift-continuity-idea/48121 "2026-01-26T19:26:39Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@dishakd](https://talk.openmrs.org/u/dishakd)
#### Post date: [January 26, 2026, 7:26pm UTC](https://talk.openmrs.org/t/seeking-feasibility-feedback-clinical-task-handover-shift-continuity-idea/48121/1 "2026-01-26T19:26:39Z")
Hi everyone,
I’m exploring potential project ideas for **Google Summer of Code 2026** with **OpenMRS** , and I’d really appreciate community feedback on the feasibility and relevance of the following idea before moving forward.
* * *
**Problem I Addressed**
In many real hospital environments, clinicians work in rotating shifts. While OpenMRS captures encounters, orders, and observations effectively, there doesn’t appear to be a structured way to manage clinical follow-up tasks and responsibility across shifts.
In practice, this can lead to:
- Missed follow-ups (e.g., reviewing lab results, reassessing patients)
- Loss of clinical context when care is handed over
- Reliance on informal methods such as paper notes or verbal handover
I’m trying to understand whether this is a problem that OpenMRS implementations commonly face and whether it’s something worth addressing at the platform/module level.
* * *
### Idea I am Proposing
**Clinical Task Handover & Shift Continuity (Concept)**
The idea is to introduce a lightweight, backend-focused mechanism that allows clinicians to create and track patient-linked clinical tasks, with support for continuity across shifts.
At a high level, this could include:
- Creating clinical follow-up tasks linked to a patient and encounter
- Assigning tasks to providers or locations (e.g., ward / department)
- Carrying over pending tasks when shifts change
- Tracking task status (pending, completed, overdue)
- Basic auditability for safety and accountability
This is only a concept at this stage, and I’m intentionally keeping the scope open.
* * *
### Questions for the Community
I’d really appreciate feedback on:
- Is this a real and recurring problem in OpenMRS implementations?
- Are there existing modules, discussions, or past efforts addressing this?
- Would this be better modeled using existing OpenMRS concepts (e.g., orders, encounters, programs)?
- Does this seem feasible and appropriate for a GSoC-scale project?
- Any concerns or alternative approaches I should consider?
---
### Author:  [@lagalagadonia](https://talk.openmrs.org/u/lagalagadonia)
#### Post date: [September 14, 2026, 2:06pm UTC](https://talk.openmrs.org/t/seeking-feasibility-feedback-clinical-task-handover-shift-continuity-idea/48121/2 "2026-09-14T14:06:12Z")
Hola. Estoy investigando un problema muy cercano: cómo mantener trazabilidad de una necesidad clínica cuando queda pendiente entre actores, turnos o servicios.
Me interesa saber si alguien conoce implementaciones reales de OpenMRS donde una tarea, referencia u orden tenga:
- responsable vigente,
- fecha o plazo esperado,
- estado vencido,
- reasignación o escalamiento,
- y una condición verificable de cierre.
En particular, ¿existe algún caso en producción donde el paso del tiempo por sí mismo cambie el estado o genere una acción automática?
Si existe algún módulo, implementación nacional o experiencia de campo, me sería muy útil conocerla.