Updated to new FHIR Resource versions for API v2

Author: jaboehri

docs/src/process-development/api-v2/dsf/requester-and-recipient.md

@@ -5,20 +5,20 @@ icon: creative
 
 ### Requester and Recipient Elements
 
-Below you will find a set of examples for each Coding used by `requester` and `recipient` elements from the [dsf-extension-process-authorization](https://github.com/datasharingframework/dsf/blob/main/dsf-fhir/dsf-fhir-validation/src/main/resources/fhir/StructureDefinition/dsf-extension-process-authorization-1.0.0.xml). CodeSystems referenced in the examples can be found [here](https://github.com/datasharingframework/dsf/tree/main/dsf-fhir/dsf-fhir-validation/src/main/resources/fhir/CodeSystem). Use this collection as a reference point when creating your own [ActivityDefinitions](../fhir/activitydefinition.md).
+Below you will find a set of examples for each Coding used by `requester` and `recipient` elements from the [dsf-extension-process-authorization](https://github.com/datasharingframework/dsf/blob/main/dsf-fhir/dsf-fhir-validation/src/main/resources/fhir/StructureDefinition/dsf-extension-process-authorization-2.0.0.xml). CodeSystems referenced in the examples can be found [here](https://github.com/datasharingframework/dsf/tree/main/dsf-fhir/dsf-fhir-validation/src/main/resources/fhir/CodeSystem). Use this collection as a reference point when creating your own [ActivityDefinitions](../fhir/activitydefinition.md).
 
 #### Requester
 The `requester` element uses one of the following Codings:
 ```xml
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all-practitioner|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization-practitioner|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role-practitioner|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-all|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-organization|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-parent-organization-role|1.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all-practitioner|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization-practitioner|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role-practitioner|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-all|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-organization|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-parent-organization-role|2.0.0" />
 ```
 
 ##### Local All
@@ -194,9 +194,9 @@ The `requester` element uses one of the following Codings:
 #### Recipient
 The `recipeint` element uses one of the following Codings:
 ```xml
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization|1.0.0" />
-<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role|1.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization|2.0.0" />
+<profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role|2.0.0" />
 ```
 
 ##### Local All

docs/src/process-development/api-v2/guides/creating-activity-definitions.md

@@ -216,19 +216,19 @@ The next slice is `requester`:
             <min value="1" />
             <type>
                 <code value="Coding" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all-practitioner|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization-practitioner|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role-practitioner|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-all|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-organization|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-parent-organization-role|1.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all-practitioner|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization-practitioner|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role-practitioner|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-all|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-organization|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-remote-parent-organization-role|2.0.0" />
             </type>
             <binding>
                 <strength value="required" />
-                <valueSet value="http://dsf.dev/fhir/ValueSet/process-authorization-requester|1.0.0" />
+                <valueSet value="http://dsf.dev/fhir/ValueSet/process-authorization-requester|2.0.0" />
             </binding>
         </element>
      ...
@@ -278,7 +278,7 @@ We now have to look at the elements that are defined in one of the profiles to f
         <max value="1" />
         <type>
             <code value="Extension" />
-            <profile value="http://dsf.dev/fhir/StructureDefinition/extension-process-authorization-organization-practitioner|1.0.0" />
+            <profile value="http://dsf.dev/fhir/StructureDefinition/extension-process-authorization-organization-practitioner|2.0.0" />
         </type>
     </element>
     <element id="Coding.system">
@@ -523,13 +523,13 @@ Now we are back to looking at the [dsf-extension-process-authorization](https://
             <min value="1" />
             <type>
                 <code value="Coding" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization|1.0.0" />
-                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role|1.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-all|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-organization|2.0.0" />
+                <profile value="http://dsf.dev/fhir/StructureDefinition/coding-process-authorization-local-parent-organization-role|2.0.0" />
             </type>
             <binding>
                 <strength value="required" />
-                <valueSet value="http://dsf.dev/fhir/ValueSet/process-authorization-recipient|1.0.0" />
+                <valueSet value="http://dsf.dev/fhir/ValueSet/process-authorization-recipient|2.0.0" />
             </binding>
         </element>
      ...

docs/src/process-development/api-v2/guides/creating-task-resources-based-on-a-definition.md

@@ -27,7 +27,7 @@ Before we start adding any elements listed in Forge's element tree, we have to i
 ```xml
 <Task xmlns="http://hl7.org/fhir">
     <meta>
-        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|1.0"/>
+        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|2.0"/>
     </meta>
 </Task>
 ```
@@ -36,9 +36,9 @@ The first element which can be found in the element tree is the `instantiatesCan
 ```xml
 <Task xmlns="http://hl7.org/fhir">
     <meta>
-        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|1.0"/>
+        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|2.0"/>
     </meta>
-    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|1.0" />
+    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|2.0" />
 </Task>
 ```
 We can continue this process for all primitive elements like these. Just make sure you pay attention to use the correct data type (e.g. proper coding value for elements with `coding` type).
@@ -50,9 +50,9 @@ By now your [Task](../fhir/task.md) resources should look something like this:
 ```xml
 <Task xmlns="http://hl7.org/fhir">
     <meta>
-        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|1.0"/>
+        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|2.0"/>
     </meta>
-    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|1.0" />
+    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|2.0" />
     <status value="requested"/>
     <intent value="order"/>
     <authoredOn value="2024-02-08T10:00:00+00:00" />
@@ -68,9 +68,9 @@ We will start the same way we started with primitive elements, by adding the `re
 ```xml
 <Task xmlns="http://hl7.org/fhir">
     <meta>
-        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|1.0"/>
+        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|2.0"/>
     </meta>
-    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|1.0" />
+    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|2.0" />
     <status value="requested"/>
     <intent value="order"/>
     <authoredOn value="2024-02-08T10:00:00+00:00" />
@@ -84,9 +84,9 @@ Then, we will add primitive elements to `requester` like we did before for `Task
 ```xml
 <Task xmlns="http://hl7.org/fhir">
     <meta>
-        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|1.0"/>
+        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|2.0"/>
     </meta>
-    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|1.0" />
+    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|2.0" />
     <status value="requested"/>
     <intent value="order"/>
     <authoredOn value="2024-02-08T10:00:00+00:00" />
@@ -101,9 +101,9 @@ Next, we will add the `identifier` element and its primitive sub-elements just l
 ```xml
 <Task xmlns="http://hl7.org/fhir">
     <meta>
-        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|1.0"/>
+        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|2.0"/>
     </meta>
-    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|1.0" />
+    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|2.0" />
     <status value="requested"/>
     <intent value="order"/>
     <authoredOn value="2024-02-08T10:00:00+00:00" />
@@ -125,9 +125,9 @@ You should now be able to fill out all elements in your [Task](../fhir/task.md)
 ```xml
 <Task xmlns="http://hl7.org/fhir">
     <meta>
-        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|1.0"/>
+        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|2.0"/>
     </meta>
-    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|1.0" />
+    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|2.0" />
     <status value="requested"/>
     <intent value="order"/>
     <authoredOn value="2024-02-08T10:00:00+00:00" />
@@ -193,9 +193,9 @@ Now you should be able to add all remaining mandatory elements to your [Task](..
 ```xml
 <Task xmlns="http://hl7.org/fhir">
     <meta>
-        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|1.0"/>
+        <profile value="http://dsf.dev/fhir/StructureDefinition/task-start-dic-process|2.0"/>
     </meta>
-    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|1.0" />
+    <instantiatesCanonical value="http://dsf.dev/bpe/Process/dicProcess|2.0" />
     <status value="requested"/>
     <intent value="order"/>
     <authoredOn value="2024-02-08T10:00:00+00:00" />