Fully Featured Practice Management System

(1)

Fully Featured Practice Management System

System Requirements Specification

This documentation contains important information for all Medtech Evolution

Version: 2.3

(2)

Hence, the minimum expectation for running just Evolution is 2 Core CPU and 6 GB Memory to support 1-5 users in a terminal server environment. Configuring the system based on the recommended specifications would help to perform well even under peak usage by all the users, or as the business grows there will be need for more hardware resources to scale.

NOTE

: Though 64bit is recommended, customers who wish to use existing 32bit

infrastructure can install 32 bit version of Evolution as the first step and upgrade

to 64bit in the future.

(5)

Medtech Evolution Deployment – Options

The deployment consists of 3 layers:

When it comes to Deployment, there are 3 models to choose:

Note:

 The above servers/desktops can either be Physical or Virtual machines

 Each deployment model has its own advantages and limitations. It requires careful planning to identify the right model for your business. You can contact Medtech for technical consulting.

 If you wish to defer your hardware investment to future, you can start with Basic deployment and upgrade to optimal or recommended deployment model in the future.

(6)

High Availability – Options

Evolution comes with recommended High availability options for customers with large databases or requiring minimal downtime (24/7 practices). There are two aspects of High Availability that need to be taken in to consideration.

System availability

Distribution of workloads across multiple computing resources such as, computers, a computer cluster, network links, central processing units or disk drives and fault tolerance.

Data availability

1. Acceptable (or actual) data loss with various failure events.

2. Toleration of application service interruptions (No toleration of data loss).

High Availability options with Medtech Evolution

Application

Deployment Layers High Availability Support Comments

Client Desktop Not Applicable -

Terminal Server (RDS) Load Balanced High Availability Clustering Follow Link

Citrix XenApp Server Load Balanced High Availability Clustering Follow Link

Database

Microsoft SQL Server

SQL Server 2012 AlwaysOn FCI Medtech

recommends SQL AlwaysOn AG SQL Server 2012 AlwaysOn AG Database Mirroring Log Shipping Application Services

Application Services Server

Not Applicable -

Note:

Medtech provides guidelines only for High Availability options in Evolution Database Layer. There are no specific guidelines for High Availability configuration on Terminal server (RDS) or Citrix XenApp Server. Please follow recommendations from Microsoft and Citrix based on your Business Continuity Plan.

SQL Server 2012/2014 AlwaysOn Failover Cluster Instances, Database Mirroring & Log shipping requires Standard or Enterprise Edition. SQL Server 2012/2014 AlwaysOn Availability Groups requires Enterprise Edition.

(7)

Desktop (Client) Requirements

Below is a list of the minimum and recommended system requirements for a Medtech Evolution Client environment. The following requirements assume both the Server and the Workstations will not be running on any other applications or services other than Medtech Evolution.

Workstation Requirements

System Requirements Minimum Recommended Workstation Requirements

Intel core i3 2 Ghz CPU or equivalent

Intel core i5 2 Ghz CPU and more or equivalent

4GB DDR3 RAM. 8GB DDR3 RAM. Standard UPS Standard UPS

32 bit Windows 7 Professional 64 bit Windows 7 Professional or 64 bit Windows 8 Professional Dialup Internet Connection

with Antivirus & Firewall Protection (if running ACC45 Electronic Forms, Web Forms, ManageMyHealth™

Portal/SMS, or HealthLink)

Broadband Internet Connection with Antivirus & Firewall Protection (if running ACC45 Electronic Forms, Web Forms, ManageMyHealth™ Portal/SMS, or HealthLink)

Note:

(8)

Terminal Server (RDS) – System Requirements

Hardware Sizing

For remote desktop services hardware, it is recommended to buy scalable servers to meet future business requirements in terms of processor and RAM. These servers have good performance ratios, rack densities, good storage support, and can accommodate more RAM if required.

Note:

It is recommended to have flexibility by having extra hardware resources in order to

