Supported Formats
Attachments
Any data file can be uploaded into the Repository. Where possible, the files are automatically identified and labeled as an “Attachment” if their contents are not viewable in the Viewer. Some attachments, such as PDF files and MS Office files may be viewable in your browser or with an application you have on your computer. In all other cases, attachments can be downloaded and processed with the appropriate application.
Supported Image Formats
The Viewer supports many proprietary whole slide image formats, DICOM standard whole slide images, some DICOM radiology formats as well common image formats.
List of supported formats
Vendor | Format |
---|---|
3DHISTECH | MRXS |
Aperio | SVS |
Aperio | AFI |
Hamamatsu | VMS |
Hamamatsu | VMU |
Hamamatsu | NDPI |
Hamamatsu | NDPIS |
Leica | SCN |
Lunaphore | OME-TIFF |
Motic | Motic SVS |
Olympus | VSI |
OME | OME-TIFF |
PerkinElmer | QPTIFF |
Sakura | SVSlide |
Ventana | BIF |
Ventana | TIF |
Zeiss | CZI |
Tiled TIFF | |
BigTIFF | |
JPEG2000 | |
DICOM | |
BMP | |
JFIF | |
PNG |
Known Limitations
The following image types are known to not work with PathcoreFlow:
- Images without a pyramid (e.g., TIFF or PNG) are much slower to render as they grow in size, which can lead to timeouts
- VSI images with a grid offset
- MRXS images without an
.mrxs
file. The scanner may not produce this file, but CaseViewer will create it if it does not already exist when it opens the image for viewing - Multi-file DICOM images
- Multi-file OME-TIFF images
Certain operations are guarded with a restriction on the maximum area that can be processed (42,000,000 pixels by default). The following requests can fail for images exceeding that limit:
- Region requests
- Thumbnail requests
- Nikon tile requests
The following actions are not performed by PathcoreFlow's image processing:
- Reading embedded metadata not directly related to the image data (e.g., patient, study)
- Reading embedded annotations out of formats such as MRXS and VSI
- Handling of files which have been modified after they appear in the Repository (when using the image indexing service)