othmane/ohif-viewer
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(Video): Added fallback checks for DICOM video (#3402)

Browse Source 
* fix(Video): Added fallback checks for DICOM video
Added some docs for video, pdf and upload.

* Added separate headings for DICOM PDF, DICOM Video and DICOM Upload in the docs.

* Updated docs for singlepart data source configuration.
This commit is contained in:
Joe Boccanfuso 2023-05-17 16:50:27 -04:00 committed by GitHub
parent f1c0581313
commit 856538537d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 35 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
extensions/dicom-video/src/getSopClassHandlerModule.js
View File

@ -12,6 +12,10 @@ const SOP_CLASS_UIDS = {
};
const sopClassUids = Object.values(SOP_CLASS_UIDS);
const secondaryCaptureSopClassUids = [
SOP_CLASS_UIDS.SECONDARY_CAPTURE_IMAGE_STORAGE,
SOP_CLASS_UIDS.MULTIFRAME_TRUE_COLOR_SECONDARY_CAPTURE_IMAGE_STORAGE,
];
const SupportedTransferSyntaxes = {
MPEG4_AVC_264_HIGH_PROFILE: '1.2.840.10008.1.2.4.102',
@ -42,11 +46,16 @@ const _getDisplaySetsFromSeries = (
return true;
}
// Assume that an instance with certain SOPClassUID and
if (
metadata.SOPClassUID === SOP_CLASS_UIDS.VIDEO_PHOTOGRAPHIC_IMAGE_STORAGE
) {
return true;
}
// Assume that an instance with one of the secondary capture SOPClassUIDs and
// with at least 90 frames (i.e. typically 3 seconds of video) is indeed a video.
return (
metadata.SOPClassUID ===
SOP_CLASS_UIDS.MULTIFRAME_TRUE_COLOR_SECONDARY_CAPTURE_IMAGE_STORAGE &&
secondaryCaptureSopClassUids.includes(metadata.SOPClassUID) &&
metadata.NumberOfFrames >= 90
);
})

BIN
platform/docs/docs/assets/img/uploader.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 287 KiB

23
platform/docs/docs/configuration/dataSources/dicom-web.md
View File

@ -153,9 +153,32 @@ window.config = {
};
```
### Data Source Configuration Options
The following properties can be added to the `configuration` property of each data source.
##### `dicomUploadEnabled`
A boolean indicating if the DICOM upload to the data source is permitted/accepted or not. A value of true provides a link on the OHIF work list page that allows for DICOM files from the local file system to be uploaded to the data source
![toolbarModule-layout](../../assets/img/uploader.gif)
#### `singlepart`
A comma delimited string specifying which payloads the data source responds with as single part. Those not listed are considered multipart. Values that can be included here are `pdf`, `video`, `bulkdata`, `thumbnail` and `image`.
For DICOM video and PDF it has been found that Orthanc delivers multipart, while DCM4CHEE delivers single part. Consult the DICOM conformance statement for your particular data source to determine which payload types it delivers.
To learn more about how you can configure the OHIF Viewer, check out our
[Configuration Guide](../index.md).
### DICOM Upload
See the [`dicomUploadEnabled`](#dicomuploadenabled) data source configuration option.
### DICOM PDF
See the [`singlepart`](#singlepart) data source configuration option.
### DICOM Video
See the [`singlepart`](#singlepart) data source configuration option.
### Running DCM4CHEE
dcm4che is a collection of open source applications for healthcare enterprise