scale if there is a need for more capacity in future.

Minimum Configuration

Concurrent

Users Operating system

Processor -

(Physical/Virtual) Memory

1 to 5 Windows server 2008 R2 Standard 2 Core 2 vCPU 6 GB 6 to 10 Windows server 2008 R2 Standard 4 Core 4 vCPU 8 GB 11 to 15 Windows server 2008 R2 Standard 4 Core 4 vCPU 10 GB 15 to 20 Windows server 2008 R2 Standard 4 Core 5 vCPU 12 GB

Recommended Configuration

Concurrent

Users Operating system

Processor -

(Physical/Virtual) Memory

1 to 5 Windows server 2012 R2 Standard 4 Core 4 vCPU 8 GB 6 to 10 Windows server 2012 R2 Standard 4 Core 4 vCPU 10 GB 11 to 15 Windows server 2012 R2 Standard 4 Core 4 vCPU 12 GB 15 to 20 Windows server 2012 R2 Standard 5 Core 5 vCPU 18 GB

Note:

 Additional system requirements will apply if the Evolution application services are run or any third party applications are run in the Terminal Server

 If concurrent users are 20 or more, Medtech recommends scale-out Terminal Servers horizontally (with Load Balancing). If concurrent users are 50 or more, a specialised deployment architecture/specification from Medtech will be provided.

 Evolution can also be deployed on Citrix XenApp Servers without any special configuration from Evolution

(9)

Database Server – System Requirements

For Medtech Evolution, hardware requirements for Database play a vital role. It is highly recommended to allocate enough resource on the Database Server for better performance and scalability. Special considerations have to be given to Storage, Memory and CPU requirements. Also pay attention to SQL server edition (Express, Standard and Enterprise).

Minimum Configuration

Concurrent Users

Database Server Version

Edition Server Operating System Processor Physical/Virtual Memory 1 to 5 SQL Server 2008 R2 SP2

Express* Windows server 2008 R2 Standard

2 Core 2 vCPU 4 GB 6 to 10 SQL Server

2008 R2 SP2

Express* Windows server 2008 R2 Standard

2008 R2 SP2

Standard Windows server 2012 Standard

2012

Standard Windows server 2012 Standard 4 Core 4 vCPU 32 GB

Recommended Configuration

Concurrent Users Database Server Version

Edition Server Operating system Processor Physical/Virtual Memory 1 to 5 SQL Server 2012

Standard Windows server 2008 R2 Standard

2012

6 Core 6 vCPU 32 GB

