|
Thin-Client
What
is a thin-client, and why are we using this technology?
Thin-Client technology
Thin-client is a hybrid taking advantage of unique features of both
client-server technology and terminal-mainframe models.
Thin-clients offer significant advantages including: lowering the total
cost of ownership, increased security, and improved ease of use.
A thin-client can use the Internet and be presented using Microsoft's
Internet Explorer. Thin-Clients use
local Internet service providers, which avoids long distance charges.
Security
Thin-clients offer inexpensive and superior security because data is
never transferred to the local hard drives or over public telephone lines. Java based applications data is transferred over public lines
and in order to secure the information requires using very expensive technology
like virtual private networks. Security
is not only a moral necessity under HIPAA legislation it is the law.
Lower
Costs
At the present time it costs around $10,000 per year to maintain a desktop. Total cost of ownership is lower for a thin-client
architecture because hardware requirements on the desktop are minimal; an Intel
486 CPU with a network card or an analogue modem is all that is needed.
Software costs are also drastically reduced because the application
resides on the central server, this avoids distribution costs, and license fees
for each individual desktops. Maintenance costs are also lower, though thin-clients require
an extra server the costs more than offset the need to ?? only a single machine
while avoiding software upgrades, compatibility issues, and desktop
support.
Remote
Access
If we are able to stabilize this technology, users will have remote access to
records and can work from home. Because
thin-clients only transfer screen shots the image has a small “foot print”
12 to 20 kilobytes. This will
allow users with an analogue modem to access the application remotely while
avoiding the need for costly cable modems or DSL lines.
Return to the top of
the page
How does a
Thin-Client Model compare to a Client Server
Model?
Client-Server
In a Client-Server Model (see
Figure #1) the patient information is retrieved through a server; it is
then downloaded into the local PC/client where the local computer does the work. When a user wants to print, the information flows from the
local hard drive directly to the printer.
Figure
1
How does
a Thin-Client model work?
In a thin-client model (see Figure #2) the computer
is like dumb terminal, and when you are working, processing happens at the
Thin-Client Server in a remote location. In
fact, what you see in front of you is just an image of the information.
When a user decides to print something, the information is on the
thin-client server. The server must
contact the local terminal and ask it where it is located, who the user is and
where the local printer is.
Figure
2
Return to the top of
the page
-
1. Double click the new
Icon on your desktop "TSCRIS"
-
2. Type in your DEMPO ID
and password (same as CRIS login - see Figure 3) at the “Windows 2000
Server” login screen
-
3. When the CRIS login
screen appears (Figure 4) type in your Logon and Password again and Click
"OK"
-
4. You should be at the
Main Menu screen for CRIS at this point
Printing
Printing from CRIS requires you to verify your printer selection at least once
per session. We know this seems like an unnecessary extra step to have to do
before you begin work but it is essential to ensure that all patient information
remains confidential and is only being printed to secure areas in the clinic. I
Return to the top of
the page
|
