clinik.tasks
Tasks represent clinical workflow items — lab orders, referral follow-ups, care coordination activities, and other actionable items that need to be tracked through a lifecycle.create
| Field | Type | Required | Description |
|---|---|---|---|
status | string | Yes | draft, requested, received, accepted, rejected, ready, cancelled, in-progress, on-hold, failed, completed |
intent | string | Yes | unknown, proposal, plan, order, original-order, reflex-order, filler-order, instance-order, option |
statusReason | string | No | Reason for current status |
businessStatus | string | No | Business-specific status (e.g. “Specimen collected”) |
priority | string | No | routine, urgent, asap, stat |
code | string | No | Task type code |
description | string | No | Human-readable description |
focusId | string | No | What the task is acting on |
patientId | string | No | Beneficiary of the task |
encounterId | string | No | Encounter context |
executionPeriod | { start?, end? } | No | Execution time window |
authoredOn | string | No | When authored (defaults to now) |
requesterId | string | No | Who is requesting |
ownerId | string | No | Who is responsible |
reasonCode | string | No | Why the task is needed |
note | string | No | Additional notes |
basedOn | string[] | No | Request IDs this task fulfills |
partOf | string[] | No | Parent task IDs |
input | TaskInputOutput[] | No | Task inputs |
output | TaskInputOutput[] | No | Task outputs |
restriction | object | No | Fulfillment restrictions |
Example
read / update / delete / search
Same pattern as other resources. Search supportspatientId, ownerId, requesterId, status, priority, code filters.