Test Equipment Interfaces

Medimizer Integrates with a variety of test equipment interfaces

All test equipment interfaces offer the ability to review and correct data in a grid form before acceptance.

Datrend to MediMizer Interface

MediMizer interfaces with the Datrend vPad.  This is a great interface because vPad links directly from the test device to your database via the cloud.  The device can be used anywhere in the world and synced when you have an internet connection.

Rigel to MediMizer Interface

MediMizer reads data from Rigel 288+, Multi-Flo, Uni-Pulse, Uni-Sim, and Uni-Therm.  The data is processed through our device data review process and is stored in MediMizer as either the original file, line item check results, or both.

Pronk to MediMizer Interface

MediMizer and Pronk have tested an original interface and are working on expanding the interface to other devices.  Please use our form to request the current interface status for your device.

Fluke Interfaces

MediMizer is integrated with 3 Fluke Biomedical options, oneQA, Ansur and medTester.

MediMizer and oneQA

oneQA is the new interface between Fluke test equipment and CMMS. Data is transferred directly into the MediMizer database or can be processed through our test equipment data review process.

MediMizer and Ansur

Ansur has been the standard Fluke interface for years and will probably be in use for a while. It is the preferred interface for some of our users.

MediMizer to medTester interface

medTester has been a solid test device for decades and those that rely on it have good reason. It is solid, it works. MediMizer owns the original medTester interface software, Sentinel, and we have used proprietary code to make the most reliable medTester interface.

MediMizer interface syncs with Fluke medTester 5000C

This classic test device is still popular because of its great design.

  • MediMizer check procedures support autosequences, medTester commands for direct programming of the medTester and pass/fail procedures.
  • In the MediMizer medTester interface, the right work order is closed when a control number is entered because we embed the work order number in the medTester data.
  • If you use medTester with Sentinel, we can migrate 100% of your data.
  • Our Add Equipment procedure presents ALL fields, not only 5. Complete data entry can be done in the field.  An incoming inspection work order is opened and closed with checks specific to the equipment type added.
  • You can work on the same work order using a device and the medTester at the same time.  Test and fail with the medTester.  Enter notes, parts, details on a device and all information will appear in one history in chronological order.
  • You can choose to send all data or any set of data to the medTester.  Send one of your accounts or site or any group of accounts/sites.  Filter by a number of key fields.
  • Sync at a faster baud rate and complete the entire sync in one process. 
  • All compliance data can be recorded on the medTester and later reported or filtered in MediMizer. How many times did a specific check fail and by what measure? You will know because MediMizer does not just put the data into a file.
  • The technician decides whether to close a work order based on the status. No longer do you have to risk automatic decisions which may not be right.
    Option to remove excess lines from results. You no longer need to store blank lines, unanswered lines or unnecessary headers.
    Data with problems such as incorrect dates or missing data can be reviewed in our review process. We present issues one by one to be fixed.  It is also an option to review good data before saving to look for typos or mistakes.
  • Option to load directly from file. MediMizer keeps all data so it can be reviewed or synced again. This makes it unnecessary to directly repair MUP files.
  • Add service work orders in the field using the Add Work Order function.
  • Add services to any work order using the Add Service function.
  • MediMizer support staff are familiar with medTester functions.
  • The correct procedure is sent based on model, equipment type and other factors. New requirements under CMS and TJC to perform manufacturer based procedures can be complied with.
  • Sync equipment with or without check procedures. This option allows standard procedures to be run from the medTester menu.
  • Inspections can be sent quarterly, semi-annually, annually, based on a floating schedule or by many other optional inspection strategies.
  • MediMizer reports include barcode which can be used with a medTester barcode scanner to enter control numbers and other data

*medTester is a trademark of Fluke Biomedical. Your medTester might show Dynatech Nevada or DNI Nevada, which was one of the original producers. Contact Fluke for the module 10 conduit upgrade software.

Request More Information

chevron-down linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram