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/ and changes regularly. See the Directory of published versions
| Active as of 2025-09-23 |
Definitions for the BusinessProcessWorkflow logical model.
Guidance on how to interpret the contents of this table can be foundhere
| 0. BusinessProcessWorkflow | |
| Definition | Logical Model for representing Generic Business Processes and Workflows from a DAK. A business process is a set of related activities or tasks performed together to achieve the objectives of the health programme area. |
| Short | Business Process Workflow (DAK) |
| Control | 0..* |
| Is Modifier | false |
| Logical Model | Instances of this logical model are not marked to be the target of a Reference |
| 2. BusinessProcessWorkflow.id | |
| Definition | An identifier for the business process workflow |
| Short | Business Process ID |
| Control | 1..1 |
| Type | id |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 4. BusinessProcessWorkflow.description[x] | |
| Definition | Description of the business process - either Markdown content or a URI to a Markdown file (absolute or relative to repository root) |
| Short | Description |
| Control | 0..1 |
| Type | Choice of: string, uri |
| [x] Note | SeeChoice of Data Typesfor further information about how to use [x] |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 6. BusinessProcessWorkflow.source | |
| Definition | Link to a BPMN file containing the workflow definition. Source URI could be absolute or relative to the root of the DAK |
| Short | Source |
| Control | 1..1 |
| Type | uri |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 8. BusinessProcessWorkflow.scenario | |
| Definition | References to user scenario IDs related to this workflow |
| Short | Scenario |
| Control | 0..* |
| Type | id |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 10. BusinessProcessWorkflow.objectives | |
| Definition | Description of the objectives of the workflow |
| Short | Objectives |
| Control | 1..1 |
| Type | markdown |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 12. BusinessProcessWorkflow.task | |
| Definition | Tasks within the business process workflow |
| Short | Task |
| Control | 0..* |
| Type | BackboneElement |
| Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) |
| 14. BusinessProcessWorkflow.task.id | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
| Short | Unique id for inter-element referencing |
| Control | 0..1 |
| Type | string |
| Is Modifier | false |
| XML Format | In the XML format, this property is represented as an attribute. |
| Summary | false |
| 16. BusinessProcessWorkflow.task.extension | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
| Short | Additional content defined by implementations |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
| Control | 0..* |
| Type | Extension |
| Is Modifier | false |
| Summary | false |
| Alternate Names | extensions, user content |
| Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists()) |
| Slicing | This element introduces a set of slices on BusinessProcessWorkflow.task.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators: |
| 18. BusinessProcessWorkflow.task.modifierExtension | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
| Short | Extensions that cannot be ignored even if unrecognized |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
| Control | 0..* |
| Type | Extension |
| Is Modifier | true because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them |
| Summary | true |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
| Alternate Names | extensions, user content, modifiers |
| Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists()) |
| 20. BusinessProcessWorkflow.task.identifier | |
| Definition | Identifier for the task |
| Short | Task ID |
| Note | This is a business identifier, not a resource identifier (see discussion) |
| Control | 1..1 |
| Type | id |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 22. BusinessProcessWorkflow.task.name | |
| Definition | Name of the task |
| Short | Task Name |
| Control | 1..1 |
| Type | string |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 24. BusinessProcessWorkflow.task.description | |
| Definition | Description of what the task involves |
| Short | Task Description |
| Control | 1..1 |
| Type | string |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
Guidance on how to interpret the contents of this table can be foundhere
| 0. BusinessProcessWorkflow | |
| Definition | Logical Model for representing Generic Business Processes and Workflows from a DAK. A business process is a set of related activities or tasks performed together to achieve the objectives of the health programme area. |
| Short | Business Process Workflow (DAK) |
| Logical Model | Instances of this logical model are not marked to be the target of a Reference |
| 2. BusinessProcessWorkflow.id | |
| Definition | An identifier for the business process workflow |
| Short | Business Process ID |
| Control | 1..1 |
| Type | id |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 4. BusinessProcessWorkflow.description[x] | |
| Definition | Description of the business process - either Markdown content or a URI to a Markdown file (absolute or relative to repository root) |
| Short | Description |
| Control | 0..1 |
| Type | Choice of: string, uri |
| [x] Note | SeeChoice of Data Typesfor further information about how to use [x] |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 6. BusinessProcessWorkflow.source | |
| Definition | Link to a BPMN file containing the workflow definition. Source URI could be absolute or relative to the root of the DAK |
| Short | Source |
| Control | 1..1 |
| Type | uri |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 8. BusinessProcessWorkflow.scenario | |
| Definition | References to user scenario IDs related to this workflow |
| Short | Scenario |
| Control | 0..* |
| Type | id |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 10. BusinessProcessWorkflow.objectives | |
| Definition | Description of the objectives of the workflow |
| Short | Objectives |
| Control | 1..1 |
| Type | markdown |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 12. BusinessProcessWorkflow.task | |
| Definition | Tasks within the business process workflow |
| Short | Task |
| Control | 0..* |
| Type | BackboneElement |
| 14. BusinessProcessWorkflow.task.identifier | |
| Definition | Identifier for the task |
| Short | Task ID |
| Note | This is a business identifier, not a resource identifier (see discussion) |
| Control | 1..1 |
| Type | id |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 16. BusinessProcessWorkflow.task.name | |
| Definition | Name of the task |
| Short | Task Name |
| Control | 1..1 |
| Type | string |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 18. BusinessProcessWorkflow.task.description | |
| Definition | Description of what the task involves |
| Short | Task Description |
| Control | 1..1 |
| Type | string |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
Guidance on how to interpret the contents of this table can be foundhere
| 0. BusinessProcessWorkflow | |
| Definition | Logical Model for representing Generic Business Processes and Workflows from a DAK. A business process is a set of related activities or tasks performed together to achieve the objectives of the health programme area. |
| Short | Business Process Workflow (DAK) |
| Control | 0..* |
| Is Modifier | false |
| Logical Model | Instances of this logical model are not marked to be the target of a Reference |
| 2. BusinessProcessWorkflow.id | |
| Definition | An identifier for the business process workflow |
| Short | Business Process ID |
| Control | 1..1 |
| Type | id |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 4. BusinessProcessWorkflow.description[x] | |
| Definition | Description of the business process - either Markdown content or a URI to a Markdown file (absolute or relative to repository root) |
| Short | Description |
| Control | 0..1 |
| Type | Choice of: string, uri |
| [x] Note | SeeChoice of Data Typesfor further information about how to use [x] |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 6. BusinessProcessWorkflow.source | |
| Definition | Link to a BPMN file containing the workflow definition. Source URI could be absolute or relative to the root of the DAK |
| Short | Source |
| Control | 1..1 |
| Type | uri |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 8. BusinessProcessWorkflow.scenario | |
| Definition | References to user scenario IDs related to this workflow |
| Short | Scenario |
| Control | 0..* |
| Type | id |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 10. BusinessProcessWorkflow.objectives | |
| Definition | Description of the objectives of the workflow |
| Short | Objectives |
| Control | 1..1 |
| Type | markdown |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 12. BusinessProcessWorkflow.task | |
| Definition | Tasks within the business process workflow |
| Short | Task |
| Control | 0..* |
| Type | BackboneElement |
| Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) |
| 14. BusinessProcessWorkflow.task.id | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
| Short | Unique id for inter-element referencing |
| Control | 0..1 |
| Type | string |
| Is Modifier | false |
| XML Format | In the XML format, this property is represented as an attribute. |
| Summary | false |
| 16. BusinessProcessWorkflow.task.extension | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
| Short | Additional content defined by implementations |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
| Control | 0..* |
| Type | Extension |
| Is Modifier | false |
| Summary | false |
| Alternate Names | extensions, user content |
| Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))ext-1: Must have either extensions or value[x], not both ( extension.exists() != value.exists()) |
| Slicing | This element introduces a set of slices on BusinessProcessWorkflow.task.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators: |
| 18. BusinessProcessWorkflow.task.modifierExtension | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
| Short | Extensions that cannot be ignored even if unrecognized |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
| Control | 0..* |
| Type | Extension |
| Is Modifier | true because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them |
| Summary | true |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
| Alternate Names | extensions, user content, modifiers |
| Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))ext-1: Must have either extensions or value[x], not both ( extension.exists() != value.exists()) |
| 20. BusinessProcessWorkflow.task.identifier | |
| Definition | Identifier for the task |
| Short | Task ID |
| Note | This is a business identifier, not a resource identifier (see discussion) |
| Control | 1..1 |
| Type | id |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 22. BusinessProcessWorkflow.task.name | |
| Definition | Name of the task |
| Short | Task Name |
| Control | 1..1 |
| Type | string |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
| 24. BusinessProcessWorkflow.task.description | |
| Definition | Description of what the task involves |
| Short | Task Description |
| Control | 1..1 |
| Type | string |
| Primitive Value | This primitive element may be present, or absent, or replaced by an extension |