Note:

 These recommendations assume no other external or third party application, database or service is installed on the Evolution database server.

 Memory and CPU usage cannot be directly attributed to concurrent users. Database size and the usage pattern need to be factored in sizing.

 SQL Server Express edition has Database Size (Max 10GB), CPU (1 socket and max 4 cores) and Memory (1 GB) utilization restrictions.

 For optimal performance, refer to the “Evolution Database Server Configuration Guide” for prerequisites, recommended configuration and limitations.

 Evolution is compatible with SQL Server 2014 (Microsoft Platform ready Test is pending as it is not made available from Microsoft. For more information please refer to this link

(10)

Application Services Server – System Requirements

Evolution Application Services are built to operate in the background. These services can be configured to start when the operating system is started and run in the background as long as Windows is running, and are designed to take advantage of multi cores available in hardware for timely processing.

Minimum Configuration

Operating System Processor - (Physical/Virtual) Memory

Windows 7 Professional

2 Core 2 vCPU 4 GB Windows server 2008 R2 Standard

Windows server 2012 Standard

Recommended Configuration

Operating System Processor – (Physical/Virtual)

Memory

Windows server 2012 R2 Standard 4 Core 4 vCPU 6 GB

Note:

 Additional system requirements will apply if third party services are run in the server

 Number of users may not be directly proportional to Application Services Server hardware sizing. Review of files to be processed will be helpful to determine the hardware requirements

 A site with 50 or more users should contact our Medtech Team for a specialised deployment architecture/specification consultancy

(11)

Network Requirements

Network Bandwidth Requirements

Type Recommended

Server Segment 1Gbps Gigabit Ethernet Client Segment 100Mbps Fast Ethernet Backbone 1Gbps Gigabit Ethernet

WAN Secured Virtual Private Network via public network or dedicated private network

Internet Broadband Internet, with proper security measures such as Antivirus & Firewall Protection

Network Device Requirements

Network Interface Card

For small networks: Unmanaged

For medium to large networks: SNMP compatible Layer 2 Device For small networks: Unmanaged Layer 2 Switch

For medium to large networks: Managed Layer 2 Switch with SNMP support

Layer 3 Device As required to isolate Medtech Evolution segment from other LAN/WAN segments

Note: It is recommended to contact your IT Technician for full details as

Medtech provides these as general recommendations.

Network Cabling Requirements

Cable Type Unshielded Twisted Pair (UTP) Category 5e or Category 6 certified Connector Type Registered Jack RJ45

Certification All cabling segments tested and certified for TIA/EIA-568-B standard

Firewall / Proxy Requirements

ACC45 Electronic Forms Allow HTTP on Internet for: emgweb.acc.org.nz

Allow HTTPS on Internet for: emg.acc.co.nz

ManageMyHealth™ Portal

Allow HTTP and HTTPS on Internet for: managemyhealth.co.nz

ManageMyHealth™ SMS Allow HTTP on Internet for: sms.managemyhealth.co.nz

Web Forms Allow HTTP on internal LAN/WAN for:

Web Forms Engine - Default = servername:8080

i.e. ServerName: Port for Apache Tomcat, installed by default with Idiom installer

MT SOAP Service - Default = servername:7080

(12)

Default = servername:5099

i.e. ServerName: Port for HealthLink Quantum – please contact HealthLink for further information.

SMTP Details Below details are required for sending email from Diagnostics Services 1) SMTP Host Address 2) Port Number 3) Is SSL Secured 4) SMTP Server 5) SMTP Authentication

Printing Requirements

Type Recommended Driver Compatibility

Windows Driver Model (WDM) compatible Driver Language Recommended:

- Printer Command Language 5 (PCL 5) - PostScript (PS)

- Printer Command Language 6 (PCL 6) NOT Recommended:

- Other manufacturer proprietary languages Paper Size MUST be capable of handling both A4 and A5 Manual Feed

(optional)

For printing pre-formatted forms and letterheads if required Multiple Trays

(optional)

For handling different paper types and paper sizes without manually changing/feeding paper if required

Label Printing (optional)

For printing laboratory, medication and mail merge labels if required

Recommended Printer Models

Recommended (general)

Any Laserjet printers Recommended

(label)

Dymo 400 Series Label printers SATO GL408 series Label printers Zebra GK420t - ZPL Label printers NOT

Recommended

All-in-one multifunction printers not using PCL5/PCL6 and Twain version 2.3

Kyocera Incompatibility

It has been reported Kyocera printers may cause intermittent illegible document printouts from Medtech Evolution

(13)

Printer Deployment Considerations

 If the practice will be printing on both A4 and A5 papers, then two separate instances of the printer will need to be installed and configured for each paper size

 When configuring multiple tray printers in Windows, aside from installing one instance of the printer for each paper size, you will also need to INACTIVATE or DISABLE or make NOT AVAILABLE the unused trays. Any auto-tray-select features will also need to be DISABLED

 Network Printers with their own IP Addresses will need to be installed as LOCAL printers on the workstations to work efficiently with Medtech Evolution

 Remote printers will also need to be installed as LOCAL printers on the Terminal Services Server for these printers to work properly in Terminal Services Client sessions. The Microsoft Terminal Service Print driver will need to be disabled on the Terminal server on the Local GPO. http://technet.microsoft.com/en-us/library/cc753853(v=ws.10).aspx.

