Logical Model for representing a complete Digital Adaptation Kit (DAK) with metadata and all 9 DAK components

Identifier for the DAK (e.g., smart.who.int.base)

Short name for the DAK (e.g., Base)

Full title of the DAK (e.g., SMART Base)

Description of the DAK - either Markdown content or a URI to a Markdown file (absolute or relative to repository root)

Version of the DAK

Publication status of the DAK

Canonical URL for the DAK (e.g., http://smart.who.int/base)

License under which the DAK is published

Year or year range for copyright

Organization responsible for publishing the DAK

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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.

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).

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.

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.

Name of the publishing organization

URL of the publishing organization

Overview of the health interventions and WHO, regional or national recommendations included within the DAK

Depiction of the human and system actors

Narratives that describe how the different personas may interact with each other

Business processes and workflows for achieving health programme objectives

Data elements required throughout the different points of a workflow

Decision-support logic and algorithms to support appropriate service delivery

Core set of indicators for decision-making, performance metrics and reporting

High-level list of core functions and capabilities that the system must have

Set of test scenarios to validate an implementation of the DAK

Logical Model for representing a complete Digital Adaptation Kit (DAK) with metadata and all 9 DAK components

Identifier for the DAK (e.g., smart.who.int.base)

Short name for the DAK (e.g., Base)

Full title of the DAK (e.g., SMART Base)

Description of the DAK - either Markdown content or a URI to a Markdown file (absolute or relative to repository root)

Version of the DAK

Publication status of the DAK

Canonical URL for the DAK (e.g., http://smart.who.int/base)

License under which the DAK is published

Year or year range for copyright

Organization responsible for publishing the DAK

Name of the publishing organization

URL of the publishing organization

Overview of the health interventions and WHO, regional or national recommendations included within the DAK

Depiction of the human and system actors

Narratives that describe how the different personas may interact with each other

Business processes and workflows for achieving health programme objectives

Data elements required throughout the different points of a workflow

Decision-support logic and algorithms to support appropriate service delivery

Core set of indicators for decision-making, performance metrics and reporting

High-level list of core functions and capabilities that the system must have

Set of test scenarios to validate an implementation of the DAK

Logical Model for representing a complete Digital Adaptation Kit (DAK) with metadata and all 9 DAK components

Identifier for the DAK (e.g., smart.who.int.base)

Short name for the DAK (e.g., Base)

Full title of the DAK (e.g., SMART Base)

Description of the DAK - either Markdown content or a URI to a Markdown file (absolute or relative to repository root)

Version of the DAK

Publication status of the DAK

Canonical URL for the DAK (e.g., http://smart.who.int/base)

License under which the DAK is published

Year or year range for copyright

Organization responsible for publishing the DAK

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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.

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).

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.

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.

Name of the publishing organization

URL of the publishing organization

Overview of the health interventions and WHO, regional or national recommendations included within the DAK

Depiction of the human and system actors

Narratives that describe how the different personas may interact with each other

Business processes and workflows for achieving health programme objectives

Data elements required throughout the different points of a workflow

Decision-support logic and algorithms to support appropriate service delivery

Core set of indicators for decision-making, performance metrics and reporting

High-level list of core functions and capabilities that the system must have

Set of test scenarios to validate an implementation of the DAK