From Closed to Open: What the Future Holds for Healthcare Data Exchange This is a recording of the call that Paul and Jon from OIE had with Zen on 2025-04-16

OIE needs community help with scoping an issue. https://github.com/OpenIntegrationEngine/engine/issues/43 is trying to scope a feature for automated testing in Mirth. Please reply in the issue in github with any existing testing tools or solutions you are familiar with. OIE is making NO commitment to implementing this feature, but it was requested. Research help is needed to determine what is even possible and remember what exists in the market already

🚀 Technical Preview 1 of Open Integration Engine is coming soon! This first milestone introduces the foundation of the project, with a core focus on de-branding and white-label readiness. It's intended for early public evaluation and community feedback as we progress toward an official release. 🔧 Future technical previews will follow to harden the platform, address known vulnerabilities, and introduce additional features. 🔗 Track the milestone: [Technical Preview 1](https://github.com/OpenIntegrationEngine/engine/milestone/1?closed=1)

Hello community - As you wander around social media, keep an eye out for questions from other Mirth users and let them know about OIE! https://www.reddit.com/r/mirth/, LinkedIn, etc.

Already posted on General. I forgot about this channel: Hi all! https://github.com/OpenIntegrationEngine/engine/releases/tag/v4.5.2-tp.1. Thanks to all of you here that help make this project a success.

@kayyagari has released Ballista 0.6.0 https://github.com/kayyagari/ballista/releases/tag/0.6.0 Ballista is not an OIE project but it is one of the #1359637915163955396 that helps run OIE and Mirth (probably works with the other forks too!). TY Kiran!

HI all, we have 4.5.2 released for production use - thanks to all who help make this project a success! For downloads, please see https://github.com/OpenIntegrationEngine/engine/releases/tag/v4.5.2

OIE Vendor Listing is now live. OIE has created a policy and a process to get listed as a vendor who supports OIE. We wanted the vendors that support OIE to have a listing so customers could find them. The policy is at - https://github.com/OpenIntegrationEngine/governance/blob/main/vendors.md The process is at - https://github.com/OpenIntegrationEngine/vendors (Just open an issue and fill in the "add vendor" template) We were inspired by https://github.com/rogin/mirth-consulting from @rich_o. We were supported and encouraged by @pbrichardson (NovaMap) who has an excellent sense of what the buisness users need from OIE

Please take a moment to skim our https://openintegrationengine.org/commercial-support-vendors/ listing. We didn't expect to have that many entires so soon.

Maybe you didn't expect to have that many 😉

The Steering Committee has consensus on the content of https://github.com/OpenIntegrationEngine/engine/milestone/2 . If other significant issues or merged PRs come up, we'll put those in the release. If a PR is submitted, tested, reviewed, etc. we'll take it and ship it. Our main focus is patching and updates. This includes support for Java 17, a large merge from BridgeLink, and a handful of individual library updates. These updates do overlap and we're working out wether we just do them all at once or go individually. Next we want to be merging the PRs from Richard . Those sat in the NextGen repo for years and we want to get them in. Some of these overlap with the library updates. There are also some housekeeping issues. Leftover branding tasks and some small tasks like removing unused code. We chose to move the Gradle PR to "Next Release + 1" . Mitch and Nico( Caigh) have all been making excellent contributions. The Steering Committe wants these changes, but to make them we have to consider a few factors: There is overlap with the other library updates - Do we jump to Gradle or take the other updates first? @User is trying to make OIE merge-compatible with BridgeLink - We expect differences between the two projects but they are both open-source. We want to be able to re-use work as much as practical. Once OIE moves to Gradle this becomes harder. Delaying just one release gives us time to come up with a strategy to either remain merge-compatible or make the choice to stop being merge-compatible. Reviews reviews reviews. We request community feedback on Gradle related issues and PRs https://github.com/search?q=repo%3AOpenIntegrationEngine%2Fengine%20gradle&type=code This is a big change. We want to do this well. We want to push good releases. If you have ideas or questions please ask in #943670760461987862

This is cool... i dunno if the SagaHealthIT guys are here.. But it looks like they just dropped a new release of MirthSync last week and are officially supporting OIE (per their readme)! https://github.com/SagaHealthcareIT/mirthsync

