[Oviyam 2] Timestamp display issue: Seconds are missing in Image View compared to other viewers

12 views
Skip to first unread message

Washington Cavalcante

unread,
Apr 9, 2026, 4:34:24 PM (19 hours ago) Apr 9
to dcm4che

Hello everyone,

I am experiencing an issue regarding the way image timestamps are displayed in Oviyam 2.7.

The Issue: When viewing studies with multiple images (e.g., surgical or bedside exams), Oviyam only displays Hours and Minutes (HH:mm). When 3 or 4 images are acquired in quick succession, they all appear with the exact same time on the interface. This makes it difficult for the technician to differentiate between them or identify the correct chronological sequence.

Technical Context:

  • In other viewers (such as easis), the same images correctly display Hours, Minutes, and Seconds (HH:mm:ss).

  • The DICOM tags (0008,0033) Content Time and (0008,0032) Acquisition Time definitely contain the seconds data, but the Oviyam UI seems to be truncating this information.

  • The backend server is dcm4chee.

Request: Does anyone know which configuration file or script in version 2.7 controls the time formatting? I would like to modify it to include seconds (HH:mm:ss) or, alternatively, force the Instance Number (0020,0013) to be displayed more prominently to help distinguish between images in the same series.

Environment:

  • PACS: dcm4chee

  • Viewer: Oviyam 2.7

  • Browser: [Your browser, e.g., Chrome/Edge]

Thank you in advance for your help!

Best regards, Washington






Meer Asgar Hussain Bahawdeen

unread,
3:03 AM (8 hours ago) 3:03 AM
to dcm4che
Hi,

Currently, Oviyam displays the study datetime rather than the individual image acquisition time. This means that all images within a single study will display the same timestamp corresponding to when the study was created, rather than the exact acquisition time of each image.

If you want to add the acquisition datetime, add it in the handler (ImageHandler.java) java class and use it in the UI (frameContent.html / frameContent.js).

Regards,

Asgar Hussain.B
Reply all
Reply to author
Forward
0 new messages