CLINICAL DEVICE CONNECTORS

Alerts & Events

8 of 10

Connect clinical devices and professional peripherals through standards-based local, network and vendor-specific interfaces.

Threshold alertsEvent streamAcknowledgementsSubscriptionsRulesEscalation

Event and alert types

Type	Examples	Typical destination
Clinical measurement event	New observation, waveform packet, trend update	FHIR ingest + patient timeline
Device status event	Disconnected, battery low, sensor removed	Operations dashboard / workflow
Threshold alert	High BP, low SpO2, abnormal rhythm indicator	Clinical alerts / escalation
Workflow event	Scan completed, transcript ready, print job done	Workflow engine / task list
Operational error	Parse error, driver failure, timeout	Monitoring, support and retries

Alert governance

Define which alerts are informational vs actionable.

Deduplicate and throttle noisy device events.

Always preserve source severity and acknowledge state.

Escalation rules should be explicit and testable.

Signal quality

Alert routing should balance safety and alarm fatigue; not every device event becomes a user-facing clinical alert.

Alert pipeline

Device emits event

Measurement, status or alert

Validate & enrich

Identity, patient context, severity

Apply rules

Thresholds, dedupe, escalation

Deliver

In-app, workflow or notifications

Acknowledge

Track response and closure

Audit & analyze

Latency, outcomes, volumes

Subscription example

typescriptCopy

agent.events.subscribe({
  connectorId: 'monitoring-gateway-01',
  eventTypes: ['observation.created', 'device.alert', 'device.status.changed'],
  callbackUrl: '/api/webhooks/devices',
  filters: { siteId: 'lux-clinic-01', severity: ['high', 'critical'] },
});