google-native logo
Google Cloud Native v0.27.0, Oct 21 22

google-native.healthcare/v1.Hl7V2Store

Creates a new HL7v2 store within the parent dataset.

Create Hl7V2Store Resource

new Hl7V2Store(name: string, args: Hl7V2StoreArgs, opts?: CustomResourceOptions);
@overload
def Hl7V2Store(resource_name: str,
               opts: Optional[ResourceOptions] = None,
               dataset_id: Optional[str] = None,
               hl7_v2_store_id: Optional[str] = None,
               labels: Optional[Mapping[str, str]] = None,
               location: Optional[str] = None,
               name: Optional[str] = None,
               notification_configs: Optional[Sequence[Hl7V2NotificationConfigArgs]] = None,
               parser_config: Optional[ParserConfigArgs] = None,
               project: Optional[str] = None,
               reject_duplicate_message: Optional[bool] = None)
@overload
def Hl7V2Store(resource_name: str,
               args: Hl7V2StoreArgs,
               opts: Optional[ResourceOptions] = None)
func NewHl7V2Store(ctx *Context, name string, args Hl7V2StoreArgs, opts ...ResourceOption) (*Hl7V2Store, error)
public Hl7V2Store(string name, Hl7V2StoreArgs args, CustomResourceOptions? opts = null)
public Hl7V2Store(String name, Hl7V2StoreArgs args)
public Hl7V2Store(String name, Hl7V2StoreArgs args, CustomResourceOptions options)
type: google-native:healthcare/v1:Hl7V2Store
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.

name string
The unique name of the resource.
args Hl7V2StoreArgs
The arguments to resource properties.
opts CustomResourceOptions
Bag of options to control resource's behavior.
resource_name str
The unique name of the resource.
args Hl7V2StoreArgs
The arguments to resource properties.
opts ResourceOptions
Bag of options to control resource's behavior.
ctx Context
Context object for the current deployment.
name string
The unique name of the resource.
args Hl7V2StoreArgs
The arguments to resource properties.
opts ResourceOption
Bag of options to control resource's behavior.
name string
The unique name of the resource.
args Hl7V2StoreArgs
The arguments to resource properties.
opts CustomResourceOptions
Bag of options to control resource's behavior.
name String
The unique name of the resource.
args Hl7V2StoreArgs
The arguments to resource properties.
options CustomResourceOptions
Bag of options to control resource's behavior.

Hl7V2Store Resource Properties

To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.

Inputs

The Hl7V2Store resource accepts the following input properties:

DatasetId string
Hl7V2StoreId string

The ID of the HL7v2 store that is being created. The string must match the following regex: [\p{L}\p{N}_\-\.]{1,256}.

Labels Dictionary<string, string>

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.

Location string
Name string

Resource name of the HL7v2 store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7v2_store_id}.

NotificationConfigs List<Pulumi.GoogleNative.Healthcare.V1.Inputs.Hl7V2NotificationConfigArgs>

A list of notification configs. Each configuration uses a filter to determine whether to publish a message (both Ingest & Create) on the corresponding notification destination. Only the message name is sent as part of the notification. Supplied by the client.

ParserConfig Pulumi.GoogleNative.Healthcare.V1.Inputs.ParserConfigArgs

The configuration for the parser. It determines how the server parses the messages.

Project string
RejectDuplicateMessage bool

Determines whether to reject duplicate messages. A duplicate message is a message with the same raw bytes as a message that has already been ingested/created in this HL7v2 store. The default value is false, meaning that the store accepts the duplicate messages and it also returns the same ACK message in the IngestMessageResponse as has been returned previously. Note that only one resource is created in the store. When this field is set to true, CreateMessage/IngestMessage requests with a duplicate message will be rejected by the store, and IngestMessageErrorDetail returns a NACK message upon rejection.

DatasetId string
Hl7V2StoreId string

The ID of the HL7v2 store that is being created. The string must match the following regex: [\p{L}\p{N}_\-\.]{1,256}.

Labels map[string]string

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.

Location string
Name string

Resource name of the HL7v2 store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7v2_store_id}.

NotificationConfigs []Hl7V2NotificationConfigArgs

A list of notification configs. Each configuration uses a filter to determine whether to publish a message (both Ingest & Create) on the corresponding notification destination. Only the message name is sent as part of the notification. Supplied by the client.

ParserConfig ParserConfigArgs

The configuration for the parser. It determines how the server parses the messages.

Project string
RejectDuplicateMessage bool

Determines whether to reject duplicate messages. A duplicate message is a message with the same raw bytes as a message that has already been ingested/created in this HL7v2 store. The default value is false, meaning that the store accepts the duplicate messages and it also returns the same ACK message in the IngestMessageResponse as has been returned previously. Note that only one resource is created in the store. When this field is set to true, CreateMessage/IngestMessage requests with a duplicate message will be rejected by the store, and IngestMessageErrorDetail returns a NACK message upon rejection.

datasetId String
hl7V2StoreId String

The ID of the HL7v2 store that is being created. The string must match the following regex: [\p{L}\p{N}_\-\.]{1,256}.

labels Map<String,String>

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.

location String
name String

Resource name of the HL7v2 store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7v2_store_id}.

notificationConfigs List<Hl7V2NotificationConfigArgs>

A list of notification configs. Each configuration uses a filter to determine whether to publish a message (both Ingest & Create) on the corresponding notification destination. Only the message name is sent as part of the notification. Supplied by the client.

parserConfig ParserConfigArgs

The configuration for the parser. It determines how the server parses the messages.

project String
rejectDuplicateMessage Boolean

Determines whether to reject duplicate messages. A duplicate message is a message with the same raw bytes as a message that has already been ingested/created in this HL7v2 store. The default value is false, meaning that the store accepts the duplicate messages and it also returns the same ACK message in the IngestMessageResponse as has been returned previously. Note that only one resource is created in the store. When this field is set to true, CreateMessage/IngestMessage requests with a duplicate message will be rejected by the store, and IngestMessageErrorDetail returns a NACK message upon rejection.

datasetId string
hl7V2StoreId string

The ID of the HL7v2 store that is being created. The string must match the following regex: [\p{L}\p{N}_\-\.]{1,256}.

labels {[key: string]: string}

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.

location string
name string

Resource name of the HL7v2 store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7v2_store_id}.

notificationConfigs Hl7V2NotificationConfigArgs[]

A list of notification configs. Each configuration uses a filter to determine whether to publish a message (both Ingest & Create) on the corresponding notification destination. Only the message name is sent as part of the notification. Supplied by the client.

parserConfig ParserConfigArgs

The configuration for the parser. It determines how the server parses the messages.

project string
rejectDuplicateMessage boolean

Determines whether to reject duplicate messages. A duplicate message is a message with the same raw bytes as a message that has already been ingested/created in this HL7v2 store. The default value is false, meaning that the store accepts the duplicate messages and it also returns the same ACK message in the IngestMessageResponse as has been returned previously. Note that only one resource is created in the store. When this field is set to true, CreateMessage/IngestMessage requests with a duplicate message will be rejected by the store, and IngestMessageErrorDetail returns a NACK message upon rejection.

dataset_id str
hl7_v2_store_id str

The ID of the HL7v2 store that is being created. The string must match the following regex: [\p{L}\p{N}_\-\.]{1,256}.

labels Mapping[str, str]

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.

location str
name str

Resource name of the HL7v2 store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7v2_store_id}.

notification_configs Sequence[Hl7V2NotificationConfigArgs]

A list of notification configs. Each configuration uses a filter to determine whether to publish a message (both Ingest & Create) on the corresponding notification destination. Only the message name is sent as part of the notification. Supplied by the client.

parser_config ParserConfigArgs

The configuration for the parser. It determines how the server parses the messages.

project str
reject_duplicate_message bool

Determines whether to reject duplicate messages. A duplicate message is a message with the same raw bytes as a message that has already been ingested/created in this HL7v2 store. The default value is false, meaning that the store accepts the duplicate messages and it also returns the same ACK message in the IngestMessageResponse as has been returned previously. Note that only one resource is created in the store. When this field is set to true, CreateMessage/IngestMessage requests with a duplicate message will be rejected by the store, and IngestMessageErrorDetail returns a NACK message upon rejection.

datasetId String
hl7V2StoreId String

The ID of the HL7v2 store that is being created. The string must match the following regex: [\p{L}\p{N}_\-\.]{1,256}.

labels Map<String>

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.

location String
name String

Resource name of the HL7v2 store, of the form projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7V2Stores/{hl7v2_store_id}.

notificationConfigs List<Property Map>

A list of notification configs. Each configuration uses a filter to determine whether to publish a message (both Ingest & Create) on the corresponding notification destination. Only the message name is sent as part of the notification. Supplied by the client.

parserConfig Property Map

The configuration for the parser. It determines how the server parses the messages.

project String
rejectDuplicateMessage Boolean

Determines whether to reject duplicate messages. A duplicate message is a message with the same raw bytes as a message that has already been ingested/created in this HL7v2 store. The default value is false, meaning that the store accepts the duplicate messages and it also returns the same ACK message in the IngestMessageResponse as has been returned previously. Note that only one resource is created in the store. When this field is set to true, CreateMessage/IngestMessage requests with a duplicate message will be rejected by the store, and IngestMessageErrorDetail returns a NACK message upon rejection.

Outputs

All input properties are implicitly available as output properties. Additionally, the Hl7V2Store resource produces the following output properties:

Id string

The provider-assigned unique ID for this managed resource.

Id string

The provider-assigned unique ID for this managed resource.

id String

The provider-assigned unique ID for this managed resource.

id string

The provider-assigned unique ID for this managed resource.

id str

