BridgeLab 1.6.0

BridgeLab 1.6.0

HL7/FHIR editor for healthcare integration professionals.

This release is about trusting what the validator says. The FHIR R4 core
now ships inside the binary, a Bundle is validated all the way down instead
of at its top level, and bridgelab-cli runs the app's own validators.

The FHIR R4 core is built in

Profile conformance used to need hl7.fhir.r4.core installed by hand
before it did anything. The distilled index (about 200 KB) now ships inside
BridgeLab, so cardinality, element types, choice elements and unknown
elements are checked against the base R4 definitions on a fresh install,
offline, in every edition — nothing to download.

The package manager lists it as Built in. A package you install yourself
supersedes it by version; implementation guides install on top as before
(installing packages stays Pro).

A Bundle is validated all the way down

Opening a message Bundle whose Observation had no status used to show two
notes about the Bundle itself and ✗ 0 ⚠ 0 — the opposite of what was
true. Now:

• every entry and every contained resource is checked as the
  resource it is, reported under its path (entry[3].resource.status),
  and against its own meta.profile;
• the Bundle's own rules are checked — every entry carries a
  fullUrl (POST excepted); a persistent fullUrl agrees with the
  resource's type and id, while a urn:uuid: one is the identity and
  needs no id, so a message Bundle written the NHS/IHE way stays clean;
  fullUrls are unique; and every Reference resolves — to an entry's
  fullUrl, a Type/id or a #contained — with a warning where the
  Bundle carries a related set and a note in a searchset;
• primitive values are checked for their lexical form — date,
  dateTime (a time needs a time zone), instant, time, code, id,
  oid, uuid, URIs without whitespace — and an endpoint written
  without a scheme (https//host) is a warning, because nothing can
  connect to it as written;
• resolve() follows urn:uuid: references, which in a message
  Bundle is every reference there is.

Two profile-engine fixes ride along: a profile declared but not installed
no longer hides every other finding, and a version pin in meta.profile
(…|1.2.0) resolves to exactly that version — or says which versions are
installed — instead of silently substituting another.

bridgelab-cli is now the app's own validators

The old CLI was a separate, minimal reimplementation. It is now a thin
front-end over the library the desktop app is built on: the same
version-aware HL7 v2 validation, the same FHIR checks with the built-in
core and installed packages, the same plugin packs and PHI anonymiser.
validate and batch detect HL7 v2 or FHIR per file; --fhir-packages DIR
points at a provisioned package folder for CI and air-gapped sites. It
reads no licence and behaves as the Community edition. A binary for each
platform is attached to this release as bridgelab-cli-<target>.

Also

• The activation dialog describes the editions by what they actually
  gate: MLLP send and HTTP GET are Community; the listener, HTTP write
  methods and any Authorization header need Pro. The welcome card for
  XSD export no longer carries a blanket PRO badge — four v2.5 messages
  export in every edition.
• Double-clicking a .hl7 file now opens BridgeLab on Linux (shipped in
  the 1.5.0 packages).

Upgrading

Nothing to do. Packages you installed keep working and outrank the built-in
core where they overlap; a resource that used to come back clean may now
show findings inside a Bundle — those were there before, unreported.

Downloads

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