{
  "resourceType": "CodeSystem",
  "status": "draft",
  "content": "complete",
  "name": "TaskBusinessStatusCS",
  "id": "task-business-status",
  "title": "Task Business Status CodeSystem",
  "description": "Coarse business sub-states recordable on a clinical task alongside its standard FHIR\nlifecycle status. The lifecycle status says where a task is in its workflow; these codes\nsay whether the chart element the task is filed against needs a human's attention.\n\nThe axis is deliberately shallow -- in practice one flag and its cleared state. Richer\nsub-states belong in `status`, in `intent`, or in a workflow's own vocabulary carried\nunder its own system.\n\nContent is `complete` for the standard vocabulary defined here (Ok, Needs review),\nconsolidating under the IG canonical base the codes that a pre-consolidation system,\n`http://well.company/task-business-status`, carried under an older canonical. Stored data\nmay still hold codings on that system, so a reader meeting older records should recognise\nit; it is being migrated to the canonical declared here, tracked as FHIR-373. Write the\ncanonical system above.\n\n⚠ As of 1.26.0 `NexusEmrCoreClinicalTask.businessStatus` binds required to\n[the union set](ValueSet-task-business-status-all.md), which admits this system and the\nstatutory correction vocabulary and nothing else. A coding on the pre-consolidation canonical is\ntherefore non-conformant rather than merely old, and this guide does not make an exception for\nit. Sub-states from other systems -- SNOMED CT workflow states, source-EMR legacy\nvocabularies -- are likewise no longer representable here: that freedom is what the required\nbinding withdrew.",
  "url": "https://fhir.apps.health/CodeSystem/task-business-status",
  "concept": [
    {
      "code": "ok",
      "display": "Ok",
      "definition": "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 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."
    },
    {
      "code": "needs-review",
      "display": "Needs review",
      "definition": "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. 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`.",
      "property": [
        {
          "code": "status",
          "valueCode": "deprecated"
        }
      ]
    }
  ],
  "experimental": false,
  "caseSensitive": true,
  "property": [
    {
      "code": "status",
      "uri": "http://hl7.org/fhir/concept-properties#status",
      "type": "code",
      "description": "Concept lifecycle status (active | deprecated | retired)."
    }
  ],
  "count": 2
}