google-apis-healthcare_v1 0.50.0 → 0.52.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2557af71b5219308eb1693becd925597fa631bfdd62ee3539f9b74700d85a786
-  data.tar.gz: '037883fa2377469b3a02ef4fe4e03f62d482ebcdaccf2051021748b504e3c2a3'
+  metadata.gz: 16aab8215081c75c33da53cae5f4c7ed56eec317a23e92400a978354bdb01d03
+  data.tar.gz: 868c58fd83ad244a0e516904a07787175dbc95755855473308a23a9253d74ec6
 SHA512:
-  metadata.gz: d5f07b28043d86e1ba36de62a6392b5f213280e41bd9063800746b06c7210c56424232e54d676551b125d39728eeacfce123272acbfb1bdf2e77c8e9b3e8dfe4
-  data.tar.gz: 3c6199ec1724d46e647f7f18aaf27d8ec7037d7042af23d8ed00f4b61f40520434aa49a27b065bf72e9e2c2ae32f4683595e5021dca4209c445805d2e2a2f6cb
+  metadata.gz: f996819c2af30fa36f48d9efa50705087134fc76e97fa1a761668187c2533e5bdc2a317c8485089c18e2b36baa60beb10dc2e31c5f6180b832577e9c9b54dda6
+  data.tar.gz: 58c24531ffacb2cbf0e5a83f8e94c4b02a3b0e5ee9120d319fba1e7f6b88a2e3b0e38959a564d78a400511ffe1b6e46e4e7c6c5ccf1e7f3fc7fa07efe350b68a

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Release history for google-apis-healthcare_v1
 
+### v0.52.0 (2023-11-05)
+
+* Regenerated from discovery document revision 20231101
+
+### v0.51.0 (2023-10-22)
+
+* Regenerated from discovery document revision 20231017
+
 ### v0.50.0 (2023-10-15)
 
 * Regenerated from discovery document revision 20231003

data/lib/google/apis/healthcare_v1/classes.rb

@@ -1573,42 +1573,41 @@ module Google
         attr_accessor :end_time
       
         # Restricts messages exported to those matching a filter, only applicable to
