fix(DicomWebProxyDataSource): bug fix to save Segmentation files back to Kheops (#5028)
This commit is contained in:
parent
66322c68a2
commit
349306da40
@ -220,7 +220,7 @@ const commandsModule = ({
|
|||||||
}
|
}
|
||||||
|
|
||||||
const { label } = segmentation;
|
const { label } = segmentation;
|
||||||
const defaultDataSource = dataSource ?? extensionManager.getActiveDataSource();
|
const defaultDataSource = dataSource ?? extensionManager.getActiveDataSource()[0];
|
||||||
|
|
||||||
const {
|
const {
|
||||||
value: reportName,
|
value: reportName,
|
||||||
@ -251,6 +251,11 @@ const commandsModule = ({
|
|||||||
|
|
||||||
const { dataset: naturalizedReport } = generatedData;
|
const { dataset: naturalizedReport } = generatedData;
|
||||||
|
|
||||||
|
// DCMJS assigns a dummy study id during creation, and this can cause problems, so clearing it out
|
||||||
|
if (naturalizedReport.StudyID === 'No Study ID') {
|
||||||
|
naturalizedReport.StudyID = '';
|
||||||
|
}
|
||||||
|
|
||||||
await selectedDataSourceConfig.store.dicom(naturalizedReport);
|
await selectedDataSourceConfig.store.dicom(naturalizedReport);
|
||||||
|
|
||||||
// add the information for where we stored it to the instance as well
|
// add the information for where we stored it to the instance as well
|
||||||
|
|||||||
@ -52,7 +52,7 @@ function createDicomWebProxyApi(dicomWebProxyConfig, servicesManager: AppTypes.S
|
|||||||
},
|
},
|
||||||
},
|
},
|
||||||
store: {
|
store: {
|
||||||
dicom: (...args) => dicomWebDelegate.store(...args),
|
dicom: (...args) => dicomWebDelegate.store.dicom(...args),
|
||||||
},
|
},
|
||||||
deleteStudyMetadataPromise: (...args) => dicomWebDelegate.deleteStudyMetadataPromise(...args),
|
deleteStudyMetadataPromise: (...args) => dicomWebDelegate.deleteStudyMetadataPromise(...args),
|
||||||
getImageIdsForDisplaySet: (...args) => dicomWebDelegate.getImageIdsForDisplaySet(...args),
|
getImageIdsForDisplaySet: (...args) => dicomWebDelegate.getImageIdsForDisplaySet(...args),
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user