Cannot retrieve from Osiri LXIV from iOS (OsiriX HD)

[Jo-Vo]

Hello,
just encountered another problem with DICOM transfers. Using OsiriX HD on iOS / iPad you cannot retrieve anything from Osiri LXIV. Query works, but when you actually want to retrieve a study you get an "OutOfResoucesSubOperations" error (on the iOS app, OsiriLXIV on the Mac doesn't show an error).
This goes for the automatic node found via Bonjour as well as for a manual configured node.

Sending studies from Osiri LXIV to the iOS app works.

[bettar]

Is this specific to using OsiriX HD on iOS / iPad ? I mean, does it work if instead you used a different DICOM application ? Also, the subject title "from Osiri LXIV from iOS" is a bit ambiguous, who is starting the association ? Is is C-GET, C-MOVE or WADO ?

[Jo-Vo]

Since I don't have any other dicom application for iOS and even don't know any other useful for this platform, I can't test this.
Maybe it could help, if I tried to retrieve something from your server? Maybe then you could see it in the look fine what's going on?

Regards

Joachim

Am 30.04.2015 um 00:47 schrieb Alex Bettarini [email protected]:

Is this specific to using OsiriX HD on iOS / iPad ? I mean, does it work if instead you used a different DICOM application ?

—
Reply to this email directly or view it on GitHub.

[Jo-Vo]

I hate typing / speech recognition on iPhone... "look fine" above should have been "log file"..

To clarify: The iOS app OsirixHD is trying to retrieve something from a Mac running OsiriLXIV (the server there is recognized automatically via Bonjour), so the iOS app is the one starting the transfer. The query works, but then the transfer fails with said error message.

Starting the trnsfer from the Mac / Sending from Osiri LXIV to the iOS app (which as well is automatically added to the send nodes via Bonjour onve it runs) works.

I don´t know which protocol the setup via Bonjour uses, but is is likely CGET because you get the exact same error whe you set up the node manually and use CGET. When using CMOVE, you get another error (MOVE destination unknown).

[Jo-Vo]

Testing with OsiriX Lite 6.5: CGET works (local network as well as mobile) as it should as well as the automatic configuration via Bonjour.
CMOVE does not work with OsiriX Lite when using mobile data (can´t test on local network, cause I´m not there at the moment)

[Jo-Vo]

Further testing..
OsiriX Lite on local network works with CMOVE when you start the transfer from iOS/OsirixHD-App.

With the previous Osiri LXIV b14 it doesn't work at all: you get an error message already when you try to do a query; sending from Osiri LXIV to the iOS app does not work with that version, too.
So the changes from b14 to b15 have improved things, but there are still problems.

Maybe DCMTK 3.6.1 is a bit buggy (or just less compatible)? Would reverting DCMTK to the version OsiriX uses help?

[bettar]

Testing with OsiriX Lite 6.5 is of limited use in this case because it is not open source, but it is very useful as a reference when we want to implement new features for example by reverse engineering.

Please download the open source 32-bit “OsiriX OS” project files from the Pixmeo site. This is the code base underlying Osiri-LXIV (even though we have surpassed it in some regards). Build OsiriX OS yourself with Xcode and test if the issue you are reporting appears there too.

If OsiriX OS works then we have a bug in Osiri-LXIV that should be relatively easy to fix.

If on the other hand OsiriX OS shows the same faulty behaviour as what you are reporting for Osiri-LXIV, we should probably consider it not a “bug” but a “new feature request”. In this case I cannot promise you a prompt resolution to the problem, especially considering that I am probably the only one in here without a job and who doesn’t receive any money for all this work that I am putting in.

About DCMTK, it’s not so much the version number that matters, as it is the way it is used: in OsiriX OS the source code is heavily customised (therefore “frozen”) and compiled into the project, in Osiri-LXIV it is a separate library module that will be easy to upgrade when updates of DCMTK become available. The customised part is now implemented with some new “glue” code and it is this part that might require some fine tuning.

[Jo-Vo]

I'm no coder and thus don't really know how to compile the source; but as it seems the current DICOM-transfer routines in Osiri XLIV are less compatible than in OsiriX, which plays well with about every other PACS / DICOM-viewer I've come across that far, be it from GE, Siemens, Sectra and the iOS apps.

The changes from b14->b15 improved things (and apparently helped other related problems as well as the C-ECHO problem also); but while otherwise a perfect replacement for OsiriX in this aspect (DICOM-communication) Osiri LXIV still is behind in terms of compatibility / the "it simply works" feel that I think made the success of OsiriX.

Maybe it helps to know that both retrieving from the iOS OsirixHD app and sending to it works in Horos.

[Jo-Vo]

As it seems Horos uses the same / a similar code base as OsiriLXIV and OsiriX OS, so maybe this points in the direction of your first suggestion
[QUOTE]If OsiriX OS works then we have a bug in Osiri-LXIV that should be relatively easy to fix.[\QUOTE]

P.S.:Reading again, the above post might sound a bit offensive/taunting - this is not what it was meant. I think we are all grateful for your work.
And I know that the DICOM "standard" (if you can call this OpenGL-like mess with most every manufacturer making their own soup with all those private tags,.. a standard) really seems to be difficult to support. This was the reason for me using Osirix in the first place, having to work with many external images from different manufactures and even more custom PACS-solutions / most often really bad bundled CD-viewers, where many commercial and expensive PACS softwares struggle.
This is the point where OsiriX really excels, it just handles them all..

[bettar]

I have been trying to replicate the problem by guessing what's going on with OsiriX HD (I don't have an iPad). Can you please contact me by email ?

[Jo-Vo]

Hello,
In the meantime I have searched for other DICOM-Apps to test with those, too. But as it seems OsiriX is the only really usefull one. There are other apps, but most of them need a Cloud-space or need a specialised in-the-middle server to transfer image data to the mobile device and don´t support DICOM query/retrieve. The others aren´t really DICOM viewers but just apps for web-servers.
Then I found one other app that pretends to to DICOM QR called "fiago", but I couldn´t get this to work neither with OsiriLXIV, nor OsiriX Lite, nor Horos, nor the Sectra PACS we have.

The OsiriX HD iOS app works with all of them except OsiriX LXIV. Maybe it would help if i tried to retrieve something from a server you set up, so you can have a look in the network logs?

An other thing: Retrieving images with OsiriX LXIV seems to take considerably longer than with OsiriX(Lite).

As a "workaround" I now have both OsiriX and OsiriLXIV running at the same time with OsiriX in server mode doing the DICOM transfer things in the background and OsiriX LXIV as a sole image viewer with the listener turned off.
Both play well together when used that way and RAM is not that a factor here (16GB).

MfG

Joachim

Am 08.05.2015 um 03:06 schrieb Alex Bettarini [email protected]:

I have been trying to replicate the problem by guessing what's going on with OsiriX HD (I don't have an iPad). Can you please contact me by email ?

—
Reply to this email directly or view it on GitHub.