| DICOM PS3.17 2024e - Explanatory Information |
|---|
An example of implementation of the Video-to-DICOM converter presented in the use cases PPPP.2 above could respect the following approach:
The metadata are sent from the Departmental System to the Video-to-DICOM converter through TCP/IP using classical protocols as DICOM Worklist or HL7 ORM.
The video/multi-frame is sent through coaxial cable using classical video protocol (e.g., uncompressed HD video over Serial Digital Interface SDI).
The time ("timestamp") is sent through IP respecting PTP, for synchronizing all the senders and receivers, through "time alignment" mechanism described in SMPTE ST 2110-10.
All this information is used to produce several RTP sessions over IP:
SMPTE ST 2110-10 compliant DICOM Metadata Flow, including payload header (RTV Meta Information) as well as dynamic payload part (DICOM Current Frame Functional Groups Module) for every frame, and including additionally the static payload part (DICOM Real-Time Video Endoscopic/Photographic Image IOD Modules) at least every second.
SMPTE ST 2110-10 compliant DICOM Metadata Flow, including payload header (RTV Meta Information) as well as dynamic payload part (DICOM Current Frame Functional Groups Module) for every sample, and including additionally the static payload part (DICOM Real-Time Audio Waveform IOD Modules) at least every second.
SMPTE ST 2110-10 compliant DICOM Metadata Flow, including payload header and static payload part (DICOM Rendition Selection Document IOD Modules) , at least every second, in order to associate the two flows above.
Eventually, the laparoscope systems will embed the Video-to-DICOM converter, as shown in the Integrated Product box of the Figure PPPP.2-1.
| DICOM PS3.17 2024e - Explanatory Information |
|---|