|
|
October 17-21, 2009 New Orleans, LA Home Abstract Archive Search Abstracts 2009 Session Grid 2009 Meeting Website Policy Statements ASA Website Feedback 
Visit Anesthesiology.org |
| Previous Abstract | Next Abstract |
| Printable Version |
|
A1120
October 15, 2007 9:00 AM - 11:00 AM Room Hall D, Area D, |
| Interoperability of Medical Devices (Plug and Play) |
|
Carl' F. Wallroth, Ph.D., Julian Goldman, M.D., Dave Osborn, Ph.D., William Weinstein, Ph.D., Dwayne Westenskow, Ph.D. Draeger Medical, Draeger AG&Co. KG, Luebeck, Germany |
|
Most medical devices are designed to operate independently and do not have a means for data communication or for external device control. The integration of individual medical devices into patient-centric medical systems can provide real time comprehensive data for the electronic medical record and can support advances in patient safety and workflow. A series of standards is being prepared to allow the implementation of such interoperability by describing the requirements for the integrated clinical environment that address the clinical, technical, regulatory, and legal concerns for such medical systems. The integrated clinical environment can support improvements in workflow and reductions in medical errors and healthcare costs throughout the continuum of care: from the home, to pre hospital transport, and to clinical areas as diverse as the OR, ICU, and general hospital ward. Figure 1 shows the relationships between the elements of the integrated clinical environment. The new international standards characterize a model-base approach to medical device integration. The device model describes medical device capabilities, and identifies the language (syntax and semantics) that the medical device speaks. A network controller uses the device model of a medical device to determine what it can ask from the medical device, what it can tell the medical device, how it needs to format these requests, and how to interpret the meaning of the results. All that the network controller needs to know, a priori, is how to interpret the device model. The device model represents the characteristics of the data flowing in and out of the medical device. It describes in words the concept a data parameter represents (e. g., blood pressure, O2 concentration, pulse rate), the units of representation (e.g., mmHg, pulses/ min), and the bit encoding of the parameter (16-bit fixed point, 32-bit floating point). Data parameters can represent physiological measurements of the patient, time of measurement, state of the medical device, etc. The critical element enabling the interaction between the network controller and a wide variety of medical devices is the meta-model framework used to characterize medical device functionality and application layer interactions. For a network controller to react intelligently to the information obtained from the array of medical devices in the clinical environment it will have to employ other models of patient physiology and operator activities. Specifying the frameworks needed to represent all of these models, as well as the framework for representing the rules relating the data in the clinical environment is the main objective of this new standard.[figure1] Anesthesiology 2007; 107: A1120 |
Figure 1
 |