Problems with OHIF generated measurment reports SR

General
1

Hello,
There is some problem with Orthanc when it tries to generate response to Ohif metadata request AND Orthanc dicomweb plugin configured with:

"StudiesMetadata": "MainDicomTags",
"SeriesMetadata": "MainDicomTags"

as well as "StorageAccessOnFind" : "Never".
In browser I see error:

{
	"HttpError" : "Bad Request",
	"HttpStatus" : 400,
	"Message" : "Bad file format",
	"Method" : "GET",
	"OrthancError" : "Bad file format",
	"OrthancStatus" : 15,
	"Uri" : "/dicom-web/studies/1.2.3.4.5.6/series/4.5.6.7.8/metadata"
}

and Orthanc log shows:

HTTP-8 OrthancException.cpp:62] Bad file format: While creating a DICOM instance, tag (0070,0022) has out-of-range value: "108.44062805175781\271.44833374023438\431.54299926757812\269.345703125"
HTTP-8 PluginsErrorDictionary.cpp:101] Exception inside the plugin engine: Bad file format

But if I use Series and Studies metadata “Full” in dicomweb plugin everything works fine.
So the question is, should i add some tag to the database to make plugin work without errors?
Orthanc version: 1.12.4
ExtraMainDicomTags used:

    "Instance": [
      "00700022",
      "00700023",
      "Rows",
      "Columns",
      "ImageType",
      "SOPClassUID",
      "ContentDate",
      "ContentTime",
      "ConceptNameCodeSequence",
      "ContentSequence",
      "CurrentRequestedProcedureEvidenceSequence",
      "ContentTemplateSequence",
      "CodingSchemeIdentificationSequence",
      "FrameOfReferenceUID",
      "PixelSpacing",
      "SpecificCharacterSet",
      "BitsAllocated",
      "BitsStored",
      "RescaleSlope",
      "RescaleIntercept",
      "SliceThickness",
      "WindowCenter",
      "WindowWidth",
      "PhotometricInterpretation",
      "PixelRepresentation"
    ],
    "Series": [
      "TimezoneOffsetFromUTC",
      "PerformedProcedureStepStartDate",
      "PerformedProcedureStepStartTime",
      "RequestAttributesSequence",
      "ContentSequence",
      "NumericValue",
      "004008EA",
      "ConceptNameCodeSequence",
      "CurrentRequestedProcedureEvidenceSequence",
      "ContentTemplateSequence",
      "CodingSchemeIdentificationSequence",
      "ReferencedSOPSequence"
    ],
    "Study": [
      "00080060",
      "TimezoneOffsetFromUTC",
      "SpecificCharacterSet"
    ],
2

Hi,

Note that, the “Full” mode is now the recommended configuration for DICOMWeb.

00700022 is part of a sequence so, anyway, it makes no real sense to add it to the ExtraMainDicomTags.

HTH,

Alain.

3

Thanks for your answer.

I tried to fit every tag to check if it help me to rid the problem.

Unfortunately using “Full” is not a solution as it has very big impact on performance, unless there is no any trick to use full metadata tags with storage access mode ‘Never’

4

Full Mode should not have any impact on performance provided this (source):

  • If Full mode is used, the plugin will read all the DICOM instances of the study/series of interest from the storage area, which gives fully accurate results but requires all the individual instances to be read and parsed from the filesystem, leading to slow performance for earliers version of the plugin. From version 1.15 of the plugin in which we have introduced caching, this mode is the most accurate and fastest one provided that you have run the Housekeeper plugin on data ingested with prior versions of the plugin - otherwise, the first access to the route might still be slow to populate the cache while later accesses will be much faster.
  • Starting from version 1.15 of the plugin and provided that the cache has been populated for all prior studies, you should favor the Full mode. The following recommandations are kept for prior version of the plugin only.

If you are still experiencing performance issue, please elaborate …