About the OmniRouter™
The OmniRouter is a software application specifically for communicating with and transmissions through OmniPACS online. The OmniRouter is an Open Source Software application compatible with Windows operating systems, that is used to transmit DICOM data to a registered OmniPACS account. OmniRouter is intended to be used by any healthcare delivery organization that has a digital radiological modality.
- Requires active Internet Connection
- Must be on same network as sending modality *
- Windows XP, Windows Vista, or Windows 7 OS
- Windows Installer 3.1 **
- .NET Framework 3.5 **
- Static IP Address is highly recommended.
- These programs are checked and may be downloaded by the OmniRouter Installer if required.
How it works
OmniRouter works as a small application or service that is run on a Windows-based PC that is within the same network as a medical digital modality. The OmniRouter runs a local DICOM listener that acquires DICOM compatible data and transmits the data securely to a private OmniPACS account.
How to install
How to install the OmniRouter™ yourself
- Go to www.omnipacs.com.
- Login to your OmniPACS account.
- Click on the "Routing" Tab.
- Click the "Download" Tab.
- Request an Activation Key.
How to share the installer
- Go to www.omnipacs.com.
- Login to your OmniPACS account.
- Click the "Routing" Tab.
- Click the "Share" button and enter the email address of the recipient.
How to Start the OmniRouter
On Windows XP, Windows Vista, or Windows 7, navigate as follows:
- Start > Programs > OmniPACS Folder > OmniRouter
How to Configure and Modify the OmniRouter
Once Installed the OmniRouter™ allows you to modify a number of settings. Modify the configuration and settings if you require more advanced options for network and system compatibility.
To modify settings navigate to File>Settings
- Customer Activation ID * — The activation key is a 25 character password that is used to seed your router. Each account must have a unique and valid activation key in order to transmit data to the OmniPACS platform.
- Institution Name * — This is a standard DICOM field which many times is set automatically within the Modality. When transmitting to OmniPACS we require that you hard set this value to the name of choice.
- Referring Physician — This is a standard DICOM field that we find many people like to customize. Referring Physician is not a required field and if left blank will inherit the original DICOM value. Note: set this field if you are using the OmniRouter on behalf of a referring physician requesting a study or image be transmitted.
- Performing Physician — This is a standard DICOM field that we find many people like to customize. Performing Physician is not a required field and if left blank will inherit the original DICOM value. Note: set this field if you are using OmniPACS to send data to a specific reading doctor or reading group (e.g. Nighthawk).
- Cache Directory — Location on local file system for cached files before WAN transmission. It is set by default but can be modified.
- * Required Field
List of Advanced Settings
- IP (Internet Protocol Address example 192.168.1.1) — This is the address that the OmniRouter will listen on and can be configured if there are multiple IPs on the PC. This is a value a modality technician will need to transmit data to your OmniPACS account. Note - we recommend whenever possible to assign the PC running the OmniRouter a static IP address. If you are unsure of what this is please see your IT Administrator or see wikipedia.org.
- Port — The port through which the OmniRouter runs its DICOM listening service. By default this port is set to 7775 but can be modified if required. This is also a value a modality technician will need to transmit data to your OmniPACS account. If you are unsure of what this is please see your IT Administrator or see wikipedia.org.
- Title — The Application Entity Target (AET) of the OmniRouter used to receive images from a modality. If you are unsure of what this is please see your IT Administrator or see wikipedia.org
Modality Integration (Device)
The key to transmitting data to your OmniPACS account is configuring the medical device or modality to send data to the OmniRouter. This usually involves the device technical support or technician in charge of basic device/modality configuration.
All modalities will require three basic values to be configured to successfully send data to the OmniRouter – these include IP, PORT, and AET see above. We've provided a sample email or letter (see below) that one can give to a modality technician to help guide them through the configuration of their modality to the OmniRouter.
- Modality should be on the same network as the PC running the OmniRouter or if more complex routing is already setup the device should be on the network.
- Modality Configuration: The modality configuration or settings needs to allow for the addition of a new DICOM AE target.
Dear John Doe,
I'm sending you the following DICOM Application Entity information so that you can configure your modalities to send data
to my OmniPACS® account. If you have any questions please contact email@example.com.
IP: [Insert actual IP]
Port: [Insert actual port - usually 7775]
How to troubleshoot with the OmniRouter™
- Logging and Messages — The OmniRouter provides a logging and messaging screen on the interface itself. Important messages are recorded there including startup and transmission issues.
- How to troubleshoot OmniRouter Configuration Issues — If you are having issues configuring your OmniRouter first make sure you are connected to the Internet. We recommend you open a web browser and go to www.omnipacs.com. If you are able to successfully load the page then you are on the Internet. If you are able to confirm Internet connectivity and your OmniRouter is running please stop then restart the OmniRouter and verify with console logging that the service is running and started "ok".
- How to troubleshoot Modality Connectivity Issues — If you are still having issues and suspect the issue is related to modality configuration:
- Ping the Modality IP from the PC running omnirouter.
- Ping the OmniRouter from the IP.
- Verify DICOM connection information.
Use of the OmniRouter™ is currently provided with NON FDA class II certification. While diagnostic interfaces provided on the OmniPACS platform are FDA and CE approved the us of OmniRouter-Beta is at your own risk. The OmniRouter is open source software and uses a standard library of mature DICOM components.
Compliance with state and federal regulations regarding patient confidentiality, security, and privacy is the responsibility of all health care providers and related Covered Entities. This includes, but is not limited to, compliance with the Health Information Portability and Accountability Act (HIPAA) of 1996. The Health Insurance Portability & Accountability Act was written into law on August 21, 1996. HIPAA regulations will have an effect on operational procedures on all healthcare provider organizations.
HIPAA recognizes that the largest task in compliance is administrative, not with the technical features of computer systems. That administrative task primarily involves policy and procedures, establishing a system security and information confidentiality policy, training all personnel in that policy and appointing a "security officer" to monitor compliance with the policy.
To help healthcare organizations achieve their goals, OmniPACS provides configurable storage and distribution systems that protect the privacy and security of patient information.
Current OmniRouter™ Version: 22.214.171.124
HTTPS Link Here