06.04.2026

Today’s release includes the following updates:

  • Tasks now support a dedicated optional priority field with values STAT, Urgent, and Routine. This release includes changes across the UI, commands, FHIR API, and SDK:
    • The patient and global task panels support sorting and filtering by priority (sort order, high to low: STAT > Urgent > Routine > none). The patient chart task panel also includes a Priority filter and the ability to set or clear priority directly from a task card. Read more.
    • Added STAT as a new priority option on Imaging Order and Refer commands. These commands already supported Routine and Urgent; the dropdown now includes all three. Refer and Imaging Order commands continue to attach Urgent / Routine task labels only if those labels are configured under Admin Settings → Task Labels, to not disrupt existing workflows.
    • Task.priority is supported on Create, Search, Read, and Update on the Task FHIR endpoint, and priority is available as a search parameter.
    • Added a priority attribute to the Task data model.
    • Added a priority parameter to the AddTask and UpdateTask effects.
    • Added a priority parameter to the TaskCommand.
    • Added STAT to the existing Priority enum on the ReferCommand and ImagingOrderCommand.
    • The priority field is now included in the context payload for all TASK_COMMAND__* events.

bugfix

  • Fixed an issue where refilling a medication via the SDK selected the wrong dispense option when a medication offers more than one similar unit (for example, “0.5 mL vial” vs “Milliliter”) and a description is passed.

sdk

  • Plugins can now attach custom HTML to staged commands via the Canvas SDK. Read more
  • Plugins can now block command deletion by returning a CommandValidationErrorEffect from a *_COMMAND__PRE_DELETE handler. This enables custom validation rules — e.g. blocking deletion of an Urgent or STAT referral.