-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
523 lines (494 loc) · 36.7 KB
/
Copy pathindex.html
File metadata and controls
523 lines (494 loc) · 36.7 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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>MessageFoundry — Open-source healthcare interface engine</title>
<meta name="description" content="MessageFoundry is an open-source, self-hosted healthcare interface engine in Python — deep HL7 v2 plus FHIR, X12 and more, with durable, at-least-once delivery.">
<link rel="canonical" href="https://messagefoundry.org/">
<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="MessageFoundry — healthcare interface engine">
<meta property="og:description" content="Open-source healthcare interface engine — route, transform, and validate messages in plain Python across many protocols and message types, with deep HL7 v2 support. Self-hosted, PHI-aware.">
<meta property="og:url" content="https://messagefoundry.org/">
<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:title" content="MessageFoundry — healthcare interface engine">
<meta name="twitter:description" content="Open-source healthcare interface engine — route, transform, and validate messages in plain Python across many protocols and message types, with deep HL7 v2 support. Self-hosted, PHI-aware.">
<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",
"@graph": [
{
"@type": "Organization",
"@id": "https://messagefoundry.org/#org",
"name": "MEFOR-ORG",
"url": "https://messagefoundry.org/",
"logo": "https://messagefoundry.org/assets/img/logo.svg",
"description": "Open-source healthcare interface engine — route, transform, and validate messages in plain Python, with deep HL7 v2 support. Self-hosted and PHI-aware.",
"sameAs": [
"https://github.com/MEFORORG/MessageFoundry",
"https://pypi.org/project/messagefoundry/"
]
},
{
"@type": "WebSite",
"@id": "https://messagefoundry.org/#website",
"name": "MessageFoundry",
"url": "https://messagefoundry.org/",
"publisher": { "@id": "https://messagefoundry.org/#org" }
},
{
"@type": "SoftwareApplication",
"@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" },
"publisher": { "@id": "https://messagefoundry.org/#org" }
}
]
}
</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">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">
<!-- ───────────────────────────── hero ───────────────────────────── -->
<section class="hero">
<div class="container hero-inner">
<div>
<span class="eyebrow">Open-source healthcare interface engine</span>
<h1>Your fast path off<br><span class="grad">legacy interface engines.</span></h1>
<p class="lead">Interface-engine costs are climbing just as healthcare budgets tighten. MessageFoundry is the open-source alternative — self-hosted, with no per-interface licensing. It connects a wide range of healthcare protocols and message types, with deep HL7 v2 support and AI-assisted migration to get your interfaces off legacy fast. It's <a href="/hl7-integration-engine/">more than an HL7 interface engine</a>.</p>
<div class="btn-row">
<a class="btn btn-primary" href="/getting-started.html">Get started →</a>
</div>
<div class="hero-meta">
<span><i class="dot"></i> Free & open source</span>
<span><i class="dot"></i> No per-interface fees</span>
<span><i class="dot"></i> No per-seat fees</span>
<span><i class="dot"></i> AI-assisted migration</span>
<span><i class="dot"></i> Early Access — new & moving fast</span>
</div>
</div>
<div>
<div class="code-card hero-card">
<input type="radio" name="hero-view" id="hv-graph" class="hv-in" checked aria-label="Show the interface as a graph">
<input type="radio" name="hero-view" id="hv-code" class="hv-in" aria-label="Show the interface as Python code">
<div class="code-card__bar">
<i></i><i></i><i></i>
<span class="code-card__name">IB_Test_ADT</span>
<div class="hv-tabs">
<label class="hv-tab" for="hv-graph">Graph</label>
<label class="hv-tab" for="hv-code">Code</label>
</div>
</div>
<div class="hv-panels">
<div class="hv-panel hv-panel--graph">
<svg class="wire-graph" viewBox="0 0 440 490" role="img" xmlns="http://www.w3.org/2000/svg">
<title>The IB_Test_ADT interface as a wired graph</title>
<desc>An MLLP inbound named IB_Test_ADT is wired by the name adt_router to a router, then by the name map_location to a handler that translates the patient location (PV1-3) from 4N-412B to ROOM412-B via the bed_locations translation table, then sends to a file outbound named FILE_Test_ADT. Non-ADT messages branch off as UNROUTED; unmapped locations are dead-lettered (held for review) — both tracked, never silently dropped.</desc>
<defs><marker id="wg-ar" viewBox="0 0 10 10" refX="8" refY="5" markerWidth="6.5" markerHeight="6.5" orient="auto"><path d="M2 1L8 5L2 9" fill="none" stroke="context-stroke" stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round"/></marker></defs>
<line class="wg-edge" x1="145" y1="92" x2="145" y2="139" marker-end="url(#wg-ar)"/>
<line class="wg-edge" x1="145" y1="204" x2="145" y2="251" marker-end="url(#wg-ar)"/>
<line class="wg-edge" x1="145" y1="332" x2="145" y2="379" marker-end="url(#wg-ar)"/>
<line class="wg-branch" x1="270" y1="172" x2="293" y2="172" marker-end="url(#wg-ar)"/>
<line class="wg-branch" x1="270" y1="292" x2="293" y2="292" marker-end="url(#wg-ar)"/>
<text class="wg-wire" x="158" y="120">router="adt_router"</text>
<text class="wg-wire" x="158" y="232">→ ["map_location"]</text>
<text class="wg-wire" x="158" y="360">Send("FILE_Test_ADT")</text>
<rect class="wg-node" x="20" y="18" width="250" height="74" rx="11"/>
<text class="wg-tag" x="145" y="42" text-anchor="middle">INBOUND</text>
<text class="wg-name" x="145" y="64" text-anchor="middle">IB_Test_ADT</text>
<text class="wg-sub" x="145" y="81" text-anchor="middle">MLLP · :2575</text>
<rect class="wg-node" x="20" y="140" width="250" height="64" rx="11"/>
<text class="wg-tag" x="145" y="159" text-anchor="middle">ROUTER</text>
<text class="wg-name" x="145" y="180" text-anchor="middle">adt_router</text>
<text class="wg-sub" x="145" y="196" text-anchor="middle">route(msg)</text>
<rect class="wg-node wg-node--xf" x="20" y="252" width="250" height="80" rx="11"/>
<text class="wg-tag" x="145" y="271" text-anchor="middle">HANDLER · TRANSFORM</text>
<text class="wg-name" x="145" y="291" text-anchor="middle">map_location</text>
<text class="wg-sub" x="145" y="308" text-anchor="middle">PV1-3 · patient location</text>
<text class="wg-sub wg-sub--xf" x="145" y="325" text-anchor="middle">4N-412B → ROOM412-B</text>
<rect class="wg-node" x="20" y="380" width="250" height="74" rx="11"/>
<text class="wg-tag" x="145" y="404" text-anchor="middle">OUTBOUND</text>
<text class="wg-name" x="145" y="426" text-anchor="middle">FILE_Test_ADT</text>
<text class="wg-sub" x="145" y="443" text-anchor="middle">File · out/adt</text>
<rect class="wg-chip" x="296" y="148" width="128" height="48" rx="8"/>
<text class="wg-ct" x="360" y="170" text-anchor="middle">UNROUTED</text>
<text class="wg-cs" x="360" y="186" text-anchor="middle">not ADT</text>
<rect class="wg-chip" x="296" y="268" width="128" height="48" rx="8"/>
<text class="wg-ct" x="360" y="290" text-anchor="middle">DEAD-LETTER</text>
<text class="wg-cs" x="360" y="306" text-anchor="middle">unmapped location</text>
<line class="wg-edge" x1="20" y1="472" x2="44" y2="472"/>
<text class="wg-leg" x="52" y="476">delivered</text>
<line class="wg-branch" x1="150" y1="472" x2="174" y2="472"/>
<text class="wg-leg" x="182" y="476">tracked — never dropped</text>
</svg>
</div>
<div class="hv-panel hv-panel--code">
<pre class="code"><span class="k">from</span> messagefoundry <span class="k">import</span> MLLP, File, Send, code_set, inbound, outbound, router, handler
<span class="c"># Connections — named endpoints, wired together by name</span>
<span class="f">inbound</span>(<span class="s">"IB_Test_ADT"</span>, <span class="f">MLLP</span>(port=<span class="n">2575</span>), router=<span class="s">"adt_router"</span>)
<span class="f">outbound</span>(<span class="s">"FILE_Test_ADT"</span>, <span class="f">File</span>(directory=<span class="s">"./out/adt"</span>, filename=<span class="s">"{MSH-10}.hl7"</span>))
<span class="c"># Router — routes each message to handlers by name</span>
<span class="d">@router</span>(<span class="s">"adt_router"</span>)
<span class="k">def</span> <span class="f">route</span>(msg):
<span class="k">if</span> msg[<span class="s">"MSH-9.1"</span>] != <span class="s">"ADT"</span>:
<span class="k">return</span> [] <span class="c"># not ADT → UNROUTED</span>
<span class="k">return</span> [<span class="s">"map_location"</span>]
<span class="c"># Translation table — edited in a grid, stored as version-controlled CSV</span>
ROOMS = <span class="f">code_set</span>(<span class="s">"bed_locations"</span>)
<span class="c"># Handler — translate the patient location for the receiver</span>
<span class="d">@handler</span>(<span class="s">"map_location"</span>)
<span class="k">def</span> <span class="f">map_location</span>(msg):
msg[<span class="s">"PV1-3.1"</span>] = ROOMS[msg[<span class="s">"PV1-3.1"</span>]] <span class="c"># unmapped → held for review</span>
<span class="k">return</span> <span class="f">Send</span>(<span class="s">"FILE_Test_ADT"</span>, msg)</pre>
</div>
</div>
<p class="hero-card__note">One example route. Use the <b>Graph / Code</b> toggle above to switch between the explainer diagram and the plain code.</p>
</div>
</div>
</div>
</section>
<!-- ───────────────────────────── project status notice ───────────────────────────── -->
<section class="section section--dark section--tight">
<div class="container">
<div class="callout" style="max-width:900px;margin-inline:auto">
<p><strong>Before you read further — this is a young project, and we're mid-build.</strong> MessageFoundry started in <b>May 2026</b>. It's in <b>Early Access</b>: beta-level software, developed quickly, with rough edges to match. We're working toward the <b>1.0 release</b> now — which is exactly why this is the moment to get involved. Decisions made in the next few months are the ones you can still influence.</p>
<p style="margin:12px 0 0"><strong>What we're asking for.</strong> Run it in a <b>sandboxed test environment</b>, point it at your interface shapes, and tell us what breaks and what's missing. Findings from real-world traffic patterns change our plans more than anything we could invent on our own — and they change them cheaply while we're still pre-1.0. <a href="/status.html">See exactly where the project stands →</a></p>
</div>
</div>
</section>
<!-- ───────────────────────────── standards trust bar ───────────────────────────── -->
<section class="section section--dark section--tight" style="border-top:1px solid var(--border-dk)">
<div class="container center">
<span class="eyebrow">Built to recognized standards</span>
<div class="badge-row" style="justify-content:center;gap:10px;max-width:920px;margin:0 auto">
<span class="badge">NIST SP 800-218 (SSDF)</span>
<span class="badge">NIST SP 800-115</span>
<span class="badge">NIST SP 800-66 Rev. 2 (HIPAA Security Rule)</span>
<span class="badge">OWASP ASVS 5.0 Level 3</span>
</div>
<p class="center" style="color:var(--muted-dk);font-size:.95rem;margin:18px auto 0;max-width:62ch">Engineered for PHI and built to the security frameworks a healthcare CISO already trusts. <a href="/security.html" style="color:var(--accent)">See our security posture & standards →</a></p>
</div>
</section>
<!-- ───────────────────────────── positioning ───────────────────────────── -->
<section class="section section--alt section--tight" style="padding-bottom:36px">
<div class="container center">
<p class="lead" style="font-size:1.28rem;color:var(--text)">A focused, open-source alternative to expensive legacy engines — for any interface you run, whatever the protocol or message type. Every message is delivered reliably and <b>never silently dropped</b>, your team <b>stays in control</b> instead of locked into a vendor's platform, and you can <b>stand it up fast and migrate your existing interfaces over</b> with AI assistance.</p>
</div>
</section>
<!-- ───────────────────────────── differentiators ───────────────────────────── -->
<section class="section">
<div class="container">
<div class="center" style="margin-bottom:42px">
<span class="eyebrow">Why MessageFoundry</span>
<h2>Built for analysts and developers alike</h2>
<p class="lead center">You don't have to be a developer to get started — setup wizards in the VS Code extension generate the wiring for you. And because Python is one of the easiest languages to learn, your interfaces stay readable and reviewable as your team grows into them.</p>
</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="M9.4 16.6 4.8 12l4.6-4.6L8 6l-6 6 6 6zm5.2 0L19.2 12l-4.6-4.6L16 6l6 6-6 6z"/></svg></span>
<h3>Your config lives in git</h3>
<p>Every interface change is a reviewable diff in version control — see who changed what, roll back in seconds, and ship with confidence. Nothing critical is hidden inside a database.</p>
</div>
<div class="card">
<span class="ico"><svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M12 3C7 3 3 4.8 3 7v10c0 2.2 4 4 9 4s9-1.8 9-4V7c0-2.2-4-4-9-4zm7 14c0 .9-2.8 2-7 2s-7-1.1-7-2v-2.3c1.7 1 4.3 1.5 7 1.5s5.3-.5 7-1.5V17zm0-5c0 .9-2.8 2-7 2s-7-1.1-7-2V9.7c1.7 1 4.3 1.5 7 1.5s5.3-.5 7-1.5V12z"/></svg></span>
<h3>Ordered, reliable delivery — no broker</h3>
<p>Durable delivery, in order to each destination — retried automatically, replayable on demand, and active-passive for high availability. No separate broker to install, run, or babysit.</p>
</div>
<div class="card">
<span class="ico"><svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M12 2 4 5v6c0 5 3.4 9.4 8 11 4.6-1.6 8-6 8-11V5l-8-3zm0 10.9h6c-.5 3.6-2.8 6.8-6 8V12.9H6V6.3l6-2.2v8.8z"/></svg></span>
<h3>Patient data protected by default</h3>
<p>Built to recognized standards — NIST SSDF, the HIPAA Security Rule, and OWASP ASVS Level 3 — with authentication, least-privilege access, a tamper-evident audit trail, and encryption on by default. PHI is protected from day one, not bolted on later.</p>
<p style="margin:10px 0 0"><a href="/security.html">Our security, standards & PHI posture →</a></p>
</div>
<div class="card">
<span class="ico"><svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M3 13h2l2 5 4-12 2 7h2l1.5-3H21v-2h-4.7L15 13l-2-7L9 18l-2-5H3z"/></svg></span>
<h3>Handles real-world, messy HL7</h3>
<p>Real-world HL7 is rarely textbook-perfect. MessageFoundry keeps quirky, non-conformant messages flowing — and applies strict validation only where you choose to turn it on.</p>
</div>
<div class="card">
<span class="ico"><svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M3 4h18v4H3V4zm0 6h18v4H3v-4zm0 6h18v4H3v-4zM6 5.5A.5.5 0 1 0 6 6.5.5.5 0 0 0 6 5.5zm0 6a.5.5 0 1 0 0 1 .5.5 0 0 0 0-1zm0 6a.5.5 0 1 0 0 1 .5.5 0 0 0 0-1z"/></svg></span>
<h3>Never lose track of a message</h3>
<p>Every message that arrives is persisted the moment it lands, then tracked to a clear outcome as it's processed in order — so nothing is silently dropped, and your counts reflect what really happened.</p>
</div>
<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>Tools for your whole team</h3>
<p>A monitoring console to watch interfaces live and replay with a click, plus a VS Code extension with setup wizards — so analysts and developers can configure, test, and operate from familiar tools.</p>
</div>
</div>
</div>
</section>
<!-- ───────────────────────────── security & standards ───────────────────────────── -->
<section class="section section--alt">
<div class="container">
<div class="center" style="margin-bottom:38px">
<span class="eyebrow">Security & standards</span>
<h2>Built to the standards your security team already trusts</h2>
<p class="lead center">For PHI, security is the foundation — not a feature. MessageFoundry follows a published <b>Secure Development Standard</b> and is aligned with the frameworks a healthcare CISO already knows, so the trust conversation starts from common ground.</p>
</div>
<div class="grid grid-2" style="margin-bottom:30px">
<div class="card">
<h3>NIST SSDF <span class="badge" style="vertical-align:middle">800-218</span></h3>
<p>Built through a secure development lifecycle — threat-modeled per interface, automatically reviewed in CI, and secure by default.</p>
</div>
<div class="card">
<h3>NIST 800-115</h3>
<p>Security testing in CI — SAST, dependency, and secret scanning on every build. An independent external review and penetration test are planned after Early Access.</p>
</div>
<div class="card">
<h3>NIST 800-66 Rev. 2</h3>
<p>Controls mapped to the <b>HIPAA Security Rule</b> — access control, audit, integrity, and transmission security.</p>
</div>
<div class="card">
<h3>OWASP ASVS 5.0 <span class="badge" style="vertical-align:middle">Level 3</span></h3>
<p>Self-assessed against the highest application-security assurance level — ASVS Level 3 — for software handling the most sensitive data. All 345 L3 requirements are assessed, and the partials still open are being closed by shipping real controls rather than reclassified away. A self-assessment, not an external audit.</p>
</div>
</div>
<div class="center">
<p class="lead center" style="max-width:64ch;margin:0 auto 24px">Secure by default — TLS on by default, encryption on, least-privilege access, a tamper-evident audit trail, and no PHI in logs — with sign-in via local accounts or Active Directory (LDAP). The software <b>supports a HIPAA-compliant deployment</b>; you stay in control of your environment.</p>
<div class="btn-row center">
<a class="btn btn-primary" href="/security.html">See our security posture →</a>
<a class="btn btn-secondary" href="/assets/MessageFoundry-Secure-Development-Standards.pdf" target="_blank" rel="noopener">Read the Standards (PDF)</a>
</div>
</div>
</div>
</section>
<!-- ───────────────────────────── graph model ───────────────────────────── -->
<section class="section section--dark">
<div class="container grid grid-2" style="align-items:start">
<div>
<span class="eyebrow">Why switch</span>
<h2>Ditch legacy prices and lock-in</h2>
<p class="lead">Open source and self-hosted, so your costs don't climb every time you add an interface, and nothing is locked inside a vendor's runtime or contract.</p>
<p style="margin-top:18px"><a href="/comparison.html#why-leave" style="color:var(--accent);font-weight:650">See why teams are leaving legacy engines →</a></p>
</div>
<ul class="feature-list">
<li><b>No per-interface licensing</b> — it fits into your environment, and you add interfaces without a bigger bill each time.</li>
<li><b>Migrate with AI, not a project</b> — the assistant drafts MessageFoundry equivalents from your existing channels, so porting can be far less work than re-platforming onto another proprietary engine.</li>
<li><b>Own your stack</b> — your configuration lives in your git and your messages in your database; switch on your terms, with no contract lock-in.</li>
<li><b>Ships through your own CI/CD</b> — review interface changes in pull requests and gate them with automated tests, like the rest of your software.</li>
<li><b>Easy to configure, powerful when needed</b> — setup wizards generate the config for you, with full Python control whenever a case calls for it.</li>
</ul>
</div>
</section>
<!-- ───────────────────────────── cta ───────────────────────────── -->
<!-- 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>What is MessageFoundry?</h3><p>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 — and runs entirely on your own infrastructure.</p></div>
<div class="faq-item"><h3>Is MessageFoundry free and open source?</h3><p>Yes. The engine is free and open source under AGPL-3.0-or-later, installable from PyPI with pip install messagefoundry. A low-cost commercial license is also available from the non-profit for organizations that can't use copyleft terms.</p></div>
<div class="faq-item"><h3>What protocols and message types does MessageFoundry support?</h3><p>It connects a wide range of protocols and message types, with deep HL7 v2 support — plus FHIR, X12/EDI, and DICOM — over transports including MLLP (with TLS), HTTP/REST, SOAP, files, SFTP, and databases.</p></div>
<div class="faq-item"><h3>Is MessageFoundry an alternative to legacy interface engines?</h3><p>Yes. MessageFoundry is a modern, open-source alternative to legacy healthcare interface engines such as Mirth Connect, Rhapsody, and Corepoint. It is self-hosted and Python-native — interfaces are plain Python under version control — with no per-interface licensing.</p></div>
<div class="faq-item"><h3>Where does my data live?</h3><p>On your own servers. MessageFoundry is self-hosted on-premises or in your private cloud, so PHI never leaves your infrastructure. It starts zero-config on SQLite and scales to PostgreSQL or SQL Server.</p></div>
<div class="faq-item"><h3>How much message volume can MessageFoundry handle?</h3><p>Comfortably more than a single hospital's interface needs, with headroom to scale. On anonymized, representative message traffic, one inbound interface sustains a measured ~50 messages per second on commodity hardware — which works out to roughly 180,000 in a peak hour. A hospital's full ADT feed peaks at only around 1-2 messages per second, so a single interface carries that workload with room to spare, and interfaces scale out horizontally for higher volumes. Real-world throughput depends on your transforms, storage, and hardware. Whatever the rate, every message is persisted before it's acknowledged and delivered in order per interface, at-least-once — so messages aren't silently dropped.</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": "What is MessageFoundry?",
"acceptedAnswer": {
"@type": "Answer",
"text": "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 — and runs entirely on your own infrastructure."
}
},
{
"@type": "Question",
"name": "Is MessageFoundry free and open source?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. The engine is free and open source under AGPL-3.0-or-later, installable from PyPI with pip install messagefoundry. A low-cost commercial license is also available from the non-profit for organizations that can't use copyleft terms."
}
},
{
"@type": "Question",
"name": "What protocols and message types does MessageFoundry support?",
"acceptedAnswer": {
"@type": "Answer",
"text": "It connects a wide range of protocols and message types, with deep HL7 v2 support — plus FHIR, X12/EDI, and DICOM — over transports including MLLP (with TLS), HTTP/REST, SOAP, files, SFTP, and databases."
}
},
{
"@type": "Question",
"name": "Is MessageFoundry an alternative to legacy interface engines?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. MessageFoundry is a modern, open-source alternative to legacy healthcare interface engines such as Mirth Connect, Rhapsody, and Corepoint. It is self-hosted and Python-native — interfaces are plain Python under version control — with no per-interface licensing."
}
},
{
"@type": "Question",
"name": "Where does my data live?",
"acceptedAnswer": {
"@type": "Answer",
"text": "On your own servers. MessageFoundry is self-hosted on-premises or in your private cloud, so PHI never leaves your infrastructure. It starts zero-config on SQLite and scales to PostgreSQL or SQL Server."
}
},
{
"@type": "Question",
"name": "How much message volume can MessageFoundry handle?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Comfortably more than a single hospital's interface needs, with headroom to scale. On anonymized, representative message traffic, one inbound interface sustains a measured ~50 messages per second on commodity hardware — which works out to roughly 180,000 in a peak hour. A hospital's full ADT feed peaks at only around 1-2 messages per second, so a single interface carries that workload with room to spare, and interfaces scale out horizontally for higher volumes. Real-world throughput depends on your transforms, storage, and hardware. Whatever the rate, every message is persisted before it's acknowledged and delivered in order per interface, at-least-once — so messages aren't silently dropped."
}
}
]
}
</script>
<section class="section">
<div class="container">
<div class="cta-band">
<h2>Get off legacy on your own terms.</h2>
<p class="lead center" style="color:var(--muted-dk)">Configure interfaces with guided wizards, keep full Python control when you need it, and run it in your own environment — with no per-interface fees.</p>
<div class="btn-row center">
<a class="btn btn-primary" href="/getting-started.html">Get started</a>
<a class="btn btn-secondary" href="/guides/">Browse the guides →</a>
<a class="btn btn-ghost" href="https://github.com/MEFORORG/MessageFoundry" target="_blank" rel="noopener">Star it on GitHub ↗</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>