SMART Base, published by WHO. This guide is not an authorized publication; it is the continuous build for version 0.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/WorldHealthOrganization/smart-base/ and changes regularly. See the Directory of published versions
| Active as of 2026-08-26 |
@prefix fhir: <http://hl7.org/fhir/> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . # - resource ------------------------------------------------------------------- <http://hl7.org/fhir/CodeSystem/SGTasks> a fhir:CodeSystem ; fhir:nodeRole fhir:treeRoot ; fhir:Resource.id [ fhir:value "SGTasks"] ; fhir:DomainResource.text [ fhir:Narrative.status [ fhir:value "generated" ] ; fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\"><div xml:lang=\"en\" lang=\"en\"><hr/><p><b>English</b></p><hr/><p class=\"res-header-id\"><b>Generated Narrative: CodeSystem SGTasks</b></p><a name=\"SGTasks\"> </a><a name=\"hcSGTasks\"> </a><p>This case-insensitive code system <code>http://smart.who.int/base/CodeSystem/SGTasks</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\">businessRuleTask<a name=\"SGTasks-businessRuleTask\"> </a></td><td>Business Rule Task</td><td>A Business Rule Task provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide.</td></tr><tr><td style=\"white-space:nowrap\">manualTask<a name=\"SGTasks-manualTask\"> </a></td><td>Manual Task</td><td>A Manual Task is a Task that is expected to be performed without the aid of any business process execution engine or any application. An example of this could be a telephone technician installing a telephone at a customer location.</td></tr><tr><td style=\"white-space:nowrap\">receiveTask<a name=\"SGTasks-receiveTask\"> </a></td><td>Receive Task</td><td>A Receive Task is a simple Task that is designed to wait for a Message to arrive from an external Participant (relative to the Process). Once the Message has been received, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">scriptTask<a name=\"SGTasks-scriptTask\"> </a></td><td>Script Task</td><td>A Script Task is executed by a business process engine. The modeler or implementer defines a script in a language that the engine can interpret. When the Task is ready to start, the engine will execute the script. When the script is completed, the Task will also be completed.</td></tr><tr><td style=\"white-space:nowrap\">sendTask<a name=\"SGTasks-sendTask\"> </a></td><td>Send Task</td><td>A Send Task is a simple Task that is designed to send a Message to an external Participant (relative to the Process). Once the Message has been sent, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">serviceTask<a name=\"SGTasks-serviceTask\"> </a></td><td>Service Task</td><td>A Service Task is a Task that uses some sort of service, which could be a Web service or an automated application. : The Service Task has exactly one set of inputs and at most one set of outputs.</td></tr><tr><td style=\"white-space:nowrap\">task<a name=\"SGTasks-task\"> </a></td><td>Task</td><td>A Task is an atomic Activity within a Process flow. A Task is used when the work in the Process cannot be broken down to a finer level of detail. Generally, an end-user and/or applications are used to perform the Task when it is executed</td></tr><tr><td style=\"white-space:nowrap\">userTask<a name=\"SGTasks-userTask\"> </a></td><td>User Task</td><td>A User Task is a typical “workflow” Task where a human performer performs the Task with the assistance of a software application and is scheduled through a task list manager of some sort.</td></tr></table></div><div xml:lang=\"fr\" lang=\"fr\"><hr/><p><b>French</b></p><hr/><p class=\"res-header-id\"><b>Narratif généré : CodeSystem SGTasks</b></p><a name=\"fr-SGTasks\"> </a><a name=\"fr-hcSGTasks\"> </a><p>This case-insensitive code system <code>http://smart.who.int/base/CodeSystem/SGTasks</code> defines the following codes:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Affichage</b></td><td><b>Définition</b></td></tr><tr><td style=\"white-space:nowrap\">businessRuleTask<a name=\"fr-SGTasks-businessRuleTask\"> </a></td><td>Business Rule Task</td><td>A Business Rule Task provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide.</td></tr><tr><td style=\"white-space:nowrap\">manualTask<a name=\"fr-SGTasks-manualTask\"> </a></td><td>Manual Task</td><td>A Manual Task is a Task that is expected to be performed without the aid of any business process execution engine or any application. An example of this could be a telephone technician installing a telephone at a customer location.</td></tr><tr><td style=\"white-space:nowrap\">receiveTask<a name=\"fr-SGTasks-receiveTask\"> </a></td><td>Receive Task</td><td>A Receive Task is a simple Task that is designed to wait for a Message to arrive from an external Participant (relative to the Process). Once the Message has been received, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">scriptTask<a name=\"fr-SGTasks-scriptTask\"> </a></td><td>Script Task</td><td>A Script Task is executed by a business process engine. The modeler or implementer defines a script in a language that the engine can interpret. When the Task is ready to start, the engine will execute the script. When the script is completed, the Task will also be completed.</td></tr><tr><td style=\"white-space:nowrap\">sendTask<a name=\"fr-SGTasks-sendTask\"> </a></td><td>Send Task</td><td>A Send Task is a simple Task that is designed to send a Message to an external Participant (relative to the Process). Once the Message has been sent, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">serviceTask<a name=\"fr-SGTasks-serviceTask\"> </a></td><td>Service Task</td><td>A Service Task is a Task that uses some sort of service, which could be a Web service or an automated application. : The Service Task has exactly one set of inputs and at most one set of outputs.</td></tr><tr><td style=\"white-space:nowrap\">task<a name=\"fr-SGTasks-task\"> </a></td><td>Task</td><td>A Task is an atomic Activity within a Process flow. A Task is used when the work in the Process cannot be broken down to a finer level of detail. Generally, an end-user and/or applications are used to perform the Task when it is executed</td></tr><tr><td style=\"white-space:nowrap\">userTask<a name=\"fr-SGTasks-userTask\"> </a></td><td>User Task</td><td>A User Task is a typical “workflow” Task where a human performer performs the Task with the assistance of a software application and is scheduled through a task list manager of some sort.</td></tr></table></div><div xml:lang=\"ar\" lang=\"ar\"><hr/><p><b>Arabic</b></p><hr/><p class=\"res-header-id\"><b>السرد المُنشأ: CodeSystem SGTasks</b></p><a name=\"ar-SGTasks\"> </a><a name=\"ar-hcSGTasks\"> </a><p>يُعرّف هذا case-insensitive نظام الشيفرة <code>http://smart.who.int/base/CodeSystem/SGTasks</code> الرمز التالي<f test=\"code-count != 1\">s</f>:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>الكود</b></td><td><b>العرض</b></td><td><b>التعريف</b></td></tr><tr><td style=\"white-space:nowrap\">businessRuleTask<a name=\"ar-SGTasks-businessRuleTask\"> </a></td><td>Business Rule Task</td><td>A Business Rule Task provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide.</td></tr><tr><td style=\"white-space:nowrap\">manualTask<a name=\"ar-SGTasks-manualTask\"> </a></td><td>Manual Task</td><td>A Manual Task is a Task that is expected to be performed without the aid of any business process execution engine or any application. An example of this could be a telephone technician installing a telephone at a customer location.</td></tr><tr><td style=\"white-space:nowrap\">receiveTask<a name=\"ar-SGTasks-receiveTask\"> </a></td><td>Receive Task</td><td>A Receive Task is a simple Task that is designed to wait for a Message to arrive from an external Participant (relative to the Process). Once the Message has been received, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">scriptTask<a name=\"ar-SGTasks-scriptTask\"> </a></td><td>Script Task</td><td>A Script Task is executed by a business process engine. The modeler or implementer defines a script in a language that the engine can interpret. When the Task is ready to start, the engine will execute the script. When the script is completed, the Task will also be completed.</td></tr><tr><td style=\"white-space:nowrap\">sendTask<a name=\"ar-SGTasks-sendTask\"> </a></td><td>Send Task</td><td>A Send Task is a simple Task that is designed to send a Message to an external Participant (relative to the Process). Once the Message has been sent, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">serviceTask<a name=\"ar-SGTasks-serviceTask\"> </a></td><td>Service Task</td><td>A Service Task is a Task that uses some sort of service, which could be a Web service or an automated application. : The Service Task has exactly one set of inputs and at most one set of outputs.</td></tr><tr><td style=\"white-space:nowrap\">task<a name=\"ar-SGTasks-task\"> </a></td><td>Task</td><td>A Task is an atomic Activity within a Process flow. A Task is used when the work in the Process cannot be broken down to a finer level of detail. Generally, an end-user and/or applications are used to perform the Task when it is executed</td></tr><tr><td style=\"white-space:nowrap\">userTask<a name=\"ar-SGTasks-userTask\"> </a></td><td>User Task</td><td>A User Task is a typical “workflow” Task where a human performer performs the Task with the assistance of a software application and is scheduled through a task list manager of some sort.</td></tr></table></div><div xml:lang=\"zh\" lang=\"zh\"><hr/><p><b>Chinese</b></p><hr/><p class=\"res-header-id\"><b>Generated Narrative: 代码系统 SGTasks</b></p><a name=\"zh-SGTasks\"> </a><a name=\"zh-hcSGTasks\"> </a><p>This case-insensitive code system <code>http://smart.who.int/base/CodeSystem/SGTasks</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\">businessRuleTask<a name=\"zh-SGTasks-businessRuleTask\"> </a></td><td>Business Rule Task</td><td>A Business Rule Task provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide.</td></tr><tr><td style=\"white-space:nowrap\">manualTask<a name=\"zh-SGTasks-manualTask\"> </a></td><td>Manual Task</td><td>A Manual Task is a Task that is expected to be performed without the aid of any business process execution engine or any application. An example of this could be a telephone technician installing a telephone at a customer location.</td></tr><tr><td style=\"white-space:nowrap\">receiveTask<a name=\"zh-SGTasks-receiveTask\"> </a></td><td>Receive Task</td><td>A Receive Task is a simple Task that is designed to wait for a Message to arrive from an external Participant (relative to the Process). Once the Message has been received, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">scriptTask<a name=\"zh-SGTasks-scriptTask\"> </a></td><td>Script Task</td><td>A Script Task is executed by a business process engine. The modeler or implementer defines a script in a language that the engine can interpret. When the Task is ready to start, the engine will execute the script. When the script is completed, the Task will also be completed.</td></tr><tr><td style=\"white-space:nowrap\">sendTask<a name=\"zh-SGTasks-sendTask\"> </a></td><td>Send Task</td><td>A Send Task is a simple Task that is designed to send a Message to an external Participant (relative to the Process). Once the Message has been sent, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">serviceTask<a name=\"zh-SGTasks-serviceTask\"> </a></td><td>Service Task</td><td>A Service Task is a Task that uses some sort of service, which could be a Web service or an automated application. : The Service Task has exactly one set of inputs and at most one set of outputs.</td></tr><tr><td style=\"white-space:nowrap\">task<a name=\"zh-SGTasks-task\"> </a></td><td>Task</td><td>A Task is an atomic Activity within a Process flow. A Task is used when the work in the Process cannot be broken down to a finer level of detail. Generally, an end-user and/or applications are used to perform the Task when it is executed</td></tr><tr><td style=\"white-space:nowrap\">userTask<a name=\"zh-SGTasks-userTask\"> </a></td><td>User Task</td><td>A User Task is a typical “workflow” Task where a human performer performs the Task with the assistance of a software application and is scheduled through a task list manager of some sort.</td></tr></table></div><div xml:lang=\"ru\" lang=\"ru\"><hr/><p><b>Russian</b></p><hr/><p class=\"res-header-id\"><b>Сгенерированный нарратив: CodeSystem SGTasks</b></p><a name=\"ru-SGTasks\"> </a><a name=\"ru-hcSGTasks\"> </a><p>Данная система кодов <code>http://smart.who.int/base/CodeSystem/SGTasks</code> case-insensitive определяет следующие коды:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>Код</b></td><td><b>Отображение</b></td><td><b>Определение</b></td></tr><tr><td style=\"white-space:nowrap\">businessRuleTask<a name=\"ru-SGTasks-businessRuleTask\"> </a></td><td>Business Rule Task</td><td>A Business Rule Task provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide.</td></tr><tr><td style=\"white-space:nowrap\">manualTask<a name=\"ru-SGTasks-manualTask\"> </a></td><td>Manual Task</td><td>A Manual Task is a Task that is expected to be performed without the aid of any business process execution engine or any application. An example of this could be a telephone technician installing a telephone at a customer location.</td></tr><tr><td style=\"white-space:nowrap\">receiveTask<a name=\"ru-SGTasks-receiveTask\"> </a></td><td>Receive Task</td><td>A Receive Task is a simple Task that is designed to wait for a Message to arrive from an external Participant (relative to the Process). Once the Message has been received, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">scriptTask<a name=\"ru-SGTasks-scriptTask\"> </a></td><td>Script Task</td><td>A Script Task is executed by a business process engine. The modeler or implementer defines a script in a language that the engine can interpret. When the Task is ready to start, the engine will execute the script. When the script is completed, the Task will also be completed.</td></tr><tr><td style=\"white-space:nowrap\">sendTask<a name=\"ru-SGTasks-sendTask\"> </a></td><td>Send Task</td><td>A Send Task is a simple Task that is designed to send a Message to an external Participant (relative to the Process). Once the Message has been sent, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">serviceTask<a name=\"ru-SGTasks-serviceTask\"> </a></td><td>Service Task</td><td>A Service Task is a Task that uses some sort of service, which could be a Web service or an automated application. : The Service Task has exactly one set of inputs and at most one set of outputs.</td></tr><tr><td style=\"white-space:nowrap\">task<a name=\"ru-SGTasks-task\"> </a></td><td>Task</td><td>A Task is an atomic Activity within a Process flow. A Task is used when the work in the Process cannot be broken down to a finer level of detail. Generally, an end-user and/or applications are used to perform the Task when it is executed</td></tr><tr><td style=\"white-space:nowrap\">userTask<a name=\"ru-SGTasks-userTask\"> </a></td><td>User Task</td><td>A User Task is a typical “workflow” Task where a human performer performs the Task with the assistance of a software application and is scheduled through a task list manager of some sort.</td></tr></table></div><div xml:lang=\"es\" lang=\"es\"><hr/><p><b>Spanish</b></p><hr/><p class=\"res-header-id\"><b>Generated Narrative: SistemaDeCodigos SGTasks</b></p><a name=\"es-SGTasks\"> </a><a name=\"es-hcSGTasks\"> </a><p>This case-insensitive code system <code>http://smart.who.int/base/CodeSystem/SGTasks</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\">businessRuleTask<a name=\"es-SGTasks-businessRuleTask\"> </a></td><td>Business Rule Task</td><td>A Business Rule Task provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide.</td></tr><tr><td style=\"white-space:nowrap\">manualTask<a name=\"es-SGTasks-manualTask\"> </a></td><td>Manual Task</td><td>A Manual Task is a Task that is expected to be performed without the aid of any business process execution engine or any application. An example of this could be a telephone technician installing a telephone at a customer location.</td></tr><tr><td style=\"white-space:nowrap\">receiveTask<a name=\"es-SGTasks-receiveTask\"> </a></td><td>Receive Task</td><td>A Receive Task is a simple Task that is designed to wait for a Message to arrive from an external Participant (relative to the Process). Once the Message has been received, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">scriptTask<a name=\"es-SGTasks-scriptTask\"> </a></td><td>Script Task</td><td>A Script Task is executed by a business process engine. The modeler or implementer defines a script in a language that the engine can interpret. When the Task is ready to start, the engine will execute the script. When the script is completed, the Task will also be completed.</td></tr><tr><td style=\"white-space:nowrap\">sendTask<a name=\"es-SGTasks-sendTask\"> </a></td><td>Send Task</td><td>A Send Task is a simple Task that is designed to send a Message to an external Participant (relative to the Process). Once the Message has been sent, the Task is completed.</td></tr><tr><td style=\"white-space:nowrap\">serviceTask<a name=\"es-SGTasks-serviceTask\"> </a></td><td>Service Task</td><td>A Service Task is a Task that uses some sort of service, which could be a Web service or an automated application. : The Service Task has exactly one set of inputs and at most one set of outputs.</td></tr><tr><td style=\"white-space:nowrap\">task<a name=\"es-SGTasks-task\"> </a></td><td>Task</td><td>A Task is an atomic Activity within a Process flow. A Task is used when the work in the Process cannot be broken down to a finer level of detail. Generally, an end-user and/or applications are used to perform the Task when it is executed</td></tr><tr><td style=\"white-space:nowrap\">userTask<a name=\"es-SGTasks-userTask\"> </a></td><td>User Task</td><td>A User Task is a typical “workflow” Task where a human performer performs the Task with the assistance of a software application and is scheduled through a task list manager of some sort.</td></tr></table></div></div>" ] ; fhir:CodeSystem.url [ fhir:value "http://smart.who.int/base/CodeSystem/SGTasks"] ; fhir:CodeSystem.version [ fhir:value "0.3.0"] ; fhir:CodeSystem.name [ fhir:value "SGTasks"] ; fhir:CodeSystem.title [ fhir:value "SMART Guidelines Tasks"] ; fhir:CodeSystem.status [ fhir:value "active"] ; fhir:CodeSystem.experimental [ fhir:value "true"^^xsd:boolean] ; fhir:CodeSystem.date [ fhir:value "2026-08-26T08:25:07+00:00"^^xsd:dateTime] ; fhir:CodeSystem.publisher [ fhir:value "WHO"] ; fhir:CodeSystem.contact [ fhir:index 0 ; fhir:ContactDetail.name [ fhir:value "WHO" ] ; fhir:ContactDetail.telecom [ fhir:index 0 ; fhir:ContactPoint.system [ fhir:value "url" ] ; fhir:ContactPoint.value [ fhir:value "http://who.int" ] ] ] ; fhir:CodeSystem.description [ fhir:value "CodeSystem for SMART Guidelines tasks which are specializations of the Business Process Modeling Notatiton (BPMN) tasks, which are included in this codesystem\n\nSee [BPMN Spectification](https://www.omg.org/spec/BPMN) for more info. The descriptions were adapted from the [normative human readable documentation](https://www.omg.org/spec/BPMN/2.0.2/PDF)."] ; fhir:CodeSystem.caseSensitive [ fhir:value "false"^^xsd:boolean] ; fhir:CodeSystem.content [ fhir:value "complete"] ; fhir:CodeSystem.count [ fhir:value "8"^^xsd:nonNegativeInteger] ; fhir:CodeSystem.concept [ fhir:index 0 ; fhir:CodeSystem.concept.code [ fhir:value "businessRuleTask" ] ; fhir:CodeSystem.concept.display [ fhir:value "Business Rule Task" ] ; fhir:CodeSystem.concept.definition [ fhir:value "A Business Rule Task provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide." ] ], [ fhir:index 1 ; fhir:CodeSystem.concept.code [ fhir:value "manualTask" ] ; fhir:CodeSystem.concept.display [ fhir:value "Manual Task" ] ; fhir:CodeSystem.concept.definition [ fhir:value "A Manual Task is a Task that is expected to be performed without the aid of any business process execution engine or any application. An example of this could be a telephone technician installing a telephone at a customer location." ] ], [ fhir:index 2 ; fhir:CodeSystem.concept.code [ fhir:value "receiveTask" ] ; fhir:CodeSystem.concept.display [ fhir:value "Receive Task" ] ; fhir:CodeSystem.concept.definition [ fhir:value "A Receive Task is a simple Task that is designed to wait for a Message to arrive from an external Participant (relative to the Process). Once the Message has been received, the Task is completed." ] ], [ fhir:index 3 ; fhir:CodeSystem.concept.code [ fhir:value "scriptTask" ] ; fhir:CodeSystem.concept.display [ fhir:value "Script Task" ] ; fhir:CodeSystem.concept.definition [ fhir:value "A Script Task is executed by a business process engine. The modeler or implementer defines a script in a language that the engine can interpret. When the Task is ready to start, the engine will execute the script. When the script is completed, the Task will also be completed." ] ], [ fhir:index 4 ; fhir:CodeSystem.concept.code [ fhir:value "sendTask" ] ; fhir:CodeSystem.concept.display [ fhir:value "Send Task" ] ; fhir:CodeSystem.concept.definition [ fhir:value "A Send Task is a simple Task that is designed to send a Message to an external Participant (relative to the Process). Once the Message has been sent, the Task is completed." ] ], [ fhir:index 5 ; fhir:CodeSystem.concept.code [ fhir:value "serviceTask" ] ; fhir:CodeSystem.concept.display [ fhir:value "Service Task" ] ; fhir:CodeSystem.concept.definition [ fhir:value "A Service Task is a Task that uses some sort of service, which could be a Web service or an automated application. : The Service Task has exactly one set of inputs and at most one set of outputs." ] ], [ fhir:index 6 ; fhir:CodeSystem.concept.code [ fhir:value "task" ] ; fhir:CodeSystem.concept.display [ fhir:value "Task" ] ; fhir:CodeSystem.concept.definition [ fhir:value "A Task is an atomic Activity within a Process flow. A Task is used when the work in the Process cannot be broken down to a finer level of detail. Generally, an end-user and/or applications are used to perform the Task when it is executed" ] ], [ fhir:index 7 ; fhir:CodeSystem.concept.code [ fhir:value "userTask" ] ; fhir:CodeSystem.concept.display [ fhir:value "User Task" ] ; fhir:CodeSystem.concept.definition [ fhir:value "A User Task is a typical “workflow” Task where a human performer performs the Task with the assistance of a software application and is scheduled through a task list manager of some sort." ] ] . # - ontology header ------------------------------------------------------------ <http://hl7.org/fhir/CodeSystem/SGTasks.ttl> a owl:Ontology ; owl:imports fhir:fhir.ttl ; owl:versionIRI <http://build.fhir.org/CodeSystem/SGTasks.ttl> .
IG © 2023+ WHO. Package smart.who.int.base#0.3.0 based on FHIR 4.0.1. Generated 2026-08-26
Links: Table of Contents |
QA Report
| Version History | License