Reusable definition of a launchable digital (eHealth) activity that can be requested for a patient in MedMij and/or Koppeltaal workflows. It describes the clinical intent and (when applicable) the technical launch details (e.g., endpoint) so that systems can create patient-specific workflow Tasks that reference this definition.

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.

Endpoint that exposes the launchable activity.

Business identifier that uniquely identifies this ActivityDefinition instance within or across systems.

Version identifier for this provider module, used to distinguish different published revisions.

Name for this activity definition (computer friendly)

Human-friendly title for display and selection.

Status of the provider module (for example draft, active, retired). Indicates whether it may be used in workflows.

Organization responsible for publishing this activity definition. The publisher owns the content and/or functionality and manages versioning.

Human-readable explanation of what the activity is and how it supports the care process. This description is reusable and not patient-specific.

Guidance on how this activity definition should be used in clinical workflows. In the MedMij use case, this text is intended for the healthcare professional who is selecting and assigning the activity to the patient.

Recommended timing for the activity when applied in a workflow (e.g., once, recurring, over a period). Patient-specific scheduling belongs in ServiceRequest resources.

Reusable definition of a launchable digital (eHealth) activity that can be requested for a patient in MedMij and/or Koppeltaal workflows. It describes the clinical intent and (when applicable) the technical launch details (e.g., endpoint) so that systems can create patient-specific workflow Tasks that reference this definition.

Endpoint that exposes the launchable activity.

Business identifier that uniquely identifies this ActivityDefinition instance within or across systems.

Version identifier for this provider module, used to distinguish different published revisions.

Name for this activity definition (computer friendly)

Human-friendly title for display and selection.

Status of the provider module (for example draft, active, retired). Indicates whether it may be used in workflows.

Organization responsible for publishing this activity definition. The publisher owns the content and/or functionality and manages versioning.

Human-readable explanation of what the activity is and how it supports the care process. This description is reusable and not patient-specific.

Guidance on how this activity definition should be used in clinical workflows. In the MedMij use case, this text is intended for the healthcare professional who is selecting and assigning the activity to the patient.

Recommended timing for the activity when applied in a workflow (e.g., once, recurring, over a period). Patient-specific scheduling belongs in ServiceRequest resources.

Reusable definition of a launchable digital (eHealth) activity that can be requested for a patient in MedMij and/or Koppeltaal workflows. It describes the clinical intent and (when applicable) the technical launch details (e.g., endpoint) so that systems can create patient-specific workflow Tasks that reference this definition.

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.

Endpoint that exposes the launchable activity.

Business identifier that uniquely identifies this ActivityDefinition instance within or across systems.

Version identifier for this provider module, used to distinguish different published revisions.

Name for this activity definition (computer friendly)

Human-friendly title for display and selection.

Status of the provider module (for example draft, active, retired). Indicates whether it may be used in workflows.

Organization responsible for publishing this activity definition. The publisher owns the content and/or functionality and manages versioning.

Human-readable explanation of what the activity is and how it supports the care process. This description is reusable and not patient-specific.

Guidance on how this activity definition should be used in clinical workflows. In the MedMij use case, this text is intended for the healthcare professional who is selecting and assigning the activity to the patient.

Recommended timing for the activity when applied in a workflow (e.g., once, recurring, over a period). Patient-specific scheduling belongs in ServiceRequest resources.