Crates

Core

The standards themselves, and the umbrella crate that re-exports them.

Transports

Getting messages across a network, and answering them.

Format conversions

ER7 in both directions against both target formats.

Tooling and helpers

The macros, the dictionary builder, and the shared XML reader.

And one crate outside the workspace

er7 is the ER7 encoding layer: delimiters, escapes, paths, byte-for-byte rendering, and batch splitting. It has no dependencies of its own, and it lives in its own repository, in its own organization, rather than in this workspace — because plenty of people want the encoding without the dictionary.

use er7::Message;

// Pipes and carets, with no opinion about what any field means.
let message = er7::parse(text)?;
assert_eq!(message.query("PID-5.1")?.as_deref(), Some("SMITH"));

You rarely add it directly. hl7-2 and the conversion crates re-export what you need, and hl7-2's byte-for-byte round-trip guarantee is really er7's guarantee, kept intact.

All of them, at a glance

Versions are the latest published at the time of writing, shown so you can gauge how settled a crate is — not as a constraint to copy. See Versions and compatibility, and Architecture for why the seams fall where they do.