google-apis-healthcare_v1 0.50.0 → 0.51.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2557af71b5219308eb1693becd925597fa631bfdd62ee3539f9b74700d85a786
-  data.tar.gz: '037883fa2377469b3a02ef4fe4e03f62d482ebcdaccf2051021748b504e3c2a3'
+  metadata.gz: f004ade76cba73c008e2b858fa78c802b766af247fb9f9edde7b2e32785b743a
+  data.tar.gz: b53c8188a9a95471676f136abb2970181b56b71d3e122f8450a28096f76d28be
 SHA512:
-  metadata.gz: d5f07b28043d86e1ba36de62a6392b5f213280e41bd9063800746b06c7210c56424232e54d676551b125d39728eeacfce123272acbfb1bdf2e77c8e9b3e8dfe4
-  data.tar.gz: 3c6199ec1724d46e647f7f18aaf27d8ec7037d7042af23d8ed00f4b61f40520434aa49a27b065bf72e9e2c2ae32f4683595e5021dca4209c445805d2e2a2f6cb
+  metadata.gz: eb584dd0962a76cde362e124d2beff50dbd5f1d80d08ddae5b93737ade12679c72d3beda411c8c8e037c329d6b5f1f7c4a9d31adb7c40ff0231671219884c1e5
+  data.tar.gz: 6c7cd3a6b39bf58e5d572152513fa72c532a321dee2449a1e69b85e2a0a9ae85d3607ed541c38e4c27108d3b632205e6ef9549a6dba3e64463b51d3efa5a6e0d

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-healthcare_v1
 
+### 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.51.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 = "20231017"
     end
   end
 end

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

@@ -4585,10 +4585,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 +4679,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

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.51.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-10-15 00:00:00.000000000 Z
+date: 2023-10-29 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.51.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-healthcare_v1
 post_install_message: 
 rdoc_options: []