Data security is important to you and TELCOR, too.

POC never stops. You need interfaces that are perpetual, notifications when things go wrong, and a reliable middleware solution that is always available. Your team needs access to patient data to provide the best healthcare outcomes, but you’re also tasked with maintaining data security. In this three-part email series, we’ll highlight how QML® addresses data security, encryption, and availability.

Part 3: Maximizing Uptime

High Availability (HA) Database Configuration in SAP Sybase SQL Anywhere 17

HA is a characteristic of a system aimed to ensure an agreed upon level of operational performance, usually uptime, for a higher-than-normal period. It is designed to eliminate a single point of failure, provide reliable crossover, and include the detection of failures as they occur. All these characteristics are included in the SAP Sybase SQL Anywhere 17 HA option.

An HA configuration includes a copy of the SAP Sybase SQL Anywhere 17 database on a separate server and sometimes in a separate data center to keep your QML system up and running even if you encounter an unscheduled downtime such as a hardware or data center failure.

TELCOR has implemented HA configurations for more than 35 healthcare systems.

TELCOR offers the SAP Sybase SQL Anywhere 17 HA option, which includes two databases, each on dedicated servers and one arbiter server. These servers can be in the same or different data centers. All three servers talk to each other and QML is connected to both databases. If the Primary database is unavailable, the Arbiter and the Mirror database detect the disconnect from the Primary. The Mirror then becomes the Primary. When the original Primary eventually comes back up, it will then be the Mirror. This switching is automatic and instantaneous and could be caused simply by a network delay to the primary or by the server itself being unavailable.

Database Backups and Data Recovery

It is crucial for a copy of the production QML database be safely stored on your network. This backup is used to reimplement the QML system in the event of server loss or database corruption. You will reduce the amount of downtime and data loss by having a backup of the QML database ready to be recovered.

Backups of the SAP Sybase SQL Anywhere 17 database are scheduled daily at 2 a.m. local time by default with a full back up on Saturday and incremental daily backups Sunday through Friday. Each daily file is stored in the QML database backup folder on the database server. The customer is responsible for copying this folder to network storage after the daily backup is completed.

The QML dashboard includes a backup tile with the date, time, storage location, and status of the daily backup. If the status states the backup is Failed, the customer is directed in a pop-up message to contact the TELCOR POC Support for triggering of a manual backup and then troubleshooting the cause of the failure.

In the event of a database error, TELCOR is responsible for restoring the database to current date. This could include:

  • Restoring the previous full backup and then applying the current database transaction log or
  • Restoring the previous full backup, applying incremental backups, and then needing to re-process files from devices to return to current state.

If you deploy the SAP Sybase SQL Anywhere 17 High Availability (HA) database option, both the Primary server and the Mirror server maintain a copy of the database and the backup folders from both servers must be copied to network storage.

If you are using VMWare, the vCenter Site Recovery Manager option can be used to replicate the QML environment eliminating the need to copy the backup folder to network storage.

While TELCOR supports QML and its components in your environment, we do not manage or maintain your server. It is crucial that Microsoft Patching and routine server reboots are scheduled for your organization’s servers on which the TELCOR software is installed. Please contact TELCOR Support if you need assistance discussing the coordination of routine server maintenance with your IT or server team.

QML Alerts

QML Alerts monitor interfaces and conditions within QML and send internal email and/or text messages to the people necessary to address the problem.

Note: Alerts are not sent to TELCOR. You may need to contact TELCOR Support for assistance in resolving the problem. You have 24x7x365 access to TELCOR Support by calling 866-489-1207.

QML Alerts help you identify problems in a timelier manner (especially during off hours) allowing you to start the resolution process faster.

QML Alerts are installed by default with QML at no additional cost to you. The TELCOR team is happy to help you implement and configure alerts as well as update alerts as needs change. The process starts with the definition of SMTP configurations to allow email outbound from the QML server. Once basic functionality is in place, you can build as many alerts as you need from the following categories.

  • ADT & Orders – When the last message was received, when the last message was processed into QML, or how many messages are waiting to be processed into QML.
  • ADT Passthrough (for cobas infinity, NovaNet, RAPIDComm, and TEG only) – How many messages are waiting to be sent from QML to the device management system.
  • Device Types (per type of device, not individual serial number) – When the last sample was received, when the last sample was processed into QML, how many samples are waiting to be processed into QML, or how many error samples exist.
  • Results Outbound to LIS/EMR – How many samples are waiting to be sent.
  • Application Acknowledgements – When the last acknowledgement was received from the LIS/EMR or how many samples are waiting to be acknowledged.
  • System – When a QML service terminates.

    Data security is important to you - and TELCOR, too. Part 1

    Read part one of this data security series.

    Data security is important to you - and TELCOR, too. Part 2

    Read part two of this data security series.