Skip to main content
All CollectionsSchedulingTasks
Automate Task Management with Task Templates (Beta)
Automate Task Management with Task Templates (Beta)

Automatically create tasks based on templates.

Updated over a week ago

Streamline Workflow with Automated Task Creation

Managing clinic tasks efficiently is crucial to ensuring nothing gets missed. With Task Templates in Digitail PIMS, clinics can automate task creation by linking templates to diagnoses, products, or services. This ensures necessary tasks are triggered automatically when these items are administered. Clinics can also create individual templates manually or add standalone tasks outside of a template for greater flexibility.


How to Set Up Task Templates

Accessing Task Templates

To set up Task Templates, follow these steps:

  1. Click on the Profile Image (top right corner) → Administration → Task Templates

  2. Click Add Template to create a new Task Template.

  3. Enter a Template Name and optional description to define its purpose.

  4. Click Save to store the template.

Editing or Removing Existing Task Templates

  1. Click Edit to modify an existing template or Delete to remove it.

  2. Adjust tasks, recurrence settings, and linked items as needed.


Linking Task Templates to Diagnoses, Products, or Services

Once a Task Template is created, it can be associated with diagnoses, products, or services to automate task generation.

📌 Important: When a linked diagnosis, product, or service is administered in a SOAP, the associated Task Template will automatically generate the required tasks.


Editing or Removing Tasks from a SOAP

After a Task Template is added to a SOAP, individual tasks can still be edited or removed if needed.

  1. Open the SOAP Record where the template tasks have been added.

  2. Click Edit on a specific task to modify details such as due time, assigned staff, or recurrence.

  3. Click Delete if a task is no longer needed in that specific instance.

  4. Changes made here do not affect the original template but only apply to this case.

📌 Tip: This is useful for cases where certain tasks may not be necessary for a specific patient visit.


Task Recurrence & Scheduling

Tasks can be configured with recurrence to ensure ongoing actions are scheduled automatically.

  • One-time tasks: Set to trigger immediately or after a delay (e.g., 5 minutes post-administration).

  • Recurring tasks: Repeat at specific intervals, such as every 4 minutes/hours, daily, or weekly.

  • Task start times: Choose whether a task should begin immediately, after a short delay, or at a scheduled time.

📌 Example Use Cases:

  • Surgery Service Tasks:

    • Immediately after service is added: Administer pre-medication.

    • 5 minutes after administration: Monitor vitals.

    • Every 30 minutes during surgery: Check anesthesia depth.

    • After surgery: Post-op pain assessment every 4 hours.

  • Dental Procedure Tasks:

    • At procedure start: Administer anesthesia.

    • 15 minutes after anesthesia: Begin dental scaling.

    • After completion: Record dental findings and schedule follow-up.

  • Hospitalization Tasks (Visible on Whiteboard):

    • Immediately on admission: Record patient weight and vitals.

    • Every 6 hours: Administer fluids.

    • Every 12 hours: Check temperature.

    • Every 24 hours: Review patient condition and update SOAP notes.


Where Tasks Are Displayed

All automatically added tasks will be visible across multiple modules in the Digitail platform:

  • SOAP Records: Tasks appear in the patient’s visit record.

  • Calendar: Scheduled tasks will be visible for easy tracking.

  • Flowboard: Ongoing tasks appear in real-time clinic workflows.

  • Whiteboard: For hospitalized patients, tasks are displayed in the Whiteboard view.

By leveraging Task Templates, clinics can ensure workflow efficiency, reduced manual work, and better organization.


Automation examples from the Digitail vet team

Example of a DKA Hospitalization & Treatment using Task automation

Example of a CPV Hospitalization & Tearment Protocol

Did this answer your question?