View raw Markdown
type: codesystemcodesystem: task-code

Task Codes

Concepts

CodeDisplayDefinition
approveActivate/approve the focal resourceTake what actions are needed to transition the focus resource from 'draft' to 'active' or 'in-progress', as appropriate for the resource type. This may involve additing additional content, approval, validation, etc.
fulfillFulfill the focal requestAct to perform the actions described in the focus request. This might result in a 'more assertive' request (order for a plan or proposal, filler order for a placer order), but is intend to eventually result in events. The degree of fulfillment requested might be limited by Task.restriction.
instantiateInstantiate the focal definitionAct to perform the actions defined in the focus definition resource (ActivityDefinition, PlanDefinition, Questionnaire, etc.) For PlanDefinition or ActivityDefinition, this might result in a 'more assertive' request (order for a plan or proposal, filler order for a placer order), but is intend to eventually result in events. For Questionnaire, this would result in a QuestionnaireResponse - and possibly resources constructed using data extracted from the response. The degree of fulfillment requested might be limited by Task.restriction.
abortMark the focal resource as no longer activeAbort, cancel or withdraw the focal resource, as appropriate for the type of resource.
replaceReplace the focal resource with the input resourceReplace the focal resource with the specified input resource
changeChange the focal resourceUpdate the focal resource of the owning system to reflect the content specified as the Task.focus
suspendSuspend the focal resourceTransition the focal resource from 'active' or 'in-progress' to 'suspended'
resumeRe-activate the focal resourceTransition the focal resource from 'suspended' to 'active' or 'in-progress' as appropriate for the resource type.
data-requestdata request taskA type of Task asking the Task.owner to deliver the data corresponding to the characteristics defined by the Task.inputs to the Task.requester

CodeSystem XML

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="task-code"/>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="oo"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="normative"/>
  </extension>
  <url value="http://hl7.org/fhir/CodeSystem/task-code"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.4.1397"/>
  </identifier>
  <version value="6.0.0"/>
  <name value="TaskCode"/>
  <title value="Task Codes"/>
  <status value="active"/>
  <experimental value="false"/>
  <description value="Codes indicating the type of action that is expected to be performed"/>
  <caseSensitive value="true"/>
  <valueSet value="http://hl7.org/fhir/ValueSet/task-code.html"/>
  <content value="complete"/>
  <concept>
    <code value="approve"/>
    <display value="Activate/approve the focal resource"/>
    <definition value="Take what actions are needed to transition the focus resource from 'draft' to 'active' or 'in-progress', as appropriate for the resource type.  This may involve additing additional content, approval, validation, etc."/>
  </concept>
  <concept>
    <code value="fulfill"/>
    <display value="Fulfill the focal request"/>
    <definition value="Act to perform the actions described in the focus request.  This might result in a 'more assertive' request (order for a plan or proposal, filler order for a placer order), but is intend to eventually result in events.  The degree of fulfillment requested might be limited by Task.restriction."/>
  </concept>
  <concept>
    <code value="instantiate"/>
    <display value="Instantiate the focal definition"/>
    <definition value="Act to perform the actions defined in the focus definition resource (ActivityDefinition, PlanDefinition, Questionnaire, etc.)  For PlanDefinition or ActivityDefinition, this might result in a 'more assertive' request (order for a plan or proposal, filler order for a placer order), but is intend to eventually result in events.  For Questionnaire, this would result in a QuestionnaireResponse - and possibly resources constructed using data extracted from the response.  The degree of fulfillment requested might be limited by Task.restriction."/>
  </concept>
  <concept>
    <code value="abort"/>
    <display value="Mark the focal resource as no longer active"/>
    <definition value="Abort, cancel or withdraw the focal resource, as appropriate for the type of resource."/>
  </concept>
  <concept>
    <code value="replace"/>
    <display value="Replace the focal resource with the input resource"/>
    <definition value="Replace the focal resource with the specified input resource"/>
  </concept>
  <concept>
    <code value="change"/>
    <display value="Change the focal resource"/>
    <definition value="Update the focal resource of the owning system to reflect the content specified as the Task.focus"/>
  </concept>
  <concept>
    <code value="suspend"/>
    <display value="Suspend the focal resource"/>
    <definition value="Transition the focal resource from 'active' or 'in-progress' to 'suspended'"/>
  </concept>
  <concept>
    <code value="resume"/>
    <display value="Re-activate the focal resource"/>
    <definition value="Transition the focal resource from 'suspended' to 'active' or 'in-progress' as appropriate for the resource type."/>
  </concept>
  <concept>
    <code value="data-request"/>
    <display value="data request task"/>
    <definition value="A type of Task asking the Task.owner to deliver the data corresponding to the characteristics defined by the Task.inputs to the Task.requester"/>
  </concept>
</CodeSystem>