IntelliVue MP80/90 & D80
Service Guide
IntelliVue Patient Monitor
MP80/90 & D80
Patient Monitoring
Part Number M8000-9351K 4535 641 12591
*M8000-9351K*
|
|
Table of Contents |
|
|
1 Introduction |
9 |
|
Who Should Use This Guide |
9 |
|
|
How to Use This Guide |
9 |
|
|
Abbreviations |
9 |
|
|
Responsibility of the Manufacturer |
10 |
|
|
Passwords |
11 |
|
|
Warnings and Cautions |
11 |
|
|
2 Theory of Operation |
13 |
Monitor Theory of Operation |
13 |
|
|
System Boundaries |
14 |
|
Hardware Building Blocks |
15 |
|
Data Flow |
19 |
|
How does the Support Tool Work with the Monitor |
23 |
|
Monitor Software Block Diagram |
24 |
|
Block Diagram Legend |
25 |
|
3 Testing and Maintenance |
33 |
Introduction |
33 |
|
Terminology and Definitions |
34 |
|
Recommended Frequency |
35 |
|
When to Perform Tests |
36 |
|
Testing Sequence |
40 |
|
Visual Inspection |
41 |
|
|
Before Each Use |
41 |
|
After Each Service, Maintenance or Repair Event |
41 |
|
Power On Test |
41 |
Safety Tests |
42 |
|
|
Warnings, Cautions, and Safety Precautions |
43 |
|
Safety Test Procedures |
44 |
Preventive Maintenance Procedures |
84 |
|
|
Noninvasive Blood Pressure Measurement Calibration |
84 |
Performance Assurance Tests |
84 |
|
|
Basic Performance Assurance Test |
84 |
|
Full Performance Assurance Test |
85 |
|
ECG/Resp Performance Test |
85 |
|
ECG Sync Performance Test |
86 |
|
SpO2 Performance Test |
86 |
|
NBP PerformanceTest |
87 |
|
Invasive Pressure Performance Test |
89 |
3
Temperature Performance Test |
90 |
M3014A Capnography Extension Performance Tests |
90 |
Microstream CO2 Performance Test |
93 |
Spirometry Performance Tests |
98 |
Cardiac Output Performance Test |
100 |
BIS Performance Test |
101 |
Vuelink Performance Test |
102 |
IntelliBridge Performance Test |
103 |
EEG, SvO2 and tcGas Performance Tests |
103 |
Nurse Call Relay Performance Test |
103 |
Power Loss Alarm Buzzer Performance Test (only if Multi-Port Nurse Call Connector Board is installed) |
105 |
IntelliVue 802.11 Bedside Adapter Communication Test |
106 |
Reporting of Test Results |
107 |
Carrying Out and Reporting Tests |
108 |
Evaluation of Test Results |
111 |
Other Regular Tests |
112 |
Touchscreen Calibration |
112 |
Disabling/Enabling Touch Operation |
112 |
Printer Test Report |
113 |
After Installation, Testing or Repair |
113 |
|
4 Troubleshooting |
115 |
Introduction |
115 |
|
How To Use This Section |
115 |
|
Who Should Perform Repairs |
115 |
|
Replacement Level Supported |
116 |
|
Hardware Revision Check |
116 |
|
Hardware/Software Compatibility Matrix |
117 |
|
Software Revision Check |
118 |
|
Software Compatibility Matrix |
119 |
|
|
Compatibilty with MMS |
119 |
|
Compatibilty with FMS |
120 |
|
Compatibility with Information Center |
120 |
|
Number of Supported Parameter Modules |
121 |
Obtaining Replacement Parts |
123 |
|
Troubleshooting Guide |
123 |
|
|
Checks for Obvious Problems |
123 |
|
Checks Before Opening the Instrument |
124 |
|
Troubleshooting Tables |
126 |
|
Status Log |
154 |
|
List of Error Codes |
156 |
|
Troubleshooting with the Support Tool |
156 |
|
Troubleshooting the Individual Measurements or Applications |
157 |
4
|
5 Repair and Disassembly |
159 |
Tools Required |
159 |
|
MP80/D80/MP90 CMU Disassembly |
159 |
|
|
Removing I/O Boards |
160 |
|
Removing the Top Cover |
162 |
|
Removing the Plastic Feet and/or the Locking Cam |
163 |
|
Removing the optional Fans (MP90 Dual CPU Versions only)* |
163 |
|
Replacing the Second (Independent) Video Board(MP90 Dual CPU Versions only) |
164 |
|
Removing the Second CPU/Main Board (MP90 Dual CPU Versions only) |
165 |
|
Accessing the Main CPU or Primary Video Board (MP90 Dual CPU Versions) |
167 |
|
Replacing the Primary Video Board |
168 |
|
Removing the Main Board |
170 |
|
Removing the Power Supply |
172 |
|
Removing the Speaker (MP80/MP90 only) |
174 |
|
Removing the Power On/Off Switch |
174 |
Flexible Module Rack (FMS) Disassembly |
175 |
|
|
Removing the Handle and the Measurement Server Mount |
175 |
Plug-in Modules |
180 |
|
|
Plug-In Module Disassembly |
181 |
Multi-Measurement Module (MMS) Disassembly |
184 |
|
|
Tools required |
184 |
|
Removing the Front Cover |
184 |
|
Removing the Mounting Pin |
185 |
|
Removing the Top Cover |
185 |
|
Removing the DC/DC Board |
186 |
|
Removing the MSL Flex Assembly |
186 |
|
Reassembling the MSL Flex Assembly |
187 |
|
Removing the NBP pump |
189 |
|
Refitting the new NBP Pump |
189 |
|
Refitting the DC/DC board |
191 |
|
Refitting the Cover |
191 |
|
Refitting the Front Cover |
192 |
|
Final Inspection |
193 |
MMS Extensions - Exchanging the Top Cover, MSL Flex Cable and the Dual Link Bar |
193 |
|
|
Exchange Procedures |
194 |
Disassembly Procedures for the M3015A MMS Extension (HW Rev. A) |
205 |
|
|
Removing the Front Cover |
205 |
|
Refit Procedures for the MMS Extension |
209 |
|
6 Parts |
211 |
MP80/MP90/D80 Parts |
212 |
|
|
Exchange Parts |
212 |
|
Replacement Parts |
213 |
Flexible Module Rack (FMS) Parts |
216 |
5
Exchange and Replacement Parts |
216 |
Multi-Measurement Module (MMS) Parts |
218 |
MMS Part Number Overview and Identification |
218 |
MMS Firmware Overview |
220 |
MMS Part Numbers - Front Bezel for M3001 #A01 & #A03 |
221 |
MMS Part Numbers - Front Bezel for M3001 #A02 |
221 |
MMS Part Numbers - Top Cover and MSL Assembly |
222 |
MMS Exchange Part Numbers |
223 |
MMS Part Numbers - Label Kits |
225 |
MMS Part Numbers - NBP Assembly |
225 |
MMS Extension Parts (M3012A, M3014A, M3015A and M3016A) |
225 |
MMS Extension Part Numbers - Release Mechanisms |
226 |
MMS Extension Part Numbers - Top Cover, Flex Cable and Link Bar |
226 |
MMS Extension Part Numbers - Front Bezels |
226 |
Exchange Parts List |
228 |
IntelliVue X2 Part Numbers |
229 |
Plug-in Modules Part Numbers |
229 |
Part Number Table |
230 |
Plug-In Modules Replaceable Parts |
233 |
BIS Solution Replaceable Parts |
238 |
BISx Solution Replacable Parts |
239 |
tcpO2/tcpCO2 Module Accessories |
240 |
IntelliVue 802.11 Bedside Adapter Part Numbers* |
241 |
External Display Part Numbers |
241 |
SpeedPoint Part Numbers |
244 |
Remote Alarm Device Part Numbers |
245 |
Remote Extension Device Part Numbers |
245 |
|
7 Installation Instructions |
247 |
Installation Checklist |
247 |
|
Unpacking the Equipment |
248 |
|
Initial Inspection |
248 |
|
|
Mechanical Inspection |
248 |
|
Electrical Inspection |
248 |
|
Claims For Damage and Repackaging |
249 |
Installing the M8008A/M8010A/M8016A CMU |
249 |
|
|
Mounting Instructions |
250 |
Connecting the Monitor to AC Mains |
251 |
|
|
Connections |
251 |
|
Installing Interface Boards |
252 |
|
Connection of Devices via the MIB/RS232 Interface G.00.xx or higher |
257 |
|
Connection of Devices via the MIB/RS232 Interface (Rev. D.00.58 to F.01.42) |
258 |
|
Connection of Devices via the MIB/RS232 Interface (Rev. A.10.15 to C.00.90) |
258 |
|
Connection of MIB Devices (Rev. below A.10.15) |
259 |
6
Connection of USB Devices |
260 |
Setting Up Multiple Displays |
264 |
Installation of Multiple Displays |
264 |
Configuring Multiple Displays |
266 |
Examples for Multiple Display Use Models |
270 |
Installing Remote Devices |
272 |
Mounting the 15” Remote Display (M8031A) |
272 |
Mounting the 15” Remote Display (M8031B) |
273 |
Mounting the 17” Remote Display (M8033A/B/C) |
274 |
Hardware Settings |
277 |
Flexible Module Rack and/or Multi-Measurement Module |
277 |
Remote Alarm Devices |
283 |
Remote Extension Device |
284 |
PS/2 Keyboard/Mouse |
286 |
Philips Clinical Network (Wired) |
286 |
Philips Clinical Network (Wireless) |
286 |
Nurse Call Relay |
287 |
Connections |
287 |
ECG Out Functionality |
287 |
Connections |
287 |
Configuration Tasks |
288 |
Checking Country-Specific Default Settings |
289 |
Setting Altitude, Line Frequency, ECG Cable Colors and Height & Weight Units |
289 |
Setting Altitude and Line Frequency |
290 |
Configuring the Equipment Label |
290 |
Configuring the printer |
290 |
Configuring IP Address, Subnet Mask and Default Gateway |
290 |
Configuration Settings for CSCN Routed Bedside Monitors (RBM) |
291 |
Configuring Routed Bedside Monitors Support |
291 |
Display Settings |
292 |
IntelliBridge EC10 |
293 |
Accessing the IntelliBridge EC10 Service Interface |
293 |
Firmware Upgrade |
294 |
Uploading and Removing Device Drivers |
295 |
Generating and Uploading Clone Files |
295 |
Viewing System Information |
296 |
Handing Over the Monitor |
297 |
|
8 Site Preparation |
299 |
Introduction |
299 |
|
|
Site Planning |
299 |
|
Roles & Responsibilities |
300 |
M8008A/M8010A/M8016A Site Requirements |
302 |
|
|
Space Requirements |
302 |
|
Environmental Requirements |
303 |
7
|
Electrical and Safety Requirements (Customer or Philips) |
303 |
Remote Device Site Requirements |
304 |
|
|
Connecting Non-Medical Devices |
305 |
|
Multi-Measurement Module (MMS) M3001A, IntelliVue X2 M3002A or Flexible Module Rack (FMS) M8048A305 |
|
|
Remote Displays (M8031A) |
310 |
|
Remote Displays (M8031B) |
311 |
|
Remote Displays - M8033A |
312 |
|
Remote Displays - M8033B |
313 |
|
Remote Displays - M8033C |
314 |
|
Remote Alarm Devices |
316 |
|
Remote Extension Device |
317 |
|
IntelliBridge |
319 |
|
Local Printer |
319 |
Philips Medical LAN |
319 |
|
RS232/MIB/LAN Interface |
320 |
|
Nurse Call Relay Interface |
321 |
|
ECG Out Interface |
321 |
|
|
9 Gas Analyzers |
323 |
|
10 Philips 15210B Calibration Unit |
325 |
Unpacking the Instrument |
325 |
|
|
Initial Inspection |
326 |
|
Instrument Identification |
326 |
|
Specification |
326 |
|
Operating Environment |
327 |
|
Operating Information |
327 |
|
Fitting the Gas Cylinders |
327 |
|
Storage of Gas Cylinders |
327 |
|
Disposal of Used Gas Cylinders |
327 |
Routine Maintenance |
327 |
|
|
Changing the Gas Cylinders |
327 |
|
Care and Cleaning |
328 |
Theory of Operation |
328 |
|
Gas Flow Performance Check |
329 |
|
|
Test Procedure |
329 |
Disassembly |
331 |
|
Parts List |
332 |
|
|
11 IntelliVue Product Structure |
335 |
Upgrade Options |
337 |
|
|
12 Index |
341 |
8
1
This Service Guide contains technical details for the IntelliVue MP80/90 Patient Monitor, the Multi-Measurement Module (MMS), the IntelliVue X2, the Flexible Module Rack (FMS) and the Measurement Server Extensions.
This guide provides a technical foundation to support effective troubleshooting and repair. It is not a comprehensive, in-depth explanation of the product architecture or technical implementation. It offers enough information on the functions and operations of the monitoring systems so that engineers who repair them are better able to understand how they work.
It covers the physiological measurements that the products provide, the Measurement Server that acquires those measurements, and the monitoring system that displays them.
This guide is for biomedical engineers or technicians responsible for troubleshooting, repairing, and maintaining Philips’ patient monitoring systems.
This guide is divided into eight sections. Navigate through the table of contents at the left of the screen to select the desired topic. Links to other relevant sections are also provided within the individual topics. In addition, scrolling through the topics with the page up and page down keys is also possible.
Abbreviations used throughout this guide are:
Name |
Abbreviation |
IntelliVue MP80/90 Patient Monitor |
the monitor |
Flexible Module Rack |
FMS |
9
1 Introduction |
Responsibility of the Manufacturer |
Name |
Abbreviation |
Multi-Measurement Module |
MMS |
Measurement Link |
MSL |
Medical Information Bus |
MIB |
Anesthetic Gas Module |
AGM |
Responsibility of the Manufacturer
Philips only considers itself responsible for any effects on safety, EMC, reliability and performance of the equipment if:
-assembly operations, extensions, re-adjustments, modifications or repairs are carried out by persons authorized by Philips, and
-the electrical installation of the relevant room complies with national standards, and
-the instrument is used in accordance with the instructions for use.
To ensure safety and EMC, use only those Philips parts and accessories specified for use with the monitor. If non-Philips parts are used, Philips is not liable for any damage that these parts may cause to the equipment.
This document contains proprietary information which is protected by copyright. All Rights Reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws.
Philips Medizin Systeme Böblingen GmbH
Hewlett-Packard Str. 2
71034 Böblingen, Germany
The information contained in this document is subject to change without notice.
Philips makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose.
Philips shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
10
Passwords |
1 Introduction |
Passwords
In order to access different modes within the monitor a password may be required. The passwords are listed below.
Monitoring Mode: No password required
Configuration Mode: 71034
Demo Mode: 14432
Service Mode: 1345
Consult the configuration guide before making any changes to the monitor configuration.
In this guide:
-A warning alerts you to a potential serious outcome, adverse event or safety hazard. Failure to observe a warning may result in death or serious injury to the user or patient.
-A caution alerts you where special care is necessary for the safe and effective use of the product. Failure to observe a caution may result in minor or moderate personal injury or damage to the product or other property, and possibly in a remote risk of more serious injury.
11
1 Introduction |
Warnings and Cautions |
12
2
The IntelliVue MP80/MP90 Patient Monitor:
-displays real-time data
-controls the attached measurement servers
-alarms in the case of patient or equipment problems
-offers limited data storage and retrieval (trending)
-interfaces to the Philips Clinical Network and other equipment
A monitor with just a single integrated measurement server can be connected to additional building blocks to form a monitoring system with a large number of measurements, additional interface capabilities and multiple slave displays. These elements cooperate as one single integrated real-time measurement system.
13
2 Theory of Operation |
Monitor Theory of Operation |
The following diagram discusses specific boundaries within the overall system with respect to their openness and real-time requirements:
Measurement LAN
combines components of one patient monitor; real time requirements across all interconnected elements
Philips Clinical Network (wired LAN)
connects multiple patient monitors, information centers, application servers; closed system, only Philips qualified products (tested and with regulatory approval) are connected, Philips is responsible for guaranteed real-time functionality and performance
Philips Clinical Network (wireless)
like Philips Clinical Network (wired) LAN, however due to current wireless technologies available it has reduced bandwidth, longer latencies, reduced functionality
Hospital LAN, Internet
Standard Network, not under Philips control, no guaranteed service, no real-time requirements
14
Monitor Theory of Operation |
2 Theory of Operation |
The following hardware building blocks make up the monitoring system:
The MP80/MP90 monitor:
-can be used with the standalone M8031A 15-inch or the M8033A 17-inch color LCD TFT display with touchscreen operation.
-can also be used with other XGA and SXGA standalone off-the-shelf displays which comply with medical standards such as IEC 60601-1 and IEC 60601-1-2.
-has the central processing unit in a separate module
-uses the Philips SpeedPoint as primary input device whereas the Philips Touchscreen and computer devices such as mice, trackball, and keyboard can be added optionally
-supports the Flexible Module Rack (FMS)
15
2 Theory of Operation |
Monitor Theory of Operation |
Building Blocks:
The M8031A 15-inch color LCD TFT display or the M8033A 17-inch color LCD TFT display (both with touchscreen operation) can be ordered optionally. Additional input devices such as mice, trackball or keyboard can also be added. If the monitor is ordered with the wireless LAN option a wireless transmitter is required. For further details regarding the wireless network please refer to the M3185A Philips Clinical Network documentation.
16
Monitor Theory of Operation |
2 Theory of Operation |
M3001A Multi-Measurement Module (MMS)
M3002A IntelliVue X2
M3012A, M3014A, M3015A, M3016A MMS Extensions
17
2 Theory of Operation |
Monitor Theory of Operation |
The AC/DC converter transforms the AC power coming from the power plug into 48 V/120W DC source and isolates the monitoring system from the AC power mains.The 48V is distributed via power bus and supplies power to all the components of the system: The 56 V DC power needed for the FMS, MMS and MMS Extension is created by an isolating DC/DC converter. The CPU is supplied with 3.3 V and 5 V DC power. The transformation is performed in two steps: The first DC/DC converter is a power regulator which reduces the variations caused by load changes on the 48V power bus. The second DC/DC converter converts the power to the needed voltage. Interface boards require a power of 10V AC.
The CPU boards have an MPC860 50 MHz or MPC86x 100 MHz processor that provides a number of on-chip, configurable interfaces. An array of 12 fast UARTS with configurable protocol options are implemented in an ASIC (along with other system functions such as independent watchdogs etc.), providing interfacing capabilities to measurement modules and I/O boards. The serial interfaces can easily be electrically isolated. The main board contains additional video hardware.
The CPUs provide two LAN interfaces to interconnect CPUs (via the MSL) and to connect to the Philips Clinical Network.
The CPU capabilities are identical. Different loading options are coded on serial EEPROMs to support the automatic configuration of the operating system at boot time.
18
Monitor Theory of Operation |
2 Theory of Operation |
Interfaces to the monitor are implemented via I/O boards. The location of these boards is restricted by general rules. The I/O slot designations diagram and the I/O matrix which outline the I/O board placement rules can be found in the Installation Instructions section.
The following is a list of Interface (I/O) boards which may be present in your monitor, depending on your purchased configuration:
-MSL
-Video (analog)
-Philips Clinical Network (LAN wired or wireless)
-Basic Alarm Relay (Nurse Call)
I/O boards:
-PS/2
-MIB/RS232
-USB
-Flexible Nurse Call
-Parallel printer
-Remote devices (Remote Alarm Device, Remote Extension Device)
-IntelliVue 802.11 Bedside Adapter
The specifications for the above listed interfaces can be found in the technical data sheet for the monitor and in the Installation and Specifications chapter of the Instructions for Use.
The following diagram shows how data is passed through the monitoring system. The individual stages of data flow are explained below.
19
2 Theory of Operation |
Monitor Theory of Operation |
Monitoring data (for example patient measurement data in the form of waves, numerics and alerts) is acquired from a variety of sources:
-Measurement Servers
The Measurement Servers connected to the internal LAN convert patient signals to digital data and apply measurement algorithms to analyze the signals.
-External measurement devices
Data can be also acquired from devices connected to interface boards of the monitor. Software modules dedicated to such specific devices convert the data received from an external device to the format used internally. This applies to parameter modules and the Anesthetic Gas Module.
-Server systems on the Philips Clinical Network
To enable networked applications such as the other bed overview, data can be acquired from server systems attached to the Philips Clinical Network, for example a Philips Information Center
All data that is acquired from measurement servers or external measurement devices is temporarily stored by a dedicated data provider system service. All monitor applications use this central service to access the data in a consistent and synchronized way rather than talking to the interfaces directly.
This service makes the applications independent of the actual type of data acquisition device.
The amount of data stored in the data provider system service varies for the different data types. For example several seconds of wave forms and the full set of current numerical values are temorarily stored in RAM.
Some applications require storage of data over longer periods of time. They can use the persistent data storage system service. Dependent on the application requirements, this service can store data either in battery backed-up (buffered) memory or in flash memory. The buffered memory will lose its contents if the monitor is without power (not connected to mains) for an extended period of time. The flash memory does not lose its contents.
The trend application for example stores vital signs data in a combination of flash memory and buffered memory, while the system configuration information (profiles) is kept purely in flash memory.
20
Monitor Theory of Operation |
2 Theory of Operation |
Applications can use high level commands to display monitoring data or status and command windows on the internal LCD panel. These commands are interpreted by the display manager application. This application controls the dedicated video hardware which includes video memory and a special ASIC.
User input is acquired from a variety of input devices, for example the SpeedPoint, the touchscreen or other standard input devices (keyboard, mouse) which may be attached to I/O boards. The system software makes sure that the user input is directed to the application which has the operating focus.
The monitoring system is very flexible and customizable regarding its data output devices. Built-in devices (for example LAN, alarm lamps, speaker, video) provide the basic output capabilities.
These capabilities can be enhanced by adding additional I/O boards, as required in the specific end-user setup. The additional I/O boards typically provide data to externally attached devices, for example to printers, RS232 based data collection devices, nurse call systems etc.
The monitor can identify I/O boards by means of a serial EEPROM device that stores type and version information. The operating system detects the I/O boards and automatically connects them with the associated (interface driver) application. For some multi-purpose cards it is necessary to configure the card for a particular purpose first (for example the dual MIB/RS232 card can support external touch display , data import, data export).
The monitor applications provide additional system functionality over the basic measurement and monitoring capabilities. This includes for example trending, report generating, event storage or derived measurements.
In general, the monitor applications use the data provider system service to access the measurement data. Application interfaces to the other system services allow the application to visualize data, to store data over extended periods of time or to output data to other devices.
21
2 Theory of Operation |
Monitor Theory of Operation |
All components of the monitoring system (including measurement servers and CPUs in the monitor) communicate using an IEEE802.3/ Ethernet LAN in the Measurement Link (MSL). This network is used to distribute data between the components, for example:
-Digitized patient signals including wave data, numerical data and status information (typically from the measurement server to a display unit)
-Control data representing user interactions (typically from the display unit to a measurement server)
-Shared data structures, for example representing patient demographical data and global configuration items
The internal LAN allows plug and play configuration of the monitoring system. The system automatically detects plugging or unplugging of measurement servers and configures the system accordingly.
The components on the internal LAN are time-synchronized to keep signal data consistent in the system. Dedicated hardware support for synchronization eliminates any latency of the network driver software.
The integrated LAN provides deterministic bandwidth allocation/reservation mechanisms so that the real-time characteristic of signal data and control data exchange is guaranteed. This applies to the data flow from the measurement server to the monitor (for example measurement signal data) and the data flow from the monitor to a measurement server (for example to feed data to a recorder module).
Integrated communication hubs in the monitor and the FMS allow flexible cabling options (star topology, daisy chaining of servers).
22
Monitor Theory of Operation |
2 Theory of Operation |
The monitoring system may be connected to the Philips Clinical Network, for example to provide central monitoring capabilities or other network services. This connection may be through a normal wired connection or through a wireless connection.
The monitor supports the connection of an external wireless adapter or an internal wireless adapter (#J35). Switching between wired and wireless networks is automatically triggered by the plugging or unplugging of the network cable.
The Philips Clinical Network protocols function very similarly to the protocols used on the internal LAN.
After configuration, the monitoring system sends the digitized patient signals including wave data, numerical data and status information onto the network. Control data representing user interactions can be exchanged between the monitoring system and a central station bi-directionally.
Additional protocols are supported for networked applications, for example for the other bed overview function, which allows viewing of monitoring data from other patients on the network.
For plug and play operation, the monitoring system uses the standard BootP protocol to automatically acquire a network address.
The support tool is a Windows application typically installed on the laptop of a customer engineer or a biomedical engineer working in the customer’s own service department.
The purpose of the support tool is to upgrade, configure and diagnose all monitoring components (modules, measurement servers, and monitors) in the system over the network.
The service protocol developed for this purpose uses a raw access to the devices without the need for IP addresses etc. over a standard customer network installation, so that even defective devices can be upgraded as long as the few kBytes of initial boot code are working. The boot code itself can also be upgraded using the same protocol.
The tool allows access to internal service information and to serial numbers. It can be remotecontrolled, for example via a dial-up connection from a response center, provided the proper infrastructure is in place.
For details see the Instructions for Use for the Support Tool.
23
2 Theory of Operation |
Monitor Theory of Operation |
shows the functional block diagram for the monitoring system. A legend explaining terms and diagram elements follows. The information below varies depending on the purchased monitor options.
IntelliVue Patient Monitoring System Functional Block Diagram
24
Monitor Theory of Operation |
2 Theory of Operation |
Functional Block |
Description |
Services |
|
Operating System |
The Operating System (OS) provides a layer of isolation |
|
between the specific hardware implementation and the |
|
application software. The OS performs system checks and |
|
allocates resources to ensure safe operation when the |
|
system is first started. This includes internal self-tests on |
|
several hardware modules and configuration checks for |
|
validity of configuration with the operating software. |
|
During normal operation, the OS continues to run checks |
|
on system integrity. If error conditions are detected the |
|
OS will halt monitoring operations and inform the |
|
operator about the error condition. |
System Services |
The System Services provide generic common system |
|
services. |
|
In particular: |
|
They use a real-time clock component to track time. They |
|
synchronize to network time sources and verify the |
|
accuracy of the system time information. They are also |
|
responsible for managing persistent user configuration |
|
data for all Measurement Servers, Flexible Module Racks |
|
and IntelliVue Patient Monitoring System software |
|
modules. User configuration data is stored in a |
|
non-volatile read/write storage device |
|
|
Applications |
|
Application Server Client |
The Application Server Client provides the Citrix1 thin |
|
client functionality. |
|
|
25
2 Theory of Operation |
Monitor Theory of Operation |
Functional Block |
Description |
|
Reports |
The Reports Service retrieves current and stored |
|
|
physiological data and status data to format reports for |
|
|
printing paper documentation. The following reports are |
|
|
supported: |
|
|
- |
Vital Signs Report |
|
- |
Graphical Trend Report |
|
- |
Event Review Report |
|
- |
Event Episode Report |
|
- ECG Report (12 Lead/Multi-Lead) |
|
|
- |
Cardiac Output Report |
|
- |
Calculations Report |
|
|
(Hemodynamic/Oxygenation/Ventilation) |
|
- |
Calculations Review Report |
|
- |
Wedge Report |
|
- |
Test Report |
|
- Other reports (e.g. Loops, Review Applications, Drug |
|
|
|
report) |
|
The Reports service generates report data which can be |
|
|
printed on a local or a central printer. |
|
Record |
The Record Service retrieves current and stored |
|
|
physiological data and status data to format a continuous |
|
|
strip recording. A recording can be triggered manually by |
|
|
the operator or automatically by an alarm condition. The |
|
|
Record Service uses the services of the Recorder Interface |
|
|
to control an M1116B Recorder in the FMS. The Record |
|
|
Service can also send data to a central recorder. |
|
|
|
|
26
Monitor Theory of Operation |
2 Theory of Operation |
Functional Block |
Description |
Alarm |
The Alarm Service contains logic that prioritizes alarm |
|
conditions that are generated either by the Measurement |
|
Servers, Flexible Module Rack, or by IntelliVue Patient |
|
Monitoring System software modules. Visual alarm |
|
signals (messages) are displayed at the top of the |
|
IntelliVue Patient Monitoring System display and alarm |
|
sounds are generated by a loudspeaker. Alarm conditions |
|
may be generated when a physiological parameter |
|
exceeds preselected alarm limits or when a physiological |
|
parameter or any other software module reports an |
|
inoperative status (technical alarm, for example, the ECG |
|
leads may have fallen off the patient). The Alarm service |
|
manages the alarm inactivation states, for example |
|
suspension of alarms, silencing of alarms, and alarm |
|
reminder. Alarm signals may also be configured as |
|
latching (alarm signals are issued until they are |
|
acknowledged by the operator, even when the alarm |
|
condition is no longer true). The Alarm service controls |
|
the visual alarm signals (alarm lamps). |
Trend |
The Trend service stores the sample values of |
|
physiological data and status data with a resolution of 12 |
|
seconds, 1 minute or 5 minutes for a period of up to 48 |
|
hours. The data is kept in battery buffered read/write |
|
storage and flash memory devices to be preserved across |
|
power failures. The stored data is protected via |
|
consistency checks and checksums. When a new patient is |
|
admitted, the trend database erases all data of the previous |
|
patient. |
HiRes |
The OxyCRG (Oxygen CardioRespiroGram) service |
|
derives a high-resolution trend graph from the |
|
Beat-to-Beat Heart Rate, SpO2 or tcpO2, and Respiration |
|
physiological data. The OxyCRG is specialized for |
|
neonatal applications, allowing the operator to identify |
|
sudden drops in Heart Rate (Bradycardia) and SpO2 or |
|
tcpO2 (Desaturations), and supporting the operator in |
|
visualizing Apnea situations. |
ADT |
The ADT (Admit/Discharge/Transmit) service maintains |
|
the patient demographics information. The operator may |
|
admit a new patient, discharge the old patient and enter or |
|
modify the patient demographics. The ADT service also |
|
supports the transport of a patient (trend database) with |
|
the M3001A Multi-Measurement Module. The ADT |
|
service controls the deletion of old patient data, the |
|
upload of trend data from the M3001A and the switching |
|
back of all settings to user defaults. It also synchronizes |
|
patient information with a central station on the network. |
|
|
27
2 Theory of Operation |
Monitor Theory of Operation |
Functional Block |
Description |
Calc Param |
The Calc Param (Calculated Parameters) service accesses |
|
current, stored and manually entered physiological data as |
|
input to calculation formulas. With these formulas, |
|
derived hemodynamic, oxygenation and ventilation |
|
variables are computed. The calculation results, including |
|
the input parameters, are stored for later review using the |
|
Trend service. |
Drug Calc |
The Drug Calc application aids in calculating drug |
|
dosages for patients. |
PV Loops |
The PV Loops application compares graphic |
|
representations of airway waves to help detect changes in |
|
the patient airway condition. |
Interface Managers |
|
MDSE |
The MDSE (Medical Data Service Element) Interface |
|
Manager is responsible for the exchange of real-time data |
|
between the IntelliVue Patient Monitoring System display |
|
unit and the Measurement Servers and Flexible Module |
|
Rack as well as between the IntelliVue Patient |
|
Monitoring System display unit and other devices |
|
attached to the network. MDSE establishes and maintains |
|
a data communication link between the devices. It |
|
provides configuration information about the remote |
|
device to applications in the local device and it allows the |
|
exchange of measurement data and status information |
|
between the devices. |
Printer |
The Printer Interface Manager provides a high level |
|
interface to a printer. It provides means to: |
|
- establish a connection to the printer |
|
- transfer data to the printer |
|
- get status of the printer |
|
- close connection to the printer |
|
The Printer Interface Manager also supervises the |
|
connection to the printer and whether the printer accepts |
|
data (for example paper out). The Printer Interface |
|
Manager notifies the operator in such cases. |
|
|
28
Monitor Theory of Operation |
2 Theory of Operation |
Functional Block |
Description |
Display & Operator |
The Display and Operator Interface Manager performs the |
Interface |
following tasks: |
|
- Screen presentation of real-time and stored |
|
physiological measurement data, alarm condition data |
|
and status information received from the MDSE |
|
interface manager, the Alarm service or other |
|
IntelliVue Patient Monitoring System modules |
|
- Screen presentation of operating controls (control |
|
windows) |
|
- Processing of operating control commands received |
|
from HIF Control interface. The module verifies and |
|
interprets the received commands and forwards them |
|
to other software modules of the IntelliVue Patient |
|
Monitoring System display unit, Measurement |
|
Servers or Flexible Module Rack |
|
- Sound generation (issues audible alarm signals and |
|
generates audible information signals, for example |
|
QRS and SpO2 tones, operator audible feedback) |
Interfaces |
|
LAN |
The LAN interface implements the physical layer of IEEE |
|
802.3. The LAN interface performs Manchester |
|
encoding/decoding, receive clock recovery, transmit pulse |
|
shaping, jabber, link integrity testing, reverse polarity |
|
detection/correction, electrical isolation, and ESD |
|
protection. Electronically separated interfaces are used for |
|
communication to the Measurement Servers or Flexible |
|
Module Rack and to the network. |
Centronics |
The Centronics interface implements the standard |
|
signaling method for bi-directional parallel peripheral |
|
devices according to IEEE 1284-I. The interface is used |
|
as a parallel interface to a standard printer with electrical |
|
isolation and ESD protection. |
|
|
29
2 Theory of Operation |
Monitor Theory of Operation |
Functional Block |
Description |
Display Controller |
The Display Controller Interface consists of a video |
|
controller chip, video RAM and the controlling software. |
|
The Display Controller interface processes the high level |
|
display commands (character and graphic generation, |
|
wave drawing) and translates them into pixels, which are |
|
written into the video RAM where the video controller |
|
chip generates the video synchronization signals and the |
|
pixel stream for the Color LCD Display. |
HIF Control |
The HIF (Human Interface Control) interface scans the |
|
Human Interface devices for operator controls (Touch |
|
Screen, Speed Point, USB and PS/2 devices), formats the |
|
collected data and sends it to the display and Operating |
|
Interface. |
ECG-Out Marker-In |
The ECG Out/Marker In interface receives the ECG |
|
waveform directly from the ECG/Resp Arrhythmia |
|
ST-Segment physiological algorithm via an RS-422 serial |
|
interface and converts the digital ECG signal to an analog |
|
ECG signal. In addition, the ECG Out controller receives |
|
from a connected device the marker information and |
|
forwards this data to the ECG/Resp Arrhythmia |
|
ST-Segment physiological algorithm. The converted |
|
analog signal is used to synchronize a connected device to |
|
the patient’s ECG |
RS-422 |
The serial link RS-422 interface communicates the ECG |
|
signal to the ECG Output/Marker In of the IntelliVue |
|
Patient Monitoring System display unit. The interface is a |
|
serial, differential, full-duplex link. The interface is ESD |
|
protected. |
PS/2 |
The PS/2 interface supports the serial protocol of standard |
|
PS/2 devices (mouse). The PS/2 serial protocol is |
|
interpreted by the HIF Control interface. |
Nurse Call |
The Nurse Call board contains 2 connectors. A phone |
|
jack type connector and a multi-port connector. The |
|
phone jack type connector has a single close-on-alarm |
|
relay. The multi-port connector has three alarm relays |
|
which are configurable to be open or closed on alarm. In |
|
addition, this interface has an audible alert capability for |
|
loss of AC power. |
MIB |
The MIB interface allows full-duplex, short-haul |
|
asynchronous binary communication between the monitor |
|
and an arbitrary (medical/non-medical) device using an |
|
eight-pin RJ45 modular connector. Switching between |
|
MIB and RS232 protocol is possible. |
|
|
30