Where wearable ECG patches and bands are used

Wearable ECG patches and bands act as edge nodes that capture cardiac signals, perform basic processing and send data wirelessly to phones, home hubs or hospital systems. They sit between the patient and the multi-parameter monitor, replacing some wired leads while still targeting medical-grade signal quality.

Typical use cases

1) 24–72 h disposable patch as a Holter alternative
A single-use chest patch records ECG continuously for one to three days in ambulatory settings. The node must deliver stable signal quality over aging gel and changing skin conditions while running from a small coin cell. Ultra-low-power AFEs, coin-cell-friendly PMICs and robust local buffering are key.

2) Long-term wrist band for chronic disease monitoring
A reusable band is worn for weeks or months at home or in the community. It captures shorter ECG segments and HRV trends throughout the day and streams them to a phone or home gateway. This scenario drives strict average current limits, strong motion-artifact resilience and reliable BLE links.

3) Post-operative and in-ward cable reduction
In hospital wards, wearable ECG patches reduce lead clutter and give patients more mobility while still feeding ECG into the central monitoring system. The node must interoperate cleanly with multi-parameter bedside monitors, preserve alarm workflows and make battery state and link status visible to clinical staff.

4) Wellness and sports monitoring with medical-grade ambitions
Bands that target stress, recovery and training insights often aim for ECG and HRV performance closer to medical devices than to casual wearables. This combines consumer expectations on comfort and cost with medical expectations on signal fidelity, pushing designers toward highly integrated AFEs, PMICs and BLE SoCs.

Role in a patient monitoring system

A wearable ECG node focuses on acquiring signals from electrodes, conditioning them through an ultra-low-power AFE, managing power, buffering data and forwarding information over BLE or other low-power radio links. A multi-parameter patient monitor then aggregates ECG from one or more nodes along with SpO₂, NIBP and temperature, handles alarm logic and presents trends to clinicians.

Clinical ECG interpretation, full HRV analysis and complete alarm strategies are covered on dedicated pages such as the ECG / HRV and Patient Monitor topics. This page concentrates on node-level hardware and low-level data paths for patches and bands.

Form factor, wear and electrode interface constraints

The way a patch or band touches the skin drives electrode impedance, common-mode behaviour and motion artefacts, and these in turn dictate the requirements placed on the ECG AFE and protection network. The goal is to keep signals usable as adhesives age, sweat accumulates and the patient moves, without violating power and safety limits.

Disposable chest patches typically offer stable placement but evolving contact quality over 24–72 hours. Electrode impedance can drift from tens of kilohms toward hundreds of kilohms or more, so the AFE must provide very high input impedance and carefully controlled bias currents. Lead-off detection must distinguish between degraded contact and a fully detached electrode.

Reusable wrist bands keep the device on the arm but see strong motion because of everyday activities and exercise. Contact area changes with wrist angle, strap tightness, sweat and hair. These conditions produce larger motion artefacts and transient impedance steps, so the front end needs robust input protection and biasing that can tolerate fast changes without saturating or losing the true cardiac signal.

Across both formats, the skin–electrode interface introduces a wide impedance range and acts as a mechanism for mains coupling. High and unbalanced impedances make common-mode rejection more difficult and increase sensitivity to 50/60 Hz interference and other environmental noise. The AFE therefore needs strong CMRR around mains frequency, a stable right-leg drive loop and input protection that does not degrade noise or bandwidth.

Detailed electrode configurations and diagnostic lead standards are handled on the ECG / HRV page. This section keeps the focus on how wearable layouts influence impedance, common mode and artefacts, and on the resulting requirements for input impedance, bias current, right-leg drive and lead-off detection.

ULP ECG AFE architecture for wearable devices

Bedside ECG front ends target diagnostic performance with generous power budgets, whereas wearable AFEs must deliver acceptable noise and common-mode rejection in motion-heavy environments under a few hundred microamps to a few milliamps of average current. This shifts priorities toward ultra-low-power biasing, integrated functions and careful trade-offs between bandwidth, noise and recovery behaviour.

Bedside monitors can draw from AC power and large batteries, allowing multi-channel AFEs with wide configurable bandwidth and very low input-referred noise. Wearable nodes, in contrast, run from coin cells or small Li-ion cells and must keep the entire node within a tight energy envelope while still resolving mV-level ECG signals through variable skin–electrode impedance and motion artefacts.

A typical wearable ECG AFE therefore combines a high-impedance differential input stage with a programmable gain amplifier, configurable high-pass and low-pass filters, an integrated sigma-delta ADC, and supporting functions such as right-leg drive, lead-off detection and internal bias control. The architecture aims to keep noise and common-mode rejection within medical expectations while limiting quiescent current and supporting duty-cycled operation.

