Platform
One platform, from silicon to hospital systems.
SVH is not a box of middleware parts. It is one platform with two halves: an agent that lives in the device, and a server that runs the fleet — joined by a connection neither side has to trust blindly.
In the device
SVH Device Agent
A hardened, memory-safe agent that gives any embedded-Linux device a hardware-rooted identity, offline-first data delivery, safe updates, and a sandbox for first- and third-party software.
Explore the agent →At the edge or in the cloud
SVH Device Operations Platform
The operations backbone: enrollment and PKI, digital device twins, the clinical data pipeline, analytics, and standards-based integration with LIS and EHR systems.
Explore the server →On site, next to the devices
SVH Device Bridge
Brings devices that run no agent into the fleet over ASTM, POCT1-A2, HL7® v2, and MQTT, and relays agent devices on isolated networks — mutual TLS end to end.
Explore the bridge →At the device vendor
SVH Vendor Server
The vendor's back office: signed license codes, device birth certificates and installation PKI, signing-key custody, and customer installations — with its own console, role-based access, and audit. It runs at the vendor, never at customer sites.
Capabilities
Everything a connected fleet needs. Nothing bolted on.
Device Management
Every device gets a cryptographic identity at enrollment and a digital twin for the rest of its life. Fleet inventory, health, certificate status, and lifecycle state — enrollment through retirement — live in one console, not in a spreadsheet.
Data Management
Clinical results are captured as a guaranteed, ordered system of record: acknowledged end to end, never dropped, and durable through network outages. Telemetry and alarms travel on separate streams so the important data is never crowded out.
Analytics & Insights
Time-series analytics over device and fleet data — utilization, reliability, quality trends. Patient identity is structurally isolated from the analytics plane, so insight never comes at the cost of privacy.
Remote Upgrade
Signed firmware and software updates delivered over the air with staged rollout, clinician-controlled scheduling, and automatic rollback. Devices that live offline update from signed USB media using the same trust chain.
Device Configuration
Desired state is declared centrally and reconciled through the device twin. Every configuration change is authorized, signed, and recorded in a tamper-evident audit trail.
Interoperability
Bidirectional, standards-based integration with the systems that run healthcare: results out to LIS and EHR, orders and demographics back in — FHIR® R4, HL7® v2 over MLLP, ASTM, and POCT1-A2, with delivery tracked end to end.
Deployment
One codebase, two shapes.
The same platform deploys as a single appliance or as independently scaled services — switched by configuration, not by rewrite.
Single appliance
The entire platform in one process on one host. Right-sized for a single-site laboratory or an on-premise edge install. Runs as rootless containers under systemd.
Distributed & scaled
The same services deployed independently with Kafka and MQTT backbones and horizontally scaled stateless gateways — for large sites, health systems, and cloud deployments.
See the platform in action.
Tell us about your devices and we will walk you through the platform, end to end.