-        # PubsubDestination and GcsDestination. The following syntax is available: * A
-        # string field value can be written as text inside quotation marks, for example `
-        # "query text"`. The only valid relational operation for text fields is equality
-        # (`=`), where text is searched within the field, rather than having the field
-        # be equal to the text. For example, `"Comment = great"` returns messages with `
-        # great` in the comment field. * A number field value can be written as an
-        # integer, a decimal, or an exponential. The valid relational operators for
-        # number fields are the equality operator (`=`), along with the less than/
-        # greater than operators (`<`, `<=`, `>`, `>=`). Note that there is no
-        # inequality (`!=`) operator. You can prepend the `NOT` operator to an
-        # expression to negate it. * A date field value must be written in the `yyyy-mm-
-        # dd` format. Fields with date and time use the RFC3339 time format. Leading
-        # zeros are required for one-digit months and days. The valid relational
-        # operators for date fields are the equality operator (`=`) , along with the
-        # less than/greater than operators (`<`, `<=`, `>`, `>=`). Note that there is no
-        # inequality (`!=`) operator. You can prepend the `NOT` operator to an
-        # expression to negate it. * Multiple field query expressions can be combined in
-        # one query by adding `AND` or `OR` operators between the expressions. If a
-        # boolean operator appears within a quoted string, it is not treated as special,
-        # and is just another part of the character string to be matched. You can
-        # prepend the `NOT` operator to an expression to negate it. The following fields
-        # and functions are available for filtering: * `message_type`, from the MSH-9.1
-        # field. For example, `NOT message_type = "ADT"`. * `send_date` or `sendDate`,
-        # the `yyyy-mm-dd` date the message was sent in the dataset's time_zone, from
-        # the MSH-7 segment. For example, `send_date < "2017-01-02"`. * `send_time`, the
-        # timestamp when the message was sent, using the RFC3339 time format for
-        # comparisons, from the MSH-7 segment. For example, `send_time < "2017-01-02T00:
-        # 00:00-05:00"`. * `create_time`, the timestamp when the message was created in
-        # the HL7v2 store. Use the RFC3339 time format for comparisons. For example, `
-        # create_time < "2017-01-02T00:00:00-05:00"`. * `send_facility`, the care center
-        # that the message came from, from the MSH-4 segment. For example, `
-        # send_facility = "ABC"`. Note: The filter will be applied to every message in
-        # the HL7v2 store whose `send_time` lies in the range defined by the `start_time`
-        # and the `end_time`. Even if the filter only matches a small set of messages,
-        # the export operation can still take a long time to finish when a lot of
-        # messages are between the specified `start_time` and `end_time` range.
+        # PubsubDestination. The following syntax is available: * A string field value
+        # can be written as text inside quotation marks, for example `"query text"`. The
+        # only valid relational operation for text fields is equality (`=`), where text
+        # is searched within the field, rather than having the field be equal to the
+        # text. For example, `"Comment = great"` returns messages with `great` in the
+        # comment field. * A number field value can be written as an integer, a decimal,
+        # or an exponential. The valid relational operators for number fields are the
+        # equality operator (`=`), along with the less than/greater than operators (`<`,
+        # `<=`, `>`, `>=`). Note that there is no inequality (`!=`) operator. You can
+        # prepend the `NOT` operator to an expression to negate it. * A date field value
+        # must be written in the `yyyy-mm-dd` format. Fields with date and time use the
+        # RFC3339 time format. Leading zeros are required for one-digit months and days.
+        # The valid relational operators for date fields are the equality operator (`=`)
+        # , along with the less than/greater than operators (`<`, `<=`, `>`, `>=`). Note
+        # that there is no inequality (`!=`) operator. You can prepend the `NOT`
+        # operator to an expression to negate it. * Multiple field query expressions can
+        # be combined in one query by adding `AND` or `OR` operators between the
+        # expressions. If a boolean operator appears within a quoted string, it is not
+        # treated as special, and is just another part of the character string to be
+        # matched. You can prepend the `NOT` operator to an expression to negate it. The
+        # following fields and functions are available for filtering: * `message_type`,
+        # from the MSH-9.1 field. For example, `NOT message_type = "ADT"`. * `send_date`
+        # or `sendDate`, the `yyyy-mm-dd` date the message was sent in the dataset's
+        # time_zone, from the MSH-7 segment. For example, `send_date < "2017-01-02"`. * `
+        # send_time`, the timestamp when the message was sent, using the RFC3339 time
+        # format for comparisons, from the MSH-7 segment. For example, `send_time < "
+        # 2017-01-02T00:00:00-05:00"`. * `create_time`, the timestamp when the message
+        # was created in the HL7v2 store. Use the RFC3339 time format for comparisons.
+        # For example, `create_time < "2017-01-02T00:00:00-05:00"`. * `send_facility`,
+        # the care center that the message came from, from the MSH-4 segment. For
+        # example, `send_facility = "ABC"`. Note: The filter will be applied to every
+        # message in the HL7v2 store whose `send_time` lies in the range defined by the `
+        # start_time` and the `end_time`. Even if the filter only matches a small set of
+        # messages, the export operation can still take a long time to finish when a lot
+        # of messages are between the specified `start_time` and `end_time` range.
         # Corresponds to the JSON property `filter`
         # @return [String]
         attr_accessor :filter

data/lib/google/apis/healthcare_v1/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module HealthcareV1
       # Version of the google-apis-healthcare_v1 gem
-      GEM_VERSION = "0.50.0"
+      GEM_VERSION = "0.52.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.12.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20231003"
+      REVISION = "20231101"
     end
   end
 end

data/lib/google/apis/healthcare_v1/service.rb

@@ -2303,9 +2303,8 @@ module Google
         # html#sect_10.6). For details on the implementation of SearchForInstances, see [
         # Search transaction](https://cloud.google.com/healthcare/docs/dicom#
         # search_transaction) in the Cloud Healthcare API conformance statement. For
