BridgeLab

Name: BridgeLab — Download free. HL7 & FHIR message workbench
Availability: InStock
Rating: 5 (1 reviews)
Author: TECHEMV SRL

BridgeLab — Free Download. HL7 & FHIR message workbench

BridgeLab is a desktop app for healthcare integration engineers who work with HL7 v2 and FHIR messages. It provides a schema-aware editor with syntax highlighting, a MLLP client and listener for bidirectional communication, structural and data-type validation, FHIRPath query execution, PHI anonymization with 21 built-in fields, batch folder validation, and XSD schema export for any supported HL7 v2 message type. The application processes multi-megabyte messages with base64 attachments through a streaming parser, runs fully offline against local test servers, and is available for Windows, macOS and Linux with interface translations in five languages.

★★★★★

5.0(1 ratings)

Download BridgeLab (Official links)

File size: 210 MB

The latest version of BridgeLab is: 2.0.0

Operating system: Windows, MacOS, Linux

Languages: English

Developer: TECHEMV SRL

Price: $0.00 USD (Freemium product ($24 or $47 per month or free version))

HL7 v2.x parser. SIMD-accelerated streaming parser that reads and processes HL7 v2 messages from version 2.3 through 2.7.1. Handles messages between 5 and 10 megabytes containing base64-encoded sections without blocking the interface. The parser operates on a zero-copy principle, passing truncated field representations to the editor so that Monaco never renders raw multi-megabyte text. Field expansion occurs on demand through right-click context actions or per-field controls.
FHIR support. Parses and validates FHIR resources in both JSON and XML formats. Supported resource types include Patient, Observation, Bundle and other standard FHIR structures. The validator checks resource conformance against the FHIR specification, reporting structural and data-type errors with precise location references. FHIRPath expressions can be evaluated against loaded resources to extract or verify specific values.
Smart truncation. Large fields are automatically replaced with a {...N bytes} marker in the editor view. Each truncated field can be expanded individually through a right-click action or expanded all at once through a menu command. This mechanism keeps memory consumption below 300 megabytes even when processing messages that contain embedded base64 PDF attachments or other binary payloads.
Validation engine. Performs structural, field-level and data-type validation across five rule categories. Checks include required field presence, data type conformance, cardinality constraints, length limits and custom declarative rules. Validation results appear as inline markers in the editor and as a summary panel. Custom rules are loaded from JSON plugin packs placed in the user configuration folder.
MLLP transport. Provides both client and server functionality for the Minimal Lower Layer Protocol. The client sends messages to remote endpoints with configurable framing, encoding selection and timeout values. The server listens on any port, accepts incoming connections, generates automatic acknowledgements and displays received messages in a live inbox. Connection profiles are stored per protocol for repeated use.
HTTP client. Supports GET, POST, PUT, DELETE and PATCH requests with Basic and Bearer authentication. Custom headers can be defined per request profile. Timeout values are configurable. The HTTP client targets local or remote endpoints and works fully offline when directed at local test servers. Response bodies are displayed in a dedicated panel with syntax highlighting for JSON and XML content.
PHI anonymization. Detects and masks 21 known Protected Health Information fields across PID, NK1, IN1 and GT1 segments. Masking is sensitivity-aware, meaning different field types receive different replacement patterns. The message structure is preserved so that anonymized output remains valid HL7. Additional regional PHI field definitions can be added through plugin packs loaded from the configuration directory.
Field Inspector. A side panel that displays HL7 standard metadata for the currently selected tree node. Metadata includes the schema-derived field name, data type, cardinality, maximum length and a textual description. Right-clicking any field in the editor or any node in the tree updates the inspector. The panel works in conjunction with the schema-aware tree to provide full field context.
Schema-aware tree. An optional tree view that injects placeholder rows for every field defined by the HL7 standard, not only those present in the loaded message. This view shows which fields could be populated according to the message structure definition. Navigation between the editor and the tree is bidirectional: right-clicking a field in the editor highlights the corresponding tree node, and right-clicking a tree node selects the matching range in Monaco.
XSD schema export. Generates standards-compliant XSD files for any supported HL7 v2 message type with a single action. The generated schemas are compatible with integration engines that accept hand-authored schemas, including Astraia, BizTalk and XMLSpy. Four common message types in version 2.5 are available in the free tier; the full catalogue and additional HL7 versions require a Pro license.
Plugin system. Reads declarative JSON packs from user folders for both validation and anonymization. Validation plugins support six check types: not_empty, regex, one_of, max_length, min_length and contains. Component-level narrowing is available through the component field. Plugins are reloaded live without restarting the application and can be enabled or disabled per pack with settings persisted across sessions.
Batch validation. Validates entire folders of HL7 messages in a single operation. Results are presented as a summary with per-file status and detailed error listings. The batch engine uses the same validation rules as the interactive editor, including custom plugin packs. Output can be exported for review or further processing.
Export functions. Converts loaded messages to JSON, CSV and other structured representations. Export targets include single messages and batch results. The conversion preserves segment and field structure, producing output suitable for downstream processing in database or analytics pipelines.
Command-line interface. A separate binary named bridgelab-cli provides validate, info, anonymize, to-json and batch commands. Output is formatted as JSON or JUnit XML for integration into continuous integration pipelines. The CLI uses the same parsing and validation engine as the desktop application.
Licensing. Uses Ed25519-signed license keys with hardware binding verified locally. Online activation exchanges a code for a signed key over a single HTTPS call, after which no network access is required. Offline keys are available for air-gapped sites. A 14-day trial starts automatically. The Community core is MIT-licensed and free for commercial use.

BridgeLab is developed by TECHEMV SRL, an Italian software company. The first public release appeared in 2025, with version 1.4.1 documented in early 2026. The application is written in Rust for the backend logic, parsing, validation, transport and licensing components, paired with Svelte 5 and TypeScript for the interface layer. Monaco Editor provides the text editing surface. The backend uses Tauri 2 as the desktop framework, tokio for MLLP transport, reqwest for HTTP communication and rusqlite for local SQLite storage. Licensing relies on Ed25519 signatures combined with hardware fingerprinting. The project follows an Open Core model: the core is MIT-licensed, while paid-tier feature implementations reside in clearly marked directories under the Business Source License 1.1. Building the Rust backend without default features produces a Community-only binary. Development continues with planned additions including SOAP 1.1/1.2 client support with WS-Security, a team test case library and package manager distributions for Homebrew, winget and AUR.