BridgeLab 1.7.0

BridgeLab 1.7.0

HL7/FHIR editor for healthcare integration professionals.

This release is about reading a message without a reference book open.
Every coded value now says what it means, everywhere you meet it, and the
listener console and send history can be filtered by what the receiver
answered.

Every coded value says what it means

The 394 HL7 value tables (about 5,000 codes) now ship inside BridgeLab,
imported from the same MIT-licensed source as the message catalogue, and
each version's catalogue records which table every coded field and
component draws from.

• Tree: the meaning sits next to the value — PID-8 M — Male,
  MSH-9 ADT^A01 — ADT message, OBX-11 F — Final results — including
  components (MSH-9.2 A01 — ADT/ACK - Admit/visit notification,
  PID-3.5 MR — Medical record number).
• Editor: hovering a field explains its code; auto-completion in any
  coded field offers the whole table, not the three fields it used to
  know.
• Field Inspector: lists the table for the selected field or
  component and now tells an HL7-defined table (ID fields — a value
  outside it is non-standard and gets a warning) from a user-defined one
  (IS fields — suggestions, never a warning). The old "value not in
  table" warning fired on user-defined tables too.

Field metadata for every standard segment, per version

Hover, auto-completion, the Field Inspector, search and the built-in
validation used to read a hand-written list of 15 segments that was the
same for every HL7 version. They now read the full catalogue of the
version the message declares (a full VID such as 2.3^ISO included): RXA-5
has a name, PID-8 in a v2.1 message has a v2.1 definition, and required
fields and lengths are checked for every segment the standard defines.

Expect a few more findings on messages that were "clean" before — an
ORU whose OBX lacks OBX-11, a PV1-16 holding free text. Those were
non-conformant before too, unreported.

ACK filters on the console and the history

The listener console and the History tab gain outcome chips — AA / AE /
AR / No ACK / Errors (Failed) — each with a live count, so "AE 12" out of
300 stands out before anyone scrolls. An MLLP send now records the ACK
code the receiver answered with (MSA-1, whatever field separator the ACK
uses) and shows it as a badge on its row: a send that reached the peer
and got an AE back is "OK" at the transport level and a rejection at
the application level, and the row now tells the two apart.

Also

• What Community gets of plugins is stated the same way everywhere
  (README, landing, manual, docs/PLUGINS.md): every pack kind and every
  check type runs in every edition; the only cap is 3 packs active at
  once (and 10 saved test cases), unlimited in Pro. The manual's plugin
  chapter gained the fhir/ folder it had been missing.
• Roadmap: message interpretation panel, sample message library and
  segment grid added; a "What BridgeLab is not" section says why an
  integration engine, a web platform and DICOM stay out.
• A release ships 12 assets instead of 19 (one en-US MSI, no macOS
  updater tarballs, AppImage without GStreamer: 78 MB).

Upgrading

Nothing to do. The history database gains an ack_code column on first
start; older rows simply have no ACK badge. Going back to 1.6.0 afterwards
is safe — the column is ignored.

Downloads

See the assets below for installers for Windows, macOS (Intel and Apple
Silicon), Linux, and the bridgelab-cli binaries.

---

BridgeLab is built by TECHEMV SRL — www.techemv.it · info@techemv.it