API Connections (FHIR/HL7)

Updated 5 May 2026

Configure hospital-level endpoints for clinical integrations. Keep credentials safe and scoped.

Overview

Hospitals can store secure connection details for external clinical systems, such as FHIR or HL7 endpoints. This keeps integration settings close to the operational context (the hospital and its branches) and avoids mixing data across companies or regions. Branch base URLs help route traffic per site where needed.

Use the Enabled toggle and Last Sync to manage rollout and monitor activity, ensuring integrations are safe, deliberate, and auditable.

How It Works

Step-by-Step Guide

Fields Table

Field Names Explained

Name

Human‑friendly label for the integration entry.

Endpoint URL

Main API server; must be unique per hospital.

Branch Base URL

Optional base path for branch‑specific endpoints.

Auth Token

Secret used to authenticate—store and rotate securely.

Enabled

Switch to activate/deactivate the connection safely.

Last Sync

Timestamp of the most recent successful interaction.

Tips

Common Mistakes

Image

API Connections (FHIR/HL7)