Method: dicomStores.export

Full name: projects.locations.datasets.dicomStores.export

Exports data to the specified destination by copying it from the DICOM store. Errors are also logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging. The metadata field type is OperationMetadata.

HTTP request


The URL uses gRPC Transcoding syntax.

Path parameters



Required. The DICOM store resource name from which to export the data. For example, projects/{projectId}/locations/{locationId}/datasets/{datasetId}/dicomStores/{dicomStoreId}.

Authorization requires the following IAM permission on the specified resource name:

  • healthcare.dicomStores.export

Request body

The request body contains data with the following structure:

JSON representation

  // Union field destination can be only one of the following:
  "gcsDestination": {
  "bigqueryDestination": {
  // End of list of possible types for union field destination.

Union field destination. Specifies the destination of the output.

To enable the Cloud Healthcare API to write to resources in your project, such as Cloud Storage buckets, you must give the Cloud Healthcare API service account the proper permissions. The service account is: service-{PROJECT_NUMBER} The PROJECT_NUMBER identifies the project that the DICOM store resides in. To get the project number, go to the Cloud Console Dashboard. destination can be only one of the following:



The Cloud Storage output destination.

The Cloud Healthcare Service Agent requires the roles/storage.objectAdmin Cloud IAM roles on the Cloud Storage location.



The BigQuery output destination.

You can only export to a BigQuery dataset that's in the same project as the DICOM store you're exporting from.

The Cloud Healthcare Service Agent requires two IAM roles on the BigQuery location: roles/bigquery.dataEditor and roles/bigquery.jobUser.

Response body

If successful, the response body contains an instance of Operation.

Authorization scopes

Requires one of the following OAuth scopes:


For more information, see the Authentication Overview.


The Cloud Storage location where the server writes the output and the export configuration.

JSON representation
  "uriPrefix": string,
  "mimeType": string


The Cloud Storage destination to export to.

URI for a Cloud Storage directory where the server writes the result files, in the format gs://{bucket-id}/{path/to/destination/dir}). If there is no trailing slash, the service appends one when composing the object path. The user is responsible for creating the Cloud Storage bucket referenced in uriPrefix.



MIME types supported by DICOM spec. Each file is written in the following format: .../{study_id}/{series_id}/{instance_id}[/{frame_number}].{extension} The frame_number component exists only for multi-frame instances.

Supported MIME types are consistent with supported formats in DICOMweb: Specifically, the following are supported:

  • application/dicom; transfer-syntax=1.2.840.10008.1.2.1 (uncompressed DICOM)
  • application/dicom; transfer-syntax=1.2.840.10008. (DICOM with embedded JPEG Baseline)
  • application/dicom; transfer-syntax=1.2.840.10008. (DICOM with embedded JPEG 2000 Lossless Only)
  • application/dicom; transfer-syntax=1.2.840.10008. (DICOM with embedded JPEG 2000)
  • application/dicom; transfer-syntax=* (DICOM with no transcoding)
  • application/octet-stream; transfer-syntax=1.2.840.10008.1.2.1 (raw uncompressed PixelData)
  • application/octet-stream; transfer-syntax=* (raw PixelData in whatever format it was uploaded in)
  • image/jpeg; transfer-syntax=1.2.840.10008. (Consumer JPEG)
  • image/png

The following extensions are used for output files:

  • application/dicom -> .dcm
  • image/jpeg -> .jpg
  • image/png -> .png
  • application/octet-stream -> no extension

If unspecified, the instances are exported in the original DICOM format they were uploaded in.