Skip to content

Task Profile

Canonicalhttps://fhir.apps.health/StructureDefinition/nexus-emr-core-clinical-task
Statusdraft · 1.33.0
BaseTask (constraint)
SourceFSH · JSON

A unit of work in the chart: who asked for it, who owns it now, what has been said about it, and which chart element it concerns. Inbox items, to-dos, follow-ups, a result that needs review -- deliberately one kind of work item.

Examples

Chart-Created · Clinical · Document Review Task, Completed · Clinical task note sign off completed · Clinical task note sign off resubmitted · Clinical task note sign off returned · Clinical task ai triage 001 · Clinical task completed 001 · Clinical task lab review 001 · Clinical task nursing pool 001 · Clinical task referral 001 · Suggested-Resource Task - Add a Chart Entry · Suggested-Resource Task - Card Alternative A (empagliflozin) · Suggested-Resource Task - Card Alternative B (dulaglutide) · Suggested-Resource Task - Retire a Chart Entry · Team-Owned Standalone · Unassigned

Clinical task note sign off returned

Sign off encounter note

Task/nexus-emr-clinical-task-note-sign-off-returned — claims conformance to Task Profile

{
  "resourceType": "Task",
  "id": "nexus-emr-clinical-task-note-sign-off-returned",
  "meta": {
    "profile": [
      "https://fhir.apps.health/StructureDefinition/nexus-emr-core-clinical-task"
    ]
  },
  "text": {
    "status": "generated",
    "div": "<div xmlns="http://www.w3.org/1999/xhtml"><p>The first sign-off request on Dr. Okafor's 14 April note, which Dr. Carter returned for changes instead of signing off: the task is <code>cancelled</code>, and <code>statusReason</code> is <strong>coded</strong> <code>returned</code>. That pair is how a returned note reads -- nothing is written on the note for it and no separate state field. The coding is what makes it a return, not the text beside it: a request archived or set aside is also cancelled with a reason, and only this coding asks the author to change anything. What she asked to be changed is not here: her comment goes to Dr. Okafor as a task of its own and never becomes part of the note or of this request. When he signed the note again, a new request was raised, and being newer it decided the note's sign-off state from then on.</p></div>"
  },
  "status": "cancelled",
  "statusReason": {
    "coding": [
      {
        "system": "https://fhir.apps.health/CodeSystem/nexus-task-status-reason",
        "code": "returned",
        "display": "Returned for changes"
      }
    ],
    "text": "Returned for changes"
  },
  "intent": "order",
  "code": {
    "coding": [
      {
        "system": "https://fhir.apps.health/CodeSystem/nexus-task-code",
        "code": "note-sign-off",
        "display": "Note sign-off"
      }
    ]
  },
  "priority": "routine",
  "description": "Sign off encounter note",
  "focus": {
    "reference": "Composition/encounter-note-avery-20260414-signed-off",
    "display": "Encounter Note - 14 Apr 2026"
  },
  "for": {
    "reference": "Patient/avery-linwood",
    "display": "Avery Linwood"
  },
  "authoredOn": "2026-04-14T10:06:00-04:00",
  "lastModified": "2026-04-14T11:40:00-04:00",
  "requester": {
    "reference": "Practitioner/dr-sam-okafor",
    "display": "Dr. Sam Okafor"
  },
  "owner": {
    "reference": "Practitioner/dr-emily-carter",
    "display": "Dr. Emily Carter"
  }
}