{
  "resourceType": "CodeSystem",
  "status": "draft",
  "content": "fragment",
  "name": "ReportingActionTaskCS",
  "id": "reporting-action-task",
  "title": "Reporting Action Task Type CodeSystem",
  "description": "The kind of work a Task created by a reporting action run asks for. A report run matches a\npopulation, a human confirms an action on it, and the executor creates one Task per patient; the\ntask type chosen on the action sheet is written as the single coding on that Task's `code`, and this\nis that coding's `system`.\n\n**The code is repeated verbatim in `Task.code.text`.** There is no display on the resource, so the\ntext is the code rather than a label for it, and a surface that wants a readable phrase supplies one.\n\n**`Task.code` carries two different vocabularies in this estate, and they overlap.** A clinical task\nraised in the chart is coded under [`nexus-task-code`](CodeSystem-nexus-task-code.md), which says\nwhich bin a task is filed in. A Task created by a reporting action run is coded under this system,\nwhich says what the sheet asked for. No concept in either is a synonym for one in the other, and\n`call` appears in both -- a chart-task category meaning \"telephone the patient\", and here \"the sheet\nasked for a phone call\". **Match on the system and the code together on this element.** Matching the\ncode alone silently conflates the two.\n\n**Content is a FRAGMENT.** Four of the codes below are the action sheet's options and `follow-up` is\nwhat a run gets when its stored parameters name no task type. The value reaches `Task.code` as the\nsheet's saved configuration holds it, rather than being checked against a list the way the priority\nbeside it is, so a code this list does not carry can appear on a stored Task. Absence from this list\ndoes not mean absence from the system; tolerate an unlisted code rather than rejecting it.\n\n**The type is not the priority and not the assignee.** Those are `Task.priority` and\n`Task.performerType`, chosen independently on the same sheet, and none of the three is recoverable\nfrom another.\n\n**MIGRATION.** Nexus EMR writes these codes today under `http://well.company/reporting-action-task`,\na system this specification does not publish, on a host it does not govern. That address is live in\ncode and in stored `Task.code` codings, and is under migration to the canonical declared here. Write\nthe canonical; expect both until the migration completes, and match both addresses exactly rather\nthan deriving one from the other.",
  "url": "https://fhir.apps.health/CodeSystem/reporting-action-task",
  "concept": [
    {
      "code": "book",
      "display": "Book an appointment",
      "definition": "Book, rebook or arrange a visit for the patient the Task is for."
    },
    {
      "code": "labs",
      "display": "Order labs",
      "definition": "Order the laboratory work the report's criteria imply for this patient."
    },
    {
      "code": "review",
      "display": "Chart review",
      "definition": "Review this patient's chart against what the report matched on."
    },
    {
      "code": "call",
      "display": "Phone call",
      "definition": "Telephone the patient. NOT the same concept as `call` in the chart-task categories: that one says a task is FILED as a phone call, this one says a reporting action asked for one. The two systems are not interchangeable and the shared code is a collision, not a mapping."
    },
    {
      "code": "follow-up",
      "display": "Follow up",
      "definition": "General follow-up. What a run gets when its stored parameters name no task type at all, rather than an option offered on the action sheet."
    }
  ],
  "experimental": false,
  "caseSensitive": true
}