batchGet(parent, ids=None, view=None, x__xgafv=None)
Gets multiple messages in the given HL7v2 store.
Close httplib2 connections.
create(parent, body=None, x__xgafv=None)
Parses and stores an HL7v2 message. This method triggers an asynchronous notification to any Pub/Sub topic configured in Hl7V2Store.Hl7V2NotificationConfig, if the filtering matches the message. If an MLLP adapter is configured to listen to a Pub/Sub topic, the adapter transmits the message when a notification is received.
Deletes an HL7v2 message.
get(name, view=None, x__xgafv=None)
Gets an HL7v2 message.
ingest(parent, body=None, x__xgafv=None)
Parses and stores an HL7v2 message. This method triggers an asynchronous notification to any Pub/Sub topic configured in Hl7V2Store.Hl7V2NotificationConfig, if the filtering matches the message. If an MLLP adapter is configured to listen to a Pub/Sub topic, the adapter transmits the message when a notification is received. If the method is successful, it generates a response containing an HL7v2 acknowledgment (`ACK`) message. If the method encounters an error, it returns a negative acknowledgment (`NACK`) message. This behavior is suitable for replying to HL7v2 interface systems that expect these acknowledgments.
list(parent, filter=None, orderBy=None, pageSize=None, pageToken=None, view=None, x__xgafv=None)
Lists all the messages in the given HL7v2 store with support for filtering. Note: HL7v2 messages are indexed asynchronously, so there might be a slight delay between the time a message is created and when it can be found through a filter.
Retrieves the next page of results.
patch(name, body=None, updateMask=None, x__xgafv=None)
Update the message. The contents of the message in Message.data and data extracted from the contents such as Message.create_time can't be altered. Only the Message.labels field is allowed to be updated. The labels in the request are merged with the existing set of labels. Existing labels with the same keys are updated.
batchGet(parent, ids=None, view=None, x__xgafv=None)
Gets multiple messages in the given HL7v2 store.
Args:
parent: string, Required. Name of the HL7v2 store to retrieve messages from, in the format: `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7v2Stores/{hl7v2_store_id}`. (required)
ids: string, The resource id of the HL7v2 messages to retrieve in the format: `{message_id}`, where the full resource name is `{parent}/messages/{message_id}` A maximum of 100 messages can be retrieved in a batch. All 'ids' have to be under parent. (repeated)
view: string, Specifies the parts of the Messages resource to return in the response. When unspecified, equivalent to BASIC.
Allowed values
MESSAGE_VIEW_UNSPECIFIED - Not specified, equivalent to FULL for getMessage, equivalent to BASIC for listMessages.
RAW_ONLY - Server responses include all the message fields except parsed_data, and schematized_data fields.
PARSED_ONLY - Server responses include all the message fields except data and schematized_data fields.
FULL - Server responses include all the message fields.
SCHEMATIZED_ONLY - Server responses include all the message fields except data and parsed_data fields.
BASIC - Server responses include only the name field.
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format
Returns:
An object of the form:
{ # Gets multiple messages in a specified HL7v2 store.
"messages": [ # The returned Messages. See `MessageView` for populated fields.
{ # A complete HL7v2 message. See [Introduction to HL7 Standards] (https://www.hl7.org/implement/standards/index.cfm?ref=common) for details on the standard.
"createTime": "A String", # Output only. The datetime when the message was created. Set by the server.
"data": "A String", # Required. Raw message bytes.
"labels": { # User-supplied key-value pairs used to organize HL7v2 stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
"a_key": "A String",
},
"messageType": "A String", # The message type for this message. MSH-9.1.
"name": "A String", # Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server.
"parsedData": { # The content of an HL7v2 message in a structured format. # Output only. The parsed version of the raw message data.
"segments": [
{ # A segment in a structured format.
"fields": { # A mapping from the positional location to the value. The key string uses zero-based indexes separated by dots to identify Fields, components and sub-components. A bracket notation is also used to identify different instances of a repeated field. Regex for key: (\d+)(\[\d+\])?(.\d+)?(.\d+)? Examples of (key, value) pairs: * (0.1, "hemoglobin") denotes that the first component of Field 0 has the value "hemoglobin". * (1.1.2, "CBC") denotes that the second sub-component of the first component of Field 1 has the value "CBC". * (1[0].1, "HbA1c") denotes that the first component of the first Instance of Field 1, which is repeated, has the value "HbA1c".
"a_key": "A String",
},
"segmentId": "A String", # A string that indicates the type of segment. For example, EVN or PID.
"setId": "A String", # Set ID for segments that can be in a set. This can be empty if it's missing or isn't applicable.
},
],
},
"patientIds": [ # All patient IDs listed in the PID-2, PID-3, and PID-4 segments of this message.
{ # A patient identifier and associated type.
"type": "A String", # ID type. For example, MRN or NHS.
"value": "A String", # The patient's unique identifier.
},
],
"schematizedData": { # The content of an HL7v2 message in a structured format as specified by a schema. # The parsed version of the raw message data schematized according to this store's schemas and type definitions.
"data": "A String", # JSON output of the parser.
"error": "A String", # The error output of the parser.
},
"sendFacility": "A String", # The hospital that this message came from. MSH-4.
"sendTime": "A String", # The datetime the sending application sent this message. MSH-7.
},
],
}
close()
Close httplib2 connections.
create(parent, body=None, x__xgafv=None)
Parses and stores an HL7v2 message. This method triggers an asynchronous notification to any Pub/Sub topic configured in Hl7V2Store.Hl7V2NotificationConfig, if the filtering matches the message. If an MLLP adapter is configured to listen to a Pub/Sub topic, the adapter transmits the message when a notification is received.
Args:
parent: string, Required. The name of the HL7v2 store this message belongs to. (required)
body: object, The request body.
The object takes the form of:
{ # Creates a new message.
"message": { # A complete HL7v2 message. See [Introduction to HL7 Standards] (https://www.hl7.org/implement/standards/index.cfm?ref=common) for details on the standard. # Required. HL7v2 message.
"createTime": "A String", # Output only. The datetime when the message was created. Set by the server.
"data": "A String", # Required. Raw message bytes.
"labels": { # User-supplied key-value pairs used to organize HL7v2 stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
"a_key": "A String",
},
"messageType": "A String", # The message type for this message. MSH-9.1.
"name": "A String", # Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server.
"parsedData": { # The content of an HL7v2 message in a structured format. # Output only. The parsed version of the raw message data.
"segments": [
{ # A segment in a structured format.
"fields": { # A mapping from the positional location to the value. The key string uses zero-based indexes separated by dots to identify Fields, components and sub-components. A bracket notation is also used to identify different instances of a repeated field. Regex for key: (\d+)(\[\d+\])?(.\d+)?(.\d+)? Examples of (key, value) pairs: * (0.1, "hemoglobin") denotes that the first component of Field 0 has the value "hemoglobin". * (1.1.2, "CBC") denotes that the second sub-component of the first component of Field 1 has the value "CBC". * (1[0].1, "HbA1c") denotes that the first component of the first Instance of Field 1, which is repeated, has the value "HbA1c".
"a_key": "A String",
},
"segmentId": "A String", # A string that indicates the type of segment. For example, EVN or PID.
"setId": "A String", # Set ID for segments that can be in a set. This can be empty if it's missing or isn't applicable.
},
],
},
"patientIds": [ # All patient IDs listed in the PID-2, PID-3, and PID-4 segments of this message.
{ # A patient identifier and associated type.
"type": "A String", # ID type. For example, MRN or NHS.
"value": "A String", # The patient's unique identifier.
},
],
"schematizedData": { # The content of an HL7v2 message in a structured format as specified by a schema. # The parsed version of the raw message data schematized according to this store's schemas and type definitions.
"data": "A String", # JSON output of the parser.
"error": "A String", # The error output of the parser.
},
"sendFacility": "A String", # The hospital that this message came from. MSH-4.
"sendTime": "A String", # The datetime the sending application sent this message. MSH-7.
},
}
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format
Returns:
An object of the form:
{ # A complete HL7v2 message. See [Introduction to HL7 Standards] (https://www.hl7.org/implement/standards/index.cfm?ref=common) for details on the standard.
"createTime": "A String", # Output only. The datetime when the message was created. Set by the server.
"data": "A String", # Required. Raw message bytes.
"labels": { # User-supplied key-value pairs used to organize HL7v2 stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
"a_key": "A String",
},
"messageType": "A String", # The message type for this message. MSH-9.1.
"name": "A String", # Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server.
"parsedData": { # The content of an HL7v2 message in a structured format. # Output only. The parsed version of the raw message data.
"segments": [
{ # A segment in a structured format.
"fields": { # A mapping from the positional location to the value. The key string uses zero-based indexes separated by dots to identify Fields, components and sub-components. A bracket notation is also used to identify different instances of a repeated field. Regex for key: (\d+)(\[\d+\])?(.\d+)?(.\d+)? Examples of (key, value) pairs: * (0.1, "hemoglobin") denotes that the first component of Field 0 has the value "hemoglobin". * (1.1.2, "CBC") denotes that the second sub-component of the first component of Field 1 has the value "CBC". * (1[0].1, "HbA1c") denotes that the first component of the first Instance of Field 1, which is repeated, has the value "HbA1c".
"a_key": "A String",
},
"segmentId": "A String", # A string that indicates the type of segment. For example, EVN or PID.
"setId": "A String", # Set ID for segments that can be in a set. This can be empty if it's missing or isn't applicable.
},
],
},
"patientIds": [ # All patient IDs listed in the PID-2, PID-3, and PID-4 segments of this message.
{ # A patient identifier and associated type.
"type": "A String", # ID type. For example, MRN or NHS.
"value": "A String", # The patient's unique identifier.
},
],
"schematizedData": { # The content of an HL7v2 message in a structured format as specified by a schema. # The parsed version of the raw message data schematized according to this store's schemas and type definitions.
"data": "A String", # JSON output of the parser.
"error": "A String", # The error output of the parser.
},
"sendFacility": "A String", # The hospital that this message came from. MSH-4.
"sendTime": "A String", # The datetime the sending application sent this message. MSH-7.
}
delete(name, x__xgafv=None)
Deletes an HL7v2 message.
Args:
name: string, Required. The resource name of the HL7v2 message to delete. (required)
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format
Returns:
An object of the form:
{ # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }
}
get(name, view=None, x__xgafv=None)
Gets an HL7v2 message.
Args:
name: string, Required. The resource name of the HL7v2 message to retrieve. (required)
view: string, Specifies which parts of the Message resource to return in the response. When unspecified, equivalent to FULL.
Allowed values
MESSAGE_VIEW_UNSPECIFIED - Not specified, equivalent to FULL for getMessage, equivalent to BASIC for listMessages.
RAW_ONLY - Server responses include all the message fields except parsed_data, and schematized_data fields.
PARSED_ONLY - Server responses include all the message fields except data and schematized_data fields.
FULL - Server responses include all the message fields.
SCHEMATIZED_ONLY - Server responses include all the message fields except data and parsed_data fields.
BASIC - Server responses include only the name field.
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format
Returns:
An object of the form:
{ # A complete HL7v2 message. See [Introduction to HL7 Standards] (https://www.hl7.org/implement/standards/index.cfm?ref=common) for details on the standard.
"createTime": "A String", # Output only. The datetime when the message was created. Set by the server.
"data": "A String", # Required. Raw message bytes.
"labels": { # User-supplied key-value pairs used to organize HL7v2 stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
"a_key": "A String",
},
"messageType": "A String", # The message type for this message. MSH-9.1.
"name": "A String", # Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server.
"parsedData": { # The content of an HL7v2 message in a structured format. # Output only. The parsed version of the raw message data.
"segments": [
{ # A segment in a structured format.
"fields": { # A mapping from the positional location to the value. The key string uses zero-based indexes separated by dots to identify Fields, components and sub-components. A bracket notation is also used to identify different instances of a repeated field. Regex for key: (\d+)(\[\d+\])?(.\d+)?(.\d+)? Examples of (key, value) pairs: * (0.1, "hemoglobin") denotes that the first component of Field 0 has the value "hemoglobin". * (1.1.2, "CBC") denotes that the second sub-component of the first component of Field 1 has the value "CBC". * (1[0].1, "HbA1c") denotes that the first component of the first Instance of Field 1, which is repeated, has the value "HbA1c".
"a_key": "A String",
},
"segmentId": "A String", # A string that indicates the type of segment. For example, EVN or PID.
"setId": "A String", # Set ID for segments that can be in a set. This can be empty if it's missing or isn't applicable.
},
],
},
"patientIds": [ # All patient IDs listed in the PID-2, PID-3, and PID-4 segments of this message.
{ # A patient identifier and associated type.
"type": "A String", # ID type. For example, MRN or NHS.
"value": "A String", # The patient's unique identifier.
},
],
"schematizedData": { # The content of an HL7v2 message in a structured format as specified by a schema. # The parsed version of the raw message data schematized according to this store's schemas and type definitions.
"data": "A String", # JSON output of the parser.
"error": "A String", # The error output of the parser.
},
"sendFacility": "A String", # The hospital that this message came from. MSH-4.
"sendTime": "A String", # The datetime the sending application sent this message. MSH-7.
}
ingest(parent, body=None, x__xgafv=None)
Parses and stores an HL7v2 message. This method triggers an asynchronous notification to any Pub/Sub topic configured in Hl7V2Store.Hl7V2NotificationConfig, if the filtering matches the message. If an MLLP adapter is configured to listen to a Pub/Sub topic, the adapter transmits the message when a notification is received. If the method is successful, it generates a response containing an HL7v2 acknowledgment (`ACK`) message. If the method encounters an error, it returns a negative acknowledgment (`NACK`) message. This behavior is suitable for replying to HL7v2 interface systems that expect these acknowledgments.
Args:
parent: string, Required. The name of the HL7v2 store this message belongs to. (required)
body: object, The request body.
The object takes the form of:
{ # Ingests a message into the specified HL7v2 store.
"message": { # A complete HL7v2 message. See [Introduction to HL7 Standards] (https://www.hl7.org/implement/standards/index.cfm?ref=common) for details on the standard. # Required. HL7v2 message to ingest.
"createTime": "A String", # Output only. The datetime when the message was created. Set by the server.
"data": "A String", # Required. Raw message bytes.
"labels": { # User-supplied key-value pairs used to organize HL7v2 stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
"a_key": "A String",
},
"messageType": "A String", # The message type for this message. MSH-9.1.
"name": "A String", # Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server.
"parsedData": { # The content of an HL7v2 message in a structured format. # Output only. The parsed version of the raw message data.
"segments": [
{ # A segment in a structured format.
"fields": { # A mapping from the positional location to the value. The key string uses zero-based indexes separated by dots to identify Fields, components and sub-components. A bracket notation is also used to identify different instances of a repeated field. Regex for key: (\d+)(\[\d+\])?(.\d+)?(.\d+)? Examples of (key, value) pairs: * (0.1, "hemoglobin") denotes that the first component of Field 0 has the value "hemoglobin". * (1.1.2, "CBC") denotes that the second sub-component of the first component of Field 1 has the value "CBC". * (1[0].1, "HbA1c") denotes that the first component of the first Instance of Field 1, which is repeated, has the value "HbA1c".
"a_key": "A String",
},
"segmentId": "A String", # A string that indicates the type of segment. For example, EVN or PID.
"setId": "A String", # Set ID for segments that can be in a set. This can be empty if it's missing or isn't applicable.
},
],
},
"patientIds": [ # All patient IDs listed in the PID-2, PID-3, and PID-4 segments of this message.
{ # A patient identifier and associated type.
"type": "A String", # ID type. For example, MRN or NHS.
"value": "A String", # The patient's unique identifier.
},
],
"schematizedData": { # The content of an HL7v2 message in a structured format as specified by a schema. # The parsed version of the raw message data schematized according to this store's schemas and type definitions.
"data": "A String", # JSON output of the parser.
"error": "A String", # The error output of the parser.
},
"sendFacility": "A String", # The hospital that this message came from. MSH-4.
"sendTime": "A String", # The datetime the sending application sent this message. MSH-7.
},
}
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format
Returns:
An object of the form:
{ # Acknowledges that a message has been ingested into the specified HL7v2 store.
"hl7Ack": "A String", # HL7v2 ACK message.
"message": { # A complete HL7v2 message. See [Introduction to HL7 Standards] (https://www.hl7.org/implement/standards/index.cfm?ref=common) for details on the standard. # Created message resource.
"createTime": "A String", # Output only. The datetime when the message was created. Set by the server.
"data": "A String", # Required. Raw message bytes.
"labels": { # User-supplied key-value pairs used to organize HL7v2 stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
"a_key": "A String",
},
"messageType": "A String", # The message type for this message. MSH-9.1.
"name": "A String", # Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server.
"parsedData": { # The content of an HL7v2 message in a structured format. # Output only. The parsed version of the raw message data.
"segments": [
{ # A segment in a structured format.
"fields": { # A mapping from the positional location to the value. The key string uses zero-based indexes separated by dots to identify Fields, components and sub-components. A bracket notation is also used to identify different instances of a repeated field. Regex for key: (\d+)(\[\d+\])?(.\d+)?(.\d+)? Examples of (key, value) pairs: * (0.1, "hemoglobin") denotes that the first component of Field 0 has the value "hemoglobin". * (1.1.2, "CBC") denotes that the second sub-component of the first component of Field 1 has the value "CBC". * (1[0].1, "HbA1c") denotes that the first component of the first Instance of Field 1, which is repeated, has the value "HbA1c".
"a_key": "A String",
},
"segmentId": "A String", # A string that indicates the type of segment. For example, EVN or PID.
"setId": "A String", # Set ID for segments that can be in a set. This can be empty if it's missing or isn't applicable.
},
],
},
"patientIds": [ # All patient IDs listed in the PID-2, PID-3, and PID-4 segments of this message.
{ # A patient identifier and associated type.
"type": "A String", # ID type. For example, MRN or NHS.
"value": "A String", # The patient's unique identifier.
},
],
"schematizedData": { # The content of an HL7v2 message in a structured format as specified by a schema. # The parsed version of the raw message data schematized according to this store's schemas and type definitions.
"data": "A String", # JSON output of the parser.
"error": "A String", # The error output of the parser.
},
"sendFacility": "A String", # The hospital that this message came from. MSH-4.
"sendTime": "A String", # The datetime the sending application sent this message. MSH-7.
},
}
list(parent, filter=None, orderBy=None, pageSize=None, pageToken=None, view=None, x__xgafv=None)
Lists all the messages in the given HL7v2 store with support for filtering. Note: HL7v2 messages are indexed asynchronously, so there might be a slight delay between the time a message is created and when it can be found through a filter.
Args:
parent: string, Required. Name of the HL7v2 store to retrieve messages from. (required)
filter: string, 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"`. * `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"`. * `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":*`.
orderBy: string, 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`
pageSize: integer, Limit on the number of messages to return in a single response. If not specified, 100 is used. May not be larger than 1000.
pageToken: string, The next_page_token value returned from the previous List request, if any.
view: string, Specifies the parts of the Message to return in the response. When unspecified, equivalent to BASIC. Setting this to anything other than BASIC with a `page_size` larger than the default can generate a large response, which impacts the performance of this method.
Allowed values
MESSAGE_VIEW_UNSPECIFIED - Not specified, equivalent to FULL for getMessage, equivalent to BASIC for listMessages.
RAW_ONLY - Server responses include all the message fields except parsed_data, and schematized_data fields.
PARSED_ONLY - Server responses include all the message fields except data and schematized_data fields.
FULL - Server responses include all the message fields.
SCHEMATIZED_ONLY - Server responses include all the message fields except data and parsed_data fields.
BASIC - Server responses include only the name field.
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format
Returns:
An object of the form:
{ # Lists the messages in the specified HL7v2 store.
"hl7V2Messages": [ # The returned Messages. Won't be more Messages than the value of page_size in the request. See view for populated fields.
{ # A complete HL7v2 message. See [Introduction to HL7 Standards] (https://www.hl7.org/implement/standards/index.cfm?ref=common) for details on the standard.
"createTime": "A String", # Output only. The datetime when the message was created. Set by the server.
"data": "A String", # Required. Raw message bytes.
"labels": { # User-supplied key-value pairs used to organize HL7v2 stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
"a_key": "A String",
},
"messageType": "A String", # The message type for this message. MSH-9.1.
"name": "A String", # Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server.
"parsedData": { # The content of an HL7v2 message in a structured format. # Output only. The parsed version of the raw message data.
"segments": [
{ # A segment in a structured format.
"fields": { # A mapping from the positional location to the value. The key string uses zero-based indexes separated by dots to identify Fields, components and sub-components. A bracket notation is also used to identify different instances of a repeated field. Regex for key: (\d+)(\[\d+\])?(.\d+)?(.\d+)? Examples of (key, value) pairs: * (0.1, "hemoglobin") denotes that the first component of Field 0 has the value "hemoglobin". * (1.1.2, "CBC") denotes that the second sub-component of the first component of Field 1 has the value "CBC". * (1[0].1, "HbA1c") denotes that the first component of the first Instance of Field 1, which is repeated, has the value "HbA1c".
"a_key": "A String",
},
"segmentId": "A String", # A string that indicates the type of segment. For example, EVN or PID.
"setId": "A String", # Set ID for segments that can be in a set. This can be empty if it's missing or isn't applicable.
},
],
},
"patientIds": [ # All patient IDs listed in the PID-2, PID-3, and PID-4 segments of this message.
{ # A patient identifier and associated type.
"type": "A String", # ID type. For example, MRN or NHS.
"value": "A String", # The patient's unique identifier.
},
],
"schematizedData": { # The content of an HL7v2 message in a structured format as specified by a schema. # The parsed version of the raw message data schematized according to this store's schemas and type definitions.
"data": "A String", # JSON output of the parser.
"error": "A String", # The error output of the parser.
},
"sendFacility": "A String", # The hospital that this message came from. MSH-4.
"sendTime": "A String", # The datetime the sending application sent this message. MSH-7.
},
],
"nextPageToken": "A String", # Token to retrieve the next page of results or empty if there are no more results in the list.
}
list_next()
Retrieves the next page of results.
Args:
previous_request: The request for the previous page. (required)
previous_response: The response from the request for the previous page. (required)
Returns:
A request object that you can call 'execute()' on to request the next
page. Returns None if there are no more items in the collection.
patch(name, body=None, updateMask=None, x__xgafv=None)
Update the message. The contents of the message in Message.data and data extracted from the contents such as Message.create_time can't be altered. Only the Message.labels field is allowed to be updated. The labels in the request are merged with the existing set of labels. Existing labels with the same keys are updated.
Args:
name: string, Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server. (required)
body: object, The request body.
The object takes the form of:
{ # A complete HL7v2 message. See [Introduction to HL7 Standards] (https://www.hl7.org/implement/standards/index.cfm?ref=common) for details on the standard.
"createTime": "A String", # Output only. The datetime when the message was created. Set by the server.
"data": "A String", # Required. Raw message bytes.
"labels": { # User-supplied key-value pairs used to organize HL7v2 stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
"a_key": "A String",
},
"messageType": "A String", # The message type for this message. MSH-9.1.
"name": "A String", # Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server.
"parsedData": { # The content of an HL7v2 message in a structured format. # Output only. The parsed version of the raw message data.
"segments": [
{ # A segment in a structured format.
"fields": { # A mapping from the positional location to the value. The key string uses zero-based indexes separated by dots to identify Fields, components and sub-components. A bracket notation is also used to identify different instances of a repeated field. Regex for key: (\d+)(\[\d+\])?(.\d+)?(.\d+)? Examples of (key, value) pairs: * (0.1, "hemoglobin") denotes that the first component of Field 0 has the value "hemoglobin". * (1.1.2, "CBC") denotes that the second sub-component of the first component of Field 1 has the value "CBC". * (1[0].1, "HbA1c") denotes that the first component of the first Instance of Field 1, which is repeated, has the value "HbA1c".
"a_key": "A String",
},
"segmentId": "A String", # A string that indicates the type of segment. For example, EVN or PID.
"setId": "A String", # Set ID for segments that can be in a set. This can be empty if it's missing or isn't applicable.
},
],
},
"patientIds": [ # All patient IDs listed in the PID-2, PID-3, and PID-4 segments of this message.
{ # A patient identifier and associated type.
"type": "A String", # ID type. For example, MRN or NHS.
"value": "A String", # The patient's unique identifier.
},
],
"schematizedData": { # The content of an HL7v2 message in a structured format as specified by a schema. # The parsed version of the raw message data schematized according to this store's schemas and type definitions.
"data": "A String", # JSON output of the parser.
"error": "A String", # The error output of the parser.
},
"sendFacility": "A String", # The hospital that this message came from. MSH-4.
"sendTime": "A String", # The datetime the sending application sent this message. MSH-7.
}
updateMask: string, Required. The update mask applies to the resource. For the `FieldMask` definition, see https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#fieldmask
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format
Returns:
An object of the form:
{ # A complete HL7v2 message. See [Introduction to HL7 Standards] (https://www.hl7.org/implement/standards/index.cfm?ref=common) for details on the standard.
"createTime": "A String", # Output only. The datetime when the message was created. Set by the server.
"data": "A String", # Required. Raw message bytes.
"labels": { # User-supplied key-value pairs used to organize HL7v2 stores. Label keys must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: \p{Ll}\p{Lo}{0,62} Label values are optional, must be between 1 and 63 characters long, have a UTF-8 encoding of maximum 128 bytes, and must conform to the following PCRE regular expression: [\p{Ll}\p{Lo}\p{N}_-]{0,63} No more than 64 labels can be associated with a given store.
"a_key": "A String",
},
"messageType": "A String", # The message type for this message. MSH-9.1.
"name": "A String", # Output only. Resource name of the Message, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7_v2_store_id}/messages/{message_id}`. Assigned by the server.
"parsedData": { # The content of an HL7v2 message in a structured format. # Output only. The parsed version of the raw message data.
"segments": [
{ # A segment in a structured format.
"fields": { # A mapping from the positional location to the value. The key string uses zero-based indexes separated by dots to identify Fields, components and sub-components. A bracket notation is also used to identify different instances of a repeated field. Regex for key: (\d+)(\[\d+\])?(.\d+)?(.\d+)? Examples of (key, value) pairs: * (0.1, "hemoglobin") denotes that the first component of Field 0 has the value "hemoglobin". * (1.1.2, "CBC") denotes that the second sub-component of the first component of Field 1 has the value "CBC". * (1[0].1, "HbA1c") denotes that the first component of the first Instance of Field 1, which is repeated, has the value "HbA1c".
"a_key": "A String",
},
"segmentId": "A String", # A string that indicates the type of segment. For example, EVN or PID.
"setId": "A String", # Set ID for segments that can be in a set. This can be empty if it's missing or isn't applicable.
},
],
},
"patientIds": [ # All patient IDs listed in the PID-2, PID-3, and PID-4 segments of this message.
{ # A patient identifier and associated type.
"type": "A String", # ID type. For example, MRN or NHS.
"value": "A String", # The patient's unique identifier.
},
],
"schematizedData": { # The content of an HL7v2 message in a structured format as specified by a schema. # The parsed version of the raw message data schematized according to this store's schemas and type definitions.
"data": "A String", # JSON output of the parser.
"error": "A String", # The error output of the parser.
},
"sendFacility": "A String", # The hospital that this message came from. MSH-4.
"sendTime": "A String", # The datetime the sending application sent this message. MSH-7.
}