-        # samples that show how to call SearchForInstances, see [Searching for studies,
-        # series, instances, and frames](https://cloud.google.com/healthcare/docs/how-
-        # tos/dicomweb#searching_for_studies_series_instances_and_frames).
+        # samples that show how to call SearchForInstances, see [Search for DICOM data](
+        # https://cloud.google.com/healthcare/docs/how-tos/dicomweb#search-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2347,9 +2346,8 @@ module Google
         # For details on the implementation of SearchForSeries, see [Search transaction]
         # (https://cloud.google.com/healthcare/docs/dicom#search_transaction) in the
         # Cloud Healthcare API conformance statement. For samples that show how to call
-        # SearchForSeries, see [Searching for studies, series, instances, and frames](
-        # https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # searching_for_studies_series_instances_and_frames).
+        # SearchForSeries, see [Search for DICOM data](https://cloud.google.com/
+        # healthcare/docs/how-tos/dicomweb#search-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2390,9 +2388,8 @@ module Google
         # For details on the implementation of SearchForStudies, see [Search
         # transaction](https://cloud.google.com/healthcare/docs/dicom#search_transaction)
         # in the Cloud Healthcare API conformance statement. For samples that show how
-        # to call SearchForStudies, see [Searching for studies, series, instances, and
-        # frames](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # searching_for_studies_series_instances_and_frames).
+        # to call SearchForStudies, see [Search for DICOM data](https://cloud.google.com/
+        # healthcare/docs/how-tos/dicomweb#search-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2470,8 +2467,8 @@ module Google
         # implementation of StoreInstances, see [Store transaction](https://cloud.google.
         # com/healthcare/docs/dicom#store_transaction) in the Cloud Healthcare API
         # conformance statement. For samples that show how to call StoreInstances, see [
-        # Storing DICOM data](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # storing_dicom_data).
+        # Store DICOM data](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
+        # store-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2618,9 +2615,8 @@ module Google
         # method returns an Operation which will be marked successful when the deletion
         # is complete. Warning: Instances cannot be inserted into a study that is being
         # deleted by an operation until the operation completes. For samples that show
-        # how to call DeleteStudy, see [Deleting a study, series, or instance](https://
-        # cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # deleting_a_study_series_or_instance).
+        # how to call DeleteStudy, see [Delete a study, series, or instance](https://
+        # cloud.google.com/healthcare/docs/how-tos/dicomweb#delete-dicom).
         # @param [String] parent
         # @param [String] dicom_web_path
         #   The path of the DeleteStudy request. For example, `studies/`study_uid``.
@@ -2658,8 +2654,8 @@ module Google
         # For details on the implementation of RetrieveStudyMetadata, see [Metadata
         # resources](https://cloud.google.com/healthcare/docs/dicom#metadata_resources)
         # in the Cloud Healthcare API conformance statement. For samples that show how
-        # to call RetrieveStudyMetadata, see [Retrieving metadata](https://cloud.google.
-        # com/healthcare/docs/how-tos/dicomweb#retrieving_metadata).
+        # to call RetrieveStudyMetadata, see [Retrieve metadata](https://cloud.google.
+        # com/healthcare/docs/how-tos/dicomweb#retrieve-metadata).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2700,9 +2696,9 @@ module Google
         # part18.html#sect_10.4). For details on the implementation of RetrieveStudy,
         # see [DICOM study/series/instances](https://cloud.google.com/healthcare/docs/
         # dicom#dicom_studyseriesinstances) in the Cloud Healthcare API conformance
-        # statement. For samples that show how to call RetrieveStudy, see [Retrieving
-        # DICOM data](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # retrieving_dicom_data).
+        # statement. For samples that show how to call RetrieveStudy, see [Retrieve
+        # DICOM data](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-
+        # dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2743,9 +2739,8 @@ module Google
         # html#sect_10.6). For details on the implementation of SearchForInstances, see [
         # Search transaction](https://cloud.google.com/healthcare/docs/dicom#
         # search_transaction) in the Cloud Healthcare API conformance statement. For
