Configuration Flexibility

One of QML software’s strengths is its hardware independence, which allows the software to reside on the customer’s chosen hardware (physical or virtual), along with other software applications that are also hardware independent.

When running with other software applications, the only requirement from TELCOR is that the required computing resources are available for the TELCOR software itself. Another of its strengths is the ability for distributed processing. Though some might think multiple pieces of hardware are required to run the TELCOR system, this is simply a customer’s choice or a recommendation by TELCOR based on volume and processing requirements.

 

Main QML Components

For configuration purposes, there are six main QML components. All of these can be installed on the same server or distributed among multiple servers, as required by IT departments for processing efficiency or as dictated by volume.

Sybase® SQL Anywhere Studio is installed by TELCOR and completely supported through the software support agreement.
ADT and Order Interface(s) include two components — a communication and a processor module, along with an ADT Passthrough component for sending real-time ADT messages once received by QML to device-type systems designed for receiving and processing this data.
QML Output (result interfaces) runs as a single background service and includes two main components. The pre-processing component gets every result ready to go to the LIS/EMR, including patient ID validation, order code mapping and more. The result interface component formats the message appropriately for the receiving system and physically sends the message as an EDI (HL7) or Script interface through a TCP connection.
QML Input (device drivers and import) includes unique components for each device type to: process files received from the device type, import data into QML and process import exceptions. All run as a single background service. Import exceptions are broken into two categories — configuration exceptions and result exceptions. Configuration exceptions can include devices not configured, and result exceptions can include “exceptional” flags received from the device, results from defined ranges and samples that are missing information, such as FI02 for blood gas results.

Unique communication services, aka NWS, for applicable device types are also included, though they run as separate services. These include sending operators for device types capable of receiving electronic operator updates. SQL Server™ is required for temporary storage by NWS. SQL Server™ Express is included with product installation. The customers SQL Server farm can be used, too.

For multiple, simultaneous access points, this may be installed on the same or separate server to be accessed through Citrix, Web/Internet Explorer via RDWeb or through physical clients installed on individual workstations.
The Alerts component provides an online, real-time status of all QML components from within QML or a website using IE 6.0 or higher. It also includes the ability to trigger automated text or email messages when unprocessed limits are recognized. Alerts will be installed with the import and output services.

 

WebMRE Configuration

WebMRE includes three main components — the SQL server used to store temporary results, the WebMRE Web page and the QML WorkQ service, all of which may be installed on the QML server or distributed amongst the hospitals’ SQL Server farm, IIS website and QML server.