The differential amplifier and PGA provide very high input impedance and low bias current so electrodes with tens to hundreds of kilohms of impedance remain usable. Programmable filters shape the ECG band, control baseline wander and limit high-frequency noise. An on-chip sigma-delta converter then digitises the conditioned signal at data rates suitable for wearable streaming and local feature extraction.

Around the main signal path, a right-leg drive loop manages common-mode voltage and 50/60 Hz rejection, while lead-off detection monitors electrode status and distinguishes degraded contact from complete detachment. Internal bias and mode control circuits further reduce average current by throttling bias levels in low-activity periods yet still permitting rapid recovery from saturation events. Detailed noise modelling, filter topology choices and clinical HRV implications are covered on the ECG / HRV page; this section focuses on the key architectural building blocks and IC roles for wearable nodes.

Power architecture and PMIC for wearable ECG nodes

Wearable ECG patches and bands rely on small coin cells or Li-ion batteries, so the power architecture must turn limited energy into reliable operation for days or weeks. Designers typically combine battery protection, charging or voltage monitoring, a PMIC that generates several rails, and fuel-gauge functions that expose remaining capacity to the application and to clinical workflows.

Disposable patches often use CR2032 or CR2450 cells to support 24–72 hours of continuous recording, which drives the whole node average current into the low hundreds of microamps. Rechargeable wrist bands more commonly use Li-ion or LiPo cells around 50–300 mAh, aiming for multi-day or multi-week use between charges with occasional high-current bursts for radio and processing. Some medical devices also dock into wireless charging cradles, relaxing energy constraints but still requiring tight thermal and cycle-life control.

A representative power tree starts at the battery and passes through protection and, for Li-ion, a charger block. A central PMIC then generates separate rails for the analog AFE, the MCU and BLE core, RF functions, sensors and any always-on logic. Analog rails tend to use low-noise LDOs to preserve ECG fidelity, while digital and RF rails use efficient buck or boost converters to handle burst currents with acceptable losses.

The average current budget is divided among the ECG AFE, BLE radio, microcontroller and security or sensing extras. The AFE may run continuously or in a duty-cycled mode depending on the monitoring strategy. BLE consumption depends strongly on advertising interval, connection interval and streaming duty cycle. The MCU spends most of its time in deep sleep and wakes only to handle events, while secure elements and crypto engines draw short bursts of current during pairing, authentication or data protection operations.

This section focuses on the low-voltage power tree inside the wearable node and does not cover mains-side isolation or medical MOPP/MOOP supply requirements, which sit at the system level and belong to the Medical Isolated Power topic. The objective here is to show how the PMIC partitions rails and current budgets so ECG AFEs, radios and security features can coexist within a realistic energy envelope.

BLE SoC, data path and on-node processing

Inside a wearable ECG patch or band, the BLE SoC forms the bridge between the ultra-low-noise AFE and the smartphone or gateway. Digitised ECG samples from the sigma-delta ADC feed into the MCU core inside the SoC, where basic filtering, R-peak detection and event tagging run at low power. A local buffer absorbs link interruptions and connection gaps so clinically relevant waveform segments and features are not lost.

The data path typically starts with continuous sampling at 250–500 samples per second per channel, with fixed or programmable resolution. The MCU then applies lightweight digital filtering, derives heart rate and R-R intervals and tags segments around irregular rhythms or poor signal quality. These samples and features are placed into a ring buffer or block-based queue that decouples the AFE data stream from the timing of BLE connection events and phone-side processing.

Several upload strategies are common. Continuous waveform streaming sends most ECG samples to the phone or gateway, enabling rich analysis at the expense of higher radio duty cycle and energy usage. Event-centric schemes send compact metrics such as heart rate, HRV features and signal quality scores during normal operation and reserve full waveform upload for short windows around detected arrhythmia, symptom button presses or clinical triggers. The choice sets the required data rate and directly shapes the average current drawn by the BLE subsystem.

BLE parameters such as advertising interval, connection interval and slave latency provide the main control knobs for balancing responsiveness with battery life. Short intervals and frequent connection events support near-real-time waveform display but pull average current up. Longer intervals and higher latency favour long-term monitoring and background uploads of features, provided that the local buffer is sized for temporary disconnections and that the application can tolerate additional delay.

