Blog
News, tutorials, and insights.
On healthcare integration, HL7, FHIR, and everything Brio-IO does better.
“Will my Mirth scripts run?” — an honest answer, at last
Every Mirth replacement promises the old scripts keep working. Brio-IO waited to make that promise until it was true: real Rhino, real E4X, positional paths just like Mirth (msg['PID']['PID.5']['PID.5.1']), createSegment across all engines. And we tell you the limits too.
Try Brio-IO live — with your own test messages
The public Brio-IO demo is a real, running system: preconfigured channels, synthetic HL7 messages flowing continuously, transformers you edit live — and you push your own test message through and download the result. A walkthrough.
Transformers in Brio-IO: three engines, one pipeline — and finally readable HL7 paths
How Brio-IO scripts transformers: Groovy, GraalJS and Rhino side by side, why the parsed `msg` gives readable property access (msg.PID.PID_5.PID_5_1), and how to migrate existing scripts step by step.
Why we replaced Mirth Connect
The story behind Brio-IO and what drove us to build a new healthcare integration server.
Getting Started: Your First HL7 Channel in 5 Minutes
From installation to your first received lab result — step by step.