<div dir="ltr">Orthanc will not modify the file by itself, except if the input file is corrupted, which could lead to undefined behavior. Garbage in, garbage out.<div><br></div><div>Regards,</div><div>Sébastien-</div><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 31, 2016 at 7:45 PM, Karsten Hilbert <span dir="ltr"><<a href="mailto:Karsten.Hilbert@gmx.net" target="_blank">Karsten.Hilbert@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, Jan 31, 2016 at 07:42:26PM +0100, Karsten Hilbert wrote:<br>
<br>
> > The Implementation Version Name in the meta information header<br>
> > says "OFFIS_DCMTK_360", but dcmtk doesn't make this kind<br>
> > of error, as far as I know, so Karsten, it would be good<br>
> > to know what system actually encoded this bad DICOM file.<br>
><br>
> That doesn't matter because:<br>
><br>
> - initially, GinkgoCADx (and hence GDCM ?) reads the file<br>
> just fine from local storage (say, CD-ROM)<br>
> - it then sends the file to a PACS<br>
> - it then retrieves the file from the same PACS<br>
> - it then does not read the very same file anymore<br>
<br>
And, may I add, this behaviour happens with DICOM files from<br>
various (commercial) sources.<br></blockquote></div>
</div></div></div>