SVH Device Bridge
Connect the fleet you already have.
Most analyzers will never embed an agent, and many sit on networks that cannot reach the platform. The SVH Device Bridge runs on site, next to them, and brings every one into the same Zero Trust fleet.
Translate
Analyzers that will never run an SVH agent connect in the protocol they already speak — ASTM, POCT1-A2, HL7® v2 over MLLP, or MQTT. Each analyzer becomes its own enrolled device, with its own identity, twin, sync state, and presence.
Relay
Agent devices on closed lab and ICU VLANs reach the platform through the bridge. The relay is TCP passthrough — mutual TLS stays end to end between device and platform, so the bridge sees only ciphertext and cannot impersonate a device.
Update proxy
The bridge updates itself over the air, and carries signed firmware to translated analyzers whose protocol can transfer it — bringing devices without an agent into the same update program.
A new model is a profile, not a release
Each analyzer model is described by a signed driver profile that maps its dialect to platform events. Profiles hot-reload; adding a model on a known protocol needs no new software build.
Admits only what you registered
An administrator pre-registers each analyzer against its bridge by model and serial. Anything else that connects is quarantined and reported, never silently admitted.
Outbound only, managed centrally
The bridge opens no management port. It dials out to the platform, joins with a single-use code, and takes its listeners, relay settings, and allowlist from the server.
Spec sheet
At a glance
| Analyzer protocols | ASTM E1381 / E1394, POCT1-A2, HL7® v2 over MLLP, MQTT; custom protocols as adapter modules |
|---|---|
| Data flows | Results, QC and calibration runs, orders and host query, operator lists and lockout, status and consumables |
| Identity | Per-bridge sub-CA issued by platform PKI; one enrolled identity per analyzer |
| Relay | TCP passthrough; device mutual TLS stays end to end |
| Connectivity | Outbound only to the platform; no inbound management port |
| Data at rest | Durable per-analyzer outbox; patient data encrypted with AES-256-GCM |
| Storage | SQLite or PostgreSQL |
| Deployment | Rootless container under systemd, or a bootable appliance image |
Bring your installed base online.
Tell us which analyzers are on your floor and we will map them to driver profiles.