Task Codes Value set¶
| Canonical | https://fhir.apps.health/ValueSet/nexus-task-codes |
|---|---|
| Status | draft · 1.33.0 |
| Source | FSH · JSON |
The category a clinical task is filed under, so a view can sort tasks into bins: reminder, call,
appointment, review-report, prevention, referral, billing, medication, other. Bound EXTENSIBLY
from NexusEmrCoreClinicalTask.code, so a deployment needing a category this value set does not
carry stays valid under its own system. Task.code is optional and this axis is independent of
whether the task carries a suggested resource and of Task.intent.
Codes from Task Code CodeSystem¶
All 17 codes from this system, defined by this specification.
| Code | Display | Definition |
|---|---|---|
reminder | Reminder | A prompt to do something at or by a time, with no other chart element behind it. The default category where nothing more specific fits the work. |
call | Call | Contact the patient or another party by telephone. |
appointment | Appointment | Work about booking, rebooking or preparing for a visit. |
review-report | Review report | An incoming result or report that needs a clinician's eyes: laboratory results, diagnostic imaging reports, cardiodiagnostics, and anything else arriving on the same inbound stream. NAMED FOR THE WORK, NOT THE SOURCE. `lab` was the obvious name and it is the wrong one: imaging and other non-laboratory reports arrive on that stream in volume, and a category called `lab` either excludes them or quietly redefines `lab` to mean something it does not mean. The task's `Task.focus` names the report itself, so the resource type is already recoverable without the category having to carry it. |
document-review | Document review | A chart document routed to a NAMED reviewer to acknowledge it: the document form assigns one task per reviewer, the task's `Task.focus` names the document, its owner is the reviewer, and the reviewer's acknowledgement is recorded on the DOCUMENT rather than here -- the `nexus-emr-reviewed` extension on the DocumentReference this task focuses on names who reviewed it and when, with absent meaning unreviewed, so a reader holding the document needs no task join to know. Completing this task is the workflow half of the same act. Distinct from `review-report` on purpose -- that code is the inbound triage stream (results and reports arriving for a clinician's eyes), while this one is an assignment a user makes from an already-filed document. The code is also this workflow's SELECTOR: the document form lists a document's reviewers by it, and acts on what it lists (a priority change re-saves every listed task; removing a reviewer cancels one), so a task that merely focuses on a document without this code is deliberately not a reviewer. |
note-sign-off | Note sign-off | An encounter note routed to a supervisor for sign-off: a learner signs the note and names the supervisor, the task's `Task.focus` names the note, its owner is the supervisor, and the sign-off is recorded on the NOTE rather than here -- a `professional` `Composition.attester` carrying `nexus-attestation-function` `VRF` names who signed off and when, and `nexus-attested-version` names the version of the note they read. Completing this task is the workflow half of that act, and completing it without that attester is not a sign-off. A note RETURNED for changes is this task `cancelled` with a `Task.statusReason` CODED `returned` from the task status-reason system; a cancellation carrying any other reason, or none, is not a return -- archiving one of these requests must not read to the learner as a request to change the note. Distinct from `document-review` because a note is approved per version and its sign-off never carries forward to a later edit, and from a co-signature, which is a `professional` attester on the note. |
note-co-signature | Note co-signature | An encounter note routed to a second clinician to co-sign it at the author's request: the task's `Task.focus` names the note and its owner is the clinician asked. The request lives HERE and not on the note -- a `Composition.attester` records an attestation given, never one asked for. The co-signature itself is an `AUTHEN` attester the co-signing clinician writes, with its `time`, when they sign; completing this task without that attester is not a co-signature. Re-routing cancels this task and raises a new one for the new clinician. Distinct from `note-sign-off`, which is a supervisor approving a learner's note, version by version. |
note-sign-off-comment | Note sign-off comment | The teaching comment a supervisor sends a learner in the same act as signing their note off. The task's owner is the note's AUTHOR, because this is work for the learner rather than the supervisor; its `Task.focus` names the note the comment is about, its requester is the supervisor, its `Task.description` is a fixed sentence saying a comment was left on a signed-off note, and what the supervisor wrote is the task's first `Task.note` -- the same shape as `note-sign-off-feedback`, because a note carries who wrote it and when where a description carries neither, and a fixed description lets a worklist row say what the task is before it is opened. A READER MUST FALL BACK TO `Task.description` for comments written before the words moved into the thread. NOT a request, and it carries no deadline: completing it means the learner has READ what their supervisor wrote, not that anything was done -- the same reading as `privacy-notice`. NOTHING ABOUT THE COMMENT IS RECORDED ON THE NOTE -- not its body, not its attesters, not the sign-off request's `statusReason` -- because teaching feedback is not part of the patient's record: signing off with a comment and signing off plainly leave the same document behind, and this task is the only place the comment exists. Deliberately NOT `note-sign-off`, which is the sign-off REQUEST: that read completes whatever carries the code and treats an open one as a note still awaiting sign-off, so a comment wearing it would be closed as a request nobody raised and would hold a signed-off note at awaiting. |
note-sign-off-feedback | Note sign-off feedback | The changes a supervisor asks a learner to make when they RETURN a note for changes rather than signing it off. The task's owner is the note's AUTHOR; its `Task.focus` names the note; its `Task.description` is a fixed sentence saying that changes were requested, and what the supervisor wrote is the task's first `Task.note`. It travels with the return itself, which is the `note-sign-off` request `cancelled` with a `Task.statusReason` coded `returned`: the request names the decision, and this task carries what the supervisor asked for. It carries no deadline, and NOTHING ABOUT IT IS RECORDED ON THE NOTE -- not its body, not its attesters, not the request's `statusReason`. It is ANSWERED BY THE REVISION: when the author signs the note again, every open task of this code focused on that note is completed, after the new sign-off request is filed. Completing it, by that path or by hand, means the learner has dealt with the feedback; it is not a sign-off and moves the note's sign-off state nowhere. A reader finds it by this code AND the note's focus together, never by focus alone, which would also reach the sign-off request on the same note and close a supervisor's ask with no sign-off behind it. Deliberately NOT `note-sign-off-comment`, which carries a supervisor's words the same way: that comment accompanies an approval and asks for nothing, while this one asks for a correction and is closed by the next signing; a reader closing one must not reach the other. Deliberately NOT `note-sign-off` either, for the reason that code gives. |
forward-result | Forward result to provider | A result or report a clinician has sent to a NAMED colleague for their attention: the forwarding user is the task's requester, its `Task.focus` names the DiagnosticReport, and ONE TASK IS RAISED PER RECIPIENT with that recipient as its owner -- two colleagues sent the same report each get their own work item and each finishes independently. The task stays `requested` until the recipient acknowledges it. Deliberately NOT the code a report's own review task carries: a reader takes a report's REVIEW STATE from that task, so a forward wearing it would flip the report's review state -- the report would read as reviewed because somebody passed it on. Distinct from `review-report`, which is the inbound triage stream of results arriving for a clinician's eyes; this code is an onward hand-off a user makes from a report already filed, the same shape as `document-review` and for the same reason. |
prevention | Prevention | Screening, immunization and other preventive-care work, typically raised from a care gap. |
referral | Referral | Work about sending a patient to another clinician or service, or about a referral already sent. |
billing | Billing | Administrative and revenue work: claim correction, uninsured-service collection, rejected-invoice follow-up. |
medication | Medication | Work about a patient's medications: renewals, changes, reconciliation, adherence follow-up. |
privacy-notice | Privacy notice | A notice to a clinician that something happened to a patient they are responsible for -- most often that somebody broke the glass on a chart where they are the most responsible provider. NOT a request and not work the recipient asked for: it is raised by the system, it carries no deadline, and completing it means the clinician has read it rather than that anything was done. Distinct from `privacy-request`, which is work arising from an INDIVIDUAL exercising a right and carries a statutory response clock. |
privacy-request | Privacy request | Work arising from an individual exercising a right over their own record: a request to access it, a request to correct it, or a statement of disagreement to be logged where a correction was refused. NAMED FOR THE RIGHT, NOT THE OUTCOME -- one bin covers access, correction and disagreement because the same privacy role handles all three and they share statutory response clocks. Which one this task is, and where it has got to, are read off `Task.businessStatus` (the correction business-status vocabulary) and off the optional second `code` coding from the international correction task-type system -- both of which are CORRECTION vocabularies, so an access request is identified only by the absence of a second coding and has no state that says the record was released. The statutory deadline is the task due date, `restriction.period.end`. Distinct from `document-review`, which is a clinician signing off a chart document, and from `other`, which says nobody found a bin. |
other | Other | Work that fits no category above. A real answer rather than an absent one: it says somebody looked and none applied, which an absent `Task.code` does not. |