{
  "resourceType": "CodeSystem",
  "status": "draft",
  "content": "complete",
  "name": "NexusTaskOutputTypeCS",
  "id": "nexus-task-output-type",
  "title": "Task Output Type CodeSystem",
  "description": "Labels for `Task.output` slots whose meaning is structural rather than descriptive -- the ones a\nconsumer branches on. Currently one concept, marking the output that names the chart resource an\naccepted suggestion produced. Ordinary outputs keep their free-text `output.type` label; this system\ndoes not enumerate the chart.\n\nThe counterpart to\n[`nexus-task-input-type`](CodeSystem-nexus-task-input-type.md), which labels the input slot\nreferencing a task's contained suggested resource. The two are not symmetric in this guide: the\ninput label is bound into the Clinical Task profile as a slice discriminator and named by two\ninvariants, while `Task.output` is not modelled there. This system is declared so the label resolves,\nand adds no element and no constraint to any profile.\n\n**A reference from this slot may not resolve against a server.** An acceptance is written as a\ntransaction and the output can name an entry within it by `urn:uuid:` transaction identity. Resolve\nagainst the bundle that carried the acceptance until that transaction has been applied.\n\n**And it may name a resource that already existed.** Where an acceptance resolves onto a record\nalready in the chart instead of adding a second one, the output names the existing resource. The\ncode identifies the outcome slot, not the operation that filled it; read `Provenance` for what was\nactually done.",
  "url": "https://fhir.apps.health/CodeSystem/nexus-task-output-type",
  "concept": [
    {
      "code": "created-resource",
      "display": "Created chart resource",
      "definition": "This output references the chart resource an accepted suggestion produced -- the entry that was written when a user accepted the task's contained prototype. The reference may be a `urn:uuid:` transaction identity, resolvable only within the bundle that carried the acceptance, and it may name a resource that already existed where the acceptance resolved onto one rather than adding a second. Used on Task.output.type."
    }
  ],
  "experimental": false,
  "caseSensitive": true,
  "count": 1
}