// the find
nextgenhealthcare/connect
The swiss army knife of healthcare integration.
Mirth Connect is a battle-tested open-source healthcare integration engine for routing and transforming HL7, XML, and other clinical messages between disparate systems. It's the de facto standard for hospital IT shops that need to wire together EHRs, labs, and billing systems without paying six figures for an enterprise ESB. If you work in health IT, you've almost certainly touched it.
The channel-based architecture (source → transformer → destinations) is genuinely well-designed: each channel is independently deployable, testable, and has its own message store, so a broken lab interface doesn't take down your ADT feed. Built-in support for HL7 v2/v3, FHIR, DICOM, and X12 means you're not reinventing parsers. The Swing admin UI is old but functional — the message browser with inline diff and reprocessing is legitimately useful for debugging production issues. Plugin architecture is solid enough that the community has built connectors for SFTP, S3, Kafka, and others that work reliably.
The codebase is deeply Java Swing — the admin client is a thick desktop app that requires JNLP/Java Web Start or the Administrator Launcher, which is increasingly painful in 2024 when browsers dropped JNLP support. Channel configuration is stored as XML blobs in a relational database, which makes version control and code review nearly impossible; diffing two channel exports is a pain. The last commit was September 2024 and the project has been in slow-burn maintenance mode since NextGen acquired Mirth — feature velocity is low and the commercial enterprise edition has diverged significantly. Transformers use JavaScript (Rhino engine) for scripting, which means you're writing ES5 with no type safety and debugging via log statements in a GUI panel.