Problems with RDSR Eurocolumbus C-arm

37 views
Skip to first unread message

rossan...@gmail.com

unread,
Jan 25, 2018, 7:17:58 AM1/25/18
to OpenREM
Goodmorning everyone.
openrem is ok with all RDSRs of our hospital except those coming from a c-arm machine of a local manufacturer (i can read those RDSR with DoseUtility software, but it generates only a text file).
Can I send someone the file to understand what the problem may be?

Thank you

Rossana

Ed McDonagh

unread,
Jan 25, 2018, 8:25:03 AM1/25/18
to OpenREM
Hi Rossana - please send it through to me and I'll take a look.

If my email address isn't visible from this message, reply and I'll contact you off list.

Kind regards,

Ed

rossan...@gmail.com

unread,
Jan 26, 2018, 11:19:12 AM1/26/18
to OpenREM
Hi Ed,
your address is not visible, mine is rossan...@hotmail.com
thanks

rossana

Ed McDonagh

unread,
Jan 27, 2018, 6:35:00 PM1/27/18
to OpenREM
Dear Rossana

Thank you for sending the file through to me.

The first problem is that the file is marked as having a character set encoding of ISO 2022 IR 144 - Cyrillic (although I haven't spottend any Cyrillic in the file), which unfortunately isn't listed (in that form) in the released version of pydicom, which OpenREM relies on. It is fixed in the current development version of pydicom, but that hasn't been released yet. I can tell you how to fix that in your local install, but there is another problem too...

For each event, the pulse width, kV and mA has been recorded as a multiple value, one for each pulse. I've not seen this before, but looking at the standard it is completely legal. The OpenREM database is set up to cater for this, but the import routine, display and export isn't!


Ed

Ed McDonagh

unread,
Mar 9, 2018, 3:41:40 AM3/9/18
to OpenREM
The per-pulse kV/mA/pulse width is now handled in OpenREM, with details of how it is dealt with for exports documented within the fluoroscopy export docs. This will be available in the 0.8.0 release.

The issue with encoding will ultimately be fixed when pynetdicom3 is released and OpenREM is modified to work with pynetdicom3 and the recently released pydicom.

In the meantime, you can now modify the existing pydicom to handle a wider range of character set encodings by following the documentation provided.

I would very much welcome comment on this documentation (and all the documentation) either here or on bitbucket.org/openrem/openrem/issues.

Kind regards

Ed



--
You received this message because you are subscribed to the Google Groups "OpenREM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrem+unsubscribe@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.

Visit this group at https://groups.google.com/group/openrem.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages