Vendor Variations
Each EMR vendor implements FHIR differently. Epic, Cerner, and others have unique extensions, profiles, and authentication flows.
Healthcare API Standard
FHIR Connector
Connect any data source to FHIR APIs. Transform legacy systems, databases, and proprietary formats into FHIR-compliant resources - or route existing FHIR traffic with powerful middleware.
Available Now
The Challenge
FHIR adoption is fragmented
Legacy Integration
Many systems still use HL7 v2. Bridging between modern FHIR and legacy messaging requires complex transformation logic.
Security Complexity
SMART on FHIR, OAuth2 scopes, and patient consent management add layers of authentication complexity.
The Solution
Transform anything to FHIR
Harmony provides HTTP endpoints with powerful JSON transformation. Connect any data source and transform it into FHIR-compliant resources - no custom code required.
Any Source to FHIR
Transform data from databases, APIs, files, or legacy systems into FHIR-compliant JSON resources.
FHIR to Any Target
Convert FHIR resources into formats your downstream systems understand - CSV, HL7 v2, proprietary APIs.
Proxy & Route
Route FHIR API requests to backend EMR systems with path-based routing and load balancing.
Authentication Passthrough
Handle OAuth2, API keys, or basic auth - authenticate once and proxy to multiple backends.
# FHIR API gateway
[pipelines.fhir]
description = "FHIR API with healthcare-grade security"
networks = ["http_net"]
endpoints = ["fhir_endpoint"]
middleware = ["basic_auth", "healthcare_policies"]
backends = ["fhir_backend"]
# FHIR endpoint
[endpoints.fhir_endpoint]
service = "fhir"
[endpoints.fhir_endpoint.options]
path_prefix = "/fhir"
# Backend
[backends.fhir_backend]
service = "fhir"
target_ref = "emr_server"
Use Cases
Connect anything to FHIR
Transform, proxy, and route data to and from FHIR APIs.
Legacy to FHIR
Transform proprietary API responses into FHIR Patient, Observation, or any resource type
CSV/JSON/XML → FHIR R4FHIR Gateway
Proxy requests to EMR FHIR endpoints with authentication, rate limiting, and logging
Client → Harmony → Epic/CernerMulti-EMR Aggregation
Query multiple EMR systems and normalise responses into a unified FHIR format
Epic + Cerner → Unified APIFHIR to Legacy
Accept FHIR resources and transform them for legacy systems that don't speak FHIR
FHIR R4 → HL7 v2/CSVWebhook to FHIR
Receive webhooks from any system and transform payloads into FHIR resources
Webhook → FHIR BundleDatabase to FHIR
Expose database queries as FHIR-compliant API endpoints via transformation
SQL Result → FHIR JSONTransformation
Transform to any FHIR resource
Use JSON transformation templates to convert your data into FHIR-compliant resources.
Patient
Map demographics from any source to FHIR Patient resources
Observation
Transform lab results, vitals, or measurements into Observations
Encounter
Convert visit records or appointments to Encounter resources
DiagnosticReport
Transform report data into structured DiagnosticReports
ImagingStudy
Create ImagingStudy references from DICOM metadata
Bundle
Aggregate multiple resources into transaction Bundles
Any Resource
Transform to any FHIR resource type using JSON templates
Custom Profiles
Output resources conforming to regional implementation guides
Capabilities
What Harmony provides
Any Source to FHIR
Transform data from databases, APIs, files, or legacy systems into FHIR-compliant JSON resources.
FHIR to Any Target
Convert FHIR resources into formats your downstream systems understand - CSV, HL7 v2, proprietary APIs.
Proxy & Route
Route FHIR API requests to backend EMR systems with path-based routing and load balancing.
Authentication Passthrough
Handle OAuth2, API keys, or basic auth - authenticate once and proxy to multiple backends.
Request Transformation
Modify FHIR requests on-the-fly - add headers, rewrite paths, or transform payloads before forwarding.
Response Normalisation
Normalise responses from different EMR vendors into a consistent FHIR format for your applications.
Workload Templates
FHIR Workload Templates
Pre-configured templates for healthcare API integration
AU eRequesting: FHIR to HTTP
Accept AU eRequesting FHIR bundles and convert to HTTP API calls
FHIR to REST
eRequesting Backend
HealthcareFHIR
Learn more →
AU eRequesting: HTTP to FHIR
Convert HTTP service requests to AU eRequesting FHIR bundles
eRequesting Integration
FHIR Bundle Generation
HealthcareFHIR
Learn more →
Data Mesh
Secure inter-proxy communication network
Multi-Org Data Exchange
Mesh Networking
HealthcareFHIR
Learn more →
FHIR Integration
Connect to FHIR-compliant health systems
FHIR Server Integration
Healthcare Interoperability
HealthcareFHIR
Learn more →
FHIR to DICOM Integration
Unified clinical and imaging data pipeline
Radiology Workflow
Comprehensive Records
HealthcareFHIR
Learn more →
FHIR to Legacy HTTP
Accept FHIR resources and transform for legacy HTTP systems
Legacy System Integration
FHIR to Flat JSON
HealthcareFHIR
Learn more →
Get Started
Connect your healthcare systems
Deploy FHIR integrations with powerful data transformation and routing.