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
POST https://healthcare.googleapis.com/v1/{name=projects/*/locations/*/datasets/*/dicomStores/*}:export
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
name |
Required. The DICOM store resource name from which to export the data. For example, Authorization requires the following IAM permission on the specified resource
|
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field 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: |
|
gcsDestination |
The Cloud Storage output destination. The Cloud Healthcare Service Agent requires the |
bigqueryDestination |
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: |
Response body
If successful, the response body contains an instance of Operation
.
Authorization scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/cloud-healthcare
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.
GcsDestination
The Cloud Storage location where the server writes the output and the export configuration.
JSON representation |
---|
{ "uriPrefix": string, "mimeType": string } |
Fields | |
---|---|
uriPrefix |
The Cloud Storage destination to export to. URI for a Cloud Storage directory where the server writes the result files, in the format |
mimeType |
MIME types supported by DICOM spec. Each file is written in the following format: Supported MIME types are consistent with supported formats in DICOMweb: https://cloud.google.com/healthcare/docs/dicom#retrieve_transaction. Specifically, the following are supported:
The following extensions are used for output files:
If unspecified, the instances are exported in the original DICOM format they were uploaded in. |