service.rb in google-apis-healthcare_v1-0.3.0

- old
+ new

@@ -827,13 +827,32 @@
         
         # Lists the DICOM stores in the given dataset.
         # @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.
         # @param [String] page_token
         #   The next_page_token value returned from the previous List request, if any.
@@ -2157,13 +2176,32 @@
         
         # Lists the FHIR stores in the given dataset.
         # @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.
         # @param [String] page_token
         #   The next_page_token value returned from the previous List request, if any.
@@ -3160,13 +3198,32 @@
         
         # Lists the HL7v2 stores in the given dataset.
         # @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.
         # @param [String] page_token
         #   The next_page_token value returned from the previous List request, if any.
@@ -3460,25 +3517,43 @@
         # delay between the time a message is created and when it can be found through a
         # filter.
         # @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
         #   for ordering are: * `send_time`
         # @param [Fixnum] page_size