Hardware and Software Specifications

Hardware and Software Specifications

Download our hardware specification checklist

  • Server

    Microsoft Windows Server 2008, 2008 R2, 2012, 2012 R2 or 2016 64 bit operating system – SBS 2008 and SBS 2011 are also supported

    • IIS installed and running
      • ‘Dynamic Content Compression’ not installed
      • ‘IP Security’ option must be installed
      • ‘Windows Authentication’ option must be installed
    • Microsoft SQL Server 2005, 2008, 2008 R2, 2012, 2014 or 2016
      • Named instance called ‘STAT’
      • Only the database engine and the complete management tools are required
      • The ‘Express’ edition has a number of limitations that make it unsuitable in most practices, such as a database size limitation.
      • An edition other than ‘Express’ is generally required.
    • 32Gb RAM recommended  (more for larger practices).  16Gb RAM minimum. For larger practices with more then 15 computers, estimate the minimum RAM required as follows
      • < 15 computers – 32Gb
      • 30 computers – 50Gb
      • 40 computers – 64Gb
      • Calculate the required RAM using the following formula : 4Gb RAM for Windows + 16Gb RAM for SQL Server +  1.5Gb RAM for each Stat thread running on the server (The number of threads is configurable, using the number of computers in use at the same time – 10 as a starting point)
    • Disk system
      • System performance is most affected by disk sub-system performance
      • Redundancy is important to protect critical patient and clinical data
      • Multi disk RAID systems ie. RAID 10 will give better performance and redundancy
      • Hard disk capacity required for data conversion: minimum 4 x existing database size
    • Microsoft .NET 4.6.2
    • WCF enabled
    • Regional Settings set to ‘English (Australia)’
    • Broadband Internet access
    • The servers time zone along with the actual date and time must be set correctly
    • Distributed Transaction Co-ordinator service set to auto start and be running
    • The network should be configured with a domain and all servers and workstations running Stat must be joined to the same domain
    • There should be an internal DNS server for the domain.
      • There will need to be an internal DNS entry for ‘StatInternal’ that resolves to the IIS server
      • There will need to be an internal DNS entry for ‘StatExternal.yourdomain.com‘ that resolves to the IIS server
      • There will need to be an external DNS entry for ‘StatExternal.yourdomain.com‘ that will allow external users to access the internal IIS server
    • Microsoft Visual C++ 2008 Redistributable Package (x86)
    • Microsoft Visual C++ 2010 Redistributable Package (x86)

    Server specifications (CPU, Memory, Hard Disk etc.) will vary depending on the number of workstations in use, other programs that you might be running and number of patients. Servers with a single CPU (e.g. Intel Core i7) will be acceptable for smaller practices, however for larger practices servers running multiple CPUs, each with multiple cores (e.g. Intel Xeon) may be required.

    Some editions of Microsoft SQL Server only support a certain CPU configurations; this must be taken into account when determining server specifications. Please discuss these issues with an appropriate hardware and network supplier.

    A minimum of RAID 1 with 2 disks would be suggested for smaller sites, however RAID 10 with 4 or more disks would enhance performance. For larger practices a minimum of RAID 10 with 4 or more disks would be required to achieve suitable performance. This allows for data redundancy and fault tolerance as well as performance.

    Microsoft Word is required under certain circumstances, please refer to Data Conversion section in this document.

    Workstations

    • Windows 7 SP1,  Windows 8/8.1 or Windows 10 (‘Home’ editions not supported)
    • Intel Core i3 or better CPU
    • 4Gb RAM minimum
    • 1920×1080 recommended. Note that both the video card and display must support this resolution. (1280×1024 minimum resolution)
    • Microsoft .NET 4.6.2
    • Regional Settings set to ‘English (Australia)’
    • Screen fonts and scaling
      • Prior to Windows 8.1 the windows default font size “Smaller” must be used
      • In Windows 8.1
        • the legacy settings must be used “Let me choose one scaling level for all my displays” with “Smaller”
        • or the screen scaling will need to be adjusted to balance screen resolution and readability. There is no one size fits all option here as this Windows option is dynamic based on a number of factors including screen size and resolution. If incorrect settings are selected then Stat may fail to display all of its screen correctly – in this case a warning is presented upon startup.
    • Stat client software on the workstations is self updating after  Stat has been upgraded on the server.  In order for this to work the users must have permissions to create and delete files in the Stat client folder (defaults to C:\Program Files\Stat Health)
    • Broadband Internet access
    • No ODBC or mapped drives/UNC paths required to the server; workstations connect using Web Services via HTTP
    • The workstation time zone along with the actual date and time must be set correctly
    • All workstations must belong to the same time zone (server time zone may be different)
    • Workstations should be set to synchronise time with the server periodically
    • Microsoft Visual C++ 2008 Redistributable Package (x86)
    • Microsoft Visual C++ 2010 Redistributable Package (x86)
    • Microsoft POS for .NET V 1.1.2

    Standalone computer (Server and Workstation)

    • One of the operating systems listed under either Server or Workstations above
    • IIS installed and running
      • ‘Dynamic Content Compression’ not installed
      • ‘IP Security’ option must be installed
      • ‘Windows Authentication’ option must be installed
    • Microsoft SQL Server 2005, 2008, 2008 R2, 2012, 2014 or 2016 with named instance ‘STAT’
      • The ‘Express’ edition has a number of limitations that make it unsuitable in most practices, such as a database size limitation.
      • An edition other than ‘Express’ is generally required.
    • 8Gb RAM minimum
    • Disk system
      • System performance is most affected by disk sub-system performance.
      • Redundancy is important to protect critical patient and clinical data
      • Multi disk RAID systems like RAID 10 will give better performance and redundancy
      • Hard disk capacity required for data conversion: minimum 4 x existing database size
    • Microsoft .NET 4.5.2
    • WCF enabled
    • Regional Settings set to ‘English (Australia)’
    • Broadband Internet access
    • The servers time zone along with the actual date and time must be set correctly
    • Distributed Transaction Co-ordinator service set to auto start and be running
    • Instead of a local DNS server, there will need to be a ‘Hosts’ file entry for ‘StatInternal’ that resolves to the local computer
    • Microsoft Visual C++ 2010 Redistributable Package (x86)
    • A minimum of RAID 1 with 2 disks would be suggested for smaller sites, however RAID 10 with 4 or more disks would enhance performance. This allows for data redundancy and fault tolerance as well as performance.
    • Microsoft Visual C++ 2008 Redistributable Package (x86)
    • Microsoft Visual C++ 2010 Redistributable Package (x86)
    • Microsoft POS for .NET V 1.1.2

    Microsoft Word is required under certain circumstances, please refer to Data Conversion section in this document.

    Network

    The Stat IIS server must have a high bandwidth connection to the SQL database server. 1Gbps minimum is recommended.

    The Stat client is designed to have a high bandwidth connection to the Stat IIS server. 1Gbps minimum is recommended.

    Where the client does not have a high bandwidth connection to the IIS server, RDS or Citrix servers are required.  The Stat client will work over a low bandwidth connection however performance will be affected.

    Stat Backup

    Stat utilises two Microsoft SQL Server databases to store all of its data.

    • Typically Stat uses a named instance of SQL Server called ‘STAT’
    • Typically Stat uses two databases, one called ‘Stat’ and the other called ‘StatClinical’

    The databases are contained in seven files on the file system. The names and locations of these files are configurable and depend on the setup of the server.

    Typically they all exist in the folder:

    C:Program FilesMicrosoft SQL ServerMSSQL.{x}MSSQLData

    where {x} is a number starting at 1. If the ‘STAT’ instance of SQL Server is the only one on the server then the folder would be:

    C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData

    The seven files are typically called:

    • Stat.mdf
    • Stat_1.ndf
    • Stat_2.ndf
    • Stat_3.ndf
    • Stat_4.ldf
    • StatClinical.mdf
    • StatClinical_1.ldf

    Stat does not have an inbuilt backup solution. An appropriate backup solution needs to be used that will allow all the data in the Stat databases to be backed up. Backing up the data multiple times a day (like hourly, or even more often) may reduce data loss if a backup needs to be restored.

    The preferred way to backup this data is by using a SQL Server compatible backup solution (e.g. StorageCraft ShadowProtect)

    It is important that whoever is given the task of setting up the backup of your system be proficient with SQL Server backup techniques so as to avoid data loss in the event of a problem that requires the database to be restored from the backup.

    It is also important that the Microsoft SQL server transaction logs be appropriately backed up and appropriately truncated otherwise they will grow to consume all available disk space.

    Click on this link for further information re Storage Craft http://www.storagecraft.com.au/best-practice-guides/BP000016%20Microsoft%20SQL%20Server%202012-2008%20R2-2008.pdf

    NB: By default Microsoft SQL Servers transaction logs are not truncated automatically. If left unchecked these transaction logs will eventually consume all available disk space. It is therefore imperative that appropriate action is taken to address transaction log size e.g. by means of SQL maintenance plans.

    Remote Connectivity

    Stat requires RDC access to the server and all workstations. This can be provided either as a direct RDC connection or via an RDC gateway. (VPN Connections are not suitable)

    Remote Desktop Service Server (Terminal Server)

    Stat is designed to allow it to run in a Microsoft Windows RDS Server environment. This capability can be used to allow access to the Stat application over lower speed networks than would be possible otherwise. This may be useful in allowing doctors and staff to access the Stat application from other locations.

    In order to provide remote support, Stat Health Systems (Aust.) requires RDC (RDP) access. If your site uses RDS please be aware that we will require one remote access CAL to be available at the time of remote access.

    SMS

    SMS functionality is available in Stat using SMS Central to supply SMS credits.

    Outbound SMS is available with just an internet connection from the server.

    To receive inbound SMS the following is also required:

    You will require your hardware supplier to configure your network as your practice will need a publicly available URL (StatExternal.yourdomain.com) and a port;

    The inbound traffic must arrive at Port 80 on the IIS Server and there are two methods to achieve this:

    • Externally the traffic arrives at Port 80 and is passed straight across to the IIS Server
    • Externally the traffic arrives at any other Port and is passed across using Port translation to Port 80 on the IIS server. (In this case Port 81 is preferred as the external Port for consistency)

    Please provide the DNS name (IP address is not suitable) along with the external port number to Stat Support.

    Printers

    There are numerous brands and models of printers on the market – only a small number have been tested by Stat.

    For the Doctor’s desk – an efficient and small laser printer for scripts, request and letters is important. Alternatively a larger printer with multiple paper trays (e.g. for script, pathology and plain paper) may be preferred. Hewlett-Packard has a large number of business laser printers, including printers in this category.

    For Reception – a heavy duty, fast and reliable printer is recommended. Hewlett-Packard has a large range of business laser printers.

    Label Printer

    Stat supports the Dymo LabelWriter 450 series label printer.

    Scanner

    Stat can automatically import files created using any device eg. scanners, cameras etc.

    Files imported into Stat can be displayed using the internal viewer or opened in a third party application eg. Adobe Acrobat Reader.

    Scanning PDF’s is very popular and Stat does support displaying PDF’s using its internal viewer. Due to the wide range of encoding options available  with PDF’s it is advisable to test that the PDF’s display correctly using the internal viewer. At this time the third party manufacturer that produces the PDF  display component does not support JPX (JPeg2000) encoded images.

    Data Conversion

    Please Note: Conversion of your data will be undertaken on your existing server. The time to run a conversion is heavily influenced by the speed of your server (CPU, RAM, Hard disk).

    If converting documents created using Microsoft Word you will require a complete copy of Microsoft Word 2010 or Microsoft Word 2013 on the Server where the conversion will be run. Microsoft Word 2010 Starter Edition is not supported.

    NB:This hardware specification is continually revised and updated to ensure the Stat application performance continues to be optimised.



  • This document contains important information regarding the configuration
    and ongoing use of your hardware and software. It isimportant that all the information is read and understood in consultation with your hardware and networking supplier.Stat relies upon the information being supplied below as being complete and accurate. In the event that the checklist has not been completed fully and accurately there will be an additional charge for any rework that is required.

    Remote Access Details





    UAC and Permissions

    Tick or Cross

    We require two administrative users called ‘StatSupport’ and ‘StatSupport2’

    Is UAC turned off on Server and Workstations for all accounts using Stat?

    Server

    Server hosting

    Physical
    HyperV
    WMWare

    32GB RAM or greater

    Disk System

    • System performance is most affected by disk sub-system performance
    • Redundancy is important to protect critical patient and clinical data
    • Multi disk RAID systems ie. RAID 10 will give better performance and redundancy
    • Hard disk capacity required for data conversion: minimum 3x existing database size

    Microsoft Windows Server 2008, 2008 R2, 2012 R2, 2016 64 bit operating system. SBS 2008 or SBS 2011 are also supported

    Microsoft SQL Server 2005, 2008, 2008 R2, 2012,  2014 or 2016 with named instance ‘STAT’

    • The ‘Express’ edition has a number of limitations that make
      it unsuitable in most practices, such as a database size limitation.
      An edition other than ‘Express’ is generally required.
    • MS SQL Server must be configured to use an appropriate maximum  amount of system memory.

    Internet Information Services (IIS) installed and running

    • ‘IP Security’ option must be installed
    • ‘Windows Authentication’ option must be installed

    WCF Activation Installed and enabled

    Microsoft .NET 4.6.2

    Microsoft Visual C++ 2010 Redistributable Package (x86)

    Regional Settings set to ‘English (Australia)’

    The time zone along with the actual date and time
    must be set correctly.

    • All workstations must be in the same time zone as each other.
    • The server is able to be in a different time zone.

    Broadband internet access.

    Distributed Transaction Co-­ordinator service set to ‘Automatic’ start and be running.

    The network should be configured with a domain and all servers and workstations running Stat must be joined to the same domain.

    There must be an internal DNS server for the domain a DNS entry for ‘StatInternal’ that resolves to the IIS server

    If using any external inbound services (e.g. SMS, Online Appointments) we also require

    • A static IP address with routing configured to allow external access  to web services
    • an internal DNS entry for ‘StatExternal.yourdomain.com’ that
      resolves to the IIS server
    • an external DNS entry for ‘StatExternal.yourdomain.com’ that will  allow external users to access the internal IIS server

    Server specifications (CPU, Memory, Hard Disk) will vary depending on;  the number of workstations in use, other programs that you might be  running and the size of the database.

    Servers with a single CPU, 32Gb RAM and a RAID 1 disks subsystem may be  acceptable for smaller practices, however for larger practices servers with  more CPU, RAM and disk resources will be required.

    A minimum of RAID 1 with 2 disks would be suggested for smaller sites; however  RAID 10 with 4 or more disks would enhance performance. For larger practices a  minimum of RAID 10 with 4 or more disks would be required to achieve suitable  performance. This allows for data redundancy and fault tolerance as well as  performance.

    Some editions of Microsoft SQL Server only support a certain CPU configuration; this must be taken into account when determining specifications.

    Workstations

    Workstation hosting

    Physical
    RDS Server
    Citrix

    Is UAC turned off on Server and Workstations
    for all accounts using Stat?

    Intel Core i3 or better CPU

    4Gb RAM or greater recommended

    1920 x 1080 recommended. Note that both the video card and display must support this resolution. (1280 x 1024 minimum resolution)

    Default Windows fonts required (Larger fonts not supported)

    Windows 7 Professional, Windows 8 Pro, Windows 8.1 Pro or Windows 10 Pro

    • Must be a member of the server domain

    Microsoft .NET 4.6.2

    Microsoft Visual C++ 2010 Redistributable Package (x86)

    Regional Settings set to ‘English (Australia)’

    The time zone along with the actual date and time must be set correctly.

    • All workstations must be in the same time zone as each other.
    • The server is able to be in a different time zone.
    • Workstations should be set to synchronise time with the server
      periodically

    Broadband Internet access

    No ODBC or mapped drives/UNC paths required to the server; workstations connect using Web Services via HTTP

    Standalone computer (Server and Workstation combined)

    Intel Core i3 or better CPU

    8GB RAM or greater

    Disk system

    • System performance is most affected by disk sub-­system
      performance
    • Redundancy is important to protect critical patient and clinical
      data
    • Multi disk RAID systems i.e. RAID 10 will give better performance and redundancy
    • Hard disk capacity required for data conversion: minimum 4x
      existing database size

    Windows 7 Professional, Windows 8 Pro, Windows 8.1 Pro or Windows 10 Pro

    If you wish to use a Server operating system use the Server checklist

    Microsoft SQL Server 2005, 2008, 2008 R2, 2012,  2014 or 2016 with named instance ‘STAT’

    • The ‘Express’ edition has a number of limitations that make it
      unsuitable in most practices, such as a database size limitation.
      An edition other than ‘Express’ is generally required.
    • MS SQL Server must be configured to use an appropriate maximum amount of system memory.

    Internet Information Services (IIS) installed and running

    • ‘IP Security’ option must be installed
    • Windows Authentication’ option must be installed

    WCF Activation Installed and enabled

    Microsoft .NET 4.5.2

    Microsoft Visual C++ 2010 Redistributable Package (x86)

    Regional Settings set to ‘English (Australia)’

    The time zone along with the actual date and time must be set correctly.

    Broadband internet access.

    Distributed Transaction Co-­ordinator service set to ‘Automatic’ start and be running.

    Instead of a local DNS server, there will need to be a ‘Hosts’ file entry for ‘StatInternal’ that resolves to the local computer

    If using any external inbound services (e.g. SMS, Online Appointments) we also require

    • A static IP address with routing configured to allow external access  to web services
    • an internal DNS entry for ‘StatExternal.yourdomain.com’ that
      resolves to the IIS server
    • an external DNS entry for ‘StatExternal.yourdomain.com’ that will  allow external users to access the internal IIS server
    • an external DNS entry for ‘StatExternal.yourdomain.com’ that will  allow external users to access the internal IIS server

    Standalone computer specifications (CPU, Memory, Hard Disk) will vary  depending on; any other programs that you might be running and the  size of the database.

    A minimum of RAID 1 with 2 disks would be suggested for smaller sites;  however RAID 10 with 4 or more disks would enhance performance.

    The choices for a standalone computer will be affected by the choice
    of either a laptop (for portability) or a single desktop computer in an
    office. It is possible to purchase laptop computers that have fast CPUs,  large RAM capacity and high speed drives in RAID configurations if  appropriate.

    Some editions of Microsoft SQL Server only support a certain CPU
    configuration; this must be taken into account when determining
    specifications.

    Microsoft Word is required under certain circumstances; please refer  to Data Conversion section in this document.

    Data Conversion

    Conversion of your data will be undertaken on your existing server.

    The time to run a conversion is heavily influenced by the performance  of your server (CPU, RAM, Hard disk).

    If converting documents created using Microsoft Word you will require a complete copy of Microsoft Word 2007 or Microsoft Word 2010 on  the Server where the conversion will be run. Microsoft Word 2010 Starter Edition is not supported.

    Stat Backup

    Stat does not have an inbuilt backup solution. All sites are responsible for ensuring an appropriate backup solution is installed and working.

    Stat utilises Microsoft SQL Server databases to store all of its data.

    • Typically Stat uses a named instance of MS SQL Server called ‘STAT’
    • Typically the Stat databases are called ‘Stat’ and ‘StatClinical’
    • There is also a database called ‘StatMIMS’ that contains reference data only

    The databases are contained in several files on the file system. The names  and locations of these files are configurable and depend on the setup of the server.

    An appropriate backup solution needs to be used that will allow all the data in the Stat databases to be backed up. Backing up the data multiple times a day (like hourly or even more often) may reduce data loss if a backup needs to be restored.

    The backup solution needs to take system performance into account
    when scheduling backups while the system is in use. If the backup ‘freezes’ the SQL database then the users may experience a period during which the software appears to be unresponsive.

    The preferred way to backup this data is by using an MS SQL Server
    compatible backup solution (e.g. StorageCraft ShadowProtect)

    It is critical that whoever is given the task of setting up the backup of
    your system be proficient with MS SQL Server backup techniques so
    as to avoid data loss in the event of a problem that requires the database to be restored from the backup. It is also important that the MS SQL server transaction logs be appropriately backed up and appropriately truncated otherwise they will grow to consume all available disk space.

    For further information see the StorageCraft backup guide for MS
    SQL available at:

    NB: By default Microsoft SQL Servers transaction logs are not truncated automatically. If left unchecked these transaction logs will eventually consume all available disk space. It is therefore imperative that appropriate action is taken to address transaction log size e.g. by means of SQL maintenance plans.

    Remote Connectivity

    Stat requires RDC access to the server and all workstations. This can
    be provided either as a direct RDC connection or via an RDC gateway.  (VPN Connections are not suitable).

    This type of access is available to Stat even if practice staff are unavailable. This allows after hours updates and support to be performed.

    If this style of connection is not possible (e.g. a standalone laptop)
    then support can be provided using LogMeIn Rescue as long as the computer is connected to the internet, however this is limited to office hours.

    This type of access is available to Stat even if practice staff are unavailable. This allows after hours updates and suppor to be performed. If this style of connection is not possible (e.g. a standalone laptop) then support can be provided using LogMeIn Rescue as long as the computer is connected to the internet, however this is limited to office hours.

    Stat is designed to allow it to run in a Microsoft Windows RDS Server environment. Thiscapability can be used to allow access to the Stat application over lower speed networks than would be possible otherwise. This may be useful in allowing doctors and staff to access the Stat application from other locations. In order to provide remote support, Stat requires RDC access.If your site uses RDS please be aware that we will requireone remote accessCAL to be available at the time of remote access.

    Stat is designed to allow it to run in a Microsoft Windows RDS Server environment. Thiscapability can be used to allow access to the Stat application over lower speed networks than would be possible otherwise. This may be useful in allowing doctors and staff to access the Stat application from other locations. In order to provide remote support, Stat requires RDC access.If your site uses RDS please be aware that we will requireone remote accessCAL to be available at the time of remote access.

    External Services (SMS, Online Appointments)

    SMS

    • Available in conjunction with SMS Central.
    • Outbound SMS is available with just an internet connection from
      the server.

    Online Appointments

    • Available in conjunction with Doc Appointments

    To receive inbound traffic the following is required:

    • A publicly available URL (StatExternal.yourdomain.com)
    • The inbound traffic must arrive on port 80 at the IIS Server e.g.
    1. Externally the traffic arrives at port 80 and is forwarded to the
      IIS Server
    2. Externally the traffic arrives at any other port and is forwarded
      to port 80 on the IIS server. (In this case port 81 is preferred
      as the external port)
    • Provide the DNS name (IP address is not suitable) along with the
      external port number to Stat Support.

    Printers

    There are numerous brands and models of printers on the market
    – only a small number have been tested by Stat.

    For the Doctor’s desk – a small laser printer for scripts, request and
    letters may be used. Alternatively a larger printer with multiple paper trays (e.g. for script, pathology and plain paper) may be preferred.

    For Reception – a heavy duty, fast and reliable printer is recommended.

    Scanner

    Stat does not interface directly with any scanner. Stat does support
    file importing from a folder as a background service. PDF files provide the best user experience especially with multi page documents.

    NB: This hardware specification is continually revised and updated
    to ensure the Stat application performance continues to be optimised.

Connect With Stat Health Systems

Join/Register

Contact

Smartspace Website Tools