DicomScope does not open my Dicom SR file though valid
Moderator: Moderator Team
DicomScope does not open my Dicom SR file though valid
I have a SR dcm file which DicomScope doesnt not open. Other Structured Report browsers are able to open the file correctly. Are there any extra validations done by DicomScope?
From the investigation done so far, I suspect it has something to do with the sequence and item delimiter tags. Is that mandatory?
From the investigation done so far, I suspect it has something to do with the sequence and item delimiter tags. Is that mandatory?
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
Did you check your SR file with dsrdump or dsr2html from the latest DCMTK release? It is also possible that your file uses a new SOP Class or other additions or corrections of the DICOM standard that were not available when DICOMscope was developed.
You could also send your SR file to us by email (dicom/at/offis/dot/de) for validation purposes.
You could also send your SR file to us by email (dicom/at/offis/dot/de) for validation purposes.
Hi Jorg, I am sure that there I am not using any new SOP class. Both the dsrdump and dsr2html gave the same following error
"error (Invalid by-value Relationship) parsing file: dicomfile.dcm"
My SR dcm file doesnt contain the item and sequence delimiters. Would that cause a problem in case of nested sequences?
Thanks.
"error (Invalid by-value Relationship) parsing file: dicomfile.dcm"
My SR dcm file doesnt contain the item and sequence delimiters. Would that cause a problem in case of nested sequences?
Thanks.
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
So, which SOP Class and Template ID (if any) are you using for the document? What is the output of dsrdump in --debug or --verbose-debug mode?
Btw, you could also try to parse the file using option --ignore-constraints which should allow you to post the dump of this document.
Btw, you could also try to parse the file using option --ignore-constraints which should allow you to post the dump of this document.
Does that mean you're using sequence and item encoding with explicit length? No, this is no problem since all DICOM implementations need to support that (incl. all DCMTK tools).My SR dcm file doesnt contain the item and sequence delimiters. Would that cause a problem in case of nested sequences?
Hi Jorg, thank you very much for the update..
dsrdump -debug gave me the following errors
DCMSR - Warning: SeriesNumber absent in SR document (type 1)
DCMSR - Warning: ReferencedPerformedProcedureStepSequence absent in SR document
(type 2)
DCMSR - Warning: PerformedProcedureCodeSequence absent in SR document (type 2)
DCMSR - Error: Cannot add "contains CONTAINER" to TEXT in Comprehensive SR
DCMSR - Error: Reading content item "1.1.1" (Invalid by-value Relationship)
DCMSR - Error: Reading content item TEXT "1.1" (Invalid by-value Relationship)
dsrdump: error (Invalid by-value Relationship) parsing file: dicomfile.dcm
-ignore-constraints gave the following error
dsrdump: error (Tag Not Found) parsing file: dicomfile.dcm
Thanks
dsrdump -debug gave me the following errors
DCMSR - Warning: SeriesNumber absent in SR document (type 1)
DCMSR - Warning: ReferencedPerformedProcedureStepSequence absent in SR document
(type 2)
DCMSR - Warning: PerformedProcedureCodeSequence absent in SR document (type 2)
DCMSR - Error: Cannot add "contains CONTAINER" to TEXT in Comprehensive SR
DCMSR - Error: Reading content item "1.1.1" (Invalid by-value Relationship)
DCMSR - Error: Reading content item TEXT "1.1" (Invalid by-value Relationship)
dsrdump: error (Invalid by-value Relationship) parsing file: dicomfile.dcm
-ignore-constraints gave the following error
dsrdump: error (Tag Not Found) parsing file: dicomfile.dcm
Thanks
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
According to the DICOM standard a "TEXT contains CONTAINER" relationship is not allowed for Comprehensive SR objects. So your document is incorrect in this respect.DCMSR - Error: Cannot add "contains CONTAINER" to TEXT in Comprehensive SR
That means that there is another problem with your document (a required attribute is missing).-ignore-constraints gave the following error
dsrdump: error (Tag Not Found) parsing file: dicomfile.dcm
So if you really want to known what's wrong with your SR document, just send it to us for validation purposes.
Hi Jorg, thanks for the updates. It was very helpful to me. I changed the TEXT to CONTAINER and with that change I was able to open the SR in DicomScope. There were some other missing tags which I have now included. The whole report is now displayed correctly but the -ignore-constraints options still gives me the 'Tag not found' error.
Also there is one pending error from the -debug option.
I have sent you the SR file in the mail id mentioned in your earlier response. Please check and let me know.
Appreciate your valuable help.
Thanks.
Also there is one pending error from the -debug option.
I have sent you the SR file in the mail id mentioned in your earlier response. Please check and let me know.
Appreciate your valuable help.
Thanks.
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
There are still a couple of issues with our SR file. Here's the verbose debug output of dsrdump:
The error message (Tag Not Found) is caused by the fact that the mandatory attribute ContinuityOfContent is missing for the CONTAINER content item 1.7.
Btw, option --ignore-item-errors will allow you to dump main parts of the SR document even if there are errors (as in your case).
Our checking tool DCMCHECK also found a couple of further violations against the DICOM standard, e.g. the value for PatientsAge does not contain the time unit (e.g. "Y" for years).
Code: Select all
%-> dsrdump dicomfile.dcm -dd
DCMSR - Warning: SeriesNumber absent in SR document (type 1)
DCMSR - Warning: ReferencedPerformedProcedureStepSequence absent in SR document (type 2)
DCMSR - Warning: PerformedProcedureCodeSequence absent in SR document (type 2)
DCMSR - Warning: CodeValue empty in ConceptNameCodeSequence (type 1)
DCMSR - Warning: CodeValue empty in ConceptNameCodeSequence (type 1)
DCMSR - Warning: CodeValue empty in ConceptNameCodeSequence (type 1)
DCMSR - Warning: CodeValue empty in ConceptNameCodeSequence (type 1)
DCMSR - Warning: CodeValue empty in ConceptNameCodeSequence (type 1)
DCMSR - Warning: CodeValue empty in ConceptNameCodeSequence (type 1)
DCMSR - Warning: CodeValue empty in ConceptNameCodeSequence (type 1)
DCMSR - Warning: CodeValue empty in ConceptNameCodeSequence (type 1)
DCMSR - Warning: CodeValue empty in ConceptNameCodeSequence (type 1)
DCMSR - Warning: ContinuityOfContent absent in CONTAINER content item (type 1)
DCMSR - Warning: Reading invalid/incomplete content item CONTAINER "1.7"
DCMSR - Error: Reading content item CONTAINER "1.7" (Tag Not Found)
------------------------------- DICOM DATA SET -------------------------------
(fffe,e000) na (Item with explicit length #=3) # 174, 1 Item
(0040,a010) CS [CONTAINS] # 8, 1 RelationshipType
(0040,a040) CS [CONTAINER] # 10, 1 ValueType
(0040,a043) SQ (Sequence with explicit length #=1) # 128, 1 ConceptNameCodeSequence
(fffe,e000) na (Item with explicit length #=4) # 120, 1 Item
(0008,0100) SH [summary] # 8, 1 CodeValue
(0008,0102) SH [INSTITUTENAME] # 14, 1 CodingSchemeDesignator
(0008,0103) SH [1.0] # 4, 1 CodingSchemeVersion
(0008,0104) LO [Summary : Conclusion of the investigation would come here] # 62, 1 CodeMeaning
(fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
(fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
(fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
------------------------------------------------------------------------------
dsrdump: error (Tag Not Found) parsing file: dicomfile.dcm
Btw, option --ignore-item-errors will allow you to dump main parts of the SR document even if there are errors (as in your case).
Our checking tool DCMCHECK also found a couple of further violations against the DICOM standard, e.g. the value for PatientsAge does not contain the time unit (e.g. "Y" for years).
-
- Posts: 2
- Joined: Mon, 2007-08-20, 07:22
- Location: Pune
Who is online
Users browsing this forum: No registered users and 1 guest