Bio-Signal Emulator

01 / 13

Operations dashboard

What the emulator is sending right now, and how much, on one screen.

• Transmission status, router connections, packet and data rates
• Inpatient and outpatient counts, patch and gateway status
• Network and gateway fault scenarios, artifact scenarios
• Reception status reported by the router, live event log

02 / 13

Hospital floor plans

Hospital size is derived from the number of patients to monitor: 2,000 patients means about 2,500 beds in three 20-storey buildings.

• Ten floor-plan archetypes chosen automatically by bed count
• Room area, bed spacing and corridor width checked against Korean medical and building codes
• Gateway coverage and dead zones, patients in transit
• Floor plans exported as metric JSON for viewers to reuse

03 / 13

Room zoom

Bed positions and orientation, room numbers and the ceiling-mounted gateway, drawn inside each room.

• Click to zoom and drag to pan; pick a floor from the section view
• Bed occupancy, with lead-off and no-signal highlighted

04 / 13

Central station

Clicking a gateway on the plan opens the central monitor for the patients connected to it.

• Waveforms: ECG II · Pleth · Resp
• Numerics: HR · SpO₂ · RR · NIBP · Temp · GLU with alarm limits
• Alarms coloured by priority: red for VFib, VT…; yellow for lead-off, AFib…
• Grids from 2×1 to 6×8

05 / 13

Numeric board

A numerics-only board for a whole ward at once, up to 16×10 (160 beds).

06 / 13

Bedside viewer

Clicking a central-station tile opens that patient's bedside monitor.

• Standard 25 mm/s · 10 mm/mV
• Alarm limits, 6-hour sparklines, trend table and patient events
• Light and night modes

07 / 13

Patient monitoring

Pick a patient from the list to see live ECG, numerics and records together.

• Monitoring orders: prescribed days, D+n, time left, patch wear days
• Switches to inject rhythms, episodes and lead-off
• NEWS2 early-warning score
• Admission record, exam schedule, movement and patch-change history

08 / 13

EMR integration testing

20 virtual institutions are built in so commercial EMR integration can be tested in advance.

• US, UK, Japan, Korea and more: FHIR R4/STU3, HL7 v2, CDA R2, REST, EUC-KR XML
• Ten authentication methods; synthetic IDs that pass each country's check digits
• Per-site self-test, sample requests, fault injection and request logs

09 / 13

Scenario presets

Fourteen representative scenarios, applied in one step.

• Fault-free baseline, daily ward routine, network failures, power outage and UPS
• Gateway replacement, motion artifacts, multiple code blues, 2.4 GHz interference
• Individual events injected at set times by trigger or script
• Every setting change is logged and can be rolled back per run

10 / 13

Signal transmission

Set the router address and channels, and switch on test drills.

• Store-and-forward, corrupted frames, ground-truth capture
• Upload recorded ECG files (ATF/CSV) and transmit them as-is

11 / 13

Field test

After the network, devices, server and viewers are installed, send events to a chosen gateway or patient and check the display and alarm tones on site.

• 13 event types in three priorities
• Critical: VFib, VT, asystole / Warning: AFib, SVT, SpO₂ drop and more
• Each event holds for a set time, then returns to normal

12 / 13

Data and logs

A registry of every patch issued, and the test data around it.

• Serials and patch IDs are never reused; issue and end times and reasons are kept
• Ground-truth label summaries, settings history, SQLite query console

13 / 13

Protocol

An entry-point API describes the protocol, channels, endpoints and current settings in machine-readable form; a router can start receiving from that document alone.

• 26 B frame header, 16 B records plus channels, CRC-32 trailer
• Ten channels, including ECG 250/500 Hz, PPG 100 Hz and acceleration 50 Hz