Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

eCW

No description
by

Nikhil Mehta

on 3 October 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of eCW

eCW - Various Architectures
Presentation By Nikhil Mehta
Presentation Tier
eCW Architecture
The top most level of the application is the user interface. The main function of the interface is to translate tasks and results into something the user can understand
Logic Tier
This layer coordinates the application, processes commands, makes logical decisions and evaluations and performs calculations. It also moves and processes data between the two surrounding layers
Data Tier
Information is stored here and retrieved from a database or file system. The information is then passed back to the login layer for processing and eventually back to the user.
Practices rolling out eClinicalWorks have two application architectures to choose from: SaaS, where the application is hosted by eCW or a Client Server,where the application is housed by your organization and maintained by the practice's Information Technology staff
Architecture Deployments
The 3 major components of eCW are the Tomcat, MySQL and FTP Services.

Depending on the additional requirements, practice may require the following server needs:
Fax Server
Reports Server
eHX Server
Test Server
Terminal Server
Citrix Server
Client Server Architecture
This differes from the client server as SaaS/ASP utilizes servers that are located at the eCW data centers. All computers at the practice connect to these through a SSL that is established between the practice and the data center
SaaS Architecture
Server: Intel Xeon Quad Cores 1.6 Ghz

# of Servers: 1 (App + DB + FTP)

RAM: 8 - 12 GB

Disk Space: 40 GB for OS & 120 GB for Data
Physical Hardware Req
1 - 5 Providers
Physical Hardware Req
10 - 25 Providers
Server: Intel Xeon Quad Cores 1.6 Ghz

# of Servers: 3 (1 App/FTP + 1 DB + 1 eBO)

RAM: 4 - 16 GB

Disk Space: 40 GB for OS & 120 GB for Data
*Database/eBO server averages 5GB each per FTE over 3 years. FTP averages11GB per FTE over 3 years.
Physical Hardware Req
26 - 50 Providers
Server: Intel Xeon Quad Cores 1.6 Ghz

# of Servers: 9 (2 App + 2 DB + 1 eBO + 1
Interface + 1 eBO )

RAM: 4 - 32 GB

Disk Space: 40 GB for OS & 120 GB for Data
Physical Hardware Req
51 - 150 Providers
Server: Intel Xeon Quad Cores 1.6 Ghz

# of Servers: 10 (3 App + 2 DB + 1 FTP + 1
Interface + 2 eBO + Test)

RAM: 4 - 32 GB

Disk Space: 40 GB for OS & 120 GB for Data
Physical Hardware Req
151+ Providers
Server: Intel Xeon Quad Cores 1.6 Ghz

# of Servers: 11+ (3+ App + 2 DB + 1 FTP + 1
Interface + 2 eBO + 1 Test)

RAM: 4 - 32 GB

Disk Space: 40 GB for OS & 120 GB for Data
Add one application server for every additional 100 users.
Hardware load balancer for two (2) or more application servers
Node OS Clustering for DB/FTP
Redundancy is defined as having a secondary peripheral, computer system or network device ready and in place that takes over when the primary unit fails.

Ability of a machine, equipment, or computer system to transfer operations from a failed component to an alternative or backup component, without interrupting operations or process flow is defined as Failover.
Redundancy & Fail Over
Example of Redundancy
Full transcript