Frequently Asked Questions

• Q: Does OPUS-CriticalCare™ or OPUS-RT™ interface with any EMR/EHR systems?
  A: All Theronyx products are architected and developed with HL7 healthcare informatics interoperability in mind. Our products are interfaced to ADT, billing, orders and results systems at virtually every customer, with several customers having unique interfaces to other systems such as ABG machines. The EMR/EHR providers with which we have current interfaces are Cerner, Eclypsis, Siemens, McKesson, Soarian, Meditech. PBAR etc.
• Q: How does Theronyx offer OPUS-CriticalCare™ and OPUS-RT™ without going through the long capital budgeting process?
  A: Through our exclusive financing partner, Med One Capital Funding, hospitals acquire complete, turnkey systems including hardware, software, implementation, training and ongoing maintenance and support for one low monthly subscription fee. Click here to begin a complete cost benefit analysis.
• Q: Are OPUS-RT™ and OPUS-CriticalCare™ certified Stage 1 Meaningful Use products under the HITECH Act?
  A: Both OPUS-CriticalCare™ and OPUS-RT™ have been certified as Stage 1 Meaningful Use EHR Products as defined by the certification criteria identified in the ONC Standards and Certification Final Rule. View the product certificates here
• Q: What are the technical specifications for utilizing OPUS-CriticalCare™?
  A: OPUS-CriticalCare™ is a thin-client, web enabled product that simply requires access to a supported web browser. Supported browsers are Mozilla Firefox (3.5.x or higher), Microsoft Internet Explorer (6.x or higher) and Google Chrome (11.x or higher). The web browser communicates with a server within the hospital. Typically the server hosts multiple virtual servers on a single physical box. The number of VM’s required for a given implementation will depend on the number of ventilators connected to the system. For complete OPUS-CriticalCare™ technical specifications contact us.
• Q: What are the technical specifications for utilizing OPUS-RT™?
  A: OPUS-RT™ is a fat-client, client/server application. Generally, client machines must run on Microsoft XP (SP2 or greater) and have at least 2GB of memory. The server should have Microsoft Server 2003 (SP2 or greater), Microsoft SQL Server 2005 (SP 3 or greater), and have minimally dual capable, 2.0 GHz with 4 GB memory and 100 GB of disk space. For complete OPUS-RT™ technical specifications click here.
• Q: Why do OPUS-RT™ customers experience less than 1% billing audit errors?
  A: OPUS-RT™ is a tightly integrated system that ensures that all orders entered into the system are completed and charged as necessary. It is virtually impossible for any patient documentation to be entered into OPUS-RT™ and not have the correct charges be sent to the hospital’s billing system via the charges HL7 interface.
• Q: How long does it take to implement OPUS-RT™ and OPUS-CriticalCare™?
  A: Our standard implementation work plans indicated that OPUS-CriticalCare™ and OPUS-RT™ can be successfully implemented with ‘Go-Live’ dates typically occurring within 60 days and 90 days following project kick-off, respectively. This assumes that key hospital and consulting personnel will be available for all interface development and testing meetings and additionally, for database configuration meetings and training sessions as outlined in the implementation work plan. In most cases, these time tables are not overly aggressive. The implementation projects for both of these applications result in a low impact on the resources of the Respiratory Care and IT departments.