Comments on: Guest Article: Rich Internet Applications for Improved Healthcare App User Experience

By: Medicaid Doctors

Medicaid Doctors — Sat, 07 Aug 2010 21:02:08 +0000

I'm not finished read this yet, but it's so fabulous 'n I'll back again when I was finished my job

By: Atul Bengeri

Atul Bengeri — Wed, 20 Feb 2008 05:46:25 +0000

When it comes to a Hospital Information System – technology is the least of the problems! More so the Thick vs thin client issue!

Training, implementation, adoption, usage are the fundamental issues that gain importance.

And when it comes to Thin vs thick – the choice is very clear – either go with a thin client and spend thickly on the backend or go with a thick client and have your investment protected!

Some food for though!

By: Paul M

Paul M — Mon, 14 Jan 2008 15:00:46 +0000

I have several health care clients and all of them are looking at thin clients for a variety of reasons: costs,support, availability, and security. The specific implementations are not just for bedside or for clinical areas but also include back office, outpatient areas and kiosks.

It seems that thick vs thin is not really the debate any more but rather how to best apply thin computing across all comupting areas.

By: Mark Singh MD

Mark Singh MD — Fri, 02 Nov 2007 00:19:58 +0000

Thin vs Thick clients is always a great discussion. Microsoft has the “Smart Client” platform which is essentially a thick client UI that uses web services on the back-end to connect with the data-store. This has the benefit of allowing the “Smart Client” application to work in distributed environment, just like a typical web application.

The “rich” windows UI of the Smart Client is the advantage over a web UI. Ajax however is making web applications look more like a rich Windows-like UI. Just check out, for example, the new Yahoo mail (my personal email platform).
Mark Singh MD
http://www.Clinicore.blogspot.com