search

OHIF / Viewers

OHIF zero-footprint DICOM viewer and oncology specific Lesion Tracker, plus shared extension packages
https://docs.ohif.org/
MIT License
3.14k stars 3.31k forks source link

Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON #4297

Open Wyd7151961 opened 2 months ago

Wyd7151961 commented 2 months ago

Describe the Bug

1.2.840.113619.2.409.65140653520588628040.1720486207.12687.0.json 微信图片_20240722162602 微信图片_20240722162645 Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON

Steps to Reproduce

Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON

The current behavior

Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON

The expected behavior

Hello, the merged DICOM file can be opened through StudyInstanceUIDs. However, when using JSON to open OHIF, an error was found. By comparing the JSON of the two, it was found that there are many DICOM tags such as 0019 in the merged DICOM file, such as 001911AD. These DICOM tags cannot find the corresponding DICOM tag names, so I don't know how to open this merged DICOM file normally in OHIF through JSON

OS

windows 10

Node version

18.16.1

Browser

chrome 125

sedghi commented 2 months ago

I can't access your files from here http://192.168.92.40:8100/dicom/jr/1.2.840.113619.2.409.65140653520588628040.1720486207.12687.3.dcm

Can you make that publicly available? Also, your JSON is not compliant with our schema. Can you generate it with our generator?

https://docs.ohif.org/configuration/dataSources/dicom-json