Skip to content

Commit 2477fb6

Browse files
committed
Update fhir-bulk-update.md
1 parent c82c887 commit 2477fb6

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

articles/healthcare-apis/fhir/fhir-bulk-update.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ To execute a bulk update, the application or user must be assigned one of the fo
4242

4343
## Request
4444

45-
You can use FHIR search parameters in the request. The bulk update operation supports standard search filters, for example: address:contains=Meadow, or Patient.birthdate=1987-02-20. You can also use _include, _revinclude, and _not-referenced to extend search criteria.
45+
You can use FHIR search parameters in the request. The bulk update operation supports standard search filters, for example: address:contains=Meadow, or Patient.birthdate=1987-02-20. You can also use _include, _revinclude, and _not-referenced to extend search criteria, and _meta-history to configure versioning behavior for metadata-only updates.
4646

4747
### Request examples
4848

@@ -61,6 +61,10 @@ You can use FHIR search parameters in the request. The bulk update operation sup
6161

6262
`PATCH {FHIR-SERVICE-HOST}/DiagnosticReport/$bulk-update?_lastUpdated=lt2021-12-12&_include=DiagnosticReport:based-on:ServiceRequest&_include:iterate=ServiceRequest:encounter`
6363

64+
4. Metadata-only updates with `_meta-history` query parameter: When FHIR server the versioning policy is set to either `versioned` or `version-update`, the `_meta-history` parameter allows you to control whether metadata-only changes to a resource create a new historical version of the resource or not. By default, any change to a resource, including metadata-only changes, creates a new version and saves the previous version as a historical record. When you set the `_meta-history` parameter to false, metadata-only changes do not create a new version, and the previous version is not saved as a historical record. This feature is useful for scenarios where frequent metadata updates are made, and you want to avoid cluttering the resource history with numerous versions that only differ in metadata. For more information and examples, see [FHIR versioning policy and history management](fhir-versioning-policy-and-history-management.md#metadata-only-updates-and-versioning).
65+
66+
`PATCH https://{FHIR-SERVICE-HOST}/$bulk-update?_meta-history=false`
67+
6468
When using bulk update with FHIR search parameters, consider using the same query in a FHIR search first, so that you can verify the data that you plan to update.
6569

6670
The following is an example request body.

0 commit comments

Comments
 (0)