Try Brio-IO live

Most product demos are a screencast or a set of slides. The Brio-IO one is a real, running system — a full setup of the Brio-IO Communication Server in the browser, with preconfigured channels, flowing traffic, and a message browser where you open every message stage by stage. No installer, no slides: you click through a real Brio-IO.

This article shows what to expect — and what the strongest moment is: push your own HL7 test message through a channel and download the result.

The live demo is here. Access is personalized — more on that at the end.

What to expect in the demo

Preconfigured example channels. After logging in, ready-made channels are waiting that show typical healthcare integrations — channel-to-channel routing, a transformer in the property idiom (GraalJS) and one in the classic E4X style (Rhino). Nothing to set up, explorable right away.

Messages that keep flowing. The built-in Message Generator is a real product feature, not a demo trick: after each reset it keeps feeding synthetic HL7v2 messages (ADT^A01) through the channels — across almost the whole two-hour cycle, not just in the first few seconds. Arrive ten minutes after a reset and you’ll see life in the message browser. And you don’t have to wait: in every connector’s test mode you generate fresh traffic yourself at the push of a button.

Edit transformers live. Open a channel’s transformer in the channel editor — it reaches straight into the parsed message via property access, e.g. msg.MSH.MSH_6.HD_1. Change a line, save and redeploy the channel — and the next messages carry your change. You see the difference right in the message browser: the raw stage (RAW) unchanged, the TRANSFORMED stage with your new value. Why the field paths look the way they do is explained in our article Transformers in Brio-IO: three engines, one pipeline.

The heart of it: push your own message through

Preconfigured channels are nice — but the question that really matters is “does this work with my data?”. That’s exactly what “Load from file” is for. With no external file-storage container, right in the browser:

1. Log in to the demo and open a connector’s test mode. Click “Load from file” and pick your file — allowed are .hl7, .txt, .xml and .json up to 1 MB. The file is read locally in the browser and lands in the message field.
2. Via Generate you send it through the connector — including the configured transformers.
3. The result appears in the message browser (status SENT, with a TRANSFORMED stage). Compare before/after and download each stage via the Download button.

That turns the demo into your own little test run: feed in a real message from your world, send it through the pipeline, look at the result and take it with you.

Shadowing preview: watch real traffic, without side effects

One of the channels carries a shadow branch. It observes the real traffic of the running channel and runs the pipeline on a live copy — without calling any real destination. For that, visible SHADOW_SENT entries appear in the message browser and grow with the traffic.

This is the precursor to what we’re building: test a change to a channel safely against real traffic before it goes live. The comparison view is coming — today you first see that the shadow branch runs along and captures traffic.

Transparency: a playground, built that way on purpose

• Reset every 2 hours. The instance is reset to a fresh seed state every two hours. Your changes are meant for trying out, not for keeping.
• Synthetic test data only. The built-in traffic is synthetic. What you push through yourself must be test data only — please no real patient, personal or clinical data.
• Deleted after 2 hours at the latest. What you enter or load never leaves the demo and is automatically deleted at the next reset — after at most two hours.

How to get in

Access is personalized: we set up a login for you personally and send the credentials by e-mail. No self-service form, no credentials on this page.

• Already have credentials? Then go straight in via “Open demo” on the demo page.
• Not yet? Ask us for access — tell us briefly which interfaces you want to integrate, and we’ll set you up.

Brio-IO convinces fastest when you try it with your own messages. The demo is ready — push your first test message through.