get | SELECT | datasetsId, dicomStoresId, locationsId, projectsId | Gets the specified DICOM store. |
list | SELECT | datasetsId, locationsId, projectsId | Lists the DICOM stores in the given dataset. |
create | INSERT | datasetsId, locationsId, projectsId | Creates a new DICOM store within the parent dataset. |
delete | DELETE | datasetsId, dicomStoresId, locationsId, projectsId | Deletes the specified DICOM store and removes all images that are contained within it. |
_list | EXEC | datasetsId, locationsId, projectsId | Lists the DICOM stores in the given dataset. |
deidentify | EXEC | datasetsId, dicomStoresId, locationsId, projectsId | De-identifies data from the source store and writes it to the destination store. The metadata field type is OperationMetadata. If the request is successful, the response field type is DeidentifyDicomStoreSummary. If errors occur, error is set. The LRO result may still be successful if de-identification fails for some DICOM instances. The output DICOM store will not contain these failed resources. Failed resource totals are tracked in Operation.metadata. Error details are also logged to Cloud Logging (see Viewing error logs in Cloud Logging). |
export | EXEC | datasetsId, dicomStoresId, locationsId, projectsId | 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. |
import | EXEC | datasetsId, dicomStoresId, locationsId, projectsId | Imports data into the DICOM store by copying it from the specified source. Errors are logged to Cloud Logging. For more information, see Viewing error logs in Cloud Logging. The metadata field type is OperationMetadata. |
patch | EXEC | datasetsId, dicomStoresId, locationsId, projectsId | Updates the specified DICOM store. |
search_for_instances | EXEC | datasetsId, dicomStoresId, locationsId, projectsId | SearchForInstances returns a list of matching instances. See [Search Transaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.6). For details on the implementation of SearchForInstances, see Search transaction in the Cloud Healthcare API conformance statement. For samples that show how to call SearchForInstances, see Searching for studies, series, instances, and frames. |
search_for_series | EXEC | datasetsId, dicomStoresId, locationsId, projectsId | SearchForSeries returns a list of matching series. See [Search Transaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.6). For details on the implementation of SearchForSeries, see Search transaction in the Cloud Healthcare API conformance statement. For samples that show how to call SearchForSeries, see Searching for studies, series, instances, and frames. |
search_for_studies | EXEC | datasetsId, dicomStoresId, locationsId, projectsId | SearchForStudies returns a list of matching studies. See [Search Transaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.6). For details on the implementation of SearchForStudies, see Search transaction in the Cloud Healthcare API conformance statement. For samples that show how to call SearchForStudies, see Searching for studies, series, instances, and frames. |
store_instances | EXEC | datasetsId, dicomStoresId, locationsId, projectsId | StoreInstances stores DICOM instances associated with study instance unique identifiers (SUID). See [Store Transaction] (http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_10.5). For details on the implementation of StoreInstances, see Store transaction in the Cloud Healthcare API conformance statement. For samples that show how to call StoreInstances, see Storing DICOM data. |