The minimum expectations for ActivityDefinition resources used in SMART Guidelines

Structure and constraints for ActorDefinition resources used in SMART Guidelines

Structure and constraints for Business Processes represented in SMART Guidelines

Defines the minimum expectations for CodeSystem resources used in SMART Guidelines

Defines the minimum expectations for ConceptMap resources used in SMART Guidelines

The minimum expectations for GraphDefinition resources used in SMART Guidelines

Structure and constraints for Group Definitions represented in SMART Guidelines

Defines the minimum expectations for ImplementationGuide resources used in SMART Guidelines

Defines the minimum expectations for Library resources used in SMART Guidelines

Defines the minimum expectations for Logical Models used in SMART Guidelines

Defines the minimum expectations for Measure resources used in SMART Guidelines

Defines the minimum expectations for PlanDefinition resources used in SMART Guidelines

Defines the minimum expectations for Questionnaire resources used in SMART Guidelines

Defines the minimum expectations for StructureDefinition resources used in SMART Guidelines

Defines the minimum expectations for StructureMap resources used in SMART Guidelines

Structure and constraints for TransactionDefinition resources used in SMART Guidelines

Defines the minimum expectations for ValueSet resources used in SMART Guidelines

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.

Source reference for Business Process Workflow - exactly one of the following must be provided:

• url (url data type): URL to retrieve BusinessProcessWorkflow definition from input/ or external source
• canonical (canonical data type): Canonical URI pointing to the BusinessProcessWorkflow definition
• instance: Inline BusinessProcessWorkflow instance data

Logical Model for representing Core Data Elements from a DAK. A core data element can be one of: a ValueSet, a CodeSystem, a ConceptMap, or a Logical Model adherent to SGLogicalModel. This is the ONE EXCEPTION to allowing FHIR R4 models into the DAK LMs.

Source reference for Core Data Element - exactly one of the following must be provided:

• url (url data type): URL to retrieve CoreDataElement definition from input/ or external source
• canonical (canonical data type): Canonical URI pointing to the CoreDataElement definition
• instance: Inline CoreDataElement instance data

Source reference for Decision Support Logic - exactly one of the following must be provided:

• url (url data type): URL to retrieve DecisionSupportLogic definition from input/ or external source
• canonical (canonical data type): Canonical URI pointing to the DecisionSupportLogic definition
• instance: Inline DecisionSupportLogic instance data

Logical Model for representing Decision-Support Logic from a DAK. Decision-support logic and algorithms to support appropriate service delivery in accordance with WHO clinical, public health and data use guidelines.

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

Logical Model representing Dublin Core metadata elements as defined at https://www.dublincore.org/specifications/dublin-core/dcmi-terms/

Logical Model for representing functional requirement from a DAK

Logical Model for representing Functional and Non-Functional Requirements from a DAK. A high-level list of core functions and capabilities that the system must have to meet the end users' needs.

Logical Model for representing Generic Personas from a DAK. Depiction of the human and system actors. Human actors are end users, supervisors and related stakeholders who would be interacting with the digital system or involved in the clinical care, public health or health system pathway.

Source reference for Generic Persona - exactly one of the following must be provided:

• url (url data type): URL to retrieve GenericPersona definition from input/ or external source
• canonical (canonical data type): Canonical URI pointing to the GenericPersona definition
• instance: Inline GenericPersona instance data

Source reference for Health Interventions - exactly one of the following must be provided:

• url (url data type): URL to retrieve HealthInterventions definition from input/ or external source
• canonical (canonical data type): Canonical URI pointing to the HealthInterventions definition
• instance: Inline HealthInterventions instance data

Logical Model for representing Health Interventions and Recommendations from a DAK. Overview of the health interventions and WHO, regional or national recommendations included within the DAK.

Logical Model for representing non-functional requirement from a DAK

Logical Model for representing Personas from a DAK

Logical Model for representing Program Indicators from a DAK. Core set of indicators that need to be aggregated for decision-making, performance metrics and subnational and national reporting.

Source reference for Program Indicator - exactly one of the following must be provided:

• url (url data type): URL to retrieve ProgramIndicator definition from input/ or external source
• canonical (canonical data type): Canonical URI pointing to the ProgramIndicator definition
• instance: Inline ProgramIndicator instance data

Source reference for Requirements - exactly one of the following must be provided:

• url (url data type): URL to retrieve Requirements definition from input/ or external source
• canonical (canonical data type): Canonical URI pointing to the Requirements definition
• instance: Inline Requirements instance data

Logical model defining the structure of sushi-config.yaml files used for FHIR Implementation Guide configuration. This model captures the essential metadata and configuration parameters needed for IG publishing.

Logical Model for representing Test Scenarios from a DAK. A set of test scenarios to validate an implementation of the DAK.

Source reference for Test Scenario - exactly one of the following must be provided:

• url (url data type): URL to retrieve TestScenario definition from input/ or external source
• canonical (canonical data type): Canonical URI pointing to the TestScenario definition
• instance: Inline TestScenario instance data

Logical Model for representing User Scenarios from a DAK. Narratives that describe how the different personas may interact with each other.

Source reference for User Scenario - exactly one of the following must be provided:

• url (url data type): URL to retrieve UserScenario definition from input/ or external source
• canonical (canonical data type): Canonical URI pointing to the UserScenario definition
• instance: Inline UserScenario instance data

Auto-generated questionnaire for decision table DAK.DT.IMMZ.D2.DT.BCG

Provide communication

Defines the minimum expectations for PlanDefinition resources used in SMART Guidelines which are derived from DAK Decision Tables

Smart Guidelines Requirements

Smart Guidelines link identifier extension

Markdown extension

Smart Guidelines Actor Reference extension

Smart Guidelines Documentation extension

Smart Guidelines markdown extension

Smart Guidelines Requirements extension

Smart Guidelines (required) string extension for use in a complex extension

Extension to reference SMART Guidelines task type

Smart Guidelines extension to support structured User Stories (As a <Actor> I want to <capability> so that <benfit>) extension

Smart Guidelines code extension

Indicates that if the conditions for this requirement are satisified, then that it should be viewed as satisifying the referenced requirement.

Value Set for Classification of Digital Health Interventions v1. Autogenerated from DAK artifacts

Value Set for Classification of Digital Health System Categories v1. Autogenerated from DAK artifacts

Value set of core data element types

Extensible value set of ISCO-08 codes for persona classification

Value Set for Smart Guidelines Documentation Decision Table Actions

Value Set for Smart Guidelines Documentation Section to autogenerate documentation from artifacts

Value Set for Smart Guidelines Persona Section to autogenerate documentation from artifacts

CodeSystem for Classification of Digital Health Interventions v1. Autogenerated from DAK artifacts

CodeSystem for Classification of Digital Health System Categories v1. Autogenerated from DAK artifacts

CodeSystem for Core Data Element types - defines the type of FHIR resource that a Core Data Element references.

ISCO-08 codes from the International Labour Organization official classification

CodeSystem for SMART Guidelines Persona Types

CodeSystem for SMART Guidelines tasks which are specializations of the Business Process Modeling Notatiton (BPMN) tasks, which are included in this codesystem

See BPMN Spectification for more info. The descriptions were adapted from the normative human readable documentation.

CodeSystem for Smart Guidelines Documentation Actions for Decision Tables"

CodeSystem for Smart Guidelines Documentation Section to autogenerate documentation from artifacts

Mapping to represent hierarchy within Hierarchy of the Classification of Digital Health Interventions v1.