Skip to content
Synura Docs

Synura Documentation

Synura is the exchange layer for healthcare data. You bring your network. You author your rules. We run the platform.
Get Started Downloads

What Synura is

Section titled “What Synura is”

Synura moves HL7 between healthcare systems and translates it where you need it translated. Customer-authored rules, deterministic execution, full audit on every message. UK data residency, AES-256-GCM at rest, TLS 1.2+ in transit. No machine learning, no inference, no third-party model providers anywhere in the data path.

The platform is built in three tiers. Each tier solves a different problem and each tier ships complete.

  • Transport. Secure HL7 movement. MLLP/TLS, HTTPS, SFTP. Routing by MSH-3/MSH-4. ACK/NACK on every message. Audit log on every delivery.
  • Translate. HL7 v2 to FHIR R4. Customer-authored mapping profiles per connection. Z-segment passthrough. STU3 to UK Core R4 (CareConnect) where you need it.
  • Orchestrate. Multi-party flows. Bidirectional org_links. Mailbox queue with two-phase delivery. HIE order queue. Encryption at rest. Custom SLA.

These docs cover every tier. Pick a starting point below based on what you already have running.

How you connect

Section titled “How you connect”

Three ways into Synura. Each one lands you on a different Quick Start.

Synura Connect

Section titled “Synura Connect”

If you do not have HL7 plumbing in place yet, install the Synura Connect agent on a host inside your network. Connect runs as a service, opens an outbound TLS tunnel to Synura, and exposes a local MLLP listener for your sending systems. No inbound firewall changes, no VPN.

Quick Start with Synura Connect →

Existing Mirth

Section titled “Existing Mirth”

If Mirth Connect is already in production at your site, the Synura Mirth Connector turns your existing instance into a Synura ingress. The installer drops in stunnel, imports the certificate trust chain, deploys the Synura mailbox poller channel, and leaves your existing Mirth channels alone.

Quick Start for existing Mirth →

Native HTTPS or MLLP

Section titled “Native HTTPS or MLLP”

If you run your own integration engine and you want to send directly, point it at your Synura endpoint. HTTPS POST or MLLP/TLS, your choice. You configure the certificate, MSH-3 and MSH-4 routing, and delivery format.

Quick Start for native integration →

Reference

Section titled “Reference”

The per-protocol guides below sit under the new narrative. They are the deep dives.

  • Connection Guide — TLS paths, certificate trust, commercial-plugin and enterprise-proxy options
  • Connecting — endpoint setup, sending-facility codes, MSH routing
  • HTTPS API — direct HTTPS ingress, request and response shapes
  • Native MLLP/TLS — direct MLLP/TLS ingress for integration engines
  • FHIR Translation — HL7 v2 to FHIR R4, mapping profiles, Z-segments
  • Manual Setup — configure each component yourself, no installer
  • TLS Troubleshooting — certificate, handshake and trust-chain issues
  • Code Samples — example payloads and client snippets
  • Downloads — installers and agents