I'm playing with the overlay.xml file to customize my RadiAnt tags layout

I wanted to obtain such a row:
'date of birth
'study date
'series time

so I edited the code this way:

<i r="0"><e k="1" i="00100030"/></i> 'date of birth
<i r="1"><e k="1" i="00080020"/></i> 'study date
<i r="2"><e k="1" i="00080031"/></i> 'series time

so let's make an example... load images from a patient who's born on 01/12/1955 (first of january) and performs an exam on 30/10(2016 (30th of october) and the series time is 10:29:00

I expect my tags code to show:
01/12/1955
30/10/2016
10:29:00

but instead I get:
19551201
20161030
102905.557000

It looks to me that RadiAnt just displays the plain DICOM tags values with no "processing" that would make them more readable.

the dates values are shown in a YYYYMMDD format, instead of a more confortable format such as DD/MM/YYYY (according to my localization)

the representation of the time value is instead completely obscure to me...


I see that in you use RadiAnt "internal special tags" this issue is workarounded using currently available special tags such as:

s=05 'date of birth and sex
s=09 'acquisition date and time

however I'd like to have a single line for birth only (no sex)
and 2 different lines for acquisition date and acquisition time
currently there are no specific special tags for such values.


I'm an user of iQ-VIEW and it has a similar way to customize DICOM tag overlays.
however it has no issues when displaying tag values such as "00100030" or 00080020"
so it seems that RadiAnt has a problem with it...

so, this is the "bug report"... now it's up to the developer to decide what to do...

solution 1: process the DICOM tag date and time values and display them in a more comfortable format

solution 2: add new specific special tags (date of birth only, study date only, image time only)

solution 3: implement a new <i> attribute to select the display format of date values.

a mockup could be:

f=1 --> DD/MM/YYYY
f=2 --> YYYY/MM/DD

The improvements will certainly be made :-)

Will be made was said in 2011 and in 2017... today we are in 2023 and I've found the same problem without a solution... or is there a solution?

This has been fixed in the latest 2023.2.0.27827 beta version.