Update fhir-versioning-policy-and-history-management.md

Author: evachen96

articles/healthcare-apis/fhir/fhir-versioning-policy-and-history-management.md

@@ -71,7 +71,7 @@ Changing the versioning policy, either at a system level or resource level, won'
 > The query parameter _summary=count and _count=0 can be added to _history endpoint to get a count of all versioned resources. This count includes soft deleted resources.
 
 ## Metadata-only updates and versioning
-If the versioning policy is set to either `versioned` or `version-update`, metadata-only updates (changes to FHIR resources that only affect the metadata) increment the resource version, create a new version, and save the old version as a historical record. If you are making metadata-only changes using PUT or PATCH updates, you can use the query parameter _meta-history for PUT and PATCH updates to configure whether or not the old version is saved as a historical record.
+If the versioning policy is set to either `versioned` or `version-update`, metadata-only updates (changes to FHIR resources that only affect the metadata) increment the resource version, create a new version, and save the old version as a historical record. If you are making metadata-only changes using PUT, PATCH, or `$bulk-update`, you can use the query parameter _meta-history for PUT, PATCH, and `$bulk-update` to configure whether or not the old version is saved as a historical record.
 - `_meta-history=true` is set by default. By default, the resource version is incremented, a new version is created, and the old version is saved as a historical record. The lastUpdated timestamp is updated to reflect the change.
 - `_meta-history=false` The `_meta-history` parameter can be configured to `false`. This means that the resource version is incremented, a new version is created, but the old version is not saved as a historical record. The lastUpdated timestamp is also still updated to reflect the change. This configuration can be used to help reduce data storage when making metadata-only updates.  
 
@@ -130,8 +130,8 @@ To demonstrate the use of the `_meta-history` parameter with PUT, follow this ex
 5. This will increment resource version and create a new version 3, but the old version 2 will not be saved as a historical record. To see this, run: `GET <fhir server>/Patient/test-patient/_history`. Two versions should be returned, versions 1 and 3. Please note that `_meta-history=false` query parameter only affects metadata-only changes made using PUT or PATCH. Using the query parameter to make metadata updates along with other non-metadata field value changes will increment the resource version and save the old version as a historical record.
 
 
-### Example of `_meta-history=false` with PATCH
-To demonstrate the use of the `_meta-history` parameter with PATCH, follow this example:
+### Example of `_meta-history=false` with PATCH or `$bulk-update`
+To demonstrate the use of the `_meta-history` parameter with PATCH or `$bulk-update`, follow this example:
 
 1. Create a resource:  
 `PUT <fhir server>/Patient/test-patient`
@@ -169,7 +169,7 @@ To demonstrate the use of the `_meta-history` parameter with PATCH, follow this
 }
 ```
 3. Run: `GET <fhir server>/Patient/test-patient/_history`. Two versions should be returned, versions 1 and 2.
-4. Use PATCH to make a metadata-only update with `_meta-history=false` query parameter. The example uses PATCH to update only the Patient.meta.tag.system value. More information about PATCH [here](rest-api-capabilities.md#patch-and-conditional-patch).
+4. Use PATCH or `$bulk-update`to make a metadata-only update with `_meta-history=false` query parameter. The example demonstrates using PATCH or `$bulk-update` to update only the Patient.meta.tag.system value. More information about PATCH [here](rest-api-capabilities.md#patch-and-conditional-patch) and `$bulk-update` [here](fhir-bulk-update.md).
 
 Using PATCH with FHIRPath patch:  
 `PATCH <fhir server>/Patient/test-patient?_meta-history=false`  
@@ -192,6 +192,30 @@ Using PATCH with FHIRPath patch:
   ]
 }
 ```
+If you wanted to bulk update multiple resources, you could use `$bulk-update`. The following example shows how to use `$bulk-update` to update the same metadata field for all Patient resources with `_meta-history=false`:
+
+`PATCH <fhir server>/Patient/$bulk-update?_meta-history=false`
+`Accept: application/fhir+json`  
+`Content-type: application/fhir+json`
+`Prefer: respond-async`
+
+``` 
+
+{
+  "resourceType": "Parameters",
+  "parameter": [
+    {
+      "name": "operation",
+      "part": [
+        { "name": "type",  "valueCode": "upsert" },
+        { "name": "path",  "valueString": "Patient.meta.tag[0].system" },
+        { "name": "value", "valueUri": "test2" }
+      ]
+    }
+  ]
+}
+```
+
 
 Using PATCH with JSON Patch:
 `PATCH <fhir server>/Patient/test-patient?_meta-history=false`  
@@ -207,6 +231,8 @@ Using PATCH with JSON Patch:
 ```
 5. This will increment resource version and create a new version 3, but the old version 2 will not be saved as a historical record. To see this, run: `GET <fhir server>/Patient/test-patient/_history`. Two versions should be returned, versions 1 and 3. Please note that `_meta-history=false` query parameter only affects metadata-only changes made using PUT or PATCH. Using the query parameter to make metadata updates along with other non-metadata field value changes will increment the resource version and save the old version as a historical record.
 
+
+
 ## Next steps
 
 In this article, you learned how to purge the history for resources in the FHIR service. For more information about how to disable history and some concepts about history management, see