Follow our journey from Harmony beta to the full Runbeam platform. Get integration insights and product updates.
Runbeam exposes a native Model Context Protocol (MCP) server with 52 tools across 11 resource categories, enabling AI coding agents like Claude Code, Cursor, and OpenAI Codex to manage Harmony gateway configurations programmatically.
Discover how HTTP/3 (QUIC) enables secure, performant connections from hospital networks to cloud AI platforms without VPNs or inbound firewall rules—while maintaining HIPAA compliance and audit-ready governance.
Learn how to bridge AI agents using MCP (Model Context Protocol) to your existing HTTP APIs without writing custom integration code—enabling Claude, GPT, and other AI systems to call any backend service.
IHE's new MADO supplement claims to fill a gap in imaging interoperability with manifest-based access. But DICOMweb already retrieves images. What problem is MADO really solving, and does the industry need it?
Learn how Runbeam bridges the gap between specialized data sources and AI systems, enabling intelligent workflows for medical imaging, healthcare data, and beyond—without rebuilding your infrastructure.
Open source healthcare teams don't have time for rewrites. Here's how to use Harmony as an integration boundary to translate protocols, transform payloads, and enforce policy—so you can ship interop features without touching your core application.
An experimental proof-of-concept demonstrating how Harmony can act as a UCP-compliant gateway, translating between AI shopping agents and legacy commerce backends using the new Universal Commerce Protocol.
Harmony 0.12 introduces a data mesh architecture for secure gateway-to-gateway communication with JWT authentication, HTTP/3 support with automatic protocol selection, provider-based configuration sync, and advanced DICOM capabilities including C-STORE support and DICOM-to-DICOMweb bridging.
Meet Santa's Workshop—a whimsical template demonstrating Harmony's core capabilities through gift logistics. See how authentication, data transformation, and multi-destination routing work in a delightfully unconventional workflow.
Two new AU eRequesting example workloads are now available in the Workloads catalogue—one that turns simple HTTP requests into AU eRequesting FHIR Bundles, and one that accepts AU eRequesting Bundles and drives downstream HTTP APIs.
A look at common Harmony configuration patterns through our new visualization system.
This release adds debug logging for JOLT transforms, environment variable validation, sensitive field patterns for log redaction, and fixes critical issues with array transformations and query parameter handling.
Harmony 0.9 introduces powerful debugging capabilities, improved DICOM structure manipulation, extended DIMSE support, and flexible environment-based configuration—enabling deeper visibility and control over healthcare data integration pipelines.
Comparing Boomi's iPaaS and low-code integration approach with Runbeam's healthcare-focused data mesh and protocol-native interoperability. Learn when a generic iPaaS is the right fit versus when you need purpose-built healthcare connectivity across FHIR, HL7, DICOM, and distributed networks.
Comparing MuleSoft's enterprise integration platform with Runbeam's healthcare-focused data mesh approach. Discover when heavyweight ESB architecture makes sense versus when purpose-built healthcare interoperability with FHIR and DICOM excels in secure, distributed environments.
Runbeam is now available in beta—a cloud control plane for managing distributed Harmony gateway instances with centralised configuration, monitoring, and policy management across your healthcare organisation.
Harmony 0.6 introduces flexible policy-based middleware for fine-grained request control, enhanced content type handling, and critical reliability fixes that build on our production-ready foundation.
Announcing Harmony 0.5.1 - a major milestone featuring hot configuration reload, Runbeam Cloud integration, full DICOM SCP support, and enhanced security for healthcare interoperability platforms
Comparing Kong's enterprise API platform with Runbeam's healthcare-focused integration approach. Explore when generic API management works versus when purpose-built healthcare interoperability excels in FHIR, HL7, DICOM, and secure data mesh architectures.
A practical guide to choosing between Runbeam and Mirth Connect for your healthcare interoperability needs. Explore use cases, deployment models, and when each platform excels in EMR-PACS integration, FHIR-HL7 bridging, and modern data mesh architectures.
Discover how Runbeam transforms healthcare interoperability with its modern data mesh orchestration platform, powered by the open-source Harmony proxy. From EMR-PACS integration to secure data exchange between organisations.
