google-apis-healthcare_v1 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 882ca8b6c1b528bea416ee217eccaed9044075d981943d62300091ef021f5d7b
-  data.tar.gz: b00068b7de55daec0c0b73905fa8a16f93635eaf3ddcd97e59c2ecb17acfbd22
+  metadata.gz: f2112a721d8dbd19788e6fc189e4092140fa1fe20d313f5a3b9d8ae45f29cc85
+  data.tar.gz: c37c73cee2ffb42bdc4745093820c9a1393d29769278dec9678f426b3f62341d
 SHA512:
-  metadata.gz: 705943a8d282166cb2af839dabe8965aa6b09fd3b4bbb5e25060fd5bc528413da00d1a2a8df5f6779f0888613d3b5064c74e6c1f88e7956f1daf393e28f4737d
-  data.tar.gz: 604d81c5e22cde796ec9fa6928fbf1b28f8c66131448680d2694d53c9ee7af1eb7475c79e7db544cda477106aeb777ecd8f4bc0e4e2da0e6066ec16d0ed015e9
+  metadata.gz: 2259a399f0b787adb36d3920ad1b9d0bc6042a3720834a67f29f86db5901ecffd5ec2a05aa0af6539a57334033f18304f73050a6f1bf0b83802a0bbbafe19a0f
+  data.tar.gz: feb8924d5c6993b8e5f73f4383148e8c69526f3b47c08003ba0f889a91d547a4e5e101b7f24dc36b4cf22e6566d092ae4bf27d2e2c654fa0ac842ad757b4394a

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-healthcare_v1
 
+### v0.3.0 (2021-02-18)
+
+* Regenerated from discovery document revision 20210205
+
 ### v0.2.0 (2021-02-05)
 
 * Regenerated from discovery document revision 20210203

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

@@ -1130,11 +1130,30 @@ module Google
         include Google::Apis::Core::Hashable
       
         # Restricts notifications sent for messages matching a filter. If this is empty,
-        # all messages are matched. Syntax: https://cloud.google.com/appengine/docs/
-        # standard/python/search/query_strings 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
+        # all messages are matched. 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 `yyyy-mm-dd` form. 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, it's 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"`. * `

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.2.0"
+      GEM_VERSION = "0.3.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.1.2"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20210203"
+      REVISION = "20210205"
     end
   end
 end

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

@@ -829,9 +829,28 @@ module Google
         # @param [String] parent
         #   Name of the dataset.
         # @param [String] filter
-        #   Restricts stores returned to those matching a filter. Syntax: https://cloud.
-        #   google.com/appengine/docs/standard/python/search/query_strings Only filtering
-        #   on labels is supported. For example, `labels.key=value`.
+        #   Restricts stores returned to those matching a filter. 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 `yyyy-mm-dd`
+        #   form. 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, it's just another part
+        #   of the character string to be matched. You can prepend the `NOT` operator to
+        #   an expression to negate it. Only filtering on labels is supported. For example,
+        #   `labels.key=value`.
         # @param [Fixnum] page_size
         #   Limit on the number of DICOM stores to return in a single response. If not
         #   specified, 100 is used. May not be larger than 1000.
@@ -2159,9 +2178,28 @@ module Google
         # @param [String] parent
         #   Name of the dataset.
         # @param [String] filter
-        #   Restricts stores returned to those matching a filter. Syntax: https://cloud.
-        #   google.com/appengine/docs/standard/python/search/query_strings Only filtering
-        #   on labels is supported, for example `labels.key=value`.
+        #   Restricts stores returned to those matching a filter. 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 `yyyy-mm-dd`
+        #   form. 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, it's just another part
+        #   of the character string to be matched. You can prepend the `NOT` operator to
+        #   an expression to negate it. Only filtering on labels is supported, for example
+        #   `labels.key=value`.
         # @param [Fixnum] page_size
         #   Limit on the number of FHIR stores to return in a single response. If not
         #   specified, 100 is used. May not be larger than 1000.
@@ -3162,9 +3200,28 @@ module Google
         # @param [String] parent
         #   Name of the dataset.
         # @param [String] filter
-        #   Restricts stores returned to those matching a filter. Syntax: https://cloud.
-        #   google.com/appengine/docs/standard/python/search/query_strings Only filtering
-        #   on labels is supported. For example, `labels.key=value`.
+        #   Restricts stores returned to those matching a filter. 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 `yyyy-mm-dd`
+        #   form. 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, it's just another part
+        #   of the character string to be matched. You can prepend the `NOT` operator to
+        #   an expression to negate it. Only filtering on labels is supported. For example,
+        #   `labels.key=value`.
         # @param [Fixnum] page_size
         #   Limit on the number of HL7v2 stores to return in a single response. If not
         #   specified, 100 is used. May not be larger than 1000.
@@ -3462,22 +3519,40 @@ module Google
         # @param [String] parent
         #   Name of the HL7v2 store to retrieve messages from.
         # @param [String] filter
-        #   Restricts messages returned to those matching a filter. Syntax: https://cloud.
-        #   google.com/appengine/docs/standard/python/search/query_strings Fields/
-        #   functions available for filtering are: * `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"`. * `send_facility`, the care center that the message came from,
-        #   from the MSH-4 segment. For example, `send_facility = "ABC"`. * `PatientId(
-        #   value, type)`, which matches if the message lists a patient having an ID of
-        #   the given value and type in the PID-2, PID-3, or PID-4 segments. For example, `
-        #   PatientId("123456", "MRN")`. * `labels.x`, a string value of the label with
-        #   key `x` as set using the Message.labels map. For example, `labels."priority"="
-        #   high"`. The operator `:*` can be used to assert the existence of a label. For
-        #   example, `labels."priority":*`.
+        #   Restricts messages returned to those matching a filter. 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 `yyyy-mm-dd`
+        #   form. 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, it's just another part
+        #   of the character string to be matched. You can prepend the `NOT` operator to
+        #   an expression to negate it. Fields/functions available for filtering are: * `
+        #   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"`. * `send_facility`, the care center
+        #   that the message came from, from the MSH-4 segment. For example, `
+        #   send_facility = "ABC"`. * `PatientId(value, type)`, which matches if the
+        #   message lists a patient having an ID of the given value and type in the PID-2,
+        #   PID-3, or PID-4 segments. For example, `PatientId("123456", "MRN")`. * `labels.
+        #   x`, a string value of the label with key `x` as set using the Message.labels
+        #   map. For example, `labels."priority"="high"`. The operator `:*` can be used to
+        #   assert the existence of a label. For example, `labels."priority":*`.
         # @param [String] order_by
         #   Orders messages returned by the specified order_by clause. Syntax: https://
         #   cloud.google.com/apis/design/design_patterns#sorting_order Fields available

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-healthcare_v1
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-02-08 00:00:00.000000000 Z
+date: 2021-02-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-apis-core
@@ -52,7 +52,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/master/generated/google-apis-healthcare_v1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-healthcare_v1/v0.2.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-healthcare_v1/v0.3.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google-apis-healthcare_v1
 post_install_message: 
 rdoc_options: []