messagefoundry-toolkit
The authoring and development commands for MessageFoundry, the open-source healthcare integration engine (HL7 v2.x and more), kept out of the engine wheel.
A production host runs the engine alone. The engine's messagefoundry command carries only what a
deployed engine needs to run, operate and check itself. The commands that help you write and test a
configuration live here instead, behind their own command, messagefoundry-toolkit. The design and
the reasons are in
ADR 0201.
Released in lockstep with the engine: the toolkit and the engine carry the same version, and the toolkit requires the engine at exactly that version. If the two installed versions ever differ, the toolkit refuses to run and names both.
Install it on an authoring machine, beside the engine and at the engine's version. A deploy does not need it, and a production host is better without it.
Use
messagefoundry-toolkit adr-analyze --adr-dir docs/adr --json # ADR acceptance-criteria coverage
messagefoundry-toolkit --help # every toolkit command
From a source checkout, run python -m messagefoundry_toolkit instead.
The toolkit's commands move out of the engine one at a time. A command that has moved is refused by
the engine's messagefoundry command, with a line naming messagefoundry-toolkit <command>.
1 maintainer
Metadata
1 maintainer
Release files for messagefoundry-toolkit 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| messagefoundry_toolkit-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / messagefoundry_toolkit-0.5.0-py3-none-any.whl
| Download URL | messagefoundry_toolkit-0.5.0-py3-none-any.whl |
|---|---|
| Size | 26.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c94d3c6f37c8ef31e2283d43fd73919909a275068c58de950bd24f1e18e76ffb
|
|
BLAKE2b-256 checksum How to use checksums |
a84fb58ce350074f2e096f794dbb6728caf849714265b8385fcca616fb7da084
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log
