Task Business Status CodeSystem Code system¶
| Canonical | ../CodeSystem/task-business-status |
|---|---|
| Status | draft · 1.26.0 |
| Content | complete |
| Source | FSH · JSON |
Coarse business sub-states recordable on a clinical task alongside its standard FHIR lifecycle status. The lifecycle status says where a task is in its workflow; these codes say whether the chart element the task is filed against needs a human's attention.
The axis is deliberately shallow -- in practice one flag and its cleared state. Richer
sub-states belong in status, in intent, or in a workflow's own vocabulary carried
under its own system.
Content is complete for the standard vocabulary defined here (Ok, Needs review),
consolidating under the IG canonical base the codes that a pre-consolidation system,
http://well.company/task-business-status, carried under an older canonical. Stored data
may still hold codings on that system, so a reader meeting older records should recognise
it; it is being migrated to the canonical declared here, tracked as FHIR-373. Write the
canonical system above.
⚠ As of 1.26.0 NexusEmrCoreClinicalTask.businessStatus binds required to
the union set, which admits this system and the
statutory correction vocabulary and nothing else. A coding on the pre-consolidation canonical is
therefore non-conformant rather than merely old, and this guide does not make an exception for
it. Sub-states from other systems -- SNOMED CT workflow states, source-EMR legacy
vocabularies -- are likewise no longer representable here: that freedom is what the required
binding withdrew.
| Code | Display | Definition |
|---|---|---|
ok |
Ok | The 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 … |
needs-review |
Needs review | DEPRECATED -- 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. Re… |