Hi,

Module SR Document General defines

- Current Requested Procedure Evidence Sequence (0040,A375) -> Full set of Composite SOP Instances, of which the creator is aware, which were created to satisfy the current Requested Procedure(s) for which this SR Document is generated or that are referenced in the content tree. One or more Items shall be included in this Sequence.

- Referenced Instance Sequence (0008,114A) -> Sequence specifying SOP Instances significantly related to the current SOP Instance. Such referenced Instances may include equivalent documents or renderings of this document. One or more Items shall be included in this Sequence.

I use both sequences with identical content, a list of composite instances which are source instances for the content of that SR.
Especially Referenced Instance Sequence (0008,114A) is a typical way across our applications to identify relationship between certain composite instances.

However, dciodvfy (Dicm3tools) complains about the content of this sequence and gives me the errors:
Error - Bad Sequence number of Items 2 (1 Required by Module definition) Element=<ReferencedInstanceSequence> Module=<SRDocumentGeneral>
Error - Bad attribute Value Multiplicity Type 1C Conditional Element=<ReferencedInstanceSequence> Module=<SRDocumentGeneral>

Any hints on this? What is wrong here?

Thanks,
Patrick

Hi Patrick

There is probably a bug in dciodvfy that has the incorrect number of sequence items for Referenced Instance Sequence in the SR Document General Module - I will fix it (I don't recall if this changed after Referenced Instance Sequence was added to this module to support referencing equivalent CDA documents in some post Sup-23 Supplement or CP, or whether I just got it wrong the first time).

That said, it is not appropriate to have the same content referenced by both Current Requested Procedure Evidence Sequence and Referenced Instance Sequence; one is for the evidence (esp. that is referenced from the content tree), the other is for equivalent documents.

I understand that Referenced Instance Sequence may be used in other IODs (esp. image IODs) in a completely different way, and you may find it convenient to abuse it this way in SRs, but that is not what it is intended for, and it will confuse receivers.

This intent is spelled out in C.17.2.6 Equivalent CDA Document [1].

Since this is apparently not obvious, I will write a CP to make it clear that the content shall not be duplicated.

David

1. https://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.17.2.6.html

On Friday, September 22, 2023 at 9:39:23 AM UTC-4, Patrick A. Nast wrote:
> Hi,
>
> Module SR Document General defines
>
> - Current Requested Procedure Evidence Sequence (0040,A375) -> Full set of Composite SOP Instances, of which the creator is aware, which were created to satisfy the current Requested Procedure(s) for which this SR Document is generated or that are referenced in the content tree. One or more Items shall be included in this Sequence.
>
> - Referenced Instance Sequence (0008,114A) -> Sequence specifying SOP Instances significantly related to the current SOP Instance. Such referenced Instances may include equivalent documents or renderings of this document. One or more Items shall be included in this Sequence.
>
> I use both sequences with identical content, a list of composite instances which are source instances for the content of that SR.
> Especially Referenced Instance Sequence (0008,114A) is a typical way across our applications to identify relationship between certain composite instances.
>
> However, dciodvfy (Dicm3tools) complains about the content of this sequence and gives me the errors:
> Error - Bad Sequence number of Items 2 (1 Required by Module definition) Element=<ReferencedInstanceSequence> Module=<SRDocumentGeneral>
> Error - Bad attribute Value Multiplicity Type 1C Conditional Element=<ReferencedInstanceSequence> Module=<SRDocumentGeneral>
>
> Any hints on this? What is wrong here?
>
> Thanks,
> Patrick

Hi David,

thanks for clarification. It's a good idea to have some clarifying statements in the attribute description for Referenced Instance Sequence (0008,114A) as well.

Thanks,
Patrick