The healthcaredata gateway.
Move imaging and clinical data straight between organizations, built on the open-source Open Integration Engine.
- Transfer any format, HL7, FHIR, DICOM, X12, between systems and organizations.
- Direct image & data exchange with no per-study transfer fees.
- Manage and monitor everything from a secure browser console, full audit trail.
What OpenShare is
Everything you need to move healthcare data.
One on-premise gateway built on the trusted open-source Mirth Connect fork. Click through what it does.
HL7, FHIR, DICOM, X12, all of it.
Whatever your systems speak flows into one gateway: clinical messages and medical images, any format, any system.
They bill the study. We bill the bytes.
PowerShare, Ambra, and lifeIMAGE price per study moved (per published agreements and case studies). OpenShare meters bandwidth: $500 per server, per month with 2.5 GB included, then $0.25 per GB. A routine CT is about eight cents. Send 10,000 studies directly, end-to-end encrypted, no cloud middleman, and pay for the gigabytes.
The OpenShare network
Hubs pay. Spokes connect free.
- 1A vendor, integrator, or receiving health system becomes the network’s paid hub: one flat membership, $500 per server, per month.
- 2Their partners, hospitals, labs, imaging centers, clinics, payers, sign up free and get Console + Monitoring + the OIE server at no cost.
- 3Everyone transfers DICOM, HL7 & FHIR directly, organization-to-organization, no per-study fees, no cloud middleman.
Free members transfer with any paid member, every connection just needs one paid hub.
See membership pricing →The OpenShare platform
One install. Everything included.
OpenShare is one product: a single install on your own server, managed from your browser. The Console, Gateway, Monitoring, Drivers, and DICOM viewer are free forever, no credit card, no trial.
The exchange network connects you to other organizations: hubs pay to reach out and connect, spokes browse, connect and receive free. See how membership works →
Built on the engine you
already trust.
OpenShare runs on Mirth Connect and the community Open Integration Engine(OIE) fork, binary-compatible, actively maintained, and free. When NextGen discontinued open-source Mirth Connect in March 2025, OIE carried the open-source path forward. Keep your channels; add the gateway. No migration required.
How it works
- 01
Drop the plugin onto your engine.
Install the OpenShare Gateway plugin on your existing Mirth Connect or OIE server, or download a pre-packaged OIE with it already inside. Your channels, transformers, extensions, and API stay exactly as they are. No migration, no re-platform, fork-agnostic.
- 02
Run it from the browser, from anywhere.
Open OpenShare Console and administer your engine in any browser, channel editing, message browsing, the dashboard, DICOM viewing, no Java client, no Web Start, no VPN, no open ports. Manage one server or all your client servers from a single tab, with real monitoring and error alerts built in.
- 03
Send data straight to your partners.
When you need to move HL7, FHIR, or DICOM to another organization, route it organization-to-organization, directly engine-to-engine, end-to-end encrypted, on a flat per-server membership billed by bandwidth, never per interface or per message. No central cloud, and OpenShare’s relay never sees the data.
- 01
Stand up the gateway beside your PACS.
OpenShare installs as an on-premise DICOM/DICOMweb gateway next to your PACS, it speaks C-STORE, C-FIND/C-GET, and STOW-RS forwarding, and autoroutes by tag like any router you already run. No archive migration, no rip-and-replace; your PACS/VNA stays the system of record.
- 02
Connect with your exchange partner.
Find them in the Contact Directory and send a sharing agreement naming both parties and the feeds that route. When they accept, the gateway opens a direct, end-to-end-encrypted link between your site and your partner’s, the referring hospital, your other locations, the trauma center, your teleradiology group. Studies travel PACS-to-PACS, with no copy on any vendor cloud.
- 03
Studies land in your PACS, the meter reads gigabytes.
Inbound studies arrive in your PACS ready for import, replacing the CD-burn-and-import workflow. Billing is by bandwidth, not by study: $500 per server, per month includes 2.5 GB of transfer, then a published $0.25 per GB. Every agreement and Q/R action is logged for audit; the per-study meter is gone for good.
Same gateway, same flat per-server price, whichever data you’re moving.
OpenShare never sees your PHI.
End-to-end encrypted, on-premise, organization-to-organization. Our relay brokers the connection but can’t decrypt it, and you can switch it off entirely.
The relay can’t read your data
Every connection is end-to-end encrypted (WebRTC DTLS), outbound-only, over a signaling-only relay. Two switches make it airtight: disable the relay for a direct-only path, or run a PHI-free dashboard, metadata only, so zero PHI ever leaves your server.
E2E · outbound-only · disable-relay · PHI-free modeSee our security architecture →Healthcare compliance, built in
HIPAA-ready architecture: end-to-end encryption, zero OpenShare access to PHI, and comprehensive audit logging for every connection. Built around the FDA Medical Device Data System classification.
HIPAA · E2E · audit trail · FDA MDDSView compliance details →Works with any server running the Gateway Plugin.
Mirth Connect
Open Integration EngineCompatible with Mirth Connect, OIE, BridgeLink, and any compatible fork. Install the Gateway Plugin on your existing healthcare integration engine, no migration required.
Ready to modernize your
integration workflow?
Free to run on your own servers. No credit card required. During open beta, network memberships aren’t on sale yet.








