Uttam Sahu
Sanjay Pithadia co-authored this article.
In our previous post, we talked about medical alarms and their compliance requirements. Now, let’s talk about the design inputs and existing implementation methods for medical alarm systems.
Figure 1 shows a high-level block diagram of multiparameter patient monitor. The block outlined in red represents the output user interface which can drive the display and speakers for the visual and audio alarms, respectively. This subsystem is common in most medical equipment. Based on the specific requirements of the end-equipment and expected failure conditions, designers use different techniques for generation the alarm tones. We will discuss the most common design inputs and implementation schemes in this article.
Figure 2 shows a block diagram of a medical device alarm implementation. One of the main requirements of a medical device design is that it needs to be single-fault proof. A “single-fault condition” in medical equipment refers to the presence of a single independent abnormal condition. During a single-fault condition, a medical device must provide basic safety from physical hazards and minimum functionality, known as “essential performance.” An alarm is part of the essential performance for most therapeutic and all critical-care medical devices. Hence, the alarm function needs to be single-fault proof.
The list of single-fault conditions for a medical alarm includes:
For medical devices where the time to respond to a failure is not very critical, the auditory and visual alarms can complement each other as redundant alarm functions. In critical-care equipment such as a ventilator, however, the response time to a failure is critical.
As you can see in Figure 2, the alarm subsystem implements redundancy by using two sets of visual and auditory alarms. The failure of the main alarm function is detected using a coincidence circuit, which typically includes a microphone placed close to the speaker to monitor the sound level. A sound received by the microphone that is not the same as the sound generated by the circuit will register an error condition. TI’s alarm tone generator reference design implements an example coincidence circuit.
There are multiple existing ways to implement the alarm functionality, such as with an MCU, a field-programmable gate array (FPGA) or complex programmable logic device (CPLD), an integrated buzzer, an audio codec, or with discrete operational amplifiers and glue logic. All of these techniques have pros and cons. Table 1 compares different implementation techniques in terms of configurability, usability, cost, bill of materials and applicability to the different end equipment.
Hardware-only solution | Audio chip | Microcontroller | Integrated buzzer | FPGA/CPLD | |
---|---|---|---|---|---|
Components | Tone generator, envelope generator, volume control, audio amplifier, speaker | Audio chip, audio amplifier, speaker | Microcontroller, amplifiers, analog mixer, audio amplifier, speaker | Integrated buzzer | FPGA/CPLD, audio digital-to-analog converter/codec, audio amplifier, speaker |
Pros |
|
|
|
|
|
Cons |
|
|
|
|
|
One technique for implementing a medical alarm uses DAC53701, a 10-bit smart digital-to-analog converter (DAC) that supports medical alarm generation using pre-programmed waveforms. This DAC can be used for both auditory and visual alarm generation, and it supports configurability of the pulse frequency and the timings for the pulse envelope and the burst. You can read more about this technique in the application brief, Demystifying Medical Alarm Designs With Smart DACs.
TI PROVIDES TECHNICAL AND RELIABILITY DATA (INCLUDING DATASHEETS), DESIGN RESOURCES (INCLUDING REFERENCE DESIGNS), APPLICATION OR OTHER DESIGN ADVICE, WEB TOOLS, SAFETY INFORMATION, AND OTHER RESOURCES “AS IS” AND WITH ALL FAULTS, AND DISCLAIMS ALL WARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT OF THIRD PARTY INTELLECTUAL PROPERTY RIGHTS.
These resources are intended for skilled developers designing with TI products. You are solely responsible for (1) selecting the appropriate TI products for your application, (2) designing, validating and testing your application, and (3) ensuring your application meets applicable standards, and any other safety, security, or other requirements. These resources are subject to change without notice. TI grants you permission to use these resources only for development of an application that uses the TI products described in the resource. Other reproduction and display of these resources is prohibited. No license is granted to any other TI intellectual property right or to any third party intellectual property right. TI disclaims responsibility for, and you will fully indemnify TI and its representatives against, any claims, damages, costs, losses, and liabilities arising out of your use of these resources.
TI’s products are provided subject to TI’s Terms of Sale (www.ti.com/legal/termsofsale.html) or other applicable terms available either on ti.com or provided in conjunction with such TI products. TI’s provision of these resources does not expand or otherwise alter TI’s applicable warranties or warranty disclaimers for TI products.
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright © 2023, Texas Instruments Incorporated