-        # samples that show how to call SearchForInstances, see [Searching for studies,
-        # series, instances, and frames](https://cloud.google.com/healthcare/docs/how-
-        # tos/dicomweb#searching_for_studies_series_instances_and_frames).
+        # samples that show how to call SearchForInstances, see [Search for DICOM data](
+        # https://cloud.google.com/healthcare/docs/how-tos/dicomweb#search-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2787,9 +2782,8 @@ module Google
         # For details on the implementation of SearchForSeries, see [Search transaction]
         # (https://cloud.google.com/healthcare/docs/dicom#search_transaction) in the
         # Cloud Healthcare API conformance statement. For samples that show how to call
-        # SearchForSeries, see [Searching for studies, series, instances, and frames](
-        # https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # searching_for_studies_series_instances_and_frames).
+        # SearchForSeries, see [Search for DICOM data](https://cloud.google.com/
+        # healthcare/docs/how-tos/dicomweb#search-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2831,8 +2825,8 @@ module Google
         # implementation of StoreInstances, see [Store transaction](https://cloud.google.
         # com/healthcare/docs/dicom#store_transaction) in the Cloud Healthcare API
         # conformance statement. For samples that show how to call StoreInstances, see [
-        # Storing DICOM data](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # storing_dicom_data).
+        # Store DICOM data](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
+        # store-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2876,9 +2870,9 @@ module Google
         # transaction. The method returns an Operation which will be marked successful
         # when the deletion is complete. Warning: Instances cannot be inserted into a
         # series that is being deleted by an operation until the operation completes.
-        # For samples that show how to call DeleteSeries, see [Deleting a study, series,
-        # or instance](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # deleting_a_study_series_or_instance).
+        # For samples that show how to call DeleteSeries, see [Delete a study, series,
+        # or instance](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#delete-
+        # dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2921,8 +2915,8 @@ module Google
         # RetrieveSeriesMetadata, see [Metadata resources](https://cloud.google.com/
         # healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API
         # conformance statement. For samples that show how to call
-        # RetrieveSeriesMetadata, see [Retrieving metadata](https://cloud.google.com/
-        # healthcare/docs/how-tos/dicomweb#retrieving_metadata).
+        # RetrieveSeriesMetadata, see [Retrieve metadata](https://cloud.google.com/
+        # healthcare/docs/how-tos/dicomweb#retrieve-metadata).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -2963,9 +2957,9 @@ module Google
         # part18.html#sect_10.4). For details on the implementation of RetrieveSeries,
         # see [DICOM study/series/instances](https://cloud.google.com/healthcare/docs/
         # dicom#dicom_studyseriesinstances) in the Cloud Healthcare API conformance
-        # statement. For samples that show how to call RetrieveSeries, see [Retrieving
-        # DICOM data](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # retrieving_dicom_data).
+        # statement. For samples that show how to call RetrieveSeries, see [Retrieve
+        # DICOM data](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#retrieve-
+        # dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -3006,9 +3000,8 @@ module Google
         # html#sect_10.6). For details on the implementation of SearchForInstances, see [
         # Search transaction](https://cloud.google.com/healthcare/docs/dicom#
         # search_transaction) in the Cloud Healthcare API conformance statement. For
-        # samples that show how to call SearchForInstances, see [Searching for studies,
-        # series, instances, and frames](https://cloud.google.com/healthcare/docs/how-
-        # tos/dicomweb#searching_for_studies_series_instances_and_frames).
+        # samples that show how to call SearchForInstances, see [Search for DICOM data](
+        # https://cloud.google.com/healthcare/docs/how-tos/dicomweb#search-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -3049,9 +3042,9 @@ module Google
         # and SOP Instance UID. Delete requests are equivalent to the GET requests
         # specified in the Retrieve transaction. Study and series search results can
         # take a few seconds to be updated after an instance is deleted using
-        # DeleteInstance. For samples that show how to call DeleteInstance, see [
-        # Deleting a study, series, or instance](https://cloud.google.com/healthcare/
-        # docs/how-tos/dicomweb#deleting_a_study_series_or_instance).
+        # DeleteInstance. For samples that show how to call DeleteInstance, see [Delete
+        # a study, series, or instance](https://cloud.google.com/healthcare/docs/how-tos/
+        # dicomweb#delete-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -3094,8 +3087,8 @@ module Google
         # cloud.google.com/healthcare/docs/dicom#dicom_studyseriesinstances) and [DICOM
         # instances](https://cloud.google.com/healthcare/docs/dicom#dicom_instances) in
         # the Cloud Healthcare API conformance statement. For samples that show how to
