Multi frame SC report

[Ronaldo Souza]

Hi,

The company I work for has this big client with an odd problem: for some reason their PACS server can't handle embedded PDFs and asked us if could provide de exact same reports as Multiframe Secondary Captures.

It would be rather easy to derive this SC report from our current Embedded PDF implementation, but I have to figure out how to fill the Frame Increment Pointer (0028,0009) since each frame will contain just pages of a report and are not linked spacially or temporarily in any way. Despite this fact, MS CoPilot suggested the following "solution":

(1) Frame Increment Pointer (0028,0009) pointing to (2) Temporal Position Index (0020,9128) present in each item of (3) Per-frame Functional Groups Sequence (5200,9230)... 1 \ 2 \ 3 \ 4 ...

Is this generally acceptable? If not, how can we fill the Frame Increment Pointer? Different AIs suggested different approaches, from the one described above to simply leaving it NULL.

Thanks in advance for any help!

Best regards,

Ronaldo Souza 

[David Clunie]

That's what Page Number Vector (0018,2001) in the SC Multi-frame Vector Module is intended for (https://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.8.6.4.html).

You should read the standard, not depend on DADS AIs.

Which MF SC SOP Class do they want you to use?

David

[Ronaldo Souza]

You should read the standard, not depend on DADS AIs.

I know... Not proud of using this AI thing, but the pace of development has increased to absurd, inhuman levels and is hard to keep up.

Now that you pointed to the Page Number Vector, it baffles me that no AI even mentioned it. The approach in my post seemed to me to be the *least* absurd one I got. :-(

Which MF SC SOP Class do they want you to use?

Either 1.2.840.10008.5.1.4.1.1.7.2  (MF Grayscale Byte SC) or ...7.4 (MF True Color SC) depending on the user config for the report.

Thanks David!

Best regards,

Ronaldo

David

On Sunday, September 28, 2025 at 10:06:47 PM UTC-4 ronaldo...@gmail.com wrote:

It would be rather easy to derive this SC report from our current Embedded PDF implementation, but I have to figure out how to fill the Frame Increment Pointer (0028,0009) since each frame will contain just pages of a report and are not linked spacially or temporarily in any way. Despite this fact, MS CoPilot suggested the follo "solution":

--
You received this message because you are subscribed to the Google Groups "DICOM Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dicomforum+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dicomforum/410c9a6c-2270-454d-b93a-c9f22d51ec8en%40googlegroups.com.