Nexiv Labs is now operating six divisions across healthcare, veterinary, commerce and infrastructure. See the group →
Division 01 — Telehealth

Nexiv Health

A virtual care platform for clinics, employers and insurers. Video and asynchronous consultations, e-prescribing, remote patient monitoring and interoperability with the clinical systems you already run.

Request a walkthrough Technical detail
HL7 FHIR R4 Encrypted records UK/EU residency
Live consult telemetry
The problem

Most telehealth is a video call with a booking form attached

That works for a pilot and collapses at scale. Clinicians end up double-keying notes, prescriptions leave the system, monitoring data has nowhere to land, and nobody can answer a subject access request without a week of manual work.

Nexiv Health is built the other way round: the clinical record and the audit trail come first, and the consultation is one event inside it. Every artefact a consultation produces — note, prescription, referral, device reading, document — is a first-class object with provenance, retention and access control attached from the moment it is created.

Consultation modes
  • Scheduled videoSlot-based booking against clinician rota, with waiting room, consent capture and optional recording.
  • On-demandQueue-based routing to the next available clinician within a defined specialty and licence region.
  • AsynchronousStructured questionnaire plus media upload; clinician responds within an SLA window.
  • Follow-upAutomated recall based on care plan milestones or monitoring thresholds.
  • EscalationOne-tap handover to in-person care with structured referral packet.
Capabilities

What ships in the platform

Consultation engine

WebRTC media with selective forwarding, adaptive bitrate and network fallback to audio. Waiting rooms, multi-party sessions for interpreters or carers, and consent recorded before media starts.

Prescribing workflow

Formulary lookup, dose checking, allergy and interaction warnings, controlled-substance gating and a signed prescription record with full issuance history.

Remote monitoring

Ingestion for blood pressure, glucose, SpO₂, weight and wearable feeds, with per-patient thresholds, trend detection and an escalation queue for the care team.

Clinician console

One workspace: queue, patient timeline, structured note templates, dictation, orders and outcomes. Designed for keyboard-first use during a live session.

Interoperability

FHIR R4 resources, SMART on FHIR launch inside host EHRs, HL7 v2 bridging for legacy estates, and document exchange for discharge summaries and referrals.

Operational analytics

Wait times, utilisation, did-not-attend rates, outcome coding and cost per consultation — with an export path into your own warehouse.

Under the hood

Architecture and data handling

Health data sets the security floor for the entire Nexiv group. Here is what that means concretely.

Platform specification
  • InteropHL7 FHIR R4, SMART on FHIR, HL7 v2.x bridge, DICOM-ready media store
  • MediaWebRTC with SFU, DTLS-SRTP, TURN relay fallback, per-session key rotation
  • ServicesTypeScript / NestJS and Go services, event-driven over Kafka
  • StoragePostgreSQL with row-level security; object store with per-tenant keys
  • EncryptionTLS 1.3 in transit; AES-256 at rest; envelope encryption via managed KMS
  • IdentityOIDC, SSO federation, step-up MFA for clinical actions, break-glass with alerting
  • AuditAppend-only access log on every record read, write and export
  • ResidencyTenant-pinned to UK or EU region; no cross-region replication of clinical data
GET /fhir/r4/Encounter/{id} 
// Every clinical read is authorised, scoped and audited.
{
  "resourceType": "Encounter",
  "id": "enc-8f21c4",
  "status": "finished",
  "class": { "code": "VR", "display": "virtual" },
  "subject": { "reference": "Patient/pat-31a9" },
  "participant": [{
    "individual": { "reference": "Practitioner/prc-77d0" }
  }],
  "period": {
    "start": "2026-08-13T09:12:04Z",
    "end":   "2026-08-13T09:29:41Z"
  },
  "meta": {
    "security": [{ "code": "R", "display": "restricted" }],
    "tag": [{ "code": "residency:uk" }]
  }
}
256-bit
AES encryption at rest, per-tenant keys
TLS 1.3
Enforced in transit, HSTS preloaded
Deployments

Who runs Nexiv Health

Clinics & provider groups

Extend capacity without extra rooms. Remote-first follow-ups, triage before an in-person slot is consumed, and a shared rota across sites.

Multi-site rota

Employers & benefits providers

Occupational health and employee virtual care under your own brand, with eligibility checks, usage reporting and strict separation from HR systems.

White-label

Insurers & care networks

Network-wide virtual first-line care with claims-ready outcome coding and per-policy entitlement enforcement at the point of booking.

Entitlement rules

Nexiv Health is a technology platform, not a healthcare provider. Clinical decisions are made by the registered professionals using it, within their own scope of practice and jurisdiction. Telehealth is never a substitute for emergency care — read the Medical & Veterinary Notice for scope, limits and what to do in an emergency.

Questions

Common questions

Yes. The primary path is FHIR R4 with SMART on FHIR launch, so clinicians open Nexiv Health from inside the host record with context already passed. For older estates we bridge HL7 v2 messages and expose a document exchange endpoint. Where no interface exists, we provide a scoped API and a reconciliation report so nothing is written blind.
Each tenant is pinned to a region at provisioning — UK or EU. Clinical data is not replicated outside that region. Backups stay in-region. Support access is proxied through a bastion that logs every session, and access to production data requires a named ticket and expires automatically. See the Trust Centre for the full description.
Only when the operating organisation enables it and the patient consents in session. Recording is off by default. When enabled, media is encrypted with a per-session key, retention is set by the tenant, and every playback is written to the access log.
A standalone deployment with your branding, rota and consultation types typically runs six to ten weeks including security review and clinical sign-off. Integration with an existing EHR is the variable: budget an additional two to six weeks depending on the interfaces available.
The operating organisation. Nexiv Health supplies the platform, the audit trail and the controls; your clinical governance lead defines protocols, scope of practice and escalation policy. We support that with configurable guardrails — specialty routing, prescribing restrictions and mandatory escalation triggers — rather than replacing the judgement behind them.

See Nexiv Health against your workflow

Bring a real pathway — a follow-up clinic, a triage queue, a monitoring cohort — and we will walk it through the platform end to end.

Book a walkthrough Security detail