ComputerConfiguration\AdministrativeTemplates\WindowsComponents\TerminalSer vices\Terminal Server\Printer Redirection.

 Ensure Automatic Search for Network Printers and Folders has been DISABLED as a policy

 "Automatic" Client Printer Mappings should be disabled in Terminal Services Client sessions. Instead, "Static" Server Printer Mappings should be created via Windows logon scripts.

 Even though no users will be logging on to the Medtech Evolution Server, a dummy printer MUST be installed on the Server for Medtech Evolution to function properly. E.g. Cute pdf, MS XPS

 All printer names must conform to the Medtech Evolution naming convention, i.e. less than 64 characters in length, and avoid using spaces and symbols like \ / : * ? " <> | in the names

 If client and Printer server has Windows 7, Windows Server 2008 R2 and later operating systems, Medtech recommends to set the Driver Isolation as Isolated for each print driver

 Pull Printing (i.e FollowMe) is not supported from Evolution.

Note:

Responsibility on Print Driver Upgrade and Driver Hotfix relies on IT Technicians but not with Medtech.

(14)

Scanning and Digital Imaging Requirements

Printer Requirements Type Recommended Scanner / Digital Camera Requirements

Driver Compatibility MUST be TWAIN 2.3 compatible Image Format

Compatibility

Scanning Module Support: - TIFF, TWAIN2.3

Drawing Tool Support:

- BMP, GIF, JPEG, TIFF, TWAIN2.3 Paper Size Capable of handling A4 Automatic Document

Feeder (optional)

For scanning multiple documents if required Recommended

Scanner Models

Recommended TWAIN 2.3 compatible

NOT Recommended Any all-in-one multifunction printers Recommended

Digital Camera Models

Recommended TWAIN 2.3 compatible

(15)

Scanner/Digital Camera

Deployment Considerations

 Scanning via Citrix and Terminal Services sessions is not supported. The workaround is to use TIFF file scanner source from Evolution through a network shared path

 Medtech Evolution can only interface with TWAIN2.3 compliant scanners and digital cameras. Aside from the recommended scanner and digital camera models listed above, Medtech CANNOT guarantee that other brands or models can be fully integrated with Medtech Evolution.

 It has been reported many all-in-one multifunction devices could cause compatibility issues or could limit scanning functionalities when scanning within Medtech Evolution – this is especially the case with the low-end models.

 It is NOT recommended to enable TWAIN GUI Mode – i.e. scanning via the GUI (graphical user interface) of the TWAIN2.3 compatible driver/software supplied by the scanner’s manufacturer – unless your scanner does not function properly when scanning directly into Medtech Evolution

 Network scanners should be installed as LOCAL scanners, i.e. TWAIN2.3 driver is locally detectable for Medtech Evolution scanning to work

 When scanning multi-page documents via the scanner’s ADF (automatic document feeder), you can add a blank piece of paper between each document – the blank page will be detected as a separator and Medtech Evolution will automatically create a new Inbox record

 Duplex scanning is not supported unless all pages to be scanned within the same document have information printed on both sides, as any blank front or back page will be detected as a document separator

NOTE:

The blank page should ALWAYS be of the maximum paper size that your

(16)

Supported Operating Systems

Supported 32-Bit/ 64-Bit Server

Operating Systems

 Windows Server 2008 R2 Standard Server (64-bit)

 Windows Server 2008 R2 Enterprise Server (64-bit)

 Windows Server 2012 Standard(64-bit)

 Windows Server 2012 R2 Standard(64-bit) Supported 32-Bit/ 64-Bit Desktop

Operating Systems

 Windows 7 Professional Edition (32-bit , 64-bit)

 Windows 7 Ultimate Edition (32-bit , 64-bit)

 Windows 7 Enterprise Edition (32-bit , 64-bit)

 Windows 8 Professional

 Windows 8 Enterprise

 Windows 8.1 Professional

 Windows 8.1 Standard

 Windows 10 *

