HL7 Terminology (THO)
7.2.0 - Publication
This page is part of the HL7 Terminology (v7.2.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
| Active as of 2026-06-01 | Maturity Level: 4 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="task-code"/>
<meta>
<lastUpdated value="2026-05-28T22:17:06.96+00:00"/>
</meta>
<language value="en"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem task-code</b></p><a name="task-code"> </a><a name="hctask-code"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Last updated: 2026-05-28 22:17:06+0000</p></div><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/task-code</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">approve<a name="task-code-approve"> </a></td><td>Activate/approve the focal resource</td><td>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.</td></tr><tr><td style="white-space:nowrap">fulfill<a name="task-code-fulfill"> </a></td><td>Fulfill the focal request</td><td>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.</td></tr><tr><td style="white-space:nowrap">instantiate<a name="task-code-instantiate"> </a></td><td>Instantiate the focal definition</td><td>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.</td></tr><tr><td style="white-space:nowrap">abort<a name="task-code-abort"> </a></td><td>Mark the focal resource as no longer active</td><td>Abort, cancel or withdraw the focal resource, as appropriate for the type of resource.</td></tr><tr><td style="white-space:nowrap">replace<a name="task-code-replace"> </a></td><td>Replace the focal resource with the input resource</td><td>Replace the focal resource with the specified input resource</td></tr><tr><td style="white-space:nowrap">change<a name="task-code-change"> </a></td><td>Change the focal resource</td><td>Update the focal resource of the owning system to reflect the content specified as the Task.focus</td></tr><tr><td style="white-space:nowrap">suspend<a name="task-code-suspend"> </a></td><td>Suspend the focal resource</td><td>Transition the focal resource from 'active' or 'in-progress' to 'suspended'</td></tr><tr><td style="white-space:nowrap">resume<a name="task-code-resume"> </a></td><td>Re-activate the focal resource</td><td>Transition the focal resource from 'suspended' to 'active' or 'in-progress' as appropriate for the resource type.</td></tr><tr><td style="white-space:nowrap">data-request<a name="task-code-data-request"> </a></td><td>Data request task</td><td>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</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="oo"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="4"/>
</extension>
<url value="http://terminology.hl7.org/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="1.0.0"/>
<name value="TaskCode"/>
<title value="Task Codes"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-06-01"/>
<publisher value="Health Level Seven International"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org"/>
</telecom>
<telecom>
<system value="email"/>
<value value="hq@HL7.org"/>
</telecom>
</contact>
<description
value="Codes indicating the type of action that is expected to be performed"/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<copyright
value="This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license"/>
<caseSensitive value="true"/>
<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>