-        # call RetrieveInstance, see [Retrieving an instance](https://cloud.google.com/
-        # healthcare/docs/how-tos/dicomweb#retrieving_an_instance).
+        # call RetrieveInstance, see [Retrieve an instance](https://cloud.google.com/
+        # healthcare/docs/how-tos/dicomweb#retrieve-instance).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -3138,8 +3131,8 @@ module Google
         # RetrieveInstanceMetadata, see [Metadata resources](https://cloud.google.com/
         # healthcare/docs/dicom#metadata_resources) in the Cloud Healthcare API
         # conformance statement. For samples that show how to call
-        # RetrieveInstanceMetadata, see [Retrieving metadata](https://cloud.google.com/
-        # healthcare/docs/how-tos/dicomweb#retrieving_metadata).
+        # RetrieveInstanceMetadata, see [Retrieve metadata](https://cloud.google.com/
+        # healthcare/docs/how-tos/dicomweb#retrieve-metadata).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -3182,9 +3175,8 @@ module Google
         # RetrieveRenderedInstance, see [Rendered resources](https://cloud.google.com/
         # healthcare/docs/dicom#rendered_resources) in the Cloud Healthcare API
         # conformance statement. For samples that show how to call
-        # RetrieveRenderedInstance, see [Retrieving consumer image formats](https://
-        # cloud.google.com/healthcare/docs/how-tos/dicomweb#
-        # retrieving_consumer_image_formats).
+        # RetrieveRenderedInstance, see [Retrieve consumer image formats](https://cloud.
+        # google.com/healthcare/docs/how-tos/dicomweb#retrieve-consumer).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -3226,8 +3218,8 @@ module Google
         # the implementation of RetrieveFrames, see [DICOM frames](https://cloud.google.
         # com/healthcare/docs/dicom#dicom_frames) in the Cloud Healthcare API
         # conformance statement. For samples that show how to call RetrieveFrames, see [
-        # Retrieving DICOM data](https://cloud.google.com/healthcare/docs/how-tos/
-        # dicomweb#retrieving_dicom_data).
+        # Retrieve DICOM data](https://cloud.google.com/healthcare/docs/how-tos/dicomweb#
+        # retrieve-dicom).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -3270,8 +3262,8 @@ module Google
         # RetrieveRenderedFrames, see [Rendered resources](https://cloud.google.com/
         # healthcare/docs/dicom#rendered_resources) in the Cloud Healthcare API
         # conformance statement. For samples that show how to call
-        # RetrieveRenderedFrames, see [Retrieving consumer image formats](https://cloud.
-        # google.com/healthcare/docs/how-tos/dicomweb#retrieving_consumer_image_formats).
+        # RetrieveRenderedFrames, see [Retrieve consumer image formats](https://cloud.
+        # google.com/healthcare/docs/how-tos/dicomweb#retrieve-consumer).
         # @param [String] parent
         #   The name of the DICOM store that is being accessed. For example, `projects/`
         #   project_id`/locations/`location_id`/datasets/`dataset_id`/dicomStores/`
@@ -4585,10 +4577,26 @@ module Google
         # 50,000 might not be fully searchable as the server might trim its generated
         # search index in those cases. Note: FHIR resources are indexed asynchronously,
         # so there might be a slight delay between the time a resource is created or