Any Operating System NOT included in the “32-Bit/64 Bit Operating System Support” section is NOT supported by Medtech.

NOTE:

Windows 10 Certification is in progress and expected to complete by October 2015. Any Evolution customers considering upgrading to Windows 10 in the meantime should contact Medtech for a review.

(17)

Non Supported Operating Systems

Non Supported 32-Bit/ 64-Bit Server Operating Systems

 Windows NT 3.51 Server or earlier

 Windows NT 4.0 Server Windows 2000

 Server Windows 2000 Advanced Server

 Windows 2000 Datacenter/Small Business Server

 Windows 2003 Compute Cluster Server

 Windows 2003 Datacenter Server

 Windows 2003 Storage Server

 Windows 2003 Web Server

 Windows 2003 Small Business Server

 Windows 2003 Standard Server (32-bit)

 Windows 2003 Enterprise Server (32-bit)

 Windows 2008 HPC Server

 Windows 2008 Server for Itanium-Based Systems

 Windows 2008 Storage Server

 Windows 2008 Web Server

 Windows 2008 R2 Datacenter Server

 Windows 2011 small business server

 Windows 8 Home

 Windows Home Server

 Any non-Windows OS Non Supported 32-Bit/64-Bit Desktop Operating Systems

Earlier versions of Window XP and Window Vista(all editions)

 Windows 7 Starter Edition

 Windows 7 Home Basic Edition

 Windows 7 Home Premium Edition

 Windows 8 Home Edition

 Windows 8 RT

 Any non-Windows OS

NOTE:

Medtech Evolution does NOT support the above versions of Microsoft Windows. Although it might be possible to run Medtech Evolution on these operating systems, Medtech will not be able to provide support if a practice encounters problems while running on these unsupported Windows versions.

(18)

Server Deployment Considerations

 Due to performance issues, it is NOT recommended to install SQL server and Medtech Evolution on ANY server that is utilized by other resource-hungry functions, such as Domain Controller, Domain Name System (DNS), Windows Internet Naming Service (WINS), Dynamic Host Configuration Protocol (DHCP), Exchange, Internet Information Services (IIS), Internet Security and Acceleration (ISA), SharePoint Services, etc. Instead, DEDICATED servers should be allocated to serve SQL and Medtech Evolution requests ONLY.

Note: If this cannot be avoided, please consult with Medtech for suggestions.

 Due to compatibility issues, it is NOT recommended to install ANY OTHER Database Management System (DBMS) such as Firebird, Informix, Oracle, Sybase, etc, on the Evolution Database Server that runs MS SQL Server

Note: If this cannot be avoided, please consult with Medtech for suggestions.

 Due to performance and compatibility issues, it is recommended to install SQL Server in a dedicated physical or virtual machine and not on any Citrix or Terminal server

 Medtech Evolution relies heavily on accurate timestamp to function properly. It is CRITICAL to ensure Regional and Language Options are set to English (New Zealand) on ALL computers, and time synchronization is set to run automatically on ALL computers across the whole internal LAN/WAN.

 Set date and time format as below:

o Short Date: d/MM/yyyy h:mm tt AM/PM

(19)

Client Deployment Considerations

 If the workstations fall below the minimum hardware requirements (please refer to the "Desktop Requirements" section above). It is recommended to use Citrix or Terminal Server to deploy Medtech Evolution

 Microsoft Terminal Services and/or Citrix Presentation Server together with Virtual Private Networking (VPN) is a proven solution in providing remote access to your Medtech Evolution clients and in deploying Medtech Evolution on multi-site practices

 Running any applications (such as Medtech Evolution) under Microsoft Terminal Services could result in a slower programme response as compared to the recommended Client/Server setup. The response time is dependent on the Terminal Server's hardware specifications.

 Where Windows 7 and above is installed, ensure "Password Protected Sharing" has been ENABLED as a policy

 For Citrix and Terminal server, Evolution should be installed by an Administrator or admin privileged user for Fresh Installation and Upgrade

 For Client server, Evolution should be installed by an Administrator or admin privileged user for Fresh Installation. But for upgrades, it does not require an administrator. Evolution Application Services should be installed by an Administrator or admin privileged user for Fresh Installation and Upgrade. It is applicable for all kinds of environments like Citrix and Terminal server, Client server, etc.

 Windows Display Properties MUST be set to a minimum resolution of 1366 x 768 pixels. Resolution of 1920 x 1080 is recommended (Monitor size = 24 inches)

 Medtech Evolution relies heavily on accurate timestamp to function properly. It is CRITICAL to ensure Regional and Language Options are set to English (New Zealand) on ALL computers, and time synchronization is set to run automatically on ALL computers across the whole internal LAN/WAN.

 Set date and time format as below:

o Short Date: d/MM/yyyy h:mm tt AM/PM

(20)

ManageMyHealth

™

Deployment Considerations

ManageMyHealth™ Portal Integration

In order to utilise the new ManageMyHealth™ portal features, your practice MUST first apply for a Portal Account with Medtech.

Please refer to the "Additional Server Requirements" and "Firewall / Proxy Requirements" sections above for connection requirements. Please contact Medtech Sales for further information on 0800 2 633 832.

Medtech SMS Integration

In order to utilise the Medtech SMS features, your practice MUST first apply for an SMS Account with Medtech.

Please refer to the "Additional Server Requirements" and "Firewall / Proxy Requirements" sections above for connection requirements. Please contact Medtech Sales for further information on 0800 2 633 832.

Web Forms Integration

Idiom MUST be installed on the Evolution Application Server, which includes all the required components – i.e. Idiom Forms Engine, Apache Tomcat 5.5.9, and Sun Java Runtime Environment 1.5.0.15. Please refer to the “Evolution Installation Guide” for more information. Oracle Java 1.5.0.15 MUST be the ONLY Java version installed on the Medtech Application Server. Although newer versions of Oracle Java (e.g. Java 1.6) can co-exist on the same computer, it is not recommended to have any newer versions of Java installed unless it is absolutely necessary.

Due to compatibility issues, it is recommended to DISABLE the "Check for Updates Automatically" option in the Java Control Panel, as Medtech cannot guarantee that any future versions of Java will be compatible.

Minimum Microsoft Internet Explorer 9.0 must be installed on the Server. Compatibility View may need to be enabled if you are having difficulties running certain Web Forms on Internet Explorer 9.0 & above. Medtech recommends verifying or confirming with the respective publisher before upgrading Internet Explorer to the latest version.

(21)

Third Party Software Integration Considerations

Adobe Acrobat Integration

 Medtech Evolution Patient Information Sheets can only work with the Reader version of Acrobat. Any other versions of Acrobat are not supported

 Each computer that requires access to the Patient Information Sheets MUST have the appropriate Acrobat Reader version installed

 The version of Acrobat Reader supported is dependent on the Medtech Evolution version installed, as shown in the following table

Supported Acrobat Versions Acrobat Reader 11.0.7

Warning:

Although it might be possible to integrate Medtech Evolution with other Acrobat versions, Medtech WILL NOT be able to provide support if a practice encounters problems while running on any Acrobat versions not listed above. Medtech highly recommends to switch-off the auto-upgrade on Adobe Acrobat reader.

Third Party Email Software Integration

MAPI compatible email client MUST be installed and configured on any Server or Client that needs to email documents or files from Medtech Evolution Outbox and/or Attachments Manager Modules.

Supported MS Office Versions MS Office 2007/2010/2013

Medtech Contact Details:

If you require further information, please do not hesitate to contact the Medtech Customer Care Team on:

Tel: 09 358 1123 Option 1 or 0800 2 MEDTECH (633 832) Email: [email protected].

Fully Featured Practice Management System