Reporting Action Task Type CodeSystem Code system¶
| Canonical | ../CodeSystem/reporting-action-task |
|---|---|
| Status | draft · 1.26.0 |
| Content | fragment |
| Source | FSH · JSON |
The kind of work a Task created by a reporting action run asks for. A report run matches a
population, a human confirms an action on it, and the executor creates one Task per patient; the
task type chosen on the action sheet is written as the single coding on that Task's code, and this
is that coding's system.
The code is repeated verbatim in Task.code.text. There is no display on the resource, so the
text is the code rather than a label for it, and a surface that wants a readable phrase supplies one.
Task.code carries two different vocabularies in this estate, and they overlap. A clinical task
raised in the chart is coded under nexus-task-code, which says
which bin a task is filed in. A Task created by a reporting action run is coded under this system,
which says what the sheet asked for. No concept in either is a synonym for one in the other, and
call appears in both -- a chart-task category meaning "telephone the patient", and here "the sheet
asked for a phone call". Match on the system and the code together on this element. Matching the
code alone silently conflates the two.
Content is a FRAGMENT. Four of the codes below are the action sheet's options and follow-up is
what a run gets when its stored parameters name no task type. The value reaches Task.code as the
sheet's saved configuration holds it, rather than being checked against a list the way the priority
beside it is, so a code this list does not carry can appear on a stored Task. Absence from this list
does not mean absence from the system; tolerate an unlisted code rather than rejecting it.
The type is not the priority and not the assignee. Those are Task.priority and
Task.performerType, chosen independently on the same sheet, and none of the three is recoverable
from another.
MIGRATION. Nexus EMR writes these codes today under http://well.company/reporting-action-task,
a system this specification does not publish, on a host it does not govern. That address is live in
code and in stored Task.code codings, and is under migration to the canonical declared here. Write
the canonical; expect both until the migration completes, and match both addresses exactly rather
than deriving one from the other.
| Code | Display | Definition |
|---|---|---|
book |
Book an appointment | Book, rebook or arrange a visit for the patient the Task is for. |
labs |
Order labs | Order the laboratory work the report's criteria imply for this patient. |
review |
Chart review | Review this patient's chart against what the report matched on. |
call |
Phone call | 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. … |
follow-up |
Follow up | 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. |