Load the series directly by accessing it via: /ohif/viewer?StudyInstanceUIDs=2.16.840.1.113669.632.20.572111.10000106690&SeriesInstanceUID=1.2.826.0.1.3680043.2.1264.3.20130320131812584
Open and see the console error
// answer to studies/2.16.840.1.113669.632.20.572111.10000106690/series?SeriesInstanceUID=1.2.826.0.1.3680043.2.1264.3.20130320131812584 is only two value: series and instance UIDs
[
{
"0020000D": {
"vr": "UI",
"Value": [
"2.16.840.1.113669.632.20.572111.10000106690"
]
},
"0020000E": {
"vr": "UI",
"Value": [
"1.2.826.0.1.3680043.2.1264.3.20130320131812584"
]
}
}
]
// Metadata call: studies/2.16.840.1.113669.632.20.572111.10000106690/series/1.2.826.0.1.3680043.2.1264.3.20130320131812584/metadata returns:
too big content
@nicoesiea, I have not been able to reproduce this issue. Can it be reproduced with any of the sample data available for https://viewer-dev.ohif.org/? If not, are you able to provide fully anonymized DICOM and scrubbed free of all PHI that it can be reproduced with? Thanks.
Sorry sorry, in fact, my backend returned a list of series instance UID in the study response. I removed them and finally, it works as expected.
Sorry for the wasted time