Difference between revisions of "ConnectR Performance"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
Line 18: Line 18:
 
100,000 x 6,000 x 14 + 1 = 9.4 GB
 
100,000 x 6,000 x 14 + 1 = 9.4 GB
  
*TPD is the number of transactions per day expected by a customer. Each registration, scheduling, result,
+
*TPD is the number of transactions per day expected by a customer. Each registration, scheduling, result, dictionary update will result in a transaction.
dictionary update will result in a transaction.
 
 
*DTH is the number of days the customer wishes to hold the audit trails on their ConnectR Server.
 
*DTH is the number of days the customer wishes to hold the audit trails on their ConnectR Server.

Revision as of 16:42, 1 December 2011

Server Requirements

The ConnectR Server software requires that a dedicated server be used to run the software. For best performance, it is recommended that the server have quick disk access, adequate processing power to convert hundreds of thousands of healthcare messages daily, and abundant RAM to minimize swap-file usage. The machine must also have a relational database management system (RDBMS), as well as the ConnectR interfaces.

Hard Disk and RAM Requirements

  • The minimum disk space requirement is 20MB. However, this will vary depending on the ConnectR functions that the user accesses. (Additional disk space will be required if the user is performing Import/Export functions. In this case, an additional 100 MB of Hard Disk space is recommended).
  • The minimum RAM requirement is 32MB, but this will depend on the functions that the user will be accessing. (Additional memory will be required if the user is performing Import/Export functions. In this case, an additional 96 MB of RAM is recommended).

Processing Transactions and Hard Drive Considerations

ConnectR Server utilizes a store and forward mechanism for each transaction it processes. Each transaction (that moves from one application to another through ConnectR) is temporarily stored on the hard drive of the ConnectR Server. The benefit to this is that each transaction can be accessed at anytime— and this means that errors in and with messages can be fixed and resubmitted at will. The disadvantage is the potential for requiring a vast amount of disk space.

Additional disk space is necessary if the customer site uses the auditing features of ConnectR to keep a record of transactions and user activities via the front-end.

From our experience at customer sites, we have developed an algorithm to determine the minimum disksize requirements for ConnectR Server:
(#TPD) x (6kB) x (#DTH) + 1GB = Minimum Hard Disk Requirement

For example, a customer predicts to have 100,000 interface transactions per day, and would like to hold the audit trail for 14 days. The disk space required on the ConnectR Server will be: 100,000 x 6,000 x 14 + 1 = 9.4 GB

  • TPD is the number of transactions per day expected by a customer. Each registration, scheduling, result, dictionary update will result in a transaction.
  • DTH is the number of days the customer wishes to hold the audit trails on their ConnectR Server.