-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfeatures.html
More file actions
557 lines (534 loc) · 36.6 KB
/
Copy pathfeatures.html
File metadata and controls
557 lines (534 loc) · 36.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Features — open-source HL7 interface engine | MessageFoundry</title>
<meta name="description" content="The open-source healthcare interface engine: connect MLLP, HL7 v2, FHIR, X12, REST, SOAP and databases; route and transform in Python; durable delivery, HA, RBAC.">
<link rel="canonical" href="https://messagefoundry.org/features.html">
<link rel="icon" href="/assets/img/favicon.svg" type="image/svg+xml">
<meta name="theme-color" content="#0b1220">
<meta property="og:type" content="website">
<meta property="og:site_name" content="MessageFoundry">
<meta property="og:title" content="Features — MessageFoundry">
<meta property="og:description" content="The open-source healthcare interface engine (Early Access): many connections and message formats, durable delivery, active-passive high availability, RBAC + encryption, an admin console and VS Code tooling — guided wizards or Python, on SQLite, PostgreSQL, or SQL Server.">
<meta property="og:url" content="https://messagefoundry.org/features.html">
<meta property="og:image" content="https://messagefoundry.org/assets/img/og.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:type" content="image/png">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:image" content="https://messagefoundry.org/assets/img/og.png">
<link rel="stylesheet" href="/assets/css/styles.css">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"publisher": { "@id": "https://messagefoundry.org/#org" },
"@id": "https://messagefoundry.org/#software",
"name": "MessageFoundry",
"applicationCategory": "Healthcare interface engine",
"applicationSubCategory": "HL7 interface engine",
"operatingSystem": "Windows, Linux, macOS",
"url": "https://messagefoundry.org/",
"downloadUrl": "https://pypi.org/project/messagefoundry/",
"description": "MessageFoundry is an open-source, self-hosted healthcare interface engine written in Python. It routes, transforms, and validates messages across a wide range of protocols and message types, with deep HL7 v2 support — a modern alternative to legacy engines like Mirth Connect, Rhapsody, and Corepoint.",
"featureList": [
"Deep HL7 v2 parsing, validation, routing, and transformation",
"FHIR, X12/EDI, and DICOM connectivity over MLLP, HTTP/REST, SOAP, files, SFTP, and databases",
"Durable, at-least-once message delivery with strict per-interface FIFO ordering",
"Measured ~50 messages/second per ordered interface in reference testing; scales horizontally by adding interfaces",
"Active-passive high availability on SQLite, PostgreSQL, or SQL Server"
],
"license": "https://www.gnu.org/licenses/agpl-3.0.html",
"isAccessibleForFree": true,
"offers": {
"@type": "Offer",
"price": "0",
"priceCurrency": "USD"
}
}
</script>
</head>
<body>
<a class="skip-link" href="#main">Skip to content</a>
<div class="eabar" role="region" aria-label="Project status">
<div class="container">
<p><strong>Early Access · beta.</strong> We're building toward 1.0 — and we want people involved now, while it can still be shaped. <a href="/status.html">Where the project stands →</a></p>
</div>
</div>
<header class="site-header">
<div class="container header-inner">
<a class="brand" href="/" aria-label="MessageFoundry home">
<img class="brand-mark" src="/assets/img/logo.svg" alt="" width="28" height="28">
<span class="brand-name">Message<span class="brand-accent">Foundry</span><span class="brand-tm">™</span></span>
</a>
<button class="nav-toggle" aria-expanded="false" aria-controls="site-nav" aria-label="Toggle navigation"><span></span><span></span><span></span></button>
<nav class="site-nav" id="site-nav">
<div class="nav-group">
<button type="button" class="nav-group__btn" aria-expanded="false" aria-haspopup="true" aria-controls="nav-product">Product</button>
<div class="nav-group__menu" id="nav-product">
<a href="/overview.html">Overview</a>
<a href="/features.html" class="active" aria-current="page">Features</a>
<a href="/features-table.html">Feature list</a>
<a href="/architecture.html">Architecture</a>
<a href="/reliability.html">Reliability (CI)</a>
<a href="/tools.html">Tools</a>
<a href="/editor.html">Editor</a>
<a href="/console.html">Console</a>
<a href="/ai.html">AI assist</a>
</div>
</div>
<a href="/security.html">Security</a>
<a href="/comparison.html">Comparison</a>
<div class="nav-group">
<button type="button" class="nav-group__btn" aria-expanded="false" aria-haspopup="true" aria-controls="nav-getstarted">Get started</button>
<div class="nav-group__menu" id="nav-getstarted">
<a href="/getting-started.html">Quickstart</a>
<a href="/guides/">Guides</a>
<a href="/documents.html">Documents</a>
</div>
</div>
<div class="nav-group">
<button type="button" class="nav-group__btn" aria-expanded="false" aria-haspopup="true" aria-controls="nav-company">About Us</button>
<div class="nav-group__menu" id="nav-company">
<a href="/about.html">About</a>
<a href="/status.html">Project status</a>
<a href="/licensing.html">Licensing</a>
<a href="/contact.html">Contact</a>
<a href="/sponsor.html">Sponsor</a>
</div>
</div>
<a class="btn btn-ghost" href="/pypi.html">PyPI<svg width="15" height="15" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M12 3l8 4.5l0 9l-8 4.5l-8 -4.5l0 -9l8 -4.5"/><path d="M12 12l8 -4.5"/><path d="M12 12l0 9"/><path d="M12 12l-8 -4.5"/><path d="M16 5.25l-8 4.5"/></svg></a>
<a class="btn btn-ghost" href="https://github.com/MEFORORG/MessageFoundry" target="_blank" rel="noopener">GitHub ↗</a>
</nav>
</div>
</header>
<main id="main">
<!-- page header -->
<section class="section section--dark section--tight">
<div class="container center">
<span class="eyebrow">Features</span>
<h1 style="max-width:26ch;margin-inline:auto">Open-source integration for many standards and connections — with the tooling to match</h1>
<p class="lead">A focused healthcare interface engine that connects a wide range of systems and message standards. Set up connections and routes with guided wizards, or extend them in Python — your choice. Durable delivery; deep HL7 v2 support; active-passive high availability; PHI-aware security; and an admin console plus VS Code tooling. Everything here ships in <b>Early Access</b>; what's coming next is at the bottom of the page.</p>
<div class="btn-row">
<a class="btn btn-primary" href="/getting-started.html">Get started</a>
<a class="btn btn-ghost" href="/features-table.html">All features at a glance →</a>
</div>
</div>
</section>
<!-- open source / no lock-in -->
<section class="section">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">Open source, no lock-in</span>
<h2>Your integration logic is yours</h2>
<p class="lead">AGPL-licensed and open: your configuration is yours — generated by wizards or written in plain Python, versioned in <em>your</em> git repository, running on <em>standard</em> databases. Nothing is locked inside a vendor's runtime, language, or contract.</p>
</div>
<ul class="feature-list">
<li><b>AGPL-3.0-or-later</b> — read it, run it, fork it. A low-cost commercial edition is available when the AGPL doesn't fit.</li>
<li><b>Configuration as code (or data)</b> — wizards generate it or you write it; either way Connections, Routers, and Handlers are diffable, reviewable modules, and connection settings can also live as data in <code>connections.toml</code> — edited by hand, with the <code>messagefoundry connection</code> CLI, or in the VS Code editor. The database holds runtime state and messages only, never configuration.</li>
<li><b>Standard databases</b> — no proprietary data platform required, and no proprietary scripting language to staff for.</li>
<li><b>No runtime or contract lock-in</b> — self-hosted, on your infrastructure, on your terms.</li>
</ul>
</div>
</section>
<!-- reliability -->
<section class="section section--alt">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">Reliability</span>
<h2>Durable by construction</h2>
<p class="lead">A durable, transactional inbox/outbox is the reliability backbone — no separate broker to run, patch, or monitor.</p>
</div>
<ul class="feature-list">
<li><b>Durable before it's acknowledged</b> — the inbound is ACKed only after the received message is committed to the store on ingest, so an accepted message survives a crash before any processing begins.</li>
<li><b>Reliable delivery</b> — every accepted message is persisted and delivered; nothing is silently dropped.</li>
<li><b>Ordered (FIFO) delivery</b> — messages to a given destination are delivered first-in, first-out, preserving per-connection sequence.</li>
<li><b>Per-outbound workers</b> — each destination drains independently; one slow or failing peer never blocks the others.</li>
<li><b>Automatic retries with a configurable failure policy</b> — back off and retry, then dead-letter, with a bulk-replay view for recovery.</li>
<li><b>Replay</b> — re-drive a stored message through delivery from the console or API.</li>
<li><b>Automatic crash recovery</b> — after a restart or crash, in-flight messages resume from the durable store with no manual cleanup.</li>
<li><b>Nothing silently dropped</b> — every message is persisted on ingest, then processed to a recorded disposition (routed, filtered, or unrouted), so nothing is ever quietly discarded.</li>
</ul>
</div>
</section>
<!-- formats -->
<section class="section">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">Message formats</span>
<h2>Deep HL7 v2 — and the formats around it</h2>
<p class="lead">HL7 v2 is the format MessageFoundry parses and validates in depth. JSON, XML/SOAP, X12/EDI, database records, and other payloads are routed, transformed, and delivered alongside it — moved through your interfaces flexibly, without assuming a rigid schema. MessageFoundry is <a href="/hl7-integration-engine/">more than an HL7 interface engine</a>.</p>
</div>
<ul class="feature-list">
<li><b>HL7 v2, deeply parsed</b> — full parsing and validation: fast and tolerant on the hot path, strict and version-aware where you opt in. Real-world HL7 is frequently non-conformant, and the engine is built to expect that.</li>
<li><b>JSON, XML/SOAP, X12/EDI, database records, and arbitrary payloads</b> — routed, transformed, enriched, and delivered with the full power of Python (a ready X12 codec, a FHIR codec with FHIRPath, one-call JSON parsing, your own library for the rest). HL7 v2 is the one with a structured, standard-aware transform model built in — a difference in built-in support, not in what's possible.</li>
<li><b>XML parsing is hardened</b> — XML payloads are read with an XXE-safe parser, so a hostile document (external entities, embedded DOCTYPE, billion-laughs expansion) is rejected, not parsed.</li>
<li><b>Encoding read from the message</b> — for HL7 v2, the field, component, repetition, escape, and subcomponent separators come from MSH, never hardcoded.</li>
<li><b>Raw message preserved</b> alongside the transformed form, so an operator always sees exactly what arrived.</li>
<li><b>Parse failures are isolated</b> — routed to the error / dead-letter path and logged, so a bad message never takes down the connection.</li>
</ul>
</div>
</section>
<!-- connections -->
<section class="section section--alt">
<div class="container">
<div class="center" style="margin-bottom:38px">
<span class="eyebrow">Connections</span>
<h2>Connect the systems you already run</h2>
<p class="lead center">Inbound and outbound connectors for the transports healthcare actually uses — registered through one contract, not special-cased in the pipeline.</p>
</div>
<div class="grid grid-3">
<div class="card">
<h3>Network</h3>
<p><b>MLLP</b> — correct <code>0x0B … 0x1C 0x0D</code> framing, inbound and outbound, with ACK/NAK generation (AA / AE / AR) and a per-connection ack mode. <b>TCP</b> for raw stream endpoints. <b>X12 / EDI</b> over TCP — ISA/IEA-framed interchanges, inbound and outbound. <b>DICOM</b> imaging — C-STORE SCP/SCU and C-ECHO over DIMSE, plus DICOMweb STOW-RS (<a href="/dicom.html" style="color:var(--accent-ink)">DICOM imaging →</a>).</p>
</div>
<div class="card">
<h3>Web services</h3>
<p><b>HTTP / REST</b>, <b>SOAP</b>, and <b>FHIR REST</b> web-service destinations — deliver to modern and legacy APIs; the FHIR destination does create / update / transaction against R4B (R5 / STU3). <span style="color:var(--muted)">Inbound REST / SOAP / FHIR listener endpoints are on the roadmap.</span></p>
</div>
<div class="card">
<h3>Files & databases</h3>
<p><b>Files</b> — local directories and remote <b>SFTP / FTP / FTPS</b>, with templated output names (e.g. <code>{MSH-10}.hl7</code>). <b>Database</b> — poll records in and write results out.</p>
</div>
</div>
<div class="callout" style="margin-top:26px">
<p><strong>Count-and-log invariant.</strong> Every message a connection takes in or puts out is counted and logged — a router or filter decision is a recorded outcome (<code>UNROUTED</code> / <code>FILTERED</code>), never a silent drop.</p>
</div>
</div>
</section>
<!-- routing -->
<section class="section section--dark">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">Routing & transformation</span>
<h2>Route, filter, and transform — wizards or code</h2>
<p class="lead">Set up routing and transformation with guided wizards, or write it in Python for full control — no proprietary DSL to learn. Send each message to one destination or many, filter what shouldn't flow, and reshape it on the way through.</p>
</div>
<ul class="feature-list">
<li><b>One-to-many routing with filtering</b> — fan a message out to multiple destinations, or filter it out entirely; every decision is a recorded outcome.</li>
<li><b>Transform, enrich, validate</b> — reshape and augment messages mid-flight, with validation where you want it.</li>
<li><b>Reference & lookup tables</b> and <b>live database lookups</b> — enrich from static tables or query a live database during processing.</li>
<li><b>Guided wizards or pure functions</b> — New Connection / New Route wizards generate the wiring, or write Routers and Handlers as plain functions registered by name.</li>
<li><b>Dry-run with before/after diff</b> — preview a route's effect on a real message before it ships.</li>
</ul>
</div>
</section>
<!-- security -->
<section class="section section--alt">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">Security & PHI</span>
<h2>PHI is a first-class concern</h2>
<p class="lead">This engine carries PHI, so authentication, authorization, audit, and encryption-at-rest are built in — not bolted on. The API binds <code>127.0.0.1</code> by default and requires authentication.</p>
</div>
<ul class="feature-list">
<li><b>Authentication</b> — local accounts with built-in, required multi-factor authentication (MFA), or Active Directory (LDAP) sign-in, with opaque, revocable sessions.</li>
<li><b>RBAC</b> — fixed built-in roles, deny-by-default, per-route and per-channel scoping.</li>
<li><b>TLS in transit, by default</b> — the API and MLLP run over TLS (including MLLP-over-TLS); for endpoints that can't do TLS, plaintext is supported within your secure network perimeter.</li>
<li><b>Tamper-evident audit log</b> — a hash-chained, user-attributed record of every PHI access (raw view, summary, replay), with a verification command.</li>
<li><b>Off-box log & audit forwarding</b> — operational and audit logs forward to your syslog or SIEM collector.</li>
<li><b>Encryption at rest</b> — message bodies are encrypted with AES-256-GCM in the store.</li>
<li><b>Retention & purge</b> — keep messages as long as policy requires, then purge on a configurable schedule.</li>
</ul>
</div>
</section>
<!-- operate -->
<section class="section">
<div class="container">
<div class="center" style="margin-bottom:38px">
<span class="eyebrow">Operate</span>
<h2>A console and an editor, both talking to one API</h2>
</div>
<div class="grid grid-3">
<div class="card">
<span class="ico"><svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M4 4h16a1 1 0 0 1 1 1v11a1 1 0 0 1-1 1h-7v2h3v2H8v-2h3v-2H4a1 1 0 0 1-1-1V5a1 1 0 0 1 1-1zm1 2v9h14V6H5z"/></svg></span>
<h3>Admin console</h3>
<p>Dashboards, message search and browse, an HL7 parse-tree viewer, delivery and audit trail, a dead-letter page, an alert-rules view, and one-click replay. A separate app that reaches the engine only over the localhost API.</p>
</div>
<div class="card">
<span class="ico"><svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M3 5a2 2 0 0 1 2-2h14a2 2 0 0 1 2 2v14a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V5zm6.5 3L6 11.5 9.5 15 11 13.5 8.9 11.5 11 9.5 9.5 8zm5 0L13 9.5l2.1 2-2.1 2L14.5 15 18 11.5 14.5 8z"/></svg></span>
<h3>VS Code extension</h3>
<p>Author and operate interfaces in your editor: completion, live HL7-aware validate-on-save, a graph view of your integration (a boxes-and-arrows diagram), source-control integration, and Stage → Promote to a running engine.</p>
</div>
<div class="card">
<span class="ico"><svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M8 3v2H5v14h3v2H3V3h5zm8 0h5v18h-5v-2h3V5h-3V3zM7 13.5 9.5 11 7 8.5 8.4 7l4 4-4 4L7 13.5z"/></svg></span>
<h3>CLI & localhost API</h3>
<p><code>messagefoundry serve</code> runs the engine and exposes connection control, message search/detail, replay, stats, and a live WebSocket feed. <code>check</code> gates commits; <code>generate</code> produces synthetic, PHI-free HL7.</p>
</div>
</div>
<div class="callout" style="margin-top:26px">
<p><strong>Alerting & operational niceties.</strong> Alerting via webhook and email when a connection stalls or a message dead-letters; a Prometheus / OpenTelemetry <code>/metrics</code> endpoint to scrape engine and connection metrics into your monitoring stack; configuration hot-reload and environment promotion (DEV/PROD values layer over the same modules); configurable ACK modes, message-size and segment guards; and a synthetic HL7 generator for testing — all included.</p>
</div>
</div>
</section>
<!-- author faster -->
<section class="section section--dark">
<div class="container">
<div class="center" style="margin-bottom:38px">
<span class="eyebrow">Author faster</span>
<h2>Wizards and a PHI-safe AI assistant lower the barrier</h2>
<p class="lead center">Power without the blank-page tax — guided generation and AI help that never sees a message body.</p>
</div>
<div class="grid grid-3">
<div class="card">
<h3>Setup wizards</h3>
<p>Guided <b>New Connection</b> and <b>New Route</b> flows that generate the Python for you — Corepoint-style guided authoring, but the output is plain code you own and review.</p>
</div>
<div class="card">
<h3>PHI-safe AI assistance</h3>
<p>An in-editor assistant governed by a central, environment-aware policy that sends <b>only code, never message bodies</b>, gated by role-based access control.</p>
</div>
<div class="card">
<h3>AI-assisted migration</h3>
<p>Moving from another engine is AI-assisted by design: paste your existing Mirth / Cloverleaf / Rhapsody logic and the assistant helps you express it as Python — which can be far less work than re-platforming. Code-only and governed.</p>
</div>
</div>
</div>
</section>
<!-- test -->
<section class="section">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">Test & verify</span>
<h2>A full test harness, included</h2>
<p class="lead">Exercise interfaces with synthetic, PHI-free traffic before anything touches production — interactively or in CI.</p>
</div>
<ul class="feature-list">
<li><b>Send / receive / file / compose / monitor</b> test bench for driving inbound and outbound endpoints by hand.</li>
<li><b>Headless scenario runner</b> for CI — assert routing and transform behavior on every commit.</li>
<li><b>Test Bench dry-runs</b> in VS Code — run <code>.hl7</code> files through a route with before/after diffs.</li>
<li><b>Synthetic HL7 generator</b> — realistic, PHI-free messages for load and edge-case testing.</li>
<li><b><code>check</code> commit gate</b> — validate configuration before it ships.</li>
</ul>
</div>
</section>
<!-- ci/cd -->
<section class="section section--dark">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">CI/CD</span>
<h2>Ships through the pipeline you already run</h2>
<p class="lead">Because interfaces are plain Python in your git repository, they move through the same delivery pipeline as the rest of your software — no vendor deployment tool to learn.</p>
</div>
<ul class="feature-list">
<li><b>Pull-request review</b> — every interface change is a readable diff your team approves, with full history and instant rollback.</li>
<li><b>A build gate</b> — <code>messagefoundry check</code> validates config and dry-runs messages, failing the build on a broken route before it merges.</li>
<li><b>Automated tests in CI</b> — a headless scenario runner asserts the engine's outcome on synthetic data, pass/fail, in GitHub Actions, GitLab CI, Jenkins, or Azure DevOps.</li>
<li><b>Reproducible promotion</b> — only a reviewed, green change is promoted to each environment, so production matches git — no config drift.</li>
<li><b>Auditable by default</b> — reviewed, tested, timestamped change control, the way compliance already expects it.</li>
</ul>
</div>
</section>
<!-- database flexibility -->
<section class="section section--alt">
<div class="container">
<div class="center" style="margin-bottom:38px">
<span class="eyebrow">Database flexibility</span>
<h2>From a single file to a highly available database</h2>
<p class="lead center">One pluggable message store behind a single contract, so the database is a deployment choice — not a code change. Start zero-config on SQLite, then move to PostgreSQL or SQL Server for highly available production with failover.</p>
</div>
<div class="grid grid-3">
<div class="card">
<h3>SQLite</h3>
<p>The zero-config, single-node default — WAL, one file, no server to run. The "it just works" path for development, demos, embedded use, and small single-box sites — and the byte-identical baseline every other backend matches.</p>
</div>
<div class="card">
<h3>PostgreSQL</h3>
<p>The production server DB for high availability: a standby shares the same store and takes over on primary failure via leader election, preserving strict per-destination FIFO ordering. The reference production backend.</p>
</div>
<div class="card">
<h3>SQL Server</h3>
<p>A first-class production backend at parity with PostgreSQL — the same staged pipeline, concurrency-safe claiming, row leases, and high-availability failover — for shops standardized on SQL Server.</p>
</div>
</div>
<div class="callout" style="margin-top:26px">
<p><strong>One Store contract.</strong> The same staged-pipeline delivery model — dispositions, retries, replay, audit, encryption at rest, and configurable retention/purge — runs across all three backends. PostgreSQL and SQL Server are interchangeable production server-DBs, so you pick whichever your environment already runs. No proprietary data platform required; your messages live in a database you control.</p>
</div>
</div>
</section>
<!-- high availability -->
<section class="section section--dark">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">High availability</span>
<h2>Stay up through failures</h2>
<p class="lead">Run a primary with a hot standby: if the primary fails, the standby takes over without losing in-flight messages. The data tier rides your database's own HA — PostgreSQL replication or SQL Server Always On.</p>
</div>
<ul class="feature-list">
<li><b>Active-passive failover</b> — a standby promotes on primary failure; in-flight work resumes from the durable store.</li>
<li><b>No message loss</b> — failover picks up from committed state, so nothing accepted is dropped.</li>
<li><b>Database-tier HA</b> — PostgreSQL streaming replication or SQL Server Always On availability groups back the store.</li>
<li><b>Runs in your environment</b> — on-premises, on your infrastructure, on your DR terms.</li>
</ul>
</div>
</section>
<!-- deployment + support -->
<section class="section">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">Deploy & operate</span>
<h2>Runs headless, where your data lives</h2>
<p class="lead">On-premises by default — no PHI leaves the local environment without explicit, reviewed configuration.</p>
</div>
<ul class="feature-list">
<li><b>Windows service via NSSM</b> — install/uninstall scripts included.</li>
<li><b>Headless engine</b> — no GUI imports; testable and runnable as a service.</li>
<li><b>One config, many environments</b> — DEV/PROD values layer over the same Python modules.</li>
</ul>
</div>
</section>
<!-- roadmap -->
<section class="section section--dark section--tight">
<div class="container">
<div class="center" style="margin-bottom:30px">
<span class="eyebrow">Roadmap</span>
<h2>Possible future additions</h2>
<p class="lead center">Everything above ships in Early Access. Here's where MessageFoundry is headed next.</p>
</div>
<div class="grid grid-2">
<div class="card">
<h3>Connectivity & standards</h3>
<p>Inbound REST, SOAP, and FHIR listener endpoints; OAuth 2.0, SMART on FHIR, and single sign-on (OIDC/SAML, AD FS/Entra ID, and passwordless Windows/Kerberos); and more databases — MySQL/MariaDB and Oracle.</p>
</div>
<div class="card">
<h3>Security & operations</h3>
<p>A multi-engine console view, and an independent external code review and penetration test.</p>
</div>
</div>
</div>
</section>
<!-- faq -->
<section class="section">
<div class="container">
<div class="center" style="margin-bottom:28px"><span class="eyebrow">FAQ</span><h2>Frequently asked questions</h2></div>
<div class="faq">
<div class="faq-item"><h3>Does MessageFoundry support HL7 v2 and FHIR?</h3><p>Yes. MessageFoundry has deep HL7 v2 support — parsing, validation, routing, and transformation — and works with FHIR, alongside X12/EDI, DICOM, JSON, and XML payloads.</p></div>
<div class="faq-item"><h3>What systems and protocols can MessageFoundry connect?</h3><p>It connects the systems you already run over MLLP (with TLS), TCP, HTTP/REST, SOAP, FHIR REST, files, SFTP/FTP, databases, and DICOM — so a wide range of protocols and message types flow through one engine.</p></div>
<div class="faq-item"><h3>Do I write interfaces in code or with a GUI?</h3><p>Both. You can set up Connections, Routers, and Handlers with guided wizards in the VS Code extension and admin console, or write them in plain Python for full control — version-controlled like any codebase.</p></div>
<div class="faq-item"><h3>Is MessageFoundry built for PHI and security?</h3><p>Yes. PHI is a first-class concern: it stays self-hosted, traffic is encrypted with TLS, message bodies at rest with AES-256-GCM, every operator is authenticated, and access is audited. It's built to NIST SSDF / 800-66 and self-assessed against OWASP ASVS Level 3.</p></div>
<div class="faq-item"><h3>How does MessageFoundry scale?</h3><p>MessageFoundry scales horizontally by adding interfaces. The unit of capacity is one inbound interface, which sustains roughly 50 messages per second in our measurements — on the order of a million messages a day — with strict in-order, durable, at-least-once processing, so messages aren't silently dropped. That is well beyond what a single hospital's routine ADT feed needs, with comfortable headroom for bursts. When you need more, you split feeds at the source across more interfaces, plus an optional multi-node tier. Aggregate throughput is not simply the sum of those interfaces — they share a store, and measured concurrent runs land below the naive total — so treat the sum as an upper bound. These figures are measured on anonymized, representative message traffic; real throughput depends on your transforms, storage, and hardware.</p><p style="margin-top:10px"><a href="/throughput/">How throughput really works →</a></p></div>
</div>
</div>
</section>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Does MessageFoundry support HL7 v2 and FHIR?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. MessageFoundry has deep HL7 v2 support — parsing, validation, routing, and transformation — and works with FHIR, alongside X12/EDI, DICOM, JSON, and XML payloads."
}
},
{
"@type": "Question",
"name": "What systems and protocols can MessageFoundry connect?",
"acceptedAnswer": {
"@type": "Answer",
"text": "It connects the systems you already run over MLLP (with TLS), TCP, HTTP/REST, SOAP, FHIR REST, files, SFTP/FTP, databases, and DICOM — so a wide range of protocols and message types flow through one engine."
}
},
{
"@type": "Question",
"name": "Do I write interfaces in code or with a GUI?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Both. You can set up Connections, Routers, and Handlers with guided wizards in the VS Code extension and admin console, or write them in plain Python for full control — version-controlled like any codebase."
}
},
{
"@type": "Question",
"name": "Is MessageFoundry built for PHI and security?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. PHI is a first-class concern: it stays self-hosted, traffic is encrypted with TLS, message bodies at rest with AES-256-GCM, every operator is authenticated, and access is audited. It's built to NIST SSDF / 800-66 and self-assessed against OWASP ASVS Level 3."
}
},
{
"@type": "Question",
"name": "How does MessageFoundry scale?",
"acceptedAnswer": {
"@type": "Answer",
"text": "MessageFoundry scales horizontally by adding interfaces. The unit of capacity is one inbound interface, which sustains roughly 50 messages per second in our measurements — on the order of a million messages a day — with strict in-order, durable, at-least-once processing, so messages aren't silently dropped. That is well beyond what a single hospital's routine ADT feed needs, with comfortable headroom for bursts. When you need more, you split feeds at the source across more interfaces, plus an optional multi-node tier. Aggregate throughput is not simply the sum of those interfaces — they share a store, and measured concurrent runs land below the naive total — so treat the sum as an upper bound. These figures are measured on anonymized, representative message traffic; real throughput depends on your transforms, storage, and hardware."
}
}
]
}
</script>
<section class="section">
<div class="container">
<div class="cta-band">
<h2>See it run for yourself</h2>
<div class="btn-row center">
<a class="btn btn-primary" href="/getting-started.html">Get started</a>
<a class="btn btn-ghost" href="/guides/">Browse the guides →</a>
<a class="btn btn-ghost" href="/comparison.html">See how it compares →</a>
</div>
</div>
</div>
</section>
</main>
<footer class="site-footer">
<div class="container">
<div class="footer-grid">
<div class="footer-brand">
<a class="brand" href="/" aria-label="MessageFoundry home">
<img class="brand-mark" src="/assets/img/logo.svg" alt="" width="28" height="28">
<span class="brand-name">Message<span class="brand-accent">Foundry</span><span class="brand-tm">™</span></span>
</a>
<p class="footer-tagline"><b>More</b> Than an HL7 Interface Engine</p>
<p>Open-source healthcare interface engine — secure by default, built to recognized standards, connecting a wide range of protocols and message types.</p>
<div class="badge-row" style="margin-top:16px">
<span class="badge">Open source</span>
<span class="badge">No lock-in</span>
<span class="badge">Self-hosted</span>
</div>
</div>
<div class="footer-col">
<h4>Product</h4>
<a href="/overview.html">Overview</a>
<a href="/features.html">Features</a>
<a href="/architecture.html">Architecture</a>
<a href="/reliability.html">Reliability</a>
<a href="/dicom.html">DICOM</a>
<a href="/security.html">Security & PHI</a>
<a href="/documents.html">Documents</a>
</div>
<div class="footer-col">
<h4>Tools</h4>
<a href="/tools.html">Tools</a>
<a href="/editor.html">Editor</a>
<a href="/console.html">Console</a>
<a href="/ai.html">AI assist</a>
</div>
<div class="footer-col">
<h4>Get started</h4>
<a href="/getting-started.html">Quickstart</a>
<a href="/guides/">Guides</a>
<a href="/comparison.html">Comparison</a>
</div>
<div class="footer-col">
<h4>Project</h4>
<a href="/status.html">Project status</a>
<a href="https://github.com/MEFORORG/MessageFoundry" target="_blank" rel="noopener">GitHub</a>
<a href="https://github.com/MEFORORG/MessageFoundry/issues" target="_blank" rel="noopener">Issues</a>
<a href="/contact.html">Contact</a>
<a href="/licensing.html">License</a>
<a href="/about.html">About</a>
<a href="/sponsor.html">Sponsor</a>
</div>
</div>
<div class="footer-bottom">
<span>© 2026 MEFOR-ORG, a non-profit — this website and its content, all rights reserved. The MessageFoundry engine is separately open source, licensed under AGPL-3.0-or-later.</span>
<span>MessageFoundry and the MessageFoundry word mark are trademarks of MEFOR-ORG. Mirth Connect, Cloverleaf, Rhapsody, Corepoint, and Ensemble are trademarks of their respective owners; MessageFoundry is independent and unaffiliated.</span>
</div>
</div>
</footer>
<script src="/assets/js/nav.js" defer></script>
</body>
</html>