The following was posted in the Innovar BridgeLink Slack. It has already been independently patched in [PR 195](https://github.com/OpenIntegrationEngine/engine/pull/195), and the fix will be included in the next OIE release. > CRITICAL BUG: CONFIGURATION DATA LOSS RISK > > Issue Summary: > A critical defect has been identified affecting both legacy Mirth Connect (through at least version 4.5.2) and BridgeLink. > > Impact: > Systems configured with a read/write database split — where the read-only connection points to a replica with any replication lag — are at risk of erasing all configuration tables and seems to be only cloud deployments. > > Details: > The issue occurs when the replica serves stale configuration data that overwrites the active configuration in the write database. This presents as configuration settings being “reset” or “wiped” to defaults. The behavior is reproducible in the Data Pruner and affects all components using the DefaultConfigurationController class. > > Severity: CRITICAL — POTENTIAL DATA LOSS > > Action Required Immediately: > Disable any read-only replica connections configured for read/write splitting. > Verify integrity of your configuration tables in the primary database. > > Innovar Engineering is actively developing and testing a hotfix to prevent this condition and will issue guidance shortly. > > — Innovar Team

The code will be public / MPL 2.0

I am pleased to announce that we are starting the new year with a new maintainer! @Nico Piel has volunteered to become a maintainer. He is leading the charge with modernizing OIE to use Gradle as our build tool. He has actively participated in several PRs and discussions. OIE is thrilled to have Nico. Maintainers help handle the code behind OIE. They're the brains behind the software while the Steering Committee handles the business side and organizational aspects. You can learn more about the roles and how to nominate people at https://github.com/OpenIntegrationEngine/governance/blob/main/governance.md#42-maintainers

Repo published also. Many thanks to @pbrichardson (NovaMap) (NovaMap) and the NovaMap Health for sponsoring and developing this indispensable plugin.

https://www.linkedin.com/feed/update/urn:li:activity:7458505266607783936/ Our 4.6.0 Release Candidate is now available for download

https://www.linkedin.com/posts/open-integration-engine_about-us-global-open-source-leadership-activity-7468612262027722752-kyvH Our application to the Eclipse Foundation has been formally submitted 🎉

https://github.com/OpenIntegrationEngine/engine/releases/tag/v4.6.0 Just released.

https://www.linkedin.com/posts/open-integration-engine-460-is-now-generally-share-7481072020060045312-pB7n/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAP9BwABS4oO6HqjmRS0sGWDuwpsFLuf1tM > Open Integration Engine 4.6.0 is now generally available. > > This is the first GA release planned, stabilized, and shipped entirely under OIE community governance, and it closes out the release candidate window on schedule. > > Highlights: > > - 24 known CVEs remediated through dependency upgrades, including 1 Critical and 10 High > - Java 17 is now the minimum supported JVM > - Faster message search and faster extension load at startup > - JavaScript pretty-printer and Toggle Comment added to the editor > serverName variable available in alert templates for multi-instance deployments > - Fixes for a macOS client crash, a potential plugin properties data loss scenario, and a 4.5.2 migration failure > > A few breaking changes to review before you upgrade: the Java 17 minimum, removal of the Xerces and xml-apis dependencies, and case-insensitive username login. > > Thank you to the seven new contributors who made their first commit to OIE in this release, and to everyone who tested the RC and filed issues. Community maintained is not a marketing phrase. It is how this release shipped. > > Release notes and installers: https://lnkd.in/gK7ztk8i

Bug fixes on Launcher, see https://github.com/pacmano1/launcher/releases. Among other things the jar ordering is preserved which was a legacy bug in Ballista. Thanks to @joshm for catching mirth 4.7.1 did not work which exposed the ordering issue. Also, since Launcher asks what engine flavor is being used to optimize file cache, it now auto-detects a potential mix up (e.g. you created a entry for an OIE engine, but specified it was "Mirth" on the conneciton profile).

Status update: Open Integration Engine has been accepted as an Eclipse Foundation project.

Fresh release of launcher today, https://github.com/diridium-com/launcher/releases, fixed a few bugs related to the cache and enabled custom icons for each server.. Also suggesting folks consider the web admin at the repo/wiki/release note. I did consider and then shelved changing the icon on the dock / windows task bar for a running admin tool session, but that required prepending a jar to the launch and is probably to risky.

Eclipse Open Integration Engine 4.7.0 is out. This is a big one. It has 101 commits from 13 contributors, fixes for 48 CVEs, a full move of the build from Ant to Gradle, and new features for both administrators and API users. It's our largest release since the project started, and it touches almost every part of the engine. What's new: - Fixes for 3 CVEs in shared engine code (SQL injection in the Database Connector API and two XML external entity issues), plus dependency upgrades that address 45 more CVEs in bundled libraries - HTTP Sender can bind outgoing connections to a specific local address, and HTTP Listener has a configurable maximum request header size - The message browser keeps your last ten search filters per channel, in memory only, so search terms don't end up on disk - A new API endpoint returns every message ID from a batch submission - JDBC drivers loaded through custom library resources work again on modern Java - Installers that bundle Java now ship Eclipse Temurin 21 - The build moved from Ant to Gradle, and there's an in-repo Docker build with smoke tests across five databases A few things to check before you upgrade: - New installs no longer start with admin/admin. Set server.initialadminpassword up front, or get the generated password from the first startup log. - The bundled SQL Server driver now encrypts by default. If your SQL Server uses a self-signed certificate, the engine won't start until you trust that certificate or add trustServerCertificate=true to the connection URL. - XML with DOCTYPE declarations is now rejected in XSLT steps, XML batch splitting and strict HL7 XML parsing. The release notes have the full CVE list and all the upgrade details. Thanks to the 13 people who contributed to this release, including six first-time contributors. Release: https://github.com/OpenIntegrationEngine/engine/releases/tag/v4.7.0