SVH Device & Data Management Server
Run the fleet. Own the data. Speak the standards.
The server is where a fleet becomes operable: every device enrolled and attested, every result captured and delivered, every hospital system spoken to in its own protocol.
Fleet operations
- Enrollment and provisioning: birth certificate to operational certificate
- Full PKI and certificate lifecycle for every device
- Digital device twin: declare desired state, watch it reconcile
- Runtime-editable roles and permissions; database, LDAP, or OIDC login
- Offline-capable operator credentials — instruments keep working without a live link
Clinical data pipeline
- Guaranteed, ordered capture of clinical results — the system of record
- Separate streams for telemetry and alarms, so results are never crowded out
- End-to-end delivery tracking: transmitted, when, and acknowledged
- Append-only, exportable audit trails
- IVD workflows: QC with Westgard rules, autoverification, delta checks, calibration and lot tracking
Analytics
- Time-series analytics across devices, sites, and fleets
- De-identified by architecture: patient identity never reaches the analytics plane
- Utilization, reliability, and quality trends out of the box
Interoperability
- FHIR® R4, HL7® v2.x over MLLP, ASTM E1394 / LIS2-A2, POCT1-A2, and JSON webhooks
- Results out; orders, worklists, and patient demographics back in
- Coded vocabularies: LOINC®, UCUM, SNOMED CT®
- A low-friction onramp for legacy clinical applications that cannot be modified
Consoles
Two consoles, one platform.
Admin Console
Platform operations: fleet status, live enrollment queues, PKI and certificate expiry, users, roles, and audit. Approvals that matter — like admitting a device to the fleet — are signed actions with re-authentication and a reason for change.
Clinical Console
Clinical results review, device configuration with signed changes, and de-identified analytics dashboards — built for shared clinical workstations, accessible to WCAG 2.2 AA, and localizable without a software release.
Deployment
Appliance to cloud, same code.
Deploy the entire platform as one process on a single host, or as independently scaled services with Kafka and MQTT backbones. Rootless containers under systemd for appliances; the same signed images on Kubernetes for cloud and cluster installs.
Engineering
Built like infrastructure.
A modular monolith with enforced boundaries, event-driven with a durable transactional outbox and at-least-once delivery. Every image ships with a CycloneDX SBOM, signed and digest-pinned. Multi- tenant from the first line of code.
See the platform in action.
Tell us about your devices and we will walk you through the platform, end to end.