Skip to main content

Task Lifecycle

Tasks are the primary way CareLaunch tracks work that needs to be done. A task can represent a case review, a follow-up, a form that needs to be completed, a reminder, or a handoff to another system. This page explains the statuses a task can have, how tasks move between them, and who can make those changes.

Statuses​

CareLaunch uses the following task statuses. The table lists 12 values, but only 11 are selectable in the task editor; accepted is shown for compatibility but cannot be chosen manually.

StatusDisplay NameDescription
draftDraftTask has been created but is not yet actionable. Used for tasks that are being assembled or are pending additional information.
requestedRequestedTask has been requested and is awaiting acceptance. This is the default status when a task is created through a data import or external API. Also used for notification retry tasks and legacy reminder and check tasks.
receivedReceivedTask has been received by the intended performer but not yet started.
acceptedAcceptedTask has been accepted by the performer and is queued for work.
rejectedRejectedTask has been declined by the intended performer.
readyReadyTask is ready to be performed. This is the default status when a task is created by an automation (for example, a "Create Task" action) or through an integration.
in-progressIn ProgressTask is actively being worked on.
on-holdOn HoldTask has been temporarily paused.
cancelledCancelledTask has been cancelled before completion. Common when a linked appointment is cancelled.
completedCompletedTask has been finished. This is typically the final active state.
failedFailedTask could not be completed due to an error (for example, a missing appointment reference or a notification delivery failure).
entered-in-errorEntered in ErrorTask was recorded by mistake.

Status Flow Diagram​

How Tasks Are Created​

Data import or external API​

When a task is created through a data import or an external API connection, it is created with the status requested unless a different status is provided. Default values are applied for intent, code, and authored-on timestamp.

Automations and integrations​

When an automation uses a Create Task action, or when a task is created through an integration such as AWS Connect, it is created with the status ready unless the automation template specifies otherwise.

The task is linked to the resource that triggered it and to the patient it relates to.

Manual Status Changes​

A user can change a task's status through the admin UI — for example, in the task edit dialog, in a task list, or by dragging a card to a different column on a board.

When a status is changed through the UI, the platform records a status-history entry so you can see when the change happened.

Automated Status Changes​

Several platform processes can change a task status automatically:

Patient portal callback​

When a patient completes a task action through the patient portal, the task is set to completed.

Late reminder check​

A scheduled check verifies whether a patient joined an appointment. New checks run directly from a schedule and do not create a FHIR Task. Existing legacy check tasks can still be processed and updated.

No-show check​

A scheduled check evaluates whether a patient attended an appointment. New checks run directly from a schedule and do not create a FHIR Task. Existing legacy check tasks can still be processed and updated.

Appointment cancelled​

When an appointment linked to a task is cancelled or dismissed, pending direct reminder and check schedules are cancelled. Related legacy tasks are set to cancelled.

Appointment not found​

If a legacy check task cannot find a valid appointment, the task is set to cancelled.

Missing reference or delivery failure​

If a legacy check task cannot proceed because it is missing an appointment reference, or if a Concierge action fails, the task is set to failed.

Notification retry​

When an initial notification fails to deliver, the platform creates a retry task. The retry task moves through requested → in-progress → completed, failed, or cancelled depending on the result.

Subtask toggle​

When a user marks a subtask complete or incomplete, the subtask's own status is updated. The standard checkbox UI does not automatically complete or reopen the parent task. Parent-task transitions depend on the workflow configuration and any organization-specific automations, so behavior can vary between tenants.

Business Status (Workflow-Based Stages)​

In addition to the overall task status, tasks that are part of a workflow use a business status to track progress through workflow-defined stages.

  • Board columns can be configured to group tasks by business status.
  • Business statuses are defined by the workflow's actions (for example, "Registered", "Records Collection", "In Review", "Completed").
  • When a task belongs to a workflow, the board's status dropdown shows the workflow stages instead of the FHIR statuses.
  • Business status changes made through the UI are recorded in the status history.

For more information on workflows, see Workflows.

Status History​

Some status changes made through the admin UI append an entry to the task's statusReason field. The entry records the task's current FHIR status and the timestamp of the change, not an explicit previous-to-new status pair. This applies to changes made through specific UI paths such as the board status dropdown, drag-and-drop, and task-list actions.

Not every UI edit path updates statusReason. For a complete record of every saved version of a task, use the History tab in the task editor, which shows the FHIR resource version history. System processes (such as appointment cancellation or notification retries) may also overwrite statusReason with a plain-text note like "Appointment cancelled". Because of this, statusReason is best treated as a helpful note for selected UI changes, not a guaranteed audit trail.

Automations​

Tasks participate in the CareLaunch automation engine in two ways.

Tasks created by automations​

The Create Task automation action creates tasks when a trigger condition is met. Common triggers include:

  • Resource Creation — for example, when a patient is created.
  • Resource Update — when a record is updated.
  • Resource Delete — when a record is removed.
  • Scheduled (Recurring) — runs on a repeating schedule.
  • Scheduled (One-Time) — runs once at a scheduled time.
  • Manual — triggered by a user.

The default status for a task created by an automation is ready unless the automation template specifies otherwise. The template can pre-populate fields such as status, code, description, owner, due date, and linked questionnaires. Automations can also create subtasks as part of a workflow.

Automations triggered by task changes​

Task creation and updates can themselves trigger automations:

  • Resource Creation trigger fires when a new task is created.
  • Resource Update trigger fires when a task is updated, including status changes.
  • Resource Delete trigger fires when a task is deleted.

Automations can filter on task fields (code, status, owner) to decide which task events trigger downstream actions.

Concierge Service Integration​

The Concierge service maps task statuses to internal action states:

Task StatusAction Status
requestedpending
completedexecuted
cancelledcancelled
failedfailed
All otherspending

Reminder and check tasks​

The platform schedules appointment reminders and checks. New reminder, late-check, and no-show-check schedules do not create FHIR Tasks; existing legacy tasks are still handled. Retry tasks are created when reminder delivery fails:

  1. Reminder schedules — Send upcoming reminders and are cancelled if the appointment is cancelled.
  2. Late reminder check schedules — Verify whether a patient joined the appointment.
  3. No-show check schedules — Evaluate post-appointment attendance.
  4. Notification retry tasks — Created when reminder delivery fails. Progress through requested → in-progress → completed/failed/cancelled.

Access Control​

ActionWho Can Perform
CreateAdmin users, automation engine, patient portal (via callback)
ReadPlatform Admin, Organization Admin, Instance Admin, assigned practitioner
Update statusPlatform Admin, Organization Admin (via UI), automation engine, system processes
Complete (portal)Patient (via callback with a valid envelope)
DeletePlatform Admin, Organization Admin
  • Tasks — task creation, types, and management overview
  • Boards — visual kanban-style task management
  • Workflows — configure task workflow stages and business statuses
  • Automations — create and manage tasks automatically
  • Service Request Lifecycle — related resource lifecycle documentation