I don’t have Osirix, just Horos. If the UI is similar you need to configure Orthanc as a “location” in Osirix;
Address: would be the public IP for your AWS instance.
AETitle: Your Orthanc AET.
Port: The exposed DICOM port on your AWS instance.
Q&R, you probably want both.
Retrieve: C-GET is what I have mine at.
TLS: This could be problematic. I would try setting it up to use a regular connection initially and then setup TLS later.
Name: Whatever you want.
Send" Probably Implicit Little Endian.
You can click on the 'Verify" to Echo the connection to see if it is working.
You might run into some issues with ports being blocked and with your orthanc.json setup.
These are ‘permissive’, but you’ll want to secure it once you get it working.
“DicomCheckCalledAet” : false,
“DicomCheckModalityHost” : false,
and you’ll want to configure your OSIRIX in the orthanc.json under DicomModalities or in the DB if you are using that method.
You should read the documentation.
“DicomModalities” : {
“OSIRIX” : {
“AET” : “OSIRIX”,
“Port” : 1112,
“Host” : “your.public.ip.address”,
“Manufacturer” : “Generic”,
“AllowEcho” : true,
“AllowFind” : true,
“AllowFindWorklist” : true, // new in 1.10.0
“AllowGet” : true,
“AllowMove” : true,
“AllowStore” : true,
“AllowStorageCommitment” : false, // new in 1.6.0
“AllowTranscoding” : true, // new in 1.7.0
“UseDicomTls” : false // new in 1.9.0
“LocalAet” : “HELLO” // new in 1.9.0
“Timeout” : 60 // new in 1.9.1
}
}
A default configuration.json file is here with examples and comments is here:
https://hg.orthanc-server.com/orthanc/file/Orthanc-1.11.1/OrthancServer/Resources/Configuration.json
Setting up TLS is a bit more complicated:
https://book.orthanc-server.com/faq/dicom-tls.html?highlight=dicommodalities
and I think that Horos has some sort of issue with the TLS setup. Osirix might be different since it is a commercial package.
Stephen. D. Scotti, M.D.