The provider-assigned unique ID for this managed resource.

id String

The provider-assigned unique ID for this managed resource.

Supporting Types

Field

MaxOccurs int

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

MinOccurs int

The minimum number of times this field must be present/repeated.

Name string

The name of the field. For example, "PID-1" or just "1".

Table string

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

Type string

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

MaxOccurs int

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

MinOccurs int

The minimum number of times this field must be present/repeated.

Name string

The name of the field. For example, "PID-1" or just "1".

Table string

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

Type string

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

maxOccurs Integer

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

minOccurs Integer

The minimum number of times this field must be present/repeated.

name String

The name of the field. For example, "PID-1" or just "1".

table String

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

type String

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

maxOccurs number

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

minOccurs number

The minimum number of times this field must be present/repeated.

name string

The name of the field. For example, "PID-1" or just "1".

table string

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

type string

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

max_occurs int

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

min_occurs int

The minimum number of times this field must be present/repeated.

name str

The name of the field. For example, "PID-1" or just "1".

table str

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

type str

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

maxOccurs Number

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

minOccurs Number

The minimum number of times this field must be present/repeated.

name String

The name of the field. For example, "PID-1" or just "1".

table String

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

type String

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

FieldResponse

MaxOccurs int

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

MinOccurs int

The minimum number of times this field must be present/repeated.

Name string

The name of the field. For example, "PID-1" or just "1".

Table string

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

Type string

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

MaxOccurs int

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

MinOccurs int

The minimum number of times this field must be present/repeated.

Name string

The name of the field. For example, "PID-1" or just "1".

Table string

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

Type string

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

maxOccurs Integer

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

minOccurs Integer

The minimum number of times this field must be present/repeated.

name String

The name of the field. For example, "PID-1" or just "1".

table String

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

type String

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

maxOccurs number

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

minOccurs number

The minimum number of times this field must be present/repeated.

name string

The name of the field. For example, "PID-1" or just "1".

table string

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

type string

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

max_occurs int

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

min_occurs int

The minimum number of times this field must be present/repeated.

name str

The name of the field. For example, "PID-1" or just "1".

table str

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

type str

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

maxOccurs Number

The maximum number of times this field can be repeated. 0 or -1 means unbounded.

minOccurs Number

The minimum number of times this field must be present/repeated.

name String

The name of the field. For example, "PID-1" or just "1".

table String

The HL7v2 table this field refers to. For example, PID-15 (Patient's Primary Language) usually refers to table "0296".

type String

The type of this field. A Type with this name must be defined in an Hl7TypesConfig.

Hl7SchemaConfig

MessageSchemaConfigs Dictionary<string, string>

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

Version List<Pulumi.GoogleNative.Healthcare.V1.Inputs.VersionSource>

Each VersionSource is tested and only if they all match is the schema used for the message.

MessageSchemaConfigs map[string]string

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

Version []VersionSource

Each VersionSource is tested and only if they all match is the schema used for the message.

messageSchemaConfigs Map<String,String>

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

version List<VersionSource>

Each VersionSource is tested and only if they all match is the schema used for the message.

messageSchemaConfigs {[key: string]: string}

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

version VersionSource[]

Each VersionSource is tested and only if they all match is the schema used for the message.

message_schema_configs Mapping[str, str]

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

version Sequence[VersionSource]

Each VersionSource is tested and only if they all match is the schema used for the message.

messageSchemaConfigs Map<String>

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

version List<Property Map>

Each VersionSource is tested and only if they all match is the schema used for the message.

Hl7SchemaConfigResponse

MessageSchemaConfigs Dictionary<string, string>

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

Version List<Pulumi.GoogleNative.Healthcare.V1.Inputs.VersionSourceResponse>

Each VersionSource is tested and only if they all match is the schema used for the message.

MessageSchemaConfigs map[string]string

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

Version []VersionSourceResponse

Each VersionSource is tested and only if they all match is the schema used for the message.

messageSchemaConfigs Map<String,String>

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

version List<VersionSourceResponse>

Each VersionSource is tested and only if they all match is the schema used for the message.

messageSchemaConfigs {[key: string]: string}

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

version VersionSourceResponse[]

Each VersionSource is tested and only if they all match is the schema used for the message.

message_schema_configs Mapping[str, str]

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

version Sequence[VersionSourceResponse]

Each VersionSource is tested and only if they all match is the schema used for the message.

messageSchemaConfigs Map<String>

Map from each HL7v2 message type and trigger event pair, such as ADT_A04, to its schema configuration root group.

version List<Property Map>

Each VersionSource is tested and only if they all match is the schema used for the message.

Hl7TypesConfig

Type List<Pulumi.GoogleNative.Healthcare.V1.Inputs.Type>

The HL7v2 type definitions.

Version List<Pulumi.GoogleNative.Healthcare.V1.Inputs.VersionSource>

The version selectors that this config applies to. A message must match ALL version sources to apply.

Type []Type

The HL7v2 type definitions.

Version []VersionSource

The version selectors that this config applies to. A message must match ALL version sources to apply.

type List<Type>

The HL7v2 type definitions.

version List<VersionSource>

The version selectors that this config applies to. A message must match ALL version sources to apply.

type Type[]

The HL7v2 type definitions.

version VersionSource[]

The version selectors that this config applies to. A message must match ALL version sources to apply.

type Sequence[Type]

The HL7v2 type definitions.

version Sequence[VersionSource]

The version selectors that this config applies to. A message must match ALL version sources to apply.

type List<Property Map>

The HL7v2 type definitions.

version List<Property Map>

The version selectors that this config applies to. A message must match ALL version sources to apply.

Hl7TypesConfigResponse

Type List<Pulumi.GoogleNative.Healthcare.V1.Inputs.TypeResponse>

The HL7v2 type definitions.

Version List<Pulumi.GoogleNative.Healthcare.V1.Inputs.VersionSourceResponse>

The version selectors that this config applies to. A message must match ALL version sources to apply.

Type []TypeResponse

The HL7v2 type definitions.

Version []VersionSourceResponse

The version selectors that this config applies to. A message must match ALL version sources to apply.

type List<TypeResponse>

The HL7v2 type definitions.

version List<VersionSourceResponse>

The version selectors that this config applies to. A message must match ALL version sources to apply.

type TypeResponse[]

The HL7v2 type definitions.

version VersionSourceResponse[]

The version selectors that this config applies to. A message must match ALL version sources to apply.

type Sequence[TypeResponse]

The HL7v2 type definitions.

version Sequence[VersionSourceResponse]

The version selectors that this config applies to. A message must match ALL version sources to apply.

type List<Property Map>

The HL7v2 type definitions.

version List<Property Map>

The version selectors that this config applies to. A message must match ALL version sources to apply.

Hl7V2NotificationConfig

Filter string

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

PubsubTopic string

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

Filter string

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

PubsubTopic string

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

filter String

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

pubsubTopic String

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

filter string

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

pubsubTopic string

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

filter str

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

pubsub_topic str

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

filter String

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

pubsubTopic String

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

Hl7V2NotificationConfigResponse

Filter string

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

PubsubTopic string

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

Filter string

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

PubsubTopic string

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

filter String

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

pubsubTopic String

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

filter string

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

pubsubTopic string

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

filter str

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

pubsub_topic str

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

filter String

Restricts notifications sent for messages matching a filter. If this is empty, 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". * 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":*.

pubsubTopic String

The Pub/Sub topic that notifications of changes are published on. Supplied by the client. The notification is a PubsubMessage with the following fields: * PubsubMessage.Data contains the resource name. * PubsubMessage.MessageId is the ID of this notification. It's guaranteed to be unique within the topic. * PubsubMessage.PublishTime is the time when the message was published. Note that notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. The Cloud Healthcare API service account, service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com, must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification cannot be published to Pub/Sub, errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging).

ParserConfig

AllowNullHeader bool

Determines whether messages with no header are allowed.

Schema Pulumi.GoogleNative.Healthcare.V1.Inputs.SchemaPackage

Schemas used to parse messages in this store, if schematized parsing is desired.

SegmentTerminator string

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

Version Pulumi.GoogleNative.Healthcare.V1.ParserConfigVersion

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

AllowNullHeader bool

Determines whether messages with no header are allowed.

Schema SchemaPackage

Schemas used to parse messages in this store, if schematized parsing is desired.

SegmentTerminator string

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

Version ParserConfigVersion

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

allowNullHeader Boolean

Determines whether messages with no header are allowed.

schema SchemaPackage

Schemas used to parse messages in this store, if schematized parsing is desired.

segmentTerminator String

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

version ParserConfigVersion

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

allowNullHeader boolean

Determines whether messages with no header are allowed.

schema SchemaPackage

Schemas used to parse messages in this store, if schematized parsing is desired.

segmentTerminator string

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

version ParserConfigVersion

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

allow_null_header bool

Determines whether messages with no header are allowed.

schema SchemaPackage

Schemas used to parse messages in this store, if schematized parsing is desired.

segment_terminator str

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

version ParserConfigVersion

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

allowNullHeader Boolean

Determines whether messages with no header are allowed.

schema Property Map

Schemas used to parse messages in this store, if schematized parsing is desired.

segmentTerminator String

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

version "PARSER_VERSION_UNSPECIFIED" | "V1" | "V2"

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

ParserConfigResponse

AllowNullHeader bool

Determines whether messages with no header are allowed.

Schema Pulumi.GoogleNative.Healthcare.V1.Inputs.SchemaPackageResponse

Schemas used to parse messages in this store, if schematized parsing is desired.

SegmentTerminator string

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

Version string

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

AllowNullHeader bool

Determines whether messages with no header are allowed.

Schema SchemaPackageResponse

Schemas used to parse messages in this store, if schematized parsing is desired.

SegmentTerminator string

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

Version string

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

allowNullHeader Boolean

Determines whether messages with no header are allowed.

schema SchemaPackageResponse

Schemas used to parse messages in this store, if schematized parsing is desired.

segmentTerminator String

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

version String

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

allowNullHeader boolean

Determines whether messages with no header are allowed.

schema SchemaPackageResponse

Schemas used to parse messages in this store, if schematized parsing is desired.

segmentTerminator string

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

version string

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

allow_null_header bool

Determines whether messages with no header are allowed.

schema SchemaPackageResponse

Schemas used to parse messages in this store, if schematized parsing is desired.

segment_terminator str

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

version str

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

allowNullHeader Boolean

Determines whether messages with no header are allowed.

schema Property Map

Schemas used to parse messages in this store, if schematized parsing is desired.

segmentTerminator String

Byte(s) to use as the segment terminator. If this is unset, '\r' is used as segment terminator, matching the HL7 version 2 specification.

version String

Immutable. Determines the version of both the default parser to be used when schema is not given, as well as the schematized parser used when schema is specified. This field is immutable after HL7v2 store creation.

ParserConfigVersion

ParserVersionUnspecified
PARSER_VERSION_UNSPECIFIED

Unspecified parser version, equivalent to V1.

V1
V1

The parsed_data includes every given non-empty message field except the Field Separator (MSH-1) field. As a result, the parsed MSH segment starts with the MSH-2 field and the field numbers are off-by-one with respect to the HL7 standard.

V2
V2

The parsed_data includes every given non-empty message field.

ParserConfigVersionParserVersionUnspecified
PARSER_VERSION_UNSPECIFIED

Unspecified parser version, equivalent to V1.

ParserConfigVersionV1
V1

The parsed_data includes every given non-empty message field except the Field Separator (MSH-1) field. As a result, the parsed MSH segment starts with the MSH-2 field and the field numbers are off-by-one with respect to the HL7 standard.

ParserConfigVersionV2
V2

The parsed_data includes every given non-empty message field.

ParserVersionUnspecified
PARSER_VERSION_UNSPECIFIED

Unspecified parser version, equivalent to V1.

V1
V1

The parsed_data includes every given non-empty message field except the Field Separator (MSH-1) field. As a result, the parsed MSH segment starts with the MSH-2 field and the field numbers are off-by-one with respect to the HL7 standard.

V2
V2

The parsed_data includes every given non-empty message field.

ParserVersionUnspecified
PARSER_VERSION_UNSPECIFIED

Unspecified parser version, equivalent to V1.

V1
V1

The parsed_data includes every given non-empty message field except the Field Separator (MSH-1) field. As a result, the parsed MSH segment starts with the MSH-2 field and the field numbers are off-by-one with respect to the HL7 standard.

V2
V2

The parsed_data includes every given non-empty message field.

PARSER_VERSION_UNSPECIFIED
PARSER_VERSION_UNSPECIFIED

Unspecified parser version, equivalent to V1.

V1
V1

The parsed_data includes every given non-empty message field except the Field Separator (MSH-1) field. As a result, the parsed MSH segment starts with the MSH-2 field and the field numbers are off-by-one with respect to the HL7 standard.

V2
V2

The parsed_data includes every given non-empty message field.

"PARSER_VERSION_UNSPECIFIED"
PARSER_VERSION_UNSPECIFIED

Unspecified parser version, equivalent to V1.

"V1"
V1

The parsed_data includes every given non-empty message field except the Field Separator (MSH-1) field. As a result, the parsed MSH segment starts with the MSH-2 field and the field numbers are off-by-one with respect to the HL7 standard.

"V2"
V2

The parsed_data includes every given non-empty message field.

SchemaPackage

IgnoreMinOccurs bool

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

Schemas List<Pulumi.GoogleNative.Healthcare.V1.Inputs.Hl7SchemaConfig>

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

SchematizedParsingType Pulumi.GoogleNative.Healthcare.V1.SchemaPackageSchematizedParsingType

Determines how messages that fail to parse are handled.

Types List<Pulumi.GoogleNative.Healthcare.V1.Inputs.Hl7TypesConfig>

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

UnexpectedSegmentHandling Pulumi.GoogleNative.Healthcare.V1.SchemaPackageUnexpectedSegmentHandling

Determines how unexpected segments (segments not matched to the schema) are handled.

IgnoreMinOccurs bool

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

Schemas []Hl7SchemaConfig

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

SchematizedParsingType SchemaPackageSchematizedParsingType

Determines how messages that fail to parse are handled.

Types []Hl7TypesConfig

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

UnexpectedSegmentHandling SchemaPackageUnexpectedSegmentHandling

Determines how unexpected segments (segments not matched to the schema) are handled.

ignoreMinOccurs Boolean

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

schemas List<Hl7SchemaConfig>

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

schematizedParsingType SchemaPackageSchematizedParsingType

Determines how messages that fail to parse are handled.

types List<Hl7TypesConfig>

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

unexpectedSegmentHandling SchemaPackageUnexpectedSegmentHandling

Determines how unexpected segments (segments not matched to the schema) are handled.

ignoreMinOccurs boolean

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

schemas Hl7SchemaConfig[]

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

schematizedParsingType SchemaPackageSchematizedParsingType

Determines how messages that fail to parse are handled.

types Hl7TypesConfig[]

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

unexpectedSegmentHandling SchemaPackageUnexpectedSegmentHandling

Determines how unexpected segments (segments not matched to the schema) are handled.

ignore_min_occurs bool

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

schemas Sequence[Hl7SchemaConfig]

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

schematized_parsing_type SchemaPackageSchematizedParsingType

Determines how messages that fail to parse are handled.

types Sequence[Hl7TypesConfig]

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

unexpected_segment_handling SchemaPackageUnexpectedSegmentHandling

Determines how unexpected segments (segments not matched to the schema) are handled.

ignoreMinOccurs Boolean

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

schemas List<Property Map>

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

schematizedParsingType "SCHEMATIZED_PARSING_TYPE_UNSPECIFIED" | "SOFT_FAIL" | "HARD_FAIL"

Determines how messages that fail to parse are handled.

types List<Property Map>

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

unexpectedSegmentHandling "UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED" | "FAIL" | "SKIP" | "PARSE"

Determines how unexpected segments (segments not matched to the schema) are handled.

SchemaPackageResponse

IgnoreMinOccurs bool

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

Schemas List<Pulumi.GoogleNative.Healthcare.V1.Inputs.Hl7SchemaConfigResponse>

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

SchematizedParsingType string

Determines how messages that fail to parse are handled.

Types List<Pulumi.GoogleNative.Healthcare.V1.Inputs.Hl7TypesConfigResponse>

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

UnexpectedSegmentHandling string

Determines how unexpected segments (segments not matched to the schema) are handled.

IgnoreMinOccurs bool

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

Schemas []Hl7SchemaConfigResponse

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

SchematizedParsingType string

Determines how messages that fail to parse are handled.

Types []Hl7TypesConfigResponse

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

UnexpectedSegmentHandling string

Determines how unexpected segments (segments not matched to the schema) are handled.

ignoreMinOccurs Boolean

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

schemas List<Hl7SchemaConfigResponse>

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

schematizedParsingType String

Determines how messages that fail to parse are handled.

types List<Hl7TypesConfigResponse>

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

unexpectedSegmentHandling String

Determines how unexpected segments (segments not matched to the schema) are handled.

ignoreMinOccurs boolean

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

schemas Hl7SchemaConfigResponse[]

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

schematizedParsingType string

Determines how messages that fail to parse are handled.

types Hl7TypesConfigResponse[]

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

unexpectedSegmentHandling string

Determines how unexpected segments (segments not matched to the schema) are handled.

ignore_min_occurs bool

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

schemas Sequence[Hl7SchemaConfigResponse]

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

schematized_parsing_type str

Determines how messages that fail to parse are handled.

types Sequence[Hl7TypesConfigResponse]

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

unexpected_segment_handling str

Determines how unexpected segments (segments not matched to the schema) are handled.

ignoreMinOccurs Boolean

Flag to ignore all min_occurs restrictions in the schema. This means that incoming messages can omit any group, segment, field, component, or subcomponent.

schemas List<Property Map>

Schema configs that are layered based on their VersionSources that match the incoming message. Schema configs present in higher indices override those in lower indices with the same message type and trigger event if their VersionSources all match an incoming message.

schematizedParsingType String

Determines how messages that fail to parse are handled.

types List<Property Map>

Schema type definitions that are layered based on their VersionSources that match the incoming message. Type definitions present in higher indices override those in lower indices with the same type name if their VersionSources all match an incoming message.

unexpectedSegmentHandling String

Determines how unexpected segments (segments not matched to the schema) are handled.

SchemaPackageSchematizedParsingType

SchematizedParsingTypeUnspecified
SCHEMATIZED_PARSING_TYPE_UNSPECIFIED

Unspecified schematized parsing type, equivalent to SOFT_FAIL.

SoftFail
SOFT_FAIL

Messages that fail to parse are still stored and ACKed but a parser error is stored in place of the schematized data.

HardFail
HARD_FAIL

Messages that fail to parse are rejected from ingestion/insertion and return an error code.

SchemaPackageSchematizedParsingTypeSchematizedParsingTypeUnspecified
SCHEMATIZED_PARSING_TYPE_UNSPECIFIED

Unspecified schematized parsing type, equivalent to SOFT_FAIL.

SchemaPackageSchematizedParsingTypeSoftFail
SOFT_FAIL

Messages that fail to parse are still stored and ACKed but a parser error is stored in place of the schematized data.

SchemaPackageSchematizedParsingTypeHardFail
HARD_FAIL

Messages that fail to parse are rejected from ingestion/insertion and return an error code.

SchematizedParsingTypeUnspecified
SCHEMATIZED_PARSING_TYPE_UNSPECIFIED

Unspecified schematized parsing type, equivalent to SOFT_FAIL.

SoftFail
SOFT_FAIL

Messages that fail to parse are still stored and ACKed but a parser error is stored in place of the schematized data.

HardFail
HARD_FAIL

Messages that fail to parse are rejected from ingestion/insertion and return an error code.

SchematizedParsingTypeUnspecified
SCHEMATIZED_PARSING_TYPE_UNSPECIFIED

Unspecified schematized parsing type, equivalent to SOFT_FAIL.

SoftFail
SOFT_FAIL

Messages that fail to parse are still stored and ACKed but a parser error is stored in place of the schematized data.

HardFail
HARD_FAIL

Messages that fail to parse are rejected from ingestion/insertion and return an error code.

SCHEMATIZED_PARSING_TYPE_UNSPECIFIED
SCHEMATIZED_PARSING_TYPE_UNSPECIFIED

Unspecified schematized parsing type, equivalent to SOFT_FAIL.

SOFT_FAIL
SOFT_FAIL

Messages that fail to parse are still stored and ACKed but a parser error is stored in place of the schematized data.

HARD_FAIL
HARD_FAIL

Messages that fail to parse are rejected from ingestion/insertion and return an error code.

"SCHEMATIZED_PARSING_TYPE_UNSPECIFIED"
SCHEMATIZED_PARSING_TYPE_UNSPECIFIED

Unspecified schematized parsing type, equivalent to SOFT_FAIL.

"SOFT_FAIL"
SOFT_FAIL

Messages that fail to parse are still stored and ACKed but a parser error is stored in place of the schematized data.

"HARD_FAIL"
HARD_FAIL

Messages that fail to parse are rejected from ingestion/insertion and return an error code.

SchemaPackageUnexpectedSegmentHandling

UnexpectedSegmentHandlingModeUnspecified
UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED

Unspecified handling mode, equivalent to FAIL.

Fail
FAIL

Unexpected segments fail to parse and return an error.

Skip
SKIP

Unexpected segments do not fail, but are omitted from the output.

Parse
PARSE

Unexpected segments do not fail, but are parsed in place and added to the current group. If a segment has a type definition, it is used, otherwise it is parsed as VARIES.

SchemaPackageUnexpectedSegmentHandlingUnexpectedSegmentHandlingModeUnspecified
UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED

Unspecified handling mode, equivalent to FAIL.

SchemaPackageUnexpectedSegmentHandlingFail
FAIL

Unexpected segments fail to parse and return an error.

SchemaPackageUnexpectedSegmentHandlingSkip
SKIP

Unexpected segments do not fail, but are omitted from the output.

SchemaPackageUnexpectedSegmentHandlingParse
PARSE

Unexpected segments do not fail, but are parsed in place and added to the current group. If a segment has a type definition, it is used, otherwise it is parsed as VARIES.

UnexpectedSegmentHandlingModeUnspecified
UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED

Unspecified handling mode, equivalent to FAIL.

Fail
FAIL

Unexpected segments fail to parse and return an error.

Skip
SKIP

Unexpected segments do not fail, but are omitted from the output.

Parse
PARSE

Unexpected segments do not fail, but are parsed in place and added to the current group. If a segment has a type definition, it is used, otherwise it is parsed as VARIES.

UnexpectedSegmentHandlingModeUnspecified
UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED

Unspecified handling mode, equivalent to FAIL.

Fail
FAIL

Unexpected segments fail to parse and return an error.

Skip
SKIP

Unexpected segments do not fail, but are omitted from the output.

Parse
PARSE

Unexpected segments do not fail, but are parsed in place and added to the current group. If a segment has a type definition, it is used, otherwise it is parsed as VARIES.

UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED
UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED

Unspecified handling mode, equivalent to FAIL.

FAIL
FAIL

Unexpected segments fail to parse and return an error.

SKIP
SKIP

Unexpected segments do not fail, but are omitted from the output.

PARSE
PARSE

Unexpected segments do not fail, but are parsed in place and added to the current group. If a segment has a type definition, it is used, otherwise it is parsed as VARIES.

"UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED"
UNEXPECTED_SEGMENT_HANDLING_MODE_UNSPECIFIED

Unspecified handling mode, equivalent to FAIL.

"FAIL"
FAIL

Unexpected segments fail to parse and return an error.

"SKIP"
SKIP

Unexpected segments do not fail, but are omitted from the output.

"PARSE"
PARSE

Unexpected segments do not fail, but are parsed in place and added to the current group. If a segment has a type definition, it is used, otherwise it is parsed as VARIES.

Type

Fields List<Pulumi.GoogleNative.Healthcare.V1.Inputs.Field>

The (sub) fields this type has (if not primitive).

Name string

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

Primitive Pulumi.GoogleNative.Healthcare.V1.TypePrimitive

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

Fields []Field

The (sub) fields this type has (if not primitive).

Name string

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

Primitive TypePrimitive

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

fields List<Field>

The (sub) fields this type has (if not primitive).

name String

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

primitive TypePrimitive

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

fields Field[]

The (sub) fields this type has (if not primitive).

name string

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

primitive TypePrimitive

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

fields Sequence[Field]

The (sub) fields this type has (if not primitive).

name str

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

primitive TypePrimitive

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

fields List<Property Map>

The (sub) fields this type has (if not primitive).

name String

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

primitive "PRIMITIVE_UNSPECIFIED" | "STRING" | "VARIES" | "UNESCAPED_STRING"

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

TypePrimitive

PrimitiveUnspecified
PRIMITIVE_UNSPECIFIED

Not a primitive.

String
STRING

String primitive.

Varies
VARIES

Element that can have unschematized children.

UnescapedString
UNESCAPED_STRING

Like STRING, but all delimiters below this element are ignored.

TypePrimitivePrimitiveUnspecified
PRIMITIVE_UNSPECIFIED

Not a primitive.

TypePrimitiveString
STRING

String primitive.

TypePrimitiveVaries
VARIES

Element that can have unschematized children.

TypePrimitiveUnescapedString
UNESCAPED_STRING

Like STRING, but all delimiters below this element are ignored.

PrimitiveUnspecified
PRIMITIVE_UNSPECIFIED

Not a primitive.

String
STRING

String primitive.

Varies
VARIES

Element that can have unschematized children.

UnescapedString
UNESCAPED_STRING

Like STRING, but all delimiters below this element are ignored.

PrimitiveUnspecified
PRIMITIVE_UNSPECIFIED

Not a primitive.

String
STRING

String primitive.

Varies
VARIES

Element that can have unschematized children.

UnescapedString
UNESCAPED_STRING

Like STRING, but all delimiters below this element are ignored.

PRIMITIVE_UNSPECIFIED
PRIMITIVE_UNSPECIFIED

Not a primitive.

STRING
STRING

String primitive.

VARIES
VARIES

Element that can have unschematized children.

UNESCAPED_STRING
UNESCAPED_STRING

Like STRING, but all delimiters below this element are ignored.

"PRIMITIVE_UNSPECIFIED"
PRIMITIVE_UNSPECIFIED

Not a primitive.

"STRING"
STRING

String primitive.

"VARIES"
VARIES

Element that can have unschematized children.

"UNESCAPED_STRING"
UNESCAPED_STRING

Like STRING, but all delimiters below this element are ignored.

TypeResponse

Fields List<Pulumi.GoogleNative.Healthcare.V1.Inputs.FieldResponse>

The (sub) fields this type has (if not primitive).

Name string

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

Primitive string

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

Fields []FieldResponse

The (sub) fields this type has (if not primitive).

Name string

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

Primitive string

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

fields List<FieldResponse>

The (sub) fields this type has (if not primitive).

name String

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

primitive String

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

fields FieldResponse[]

The (sub) fields this type has (if not primitive).

name string

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

primitive string

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

fields Sequence[FieldResponse]

The (sub) fields this type has (if not primitive).

name str

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

primitive str

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

fields List<Property Map>

The (sub) fields this type has (if not primitive).

name String

The name of this type. This would be the segment or datatype name. For example, "PID" or "XPN".

primitive String

If this is a primitive type then this field is the type of the primitive For example, STRING. Leave unspecified for composite types.

VersionSource

MshField string

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

Value string

The value to match with the field. For example, "My Application Name" or "2.3".

MshField string

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

Value string

The value to match with the field. For example, "My Application Name" or "2.3".

mshField String

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

value String

The value to match with the field. For example, "My Application Name" or "2.3".

mshField string

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

value string

The value to match with the field. For example, "My Application Name" or "2.3".

msh_field str

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

value str

The value to match with the field. For example, "My Application Name" or "2.3".

mshField String

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

value String

The value to match with the field. For example, "My Application Name" or "2.3".

VersionSourceResponse

MshField string

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

Value string

The value to match with the field. For example, "My Application Name" or "2.3".

MshField string

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

Value string

The value to match with the field. For example, "My Application Name" or "2.3".

mshField String

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

value String

The value to match with the field. For example, "My Application Name" or "2.3".

mshField string

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

value string

The value to match with the field. For example, "My Application Name" or "2.3".

msh_field str

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

value str

The value to match with the field. For example, "My Application Name" or "2.3".

mshField String

The field to extract from the MSH segment. For example, "3.1" or "18[1].1".

value String

The value to match with the field. For example, "My Application Name" or "2.3".

Package Details

Repository
Google Cloud Native pulumi/pulumi-google-native
License
Apache-2.0