Release notes

This page documents production updates to Cloud Healthcare API. Check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.

You can see the latest product updates for all of Google Cloud on the Google Cloud page, or browse and filter all release notes in the Google Cloud Console.

To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly:

May 04, 2021


The defaultSearchHandlingStrict field in the projects.locations.datasets.fhirStores.FhirStore resource is now available in the v1 version of the Cloud Healthcare API.

April 23, 2021


The reference patterns document provides sample code and technical reference guides for common Cloud Healthcare API use cases.

April 20, 2021


Resource indexing will now complete before the service sends asynchronous notifications such as Pub/Sub notifications. This ensures that services receiving notifications through Pub/Sub can assume that the resource is searchable when the notification is received.

February 11, 2021


It is now possible to view the details of in-process long-running operations (LRO) from within the Healthcare Browser in the Cloud Console.

February 09, 2021


It is now possible set the value of the writeDisposition enum when exporting FHIR resources.

February 08, 2021


The Cloud Healthcare API now supports getting HL7v2 messages in bulk. See Retrieving HL7v2 messages in bulk.

February 04, 2021


The Quickstart using curl or Windows PowerShell has been updated with additional information on storing and viewing DICOM, FHIR, and HL7v2 data.

January 29, 2021


The Cloud Healthcare API offers single-region support in the us-east4 (North Virginia) region.

November 26, 2020


It is now possible to convert Clinical Document Architecture (CDA) XML files to JSON using the new XmlToJson tool.

November 05, 2020


The Cloud Healthcare API offers single-region support in the europe-west6 (Zurich, Switzerland) region.

October 12, 2020


October 08, 2020


The Consent Management API is available in beta.

October 07, 2020


The Cloud Healthcare API offers single-region support in the southamerica-east1 (Osasco (São Paulo), Brazil) region.

The Cloud Healthcare API offers single-region support in the australia-southeast1 (Sydney, Australia) region.

September 17, 2020


You can now configure a ParserVersion in an HL7v2 store, which allows you to set the version of the unschematized parser. A new parser version, V2, has been added, which allows parsedData to include every given non-empty message field. This version parses the MSH segment starting with the MSH-1 field and is in accordance with the HL7v2 standard.

September 08, 2020


Two new permissions, healthcare.locations.get and healthcare.locations.list, have been added to the IAM permissions. These permissions are checked whenever the new GetLocation and ListLocations methods are called.

August 26, 2020


The v1beta1 API has begun updating to a revised version. The update will occur over the next several weeks. View Updates to the v1beta1 API for a list of changes and how to update your client code.

August 03, 2020


The Cloud Healthcare API now supports importing HL7v2 messages from Cloud Storage. See Importing HL7v2 messages from Cloud Storage for more information.

June 08, 2020


It is now possible to de-identify data from within the Healthcare Browser in the Cloud Console.

June 02, 2020


It is now possible to import DICOM data to and export DICOM data from BigQuery using the Healthcare Browser in the Cloud Console. You can also import DICOM data from Cloud Storage using the Healthcare Browser.

May 29, 2020


The Cloud Healthcare API offers single-region support in the asia-east2 (Hong Kong) region.

May 26, 2020


Search results for DICOM studies and series might take several seconds to update after deleting an instance using instances.delete.

April 23, 2020


Code samples are available for the Cloud Healthcare API v1 in Go, Java, Node.js, and Python.

April 07, 2020


It is now possible to export resource changes to BigQuery each time a FHIR resource is created, updated, patched, or deleted in a FHIR store, using the new field for a store, streamConfigs.

You can now configure the HL7v2 store with multiple Pub/Sub topics and use filters to send notifications to different Pub/Sub topics.

General availability release Cloud Healthcare API is generally available with release version v1.

For information on the differences between the v1beta1 release and the v1 release, see Transitioning to the v1 API.

February 13, 2020


The messages field returned by the projects.locations.datasets.hl7V2Stores.messages.list method is deprecated. The method returns hl7_v2_messages, an array of messages. The new view input parameter specifies the fields to return. After the deprecation period ends on March 2, 2020, the method will only return hl7_v2_messages.

February 10, 2020


The Cloud Healthcare API supports all major release versions of the FHIR standard. You can specify DSTU2, STU3, or R4 when you create a FHIR store.

Required permissions for the FHIR store have changed. You can now grant user access as follows: * Access to APIs no longer includes read access to the FHIR store configuration.
* Access to the search API does not require get access. * Access to executeBundle does not give create, update, delete, or get permission.

Logging has been added for executeBundle.

October 24, 2019


DICOM and FHIR de-identification at the individual store level is now available in beta. De-identification using filters is also now available in beta. See the de-identification documentation for DICOM and FHIR data for more information.

September 24, 2019


Public access to the Cloud Healthcare API v1alpha2 version has been discontinued. Access to the v1alpha2 version is now restricted to Trusted Testers. To become a Trusted Tester, complete this form.

September 16, 2019


The Cloud Healthcare API offers single-region support in the asia-southeast1 (Singapore) and us-west2 (Los Angeles) regions.

September 12, 2019


Cloud Healthcare API gcloud tool commands are now available in gcloud beta.

August 13, 2019


DICOM de-identification supports an additional configuration option of not automatically regenerating unique identifiers (UIDs), such as StudyInstanceUID, SeriesInstanceUID, and SOPInstanceUID as part of the operation. See the documentation for more information on when you might want to enable this option.

July 26, 2019


The Cloud Healthcare API offers single-region support in the asia-northeast1 (Tokyo) region.

July 15, 2019


The Cloud Healthcare API offers single-region support in the europe-west4 (Netherlands) region.

July 10, 2019


The Cloud Healthcare API offers multi-region support in the us (United States) region.

June 19, 2019


DICOM de-identification has improved image output quality. There is now support for lossless image output for lossless image input formats.

April 04, 2019


The Google Cloud Console provides a user interface to the Cloud Healthcare API. The console allows you to:

An expanded set of configuration options are available for de-identification operations on DICOM and FHIR data. These options provide greater control over how resources (including pixel data) are processed. For details, see De-identifying sensitive data.

DICOMweb has improved performance.

DICOM has these conformance enhancements:

  • The API supports QIDO-RS result pagination, fuzzy patient-name matching, and transcoding additional DICOM transfer syntaxes, including lossless JPEG.
  • To avoid managing multipart headers on the client side, the API supports single-part WADO-RS and STOW-RS requests. See the DICOM conformance statement for details.

User labels on DICOM, HL7v2, and FHIR stores make it possible to filter resources and view billing charges based on label values.

Public beta release The Cloud Healthcare API provides a managed solution for storing and accessing healthcare data in Google Cloud Platform (GCP).