From e5efa3d941d97b8b3b4e1ec2d57c0313467535b4 Mon Sep 17 00:00:00 2001
From: ssi-db <61754411+ssi-db@users.noreply.github.com>
Date: Wed, 9 Oct 2024 11:46:09 -0700
Subject: [PATCH] FHIR-47385 Clarify Task introduction text

---
 source/task/structuredefinition-Task.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/task/structuredefinition-Task.xml b/source/task/structuredefinition-Task.xml
index d2809d8b5c8..2c41bfd4a8e 100644
--- a/source/task/structuredefinition-Task.xml
+++ b/source/task/structuredefinition-Task.xml
@@ -77,7 +77,7 @@
     <element id="Task">
       <path value="Task"/>
       <short value="A task to be performed"/>
-      <definition value="A task to be performed as a part of a workflow and the related informations like inputs, outputs and execution progress. While very simple workflows can be implemented with Request alone, most workflows would require a Task (explicit or contained) as a means to track the execution data (i.e. inputs, outputs, status). Please refer to the workflow page for more details."/>
+      <definition value="A task to be performed as a part of a workflow and the related informations like inputs, outputs and execution progress. While very simple workflows can be implemented with [[[Request]]] alone, most workflows would require a Task (explicit or contained) as a means to track the execution progress (i.e. inputs, outputs, status). Please refer to [Fulfillment/Execution](request.html#fulfillment)."/>
       <min value="0"/>
       <max value="*"/>
       <constraint>