From 1048df4d872a7ae0cd19afdf37e600d06faf06ac Mon Sep 17 00:00:00 2001 From: Tadgh Date: Fri, 13 Nov 2020 15:54:43 -0500 Subject: [PATCH] Update rest_operations.md --- .../ca/uhn/hapi/fhir/docs/server_plain/rest_operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_plain/rest_operations.md b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_plain/rest_operations.md index 8e20f8975e4..2b47e433c1f 100644 --- a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_plain/rest_operations.md +++ b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_plain/rest_operations.md @@ -389,7 +389,7 @@ Tags have very specific semantics, which may not be obvious simply by using the ## Accessing Tags in a Read / VRead / Search Method -Tags are stored within a resource object, in the Resource.meta element. It is important to note that changing a resources tags will not cause a version update to that resource. +Tags are stored within a resource object, in the Resource.meta element. It is important to note that changing a resource's tags will not cause a version update to that resource. In a server implementation, you may populate your tags into the returned resource(s) and HAPI will automatically place these tags into the response headers (for read/vread) or the bundle category tags (for search). The following example illustrates how to return tags from a server method. This example shows how to supply tags in a read method, but the same approach applies to vread and search operations as well.