Task Status Reason CodeSystem Code system¶
| Canonical | https://fhir.apps.health/CodeSystem/nexus-task-status-reason |
|---|---|
| Status | draft · 1.33.0 |
| Content | complete |
| Source | FSH · JSON |
Why a task reached its status, for the cases where a reader derives a state from the reason rather than only displaying it.
Task.statusReason is free text elsewhere in the chart, which is sufficient wherever the reason is
read by a person. It is not sufficient where a reason CHANGES WHAT A READER CONCLUDES: a note's
sign-off state is read from the most recent sign-off request, and a request cancelled because the
note was returned for changes asks the learner to act, while a request cancelled for any other
reason asks them for nothing.
Only reasons a state is derived from are coded here. Every other closure in Nexus EMR writes
statusReason.text with no coding -- the Inbox's Archive and Reject, and a declined suggestion.
That is intentional: a reader keys on the coding it cares about and treats the absence of one as
"no coded reason", instead of enumerating the reasons it must ignore.
Match the coding, never the text. The text beside a coding is advisory, is not a translation of the code, and is not stable.
| Code | Display | Definition |
|---|---|---|
returned | Returned for changes | The request was cancelled because the reviewer sent the work back to its author to be changed, rather than approving it or setting it aside. On a `note-sign-off` request this is what makes a note read as RETURNED: the supervisor read the note, did not sign it off, and is asking the learner for a correction. It is the only cancellation that asks the author for anything, which is why it alone is coded -- a request archived, declined, or handed to another supervisor is cancelled with no coding and leaves the note awaiting a supervisor, who can still sign it off or return it from the note. What the reviewer asked to be changed is NOT carried here: that goes to the author as a task of its own, and this reason names only the decision. |