

If your OsiriX workstation is configured for multiple OsiriX users who log in via the fast user switch, then each user must have a separate AE title and port number. “Preferences” window to configure the “DICOM Listener” Don't forget to leave OsiriX running - the DICOM Listener works only if OsiriX is active!

Then, contact your “friendly” PACS manager to configure the PACS. OsiriX and the PACS workstation must be first configured: Assign an AETitle and a Port number to OsiriX in the “Preferences” window. In this configuration, DICOM images are sent from a PACS workstation to a Mac computer running OsiriX, which passively receives the images. If you are working in a PACS environment, the easiest way to import DICOM images into OsiriX is to configure OsiriX as a “DICOM Listener”. Using OsiriX as a Passive DICOM Listener Edit Images can either be pushed from the PACS using a DICOM "store" function, or they can be "pulled" by the DICOM query-retrieve function of OsiriX. Importing DICOM Images into OsiriX via a Network Edit