Most BLE SoCs for medical wearables also support secure over-the-air firmware updates. The data path and flash layout must reserve space and bandwidth for future algorithm updates, bug fixes and new event types without disrupting ECG capture. Details of BLE protocol stack design and upstream gateway or cloud analytics are handled on the Medical Gateway & Connectivity and Security & Compliance pages; this section focuses on node-level data movement and processing.

On-device data security and privacy hooks

A wearable ECG patch or band handles sensitive cardiac data directly on the node, so basic security and privacy hooks must be implemented at the device level. These hooks complement system-level security and regulatory measures rather than replace them, and they focus on the BLE link, on-device storage and firmware integrity of the patch or band itself.

For the wireless link, BLE pairing and encryption modes determine who can see ECG data. Stronger pairing schemes with man-in-the-middle protection and encrypted links reduce the risk of unauthorised apps reading streams or captured segments. Node firmware must support secure pairing flows defined by the companion application and expose clear rules for when devices may be reset, re-paired or unbound.

Locally, ECG samples and event windows often reside in flash or EEPROM as buffers or short-term history. Without protection, opened enclosures or debug access could expose these records. Encrypting stored data with keys managed inside the BLE SoC or an external secure element, combined with defined wipe procedures when a patch is discarded or a band is reassigned, reduces the chance of residual data being recovered from retired devices.

Each device should also present a unique identity and maintain firmware integrity. Unique IDs support binding between patients, clinical systems and specific patches or bands, while secure boot and signed firmware updates help prevent unauthorised code from running on the node. Simple anti-tamper hooks, such as enclosure open detection or debug-port monitoring, can trigger protective actions like key invalidation or data wipe when obvious tampering is detected.

Cryptographic engines inside the BLE SoC and, where needed, external secure elements provide hardware support for key storage, link encryption, random-number generation and integrity checks. This section concentrates on node-level hooks that a wearable ECG patch or band must expose. The broader security architecture, regulatory mapping and hospital system integration are detailed on the Security & Compliance page.

Safety, reliability and lifecycle for wearable ECG patches and bands

Wearable ECG devices span single-use adhesive patches and reusable wrist bands, and each form factor drives different safety and reliability expectations. Single-use patches usually embed a sealed coin cell and remain on the skin for 24–72 hours, while reusable bands host rechargeable Li-ion cells and must survive months or years of daily use, charging cycles and exposure to sweat and moisture.

Single-use patches tend to rely on non-rechargeable coin cells with over-discharge protection and physical sealing around the cell and electrodes. The focus is on short-term robustness under sweat, shower exposure and daily movement without leakage, overheating or sudden power loss. Reusable bands, by contrast, use small Li-ion or LiPo packs that demand comprehensive charge, discharge and short-circuit protection along with careful thermal management over many charge cycles.

Patient safety begins at the electrode interface. Protection networks on the ECG inputs, including series resistors and clamping elements, limit fault currents and support ESD robustness during everyday handling. Battery protection and thermal monitoring guard against overheating and thermal runaway by watching cell and board temperature and enforcing shutdown or derating when limits are approached. These measures help keep surface temperature and internal fault energy within medically acceptable bounds.

Contact quality also affects safety, because poor electrode contact can corrupt ECG waveforms and mislead rhythm assessment. Algorithms and system design must attach explicit signal-quality flags to each segment so clinicians and cloud analytics can distinguish reliable data from motion-corrupted or low-contact periods. These flags should be propagated alongside waveform and feature data to upstream systems instead of silently discarding or misclassifying degraded signals.

Long-term reliability depends on environmental resistance and mechanical durability. Reusable bands must tolerate sweat, rain and repeated washing, which drive IP rating requirements and corrosion resistance for electrodes, housings and charging contacts. Connectors, flex cables, housings and buttons are subject to thousands of flex and insertion cycles. Single-use patches focus more on adhesive performance and mechanical stability over a few days so peeling, folding or concentrated stress does not damage the electronics. System level EMC tests, leakage limits and formal safety standards mapping are covered on the EMC & Patient Safety page; this section highlights node-level safety hooks specific to wearable ECG patches and bands.

Application mini-stories and BOM hooks for wearable ECG nodes

Concrete application stories help translate IC roles into real-world design choices. Different monitoring models place different demands on the AFE, PMIC, BLE SoC and security blocks in a wearable ECG node. The following scenarios focus on how IC categories are combined rather than on specific brands or full system architectures.

A 72-hour Holter replacement patch targets patients who need short-term rhythm assessment without carrying a traditional recorder and lead set. The design aims for cable-free 24–72 hour wear with data completeness above 95 percent, while remaining thin, comfortable and disposable. The bill of materials centres on an ultra-low-power ECG AFE, a coin-cell PMIC for CR-series batteries, a BLE SoC capable of waveform and event streaming and secure storage for buffering captured segments until they are uploaded.

