Your gateway. Your images.Your terms.
Incumbent networks want you to install their gateway, ship your studies to their cloud, and typically pay per image. OpenShare turns the integration server you already run into the gateway, and studies travel directly to the organization you chose, end-to-end encrypted, with no per-study fee.
Your gateway dials out.
Nothing dials in.
The gateway opens a single outbound WebRTC (DTLS) connection. Studies then travel directly between your gateway and your partner’s. There is no VPN to build, no inbound firewall rule to open, no port forwarding and no DMZ.
OpenShare brokers the introduction and carries signaling and policy, never the study. Where a strict network blocks a direct path, traffic falls back through a TURN relay, which forwards encrypted bytes it cannot read. OpenShare never has access to unencrypted PHI.
- Outbound-only connection, zero inbound ports
- Works behind strict NAT and hospital firewalls
- End-to-end encrypted with WebRTC DTLS, relay fallback included
- Studies reach the organization you chose, with no cloud copy
The same plugin turns the engine you already run into a gateway, and gives you browser-based administration, monitoring, and access control down to the channel. It installs into your existing server, and it is free to run.
See the open stack →Vendors pay. You connect free.
Have a third-party vendor that needs your DICOM or EHR data? Point them at OpenShare. Running the Gateway is free for you. The vendor pays to connect and does the integration work, so onboarding a partner is a feed on your side, not a project.
- Stand up a DICOM feed, or query/retrieve against your PACS.
- No new licensing, no per-image fees, no contract to negotiate.
- Holds the paid membership that the connection runs on.
- Proposes and builds the channel in OpenShare.
- Owns the sharing agreement and integration work.
Reach your own servers,
and the organizations you choose.
It’s all one OpenShare plugin, and its end-to-end-encrypted connection works two ways. It reaches the Mirth/OIE servers you run, and it reaches other organizations, so you can send and receive DICOM, HL7, FHIR and more with no intermediary holding your data.
Same plugin, same server, same encrypted link. Exchange is the directory and the agreements that decide who you connect with.
See how Exchange works →Your own servers: browser-based administration, monitoring, and access control. Free to run.
Exchange: direct exchange between organizations. DICOM, HL7, FHIR, X12. No intermediary, no per-study fees.
Frequently asked questions.
Do we have to install another appliance?
No. The plugin turns the Mirth Connect or OIE server you already run into the gateway. If you do not run one yet, you can stand one up and install the plugin into it, and it is free to run.
Do our studies pass through OpenShare?
Studies travel directly between your gateway and your partner’s, end-to-end encrypted with WebRTC DTLS. OpenShare brokers the introduction and is not in the conversation. Where a strict network forces traffic through a relay, the relay forwards encrypted bytes it cannot read. OpenShare never has access to unencrypted PHI.
Who can pull images from us?
Only an organization you have an agreement with, on a channel you granted them, and only after you approved it. Grants are scoped to a single partner and a single channel, and revoking one is immediate: the connection it depended on is torn down with it.
Is there a per-study or per-image fee?
No. Incumbent image exchange networks typically price per image or per transaction, per published agreements and case studies. OpenShare does not. See pricing for what a membership costs.
How does this compare to PowerShare or Ambra?
They are centralized: you install their gateway, your studies are uploaded to their cloud, and you typically pay per image (est.). OpenShare is direct: studies travel to the organization you chose, and no copy is made in a vendor cloud. See the side-by-side comparison.
