# Tasks

Tasks in Welkin are action items assigned to care team members, linked to a specific patient. They keep clinical workflows on track by capturing things that need to happen — follow-up calls, form completions, approvals, referrals, or any ad-hoc action that doesn't happen inside an encounter.

***

## Task structure

Each task includes:

* **Title / Description** — what needs to be done
* **Patient** — the patient the task is related to
* **Assigned to** — which care team member is responsible
* **Due date** — when the task should be completed
* **Priority** — urgency level (e.g., High, Normal, Low)
* **Status** — current state of the task
* **Created by** — the user or automation that created it
* **Notes** — optional additional context

***

## Task statuses

| Status          | Description                   |
| --------------- | ----------------------------- |
| **To Do**       | Task created, not yet started |
| **In Progress** | Task is being worked on       |
| **Completed**   | Task is done                  |
| **Cancelled**   | Task is no longer needed      |

***

## Creating a task

### From a patient record

1. Open the patient record
2. Navigate to the **Tasks** tab
3. Click **+ Add Task**
4. Fill in the title, assignee, due date, and priority
5. Click **Save**

The task is now visible both on the patient record and in the assignee's task list.

### From the global Tasks view

1. In the left sidebar, navigate to **Tasks**
2. Click **+ New Task**
3. Search for and select the **patient** to link the task to
4. Fill in the remaining fields and click **Save**

### Via automation

Tasks can be created automatically by Welkin's automation engine when specific conditions are met — for example, when a patient completes an assessment, enters a new program phase, or misses a scheduled encounter. Automation-created tasks follow the same structure and appear in the same views. For configuration details, see [Automation](https://github.com/welkincloud-io/welkin-docs/blob/master/kb/admin/automation.md).

***

## Viewing and managing tasks

### Patient-level task list

All tasks for a specific patient are visible in the **Tasks** tab of their patient profile. You can filter by status, assignee, or due date.

### My Tasks / All Tasks view

The global **Tasks** view (accessible from the left sidebar) provides a list of:

* **My Tasks** — tasks assigned to the currently logged-in user
* **All Tasks** — all tasks across the organization (for roles with access)

Both views support filtering by patient, assignee, due date range, priority, and status.

***

## Completing a task

1. Open the task (from the patient record or the task list)
2. Update the status to **Completed**
3. Add a completion note if needed
4. Save

Completed tasks remain visible in the patient's task history for audit purposes.

***

## Reassigning a task

1. Open the task
2. Change the **Assigned to** field to a different care team member
3. Save — the new assignee will receive a notification

***

## Task reminders

When a task is approaching its due date or becomes overdue, Welkin sends a notification to the assignee. Notification settings can be adjusted in [User Profile](/care/getting-started/user-profile.md) and configured system-wide by administrators in Designer.

***

## Related articles

* [Care Portal Overview](/care/readme.md)
* [Notifications & Alerts](/care/getting-started/notifications-and-alerts.md)
* [Patient Profile Overview](/care/patients/patient-profile-overview.md)
* [Automation](https://github.com/welkincloud-io/welkin-docs/blob/master/kb/admin/automation.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.welkinhealth.com/care/tasks/tasks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.