-        # changes and when the change is reflected in search results. For samples and
-        # detailed information, see [Searching for FHIR resources](https://cloud.google.
-        # com/healthcare/docs/how-tos/fhir-search) and [Advanced FHIR search features](
-        # https://cloud.google.com/healthcare/docs/how-tos/fhir-advanced-search).
+        # changed, and the time when the change reflects in search results. The only
+        # exception is resource identifier data, which is indexed synchronously as a
+        # special index. As a result, searching using resource identifier is not subject
+        # to indexing delay. To use the special synchronous index, the search term for
+        # identifier should be in the pattern `identifier=[system]|[value]` or `
+        # identifier=[value]`, and any of the following search result parameters can be
+        # used: * `_count` * `_include` * `_revinclude` * `_summary` * `_elements` If
+        # your query contains any other search parameters, the standard asynchronous
+        # index will be used instead. Note that searching against the special index is
+        # optimized for resolving a small number of matches. The search isn't optimized
+        # if your identifier search criteria matches a large number (i.e. more than 2,
+        # 000) of resources. For a search query that will match a large number of
+        # resources, you can avoiding using the special synchronous index by including
+        # an additional `_sort` parameter in your query. Use `_sort=-_lastUpdated` if
+        # you want to keep the default sorting order. Note: The special synchronous
+        # identifier index are currently disabled for DocumentReference and
+        # DocumentManifest searches. For samples and detailed information, see [
+        # Searching for FHIR resources](https://cloud.google.com/healthcare/docs/how-tos/
+        # fhir-search) and [Advanced FHIR search features](https://cloud.google.com/
+        # healthcare/docs/how-tos/fhir-advanced-search).
         # @param [String] parent
         #   Name of the FHIR store to retrieve resources from.
         # @param [Google::Apis::HealthcareV1::SearchResourcesRequest] search_resources_request_object
@@ -4663,10 +4671,26 @@ module Google
         # 50,000 might not be fully searchable as the server might trim its generated
         # search index in those cases. Note: FHIR resources are indexed asynchronously,
         # so there might be a slight delay between the time a resource is created or
-        # changes and when the change is reflected in search results. For samples and
-        # detailed information, see [Searching for FHIR resources](https://cloud.google.
-        # com/healthcare/docs/how-tos/fhir-search) and [Advanced FHIR search features](
-        # https://cloud.google.com/healthcare/docs/how-tos/fhir-advanced-search).
+        # changed, and the time when the change reflects in search results. The only
+        # exception is resource identifier data, which is indexed synchronously as a
+        # special index. As a result, searching using resource identifier is not subject
+        # to indexing delay. To use the special synchronous index, the search term for
+        # identifier should be in the pattern `identifier=[system]|[value]` or `
+        # identifier=[value]`, and any of the following search result parameters can be
+        # used: * `_count` * `_include` * `_revinclude` * `_summary` * `_elements` If
+        # your query contains any other search parameters, the standard asynchronous
+        # index will be used instead. Note that searching against the special index is
+        # optimized for resolving a small number of matches. The search isn't optimized
+        # if your identifier search criteria matches a large number (i.e. more than 2,
+        # 000) of resources. For a search query that will match a large number of
+        # resources, you can avoiding using the special synchronous index by including
+        # an additional `_sort` parameter in your query. Use `_sort=-_lastUpdated` if
+        # you want to keep the default sorting order. Note: The special synchronous
+        # identifier index are currently disabled for DocumentReference and
+        # DocumentManifest searches. For samples and detailed information, see [
+        # Searching for FHIR resources](https://cloud.google.com/healthcare/docs/how-tos/
+        # fhir-search) and [Advanced FHIR search features](https://cloud.google.com/
+        # healthcare/docs/how-tos/fhir-advanced-search).
         # @param [String] parent
         #   Name of the FHIR store to retrieve resources from.
         # @param [String] resource_type
@@ -4937,7 +4961,7 @@ module Google
           execute_or_queue_command(command, &block)
         end
         
-        # Gets metrics asssociated with the HL7v2 store.
+        # Gets metrics associated with the HL7v2 store.
         # @param [String] name
         #   The resource name of the HL7v2 store to get metrics for, in the format `
         #   projects/`project_id`/locations/`location_id`/datasets/`dataset_id`/

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-healthcare_v1
 version: !ruby/object:Gem::Version
-  version: 0.50.0
+  version: 0.52.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-10-15 00:00:00.000000000 Z
+date: 2023-11-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-apis-core
@@ -58,7 +58,7 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
   changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-healthcare_v1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-healthcare_v1/v0.50.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-healthcare_v1/v0.52.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-healthcare_v1
 post_install_message: 
 rdoc_options: []