Several biomedical test equipment manufacturers develop and market systems used to manage the preventative maintenance (PM) testing and service for all manner of biomedical equipment. These programs typically manage a database of equipment information, test schedules, maintenance procedures and test results. Such systems are widely used to manage large fleets of medical equipment. The programs are meant to be used with a variety of specialized test apparatus, most of which would be manufactured by the same company. Such equipment includes electrical safety testers, electro-surgery testers, ultrasound testers, ECG simulators, etc. Many of these systems may be used as stand-alone equipment management databases or in conjunction with other, intermediary an often more portable, devices that interface directly with the various test apparatus during testing, but which then interface with the host computer system later so that test data may be assimilated into the central database management system.
The PneuView system includes facilities allowing for simple compatibility with equipment management systems like those just described. These are designed to be straightforward and intuitive to any user of such a database system. There are at least two ways of linking test data taken by the PneuView system to such 32 database systems: one applicable if the user also employs an intermediary data collection device, and another if he/she instead interfaces directly with a computer hosting the equipment management system.
If an intermediary device is used, PM and service templates for testing ventilators (for example) set up using the central equipment management program can be set to include a separate task item calling for a specific PneuView test to be performed as part of the maintenance or service work order (another task might be an electrical safety test). Such a test takes the form of a PneuView Template, designed by either the user or MII, specific to that ventilator. The technician can perform the electrical safety tests (for example) prompted by intermediary device, and then perform tests specified by the PneuView template(s). The intermediary device generates its results text file, and the data export facilities included with PneuView do the same. When the Sentinel 32 system is later used to close that work order, both tasks are closed and the appropriate results text file associated with each respective task is included with the respective test record.
In cases where an intermediary device is not used (the norm for ventilator testing, in most cases), the scenario is simpler. Templates stored with the central equipment management system for ventilator tests include a task calling for tests using the PneuView system and detail using PneuView templates. After the user performs the required tests, PneuView generates a results text file, which the user would in turn associate with the test record when that task/work order is later closed using the equipment management system software.
In either case, the procedure is straightforward. Equipment management programs generally include a facility for attaching at least a text file to each “Task” itemized on the work orders they are designed and used to generate. While attaching the text results file created by most intermediary devices is automatic, it is simple for the user to attach a separate text file to a task when closing a work order.