About Diridium

We've been doing healthcare integration for over 25 years.

Paul Coyne, Principal of Diridium Technologies

Paul Coyne, Principal

Twenty-five years in healthcare integration. The work is mostly the same hard problems with different acronyms attached: architect for reuse, and the protocols mostly take care of themselves.

Diridium engagements are principal-led. Paul does the senior architecture and build work directly. When a project calls for specific tooling or domain depth, he brings in vetted senior practitioners on a project basis.

Most engagements start with a specific integration problem and grow from there. Typical clients stay for years, expanding the relationship into adjacent architecture, compliance, and vendor decisions.

Deeply involved with both major healthcare integration engines. Steering committee member and listed maintainer of the Open Integration Engine, with authorship of three plugins featured on the project home page (Cache Manager, Channel & Code Template History, Source Code Search) and co-sponsorship of the TLS plugin with NovaMap Health. Top community contributor on Mirth Connect's forums (second only to a NextGen employee) and active in its GitHub discussions. Listed OIE commercial support vendor.

More public work at github.com/pacmano1 and on the Mirth Connect forums as pacmano.

Compliance & Certifications

  • HIPAA Business Associate compliant
  • Implements HiTrust CSF controls
  • Annual security audits and policy reviews
  • Encrypted data at rest and in transit

Compliance & security

Healthcare data is regulated, and we treat it that way. We're a HIPAA Business Associate and we assume any data we touch contains ePHI.

Our policies are version-controlled, reviewed annually, and retained for six years. The program runs continuously, not just before client audits.

View HIPAA Policies

Open source

Investing in the open-source tooling we and our clients depend on is part of how we operate. The contributions we make to the Open Integration Engine and Mirth Connect come from the same logic: the better the underlying tools, the better every engagement built on them.

Open standards and open-source tooling are good for healthcare interoperability. That's why we work with OIE, BridgeLink, and the rest of the open-source ecosystem alongside commercial platforms like Mirth Connect.

Want to talk?

Send us a paragraph about what you're trying to do. We respond within 48 hours.

Get in touch