CLINICAL DEVICE CONNECTORS

Device Commands & Control

7 of 10

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

ReadCommandAcknowledgeSafety boundariesTimeoutsAudit

Command & control model

Capability	Examples	Important rule
Read / poll	Fetch current measurement, status, battery, availability	Supported broadly and generally lower risk
Session control	Open session, start stream, subscribe to events	Use explicit lifecycle and timeout handling
Operational command	Trigger print, reset buffer, acknowledge alert	Require permission and auditable acknowledgment
Clinical control	Change therapy-related settings	Only when explicitly supported, governed and validated

Safety principles

Not every device should expose remote commands.

Capabilities must be explicit and narrow, not assumed from transport access.

Commands need user, role and tenant context plus device acknowledgment.

Time-bound sessions and replay protection are strongly recommended.

Clinical safety

Therapy-affecting or patient-safety-sensitive commands require separate review, stronger controls and vendor-specific validation.

Command lifecycle

Authorize

Role, tenant and scope checks

Validate

Capability + payload schema

Send

Connector transmits command

Acknowledge

Device or vendor confirms

Handle timeout

Retry or fail safely

Audit

Persist trace of who did what

Illustrative command example

typescriptCopy

await mediloop.devices.sendCommand({
  connectorId: 'pump-connector-01',
  deviceId: 'pump-room12-bed2',
  command: 'acknowledge-alert',
  payload: { alertId: 'a-1289' },
  actor: { membershipId: 'mem_123', role: 'nurse' },
  correlationId: 'corr_8ac12',
});