A long-term chronic disease management band emphasises repeated short ECG captures and HRV trends over months or years. Here the priorities shift toward very low average power, comfortable wrist form factors and robust cloud synchronisation. Highly integrated SoCs that combine MCU, BLE and sensor hub functions reduce footprint and idle current. A dedicated fuel-gauge-capable PMIC tracks Li-ion or LiPo battery health, while an accelerometer or IMU supports motion artefact tagging and activity classification. Security hooks such as a secure element enhance long-term identity and key management.

A post-operative in-hospital removable patch supports enhanced monitoring during the days after surgery. The node must integrate cleanly with ward gateways and alarm workflows while operating in a dense medical environment. Ultra-low-power AFEs with strong interference recovery, BLE or multi-radio SoCs that interoperate with hospital gateways, secure storage and secure elements for hospital-grade authentication all become important. Upstream alarm routing, server logic and user interfaces are handled by the Medical Gateway & Connectivity and EMC & Patient Safety topics; this section concentrates on the node-side IC categories that appear in the BOM.

Design checklist and IC role mapping for wearable ECG nodes

Before finalising a wearable ECG patch or band, the design should close a small but critical checklist that covers electrodes and AFE performance, power and battery planning, BLE data flow, node-level security and safety and reliability requirements. Once those points are defined, the bill of materials can be mapped to a small set of IC roles that appear in most wearable ECG nodes.

Design checklist for wearable ECG nodes

1. Electrodes & ECG AFE

• □ Target input noise level defined over required ECG/HRV bandwidth (for example 0.05–40 Hz).
• □ AFE bandwidth and filter settings meet clinical and device-class requirements without clipping useful content.
• □ Input range and protection network accommodate electrode offset, motion artefacts and expected deflection levels.
• □ CMRR at 50/60 Hz meets the target for the chosen gain and electrode layout.
• □ RLD configuration verified for stability and safety with the patch or band electrode geometry.
• □ Lead-off and contact-quality detection implemented and mapped into the data stream as quality flags.

2. Power and battery planning

• □ Battery chemistry and capacity chosen for the target lifetime (for example 72 h patch or multi-week band).
• □ Average and peak current budgets closed for AFE, BLE, MCU and auxiliary sensors.
• □ Voltage rails and regulators defined for analogue, digital, radio and always-on domains.
• □ For rechargeable bands, charge profile, termination and cell protection follow the battery datasheet.
• □ UVLO, over-voltage, short-circuit and thermal protections in the PMIC verified against fault cases.

3. BLE link, sampling and data strategy

• □ ECG sampling rate and resolution set for the application (for example 250–500 sps, 16 bit).
• □ Upload strategy defined: continuous waveform, burst uploads around events or feature-only reporting.
• □ Local buffer depth sized for expected phone behaviour and temporary link loss.
• □ Advertising and connection intervals tuned for the desired balance between latency and battery life.
• □ OTA firmware update flow tested including time, energy budget and rollback behaviour.

4. Node-level security

• □ BLE pairing mode and encryption level chosen for medical data confidentiality.
• □ On-node ECG history and buffers stored encrypted; keys are not kept in plain flash.
• □ Unique device identity provisioned and tied to patient or asset records.
• □ Secure boot and signed firmware images enforced where supported.
• □ Optional secure element or HSM used where regulations or risk analysis demand stronger key protection.

5. Safety and reliability of the node

• □ Electrode protection network designed for ESD and expected transients on the skin interface.
• □ Battery and board temperature monitoring thresholds defined and validated.
• □ Environmental requirements for sweat, water ingress and corrosion met for the chosen form factor.
• □ Mechanical lifetime, connector cycles and strap durability aligned with single-use or reusable targets.
• □ Signal-quality flagging integrated so that poor-contact segments are clearly marked up the chain.
• □ System-level EMC tests and leakage limits tracked on the EMC & Patient Safety topic.

IC role mapping with example part numbers

Most wearable ECG designs can be expressed in terms of a small set of IC roles. The examples below illustrate typical device families rather than prescribing a specific brand.

Recommended topics you might also need

• ECG / HRV
• Pulse Oximetry (SpO₂)
• Continuous Glucose Monitoring (CGM)
• Hearing Aid / Cochlear (External)
• Security & Compliance

FAQs about wearable ECG patches and bands

These questions collect common design decisions for wearable ECG nodes and point back to the sections on form factor, AFE, power, BLE data paths, security, safety and IC role mapping.