Task Output Type CodeSystem Code system¶
| Canonical | ../CodeSystem/nexus-task-output-type |
|---|---|
| Status | draft · 1.26.0 |
| Content | complete |
| Source | FSH · JSON |
Labels for Task.output slots whose meaning is structural rather than descriptive -- the ones a
consumer branches on. Currently one concept, marking the output that names the chart resource an
accepted suggestion produced. Ordinary outputs keep their free-text output.type label; this system
does not enumerate the chart.
The counterpart to
nexus-task-input-type, which labels the input slot
referencing a task's contained suggested resource. The two are not symmetric in this guide: the
input label is bound into the Clinical Task profile as a slice discriminator and named by two
invariants, while Task.output is not modelled there. This system is declared so the label resolves,
and adds no element and no constraint to any profile.
A reference from this slot may not resolve against a server. An acceptance is written as a
transaction and the output can name an entry within it by urn:uuid: transaction identity. Resolve
against the bundle that carried the acceptance until that transaction has been applied.
And it may name a resource that already existed. Where an acceptance resolves onto a record
already in the chart instead of adding a second one, the output names the existing resource. The
code identifies the outcome slot, not the operation that filled it; read Provenance for what was
actually done.
| Code | Display | Definition |
|---|---|---|
created-resource |
Created chart resource | 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… |