Cloud Healthcare API release notes

Getting all FHIR Encounter resource details is available in Preview.

Using customer-managed encryption keys (CMEK) to encrypt Cloud Healthcare API datasets is generally available (GA) and available in Preview. For more information, see Enable customer-managed encryption keys (CMEK) for Cloud Healthcare API datasets.

The fhir_read_ops, fhir_write_ops, and fhir_search_ops quota metrics are generally available (GA) and have replaced the legacy fhir_ops quota metric. For more information, see FHIR quotas.

Importing and exporting FHIR resources, including their historical versions, as history bundles using Cloud Storage is available in Preview.

Using a filter when exporting HL7v2 messages to Cloud Storage is generally available (GA) and available in Preview.

The Healthcare Natural Language API supports the following entity mention types in Preview:

• Oncology
• Social determinants of health (SDOH)
• Protected health information (PHI)

Explaining data access using FHIR is available in Preview.

You can use the Google Cloud console to view DICOM store metrics.

You can use the Google Cloud console to view HL7v2 store metrics.

Recover FHIR resources with point-in-time recovery (PITR) is generally available (GA).

You can use the Google Cloud console to enable FHIR implementation guides.

DICOM RetrieveBulkdata endpoint is available in Preview. This allows RetrieveMetadata to return BulkDataURIs for bulkdata tags. For more information, see Retrieve bulkdata.

Configuring Blob storage settings is now available in Preview. With this feature you can do the following:

• Specify a storage class to import DICOM objects
• Specify a storage class to store DICOM instances
• Change DICOM storage classes

Connecting to applications using SMART on FHIR in the Cloud Healthcare API is available in Preview.

Recover FHIR resources with point-in-time recovery (PITR) is available in Preview.

The Cloud Healthcare API offers multi-region support in the Europe (eu) region.

FHIR access control with admin cascading policy is available in Preview.

Pub/Sub notifications for DICOM store bulk import is generally available (GA).

The following conditional FHIR methods are generally available (GA) using the FHIR identifier search parameter:

• The fhir.create FHIR standard conditional create
• fhir.conditionalDelete
• fhir.conditionalPatch
• fhir.conditionalUpdate

You can extract the Healthcare Natural Language API entities as a FHIR R4 bundle, as an additional output format, when using the nlp.analyzeEntities method.

FHIR admin consent for FHIR access control is available in Preview.

Streaming DICOM metadata to BigQuery is generally available (GA).

The Cloud Healthcare API offers single-region support in the northamerica-northeast2 (Toronto, Canada) region.

The Cloud Healthcare API offers single-region support in the me-west1 (Tel Aviv, Israel) region.

The V3 HL7v2 store parser version is generally available (GA).

The Cloud Healthcare API offers single-region support in the asia-east1 (Taiwan) and the asia-northeast2 (Osaka, Japan) regions.

When you export DICOM metadata to BigQuery, the generated BigQuery table now contains two new columns, and contains metadata identifying if the DICOM instance in the DICOM store was deleted. For more information, see LastUpdated and Type columns.

FHIR access control is available in Preview.

The Cloud Healthcare API offers single-region support in the asia-southeast2 (Jakarta, Indonesia) region.

Improved performance when searching for large FHIR resources in the FHIR viewer.

Added the complexDataTypeReferenceParsing field to the FHIR store resource, which lets you parse references within complex FHIR data types, such as FHIR extensions.

When a FHIR resource is modified, the full contents of the FHIR resource can be sent in a Pub/Sub notification. For more information, see FHIR notifications containing FHIR data.

You can now specify PATCH requests in a FHIR bundle. This feature is available in Preview. See Executing a PATCH request in a FHIR bundle for more information.

The Cloud Healthcare API offers single-region support in the us-east1 (South Carolina) region.

The Cloud Healthcare API offers single-region support in the us-west1 (Oregon) region.

The Cloud Healthcare API offers single-region support in the us-west3 (Salt Lake City) region.

The _type and _since parameters are available for the fhirStores.export method. You can use these parameters to filter resources from exporting. This increases the speed of the export process and eliminates unwanted export data.

You can now stream and export FHIR resources to BigQuery using the FHIR analytics schema with support for repeated extension columns and contained resources as JSON strings.

The Healthcare Natural Language API now uses Vertex AI to extract medical insights from medical text. A new model is now used for healthcare-specific entity extraction.

It is now possible to validate a FHIR resource for a specific profile or for all profiles defined for a FHIR store to ensure that your FHIR resource conforms to one more profiles.

It is now possible to connect multiple FHIR stores within a dataset using federation. FHIR stores within a federated dataset are separate stores with separate access control and configuration, but FHIR references can refer across store boundaries with all the functionality normally available for references within the same store

It is now possible to determine the base resource validation level using the projects.locations.datasets.fhirStores.patch method.

An interactive version of the Cloud Healthcare API quickstart is now available in the Cloud Console. Access the quickstart.

The Cloud Healthcare API offers single-region support in the europe-west3 (Frankfurt) region.

The Cloud Healthcare API offers single-region support in the asia-northeast3 (Seoul) region.

The Cloud Healthcare API offers single-region support in the asia-south1 (Mumbai) region.

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

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

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

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

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

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

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

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

You can use the WriteDisposition enum to determine whether to overwrite or append to an existing BigQuery table when calling the following methods:

• projects.locations.datasets.dicomStores.export
• projects.locations.datasets.fhirStores.export
• projects.locations.datasets.annotationStores.export
• projects.locations.datasets.annotationStores.evaluate

The Consent Management API is available in beta.

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.

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.

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.

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

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

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.

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

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

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.

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.

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.

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

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

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.

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

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

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

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

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.