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.
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: https://cloud.google.com/feeds/cloud-healthcare-release-notes.xml
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.
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:
- Create and manage healthcare datasets
- Create and manage FHIR stores, DICOM stores, and HL7v2 stores
- Manage permissions
- View the status of long-running operations
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).