IC physiology management |
| On an intensive care, physiology should be available everywhere when needed and the
information should be as complete as possible. When not needed, its processing should be
as unobtrusive as possible, bringing no extra work on top of all the things that have to
be done in the course of normal care. The physiological management systems should obtain its information automatically from the standard devices used on the unit, such as clinical patient monitors and mechanical ventilators. It should store all this information and put it at the units disposal whenever and wherever it is needed. It should be able to scan all the data for pathology and permanently save all relevant information – a physiological snapshot – around detected events. It must build up a permanent physiological record of each patient and discard information when it is no longer relevant. At all times, the users should be able to redefine what is relevant and what is not. |
Transistor |
| Transistor provides distributed, full disclosure, physiological datamanagement through
a set of applications (see picture). Central to Transistor is the Collector where all available physiology is stored in a circular storage buffer. The physiological data are acquired by Acquistion clients (see picture). The whole acquisition process is automatic. It is driven by the available physiology, the category of the patient or bed and the available acquisition capacity. The Extractor continuously scans the data in the collector to generate trends, annotations and ‘snapshots’ and even regular printouts. Again the category of the patient or bed determines this processing. The kind of processing can be defined by the user using either predefined processing configurations or using the 32-bits version of SPL, the notorious signal processing language developed for POLY. Results of the Extractor are stored on the Physiological server. The P&O server links Transistor to the Patient Data Management System (such as our own PDMS) of the unit to provide the patient data for each bed and to provide access authorization. The Viewer is used to visualize the information held in Transistor. For each patient- or bedcategory, default views (see picture for an example) can be defined and stored on the Physiological server, thus providing a standardized view on patients. These views can be easily adapted (and stored) by the user to accommodate specific needs. |
 |
| Fig. 1 - Schematic representation of Transistor |
|
| Fig. 2 - Schematic representation of a single workstation acquisition/collector system |
|
| Fig. 2 - Schematic representation of a multiple workstation acquisition/collector system |
Realization |
| Transistor will run on Windows PC’s connected by any network that supports
TCP/IP. For some acquisition clients (notably those that work with Agilent Technologies
SDN network) Windows NT is required. Depending on the workload and the desired level of
reliability, Windows NT servers are recommended, but all other parts of Transistor will
also run under Windows 95 and Windows 98. Installation and configuration of Transistor can be an intense process (depending on the ambitions of the user) but have a high ‘set-it-and-forget-it’ nature: once defined, Transistor is designed to just be there when you need it. Transistor is being developed in close collaboration with three University Hospitals in the Netherlands: AMC, Amsterdam, AZVU, Amsterdam and AZN, Nijmegen. |
| If you would like to receive more information about Transistor, please fill out the following . |
| Copyright © 2000-2006 Inspektor Research Systems BV (tel: +31 20 676 49 88) Please read our legal notice. For site related questions and remarks please contact our webmaster. |
