CorEMR Hardware Requirements

Operating System, Application, and SQL Versions

CorEMR prefers to run our application on Microsoft Windows Server 2022. Microsoft SQL Server (2022) is recommended for our database. Below is the list of compatible software and recommend versions for current versions of our software.

Operating System Web Application Database
Microsoft Windows Server 2019 or higher IIS (on Microsoft Windows) Microsoft SQL Server 2019 or higher

Server Hardware

The CorEMR server software will run on VMWare or most current server hardware. Your IT team is responsible for designing a system that works for your facility. With server virtualization there is flexibility for processor, RAM, and disk space expansion. Our minimum recommendations for a VM are listed in the next table. Server resource will vary based on circumstance (discussed further below).

For standalone (physical) servers, choose equivalent or better hardware. CorEMR recommends a Dell PowerEdge R540 rack mountable server or equivalent (HP, IBM, etc). Currently, the minimum configuration for a Dell R540 is the Intel® Xeon® Silver 4208 (8 cores, 16 logical processors/threads, 2.10 GHZ) so for single sites servers resource is typically not an issue. The application server will be more processor intensive, while the SQL Server will be more memory and disk read/write intensive.

Many variables on a server are outside of the scope of the CorEMR software and support. Additional resource may need to be allocated to accommodate added server load based on VM configurations, network speeds/infrastructure, third-party applications (antivirus, performance monitors), active patient count, the number of active users, data growth, provider specific procedure, and many other factors.

Application Server (for 600+ patients, use separate DB server)

up to 600/up to 75 4 Logical Cores @ 2.1GHZ 16 GB(+8GB if shared) 2 x 500 (Raid-1)
600-1200/75-120 4 Logical Cores @ 2.2GHZ 16 GB 2 x 1 TB (Raid-1)
1200-3000/120-250 8 Logical Cores @ 2.2GHZ 32 GB 4 x 1 TB (Raid-5/10)
3000-6000/250-450 8 Logical Cores @ 2.5GHZ 32 GB 4 x 2 TB (Raid-5/10)

Suggested disk structure for the APP instnace is to have at least two dedicated drives: OS drive (C:), DATA (eg: E:) CorEMR install/Document storage drive.

Database (SQL) Server (separate for 600+ patients)

600-1200 2 Logical Cores @ 2.2GHZ 24 GB 2 x 250 GB (Raid-1)
1200-3000 4 Logical Cores @ 2.2GHZ 32 GB 2 x 250 GB (Raid-5/10)
3000-6000 4 Logical Cores @ 2.5GHZ 32 GB 2 x 500 GB (Raid-5/10)
6000-12000 8 Logical Cores @ 2.5GHZ 64 GB 2 x 500 GB (Raid-5/10)

The more database can be loaded into RAM, the better. Matching RAM to the size of the .mdf is optimal. The SQL Version for a new server must be same OR newer than the version a database is being copied from (for migration or new server). 4 GB of the first 16 GB should be reserved for OS. 1 GB per additional 8GB should be reserved after that. Configure the remaining memory as the maximum server memory allocated for the Microsoft SQL Server buffer pool. Example: 32GB total = 26 GB setting for SQL.

Microsoft SQL Express is NOT recommended. While SQL Express is a low-cost solution, it has limitations that decrease performance CorEMR recommends. If SQL Express limits are reached and/or we are asked to troubleshoot performance issues, your first step will be to apply a full license to your MSSQL installation.

Suggested disk structure for SQL is to have three dedicated drives: OS drive (C:), DATA (eg: F:)for MDF files, and LOGS (eg: L:) for LOG files.

CorEMR Multifacility Sites and Multisite Servers

A multifacility is one CorEMR website with multiple facilities. Users can switch between facilities with a single login. A multifacility site will have higher load on both IIS and the database (single database) than single facility sites.

A multisite is one server running multiple websites. Those sites could be single facilities and/or multifacilities. As a general guide, take the sum total of patients and users to calculate the needed resource. There will be considerably more web requests for multifacility and multisite servers. Additional resource should be considered as the increased requests will demand more than the single site server recommendations.

Disk Space Growth and Disk Configuration

Disk space needs will vary based on patient count and facility practices (mostly the volume of patient document scanning). You will need to analyze recent disk growth on occasion to project disk expansion needs. For a 1000 bed facility, CorEMR estimates the DB to grow ~200MB/year and document storage ~50GB per year.

Disk redundancy or server backup is required. Scheduled backups (facility responsibility) should provide adequate data protection. Imaging or cloning of physical (or VM) servers is also acceptable. We also recommend using backup/redundant power supply for your server(s) and dedicated hard drive with direct access from the virtual machine.

Client Software and Hardware

CorEMR runs from a web server and is accessed by the client only using a web browser. Almost any computer with Chrome, Edge, Firefox, Safari installed should be able to use CorEMR. Cookies, JavaScript, and popups must be permitted. A document scanner web plugin (Dynamsoft) and signature pad software are provided to install on the client machines as needed.

CorEMR requires the nurses and end users’ access CorEMR with HTTPS for full functionality. This does require a valid SSL certificate and domain to be used for medical staff to access CorEMR.

Your end-user resource requirements will vary more on what other functions the users perform on their machines. All data entered into CorEMR is stored on a remote server. Only a computer capable of running a web-based application is needed. Most users will use an office suite (MS Word, Excel), access email, install other 3rd party software, etc. As a general guide for an office capable machine, we recommend the following:

  • Processor: Pentium G series 3.0 Ghz (or newer)
  • Memory: 4GB RAM (minimum)
  • Hard Drive: 250GB
  • Recommended Operating System: Windows 10

Hardware inventory will depend on your current staff levels and facility capacity. We recommend one laptop per medication cart. Doctors should have access to a computer for sick calls. The Health Services Administrator and secretary should have a dedicated machine. Medical staff will need adequate access to a workstation. At least one document scanner should be present (additional for high volume scanning). Most facilities now implement barcode scanners and signature pads as well.

Document Scanner

CorEMR suggests purchasing a sheet-fed document scanner to scan and save paper documents into the Electronic Medical Record. The scanner must be TWAIN COMPLIANT with a true TWAIN driver for compatibility with CorEMR. The Fujitsu fi-7160 and Epson ES-400 scanner have been tested successfully with CorEMR.

Barcode Scanner (handheld)

If your facility uses patient wristbands or badges with UPC codes that can identify the patient and be read by a scanner, CorEMR can use these to aid in Medication distribution and identification. The Symbol brand LS2208 is compatible.

Signature Pad

CorEMR has successfully tested Topaz Signature Pad Models T-L462-HSB-R (viewing screen) and T-S261-HSB-R (no viewing screen).