SMART Base
0.2.0 - ci-build

SMART Base, published by WHO. This guide is not an authorized publication; it is the continuous build for version 0.2.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/tree/claude/update-readme-build-urls-W2FrH and changes regularly. See the Directory of published versions
Built from commit 9142186c.   Branch: claude/update-readme-build-urls-W2FrH.

: SMART Guidelines Tasks - TTL Representation

Active as of 2026-03-19

Raw ttl | Download

@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

# - resource -------------------------------------------------------------------

 a fhir:CodeSystem ;
  fhir:nodeRole fhir:treeRoot ;
  fhir:id [ fhir:v "SGTasks"] ; # 
  fhir:text [
fhir:status [ fhir:v "generated" ] ;
fhir:div [ fhir:v "<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>"^^rdf:XMLLiteral ]
  ] ; # 
  fhir:url [
fhir:v "http://smart.who.int/base/CodeSystem/SGTasks"^^xsd:anyURI ;
fhir:l <http://smart.who.int/base/CodeSystem/SGTasks>
  ] ; # 
  fhir:version [ fhir:v "0.2.0"] ; # 
  fhir:name [ fhir:v "SGTasks"] ; # 
  fhir:title [ fhir:v "SMART Guidelines Tasks"] ; # 
  fhir:status [ fhir:v "active"] ; # 
  fhir:experimental [ fhir:v true] ; # 
  fhir:date [ fhir:v "2026-03-19T22:19:23+00:00"^^xsd:dateTime] ; # 
  fhir:publisher [ fhir:v "WHO"] ; # 
  fhir:contact ( [
fhir:name [ fhir:v "WHO" ] ;
    ( fhir:telecom [
fhir:system [ fhir:v "url" ] ;
fhir:value [ fhir:v "http://who.int" ]     ] )
  ] ) ; # 
  fhir:description [ fhir:v "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:caseSensitive [ fhir:v false] ; # 
  fhir:content [ fhir:v "complete"] ; # 
  fhir:count [ fhir:v "8"^^xsd:nonNegativeInteger] ; # 
  fhir:concept ( [
fhir:code [ fhir:v "businessRuleTask" ] ;
fhir:display [ fhir:v "Business Rule Task" ] ;
fhir:definition [ fhir:v "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:code [ fhir:v "manualTask" ] ;
fhir:display [ fhir:v "Manual Task" ] ;
fhir:definition [ fhir:v "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:code [ fhir:v "receiveTask" ] ;
fhir:display [ fhir:v "Receive Task" ] ;
fhir:definition [ fhir:v "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:code [ fhir:v "scriptTask" ] ;
fhir:display [ fhir:v "Script Task" ] ;
fhir:definition [ fhir:v "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:code [ fhir:v "sendTask" ] ;
fhir:display [ fhir:v "Send Task" ] ;
fhir:definition [ fhir:v "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:code [ fhir:v "serviceTask" ] ;
fhir:display [ fhir:v "Service Task" ] ;
fhir:definition [ fhir:v "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:code [ fhir:v "task" ] ;
fhir:display [ fhir:v "Task" ] ;
fhir:definition [ fhir:v "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:code [ fhir:v "userTask" ] ;
fhir:display [ fhir:v "User Task" ] ;
fhir:definition [ fhir:v "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." ]
  ] ) . #