TELCOR has proven and sustained performance when it comes to growth in our POCT product line. Our customer retention rate is 98% which speaks for itself. But don’t just take our word, ask our customers what it’s like to work with us. It’s more than a single event or feature or moment in time, rather about sustainability and adaptability to the market over the lifetime of a product.
QML can be used to connect any device type found in the hospital, rehab, ambulatory and long-term care settings. TELCOR also offers a module for charting of results to manual tests, many of which are found in ambulatory settings.
QML was the first POCT middleware system to send unsolicited results to an LIS via an HL7 interface in addition to entering results via a scripted interface. Since then, we have expanded the HL7 result interface to include solicited results, multiple simultaneous result interfaces to one or multiple host systems, as well as hundreds of configuration settings allowing each customer’s interface to be customized without custom code. An orders interface enhances solicited results processing when results are to be posted to pre-existing orders. ADT interfaces provide for patient ID validations and patient lists to devices. eLearning interfaces eliminate the manual documentation and tracking of operator competency.
TELCOR invests heavily in R&D bringing new features and functions to our software. Many requests come from our customers, others updates include validation on updated platforms, technology upgrades, performance enhancements, updates to existing device connectivity and connectivity to new device types. Customers have access to all versions and enhancements at no additional cost as part of their Software Support Agreement assuring an application that remains current with the ever-changing point of care testing landscape.
None of us can predict when existing devices will need to be replaced, and when or what new devices will be available. That is why selecting a middleware system that can connect any vendor’s devices is important. When devices and interfaces are tied to a device vendor’s middleware system and there is a need to replace that device, customers face replacement of their entire middleware infrastructure including all host system interfaces which can consume significant resources, including employee time and other direct costs.