lib/google/apis/healthcare_v1/classes.rb in google-apis-healthcare_v1-0.50.0 vs lib/google/apis/healthcare_v1/classes.rb in google-apis-healthcare_v1-0.51.0

- old
+ new

@@ -1571,45 +1571,44 @@ # Corresponds to the JSON property `endTime` # @return [String] 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 # The Cloud Storage output destination. The Cloud Healthcare Service Agent