Web-Based RIS vs Client/Server RIS

Today, there are two major types of RIS system architectures.  One is Web-Based and the other is Client/Server. 

Client/Server, as the name implies, consist of a file server and one or more 'thick' clients (workstations) attached via Ethernet cables.  Multiple sites can be connected via T1 or DSL land lines.  

Pros:

• Data resides on a file server that typically resides on-site.  
• The system is more 'closed' to the outside than Web-Based and thus easier to secure.
• Computer languages that are used to develop Client/Server applications are much more powerful than those used by Web-Based, thus allowing more features and functionality. 
• Not impacted by internet outages. 

Cons:

• The 'Thick' clients get their name from the fact that they require more memory and storage than those 'Thin' clients of a Web-Based application.  
• Can't share the data over the internet.

Web-Based, as the name implies, works over the World Wide Web via the internet.  This type of system uses 'thin' clients (workstations) and can be accessed anywhere there is an internet signal.

Pros:

• 'Thin' clients are less expensive than 'Thick' clients.
• Typically requires less attention from IT department.
• Can share data anywhere in the world.

Cons:

• Data is highly exposed over the internet despite secure internet connections.
• Features and functionality are limited compared to Client/Server applications.
• Internet outages cause RIS system downtime.

This is the first question that should be answered before searching for a radiology information system for your facility/department.

Questions:

1. Are there other sites that need to be connected to this application?
2. Are there wired (typically underground) connections between the sites that need access to this system?  These connections are called T1 or DSL lines.
3. Are basic RIS features adequate for your needs?
4. Do you trust the internet?
5. Do you have a strong IT department?
6. Is your area prone to internet outages?

If you answered YES to #1, #3 and #4, and you answered NO to #2 and #6, a Web-Based architecture might be suitable for your needs.

All other scenarios would point you towards a Client/Server application.