Google Cloud Healthcare HL7 V2 Store

This page shows how to write Terraform for Cloud Healthcare HL7 V2 Store and write them securely.

google_healthcare_hl7_v2_store (Terraform)

The HL7 V2 Store in Cloud Healthcare can be configured in Terraform with the resource name google_healthcare_hl7_v2_store. The following sections describe 1 example of how to use the resource and its parameters.

Example Usage from GitHub

main.tf#L7
resource "google_healthcare_hl7_v2_store" "this" {
  dataset = var.dataset
  labels  = var.labels
  name    = var.name

  dynamic "notification_config" {

Review your Terraform file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

Identifies the dataset addressed by this request. Must be in the format 'projects/[project]/locations/[location]/datasets/[dataset]'

  • id optional computed - string
  • labels optional - map from string to 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]][p[Ll]p[Lo]p[N]_-][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. An object containing a list of "key": value pairs. Example: [ "name": "wrench", "mass": "1.3kg", "count": "3" ].

The resource name for the Hl7V2Store. Changing this property may recreate the Hl7v2 store (removing all data)

The fully qualified name of this dataset

  • notification_config list block

    The Cloud Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data will contain the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com must have publisher permissions on the given Cloud Pub/Sub topic. Not having adequate permissions will cause the calls that send notifications to fail.

  • notification_configs list block

    Restricts notifications sent for messages matching a filter. If this is empty, all messages are matched. Syntax: https://cloud.google.com/appengine/docs/standard/python/search/query_strings Fields/functions available for filtering are: messageType, from the MSH-9.1 field. For example, NOT messageType = "ADT". senddate or sendDate, the YYYY-MM-DD date the message was sent in the dataset's timeZone, from the MSH-7 segment. For example, send_date < "2017-01-02". sendTime, the timestamp when the message was sent, using the RFC3339 time format for comparisons, from the MSH-7 segment. For example, sendTime < "2017-01-02T00:00:00-05:00". sendFacility, the care center that the message came from, from the MSH-4 segment. For example, sendFacility = "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":_.

    The Cloud Pub/Sub topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data will contain the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. Topic names must be scoped to a project. service-PROJECT_NUMBER@gcp-sa-healthcare.iam.gserviceaccount.com must have publisher permissions on the given Cloud Pub/Sub topic. Not having adequate permissions will cause the calls that send notifications to fail. If a notification cannot be published to Cloud Pub/Sub, errors will be logged to Stackdriver

  • parser_config list block

    Determines whether messages with no header are allowed.

    JSON encoded string for schemas used to parse messages in this store if schematized parsing is desired.

    Byte(s) to be used as the segment terminator. If this is unset, 'r' will be used as segment terminator. A base64-encoded string.

  • timeouts single block

Explanation in Terraform Registry

A Hl7V2Store is a datastore inside a Healthcare dataset that conforms to the FHIR (https://www.hl7.org/hl7V2/STU3/) standard for Healthcare information exchange To get more information about Hl7V2Store, see:

Frequently asked questions

What is Google Cloud Healthcare HL7 V2 Store?

Google Cloud Healthcare HL7 V2 Store is a resource for Cloud Healthcare of Google Cloud Platform. Settings can be wrote in Terraform.

Where can I find the example code for the Google Cloud Healthcare HL7 V2 Store?

For Terraform, the niveklabs/google source code example is useful. See the Terraform Example section for further details.

security-icon

Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.