Skip to content

Task Business Statuses Value set

Canonicalhttps://fhir.apps.health/ValueSet/task-business-statuses
Statusdraft · 1.33.0
SourceFSH · JSON

Business sub-states that can be recorded on a clinical task alongside its lifecycle status -- whether the chart element the task is filed against needs a human's eyes, which is a different question from where the task sits in its workflow (status) and from whether a machine proposal has been accepted (intent + status).

Reached from NexusEmrCoreClinicalTask.businessStatus through Task Business Statuses (all recognised), which binds required. A sub-state with no concept here is an error rather than a local extension -- adding one means adding it to this set, in a reviewed release.

Codes from Task Business Status CodeSystem

All 2 codes from this system, defined by this specification.

CodeDisplayDefinitionProperties
status
okOkThe flag is not set: nothing about the chart element this task references needs attention. Carries no information that an absent `businessStatus` does not also carry -- it exists so a writer can CLEAR the flag in place rather than remove the coding, and a reader should treat `ok` and absent as the same fact.
needs-reviewNeeds reviewDEPRECATED -- do not write. Inbound/legacy only: it marks a chart element the task is filed against (a result, document or referral) as unread or warranting a clinician's eyes. Retained because roughly two years of stored data carry it and it must stay representable. Do NOT forward-pull it into new Nexus EMR workflows: the case it was built for -- a completed referral that a new message should resurface -- is modelled as a NEW Task on the same ServiceRequest, because once a task is completed it does not come back to life. Inbound data carrying this code is transformed at the C3 gateway. The reason, when there is one, is free text in `businessStatus.text`.deprecated