HERMES EDI

Abstract

Hermes EDI is a HIPAA X12 5010 837P/837I parser and 999 acknowledgement generator, shipped as a standalone Python library, a CLI, and a polling daemon. The pipeline runs Bronze → Silver → Gold → Platinum: each layer carries a defined PHI gradient (Bronze HIGH down to Platinum MINIMIZED) and a cryptographically anchored lineage chain (SHA-256 + UUID + monotonic_ns + parent_layer_id + runtime_id). Validation runs against the X12 5010 TR3 implementation guide (envelope reconciliation, sequence rules, element rules), and the 999 it emits is a complete X12 5010X231A1 acknowledgement, not a courtesy ping. A later pass added 276/277 claim-status validation, checked against an independent parser as a differential oracle.

Provenance

Came out of years of HIPAA X12 Electronic Data Interchange work in enterprise healthcare: the place where compliance, throughput, and human-readable errors all have to be true at once, and where most libraries nail one and fail the other two.

Declassified

It's public on GitHub under Apache 2.0, and the pattern is the whole point. Most Electronic Data Interchange libraries flatten PHI exposure to a yes/no, treat validation as pass/fail, and send back 999s that don't really mean anything. Hermes treats PHI as a gradient, validation as a typed pipeline that keeps error provenance at every layer, and the 999 as a real acknowledgement against the TR3 spec. 1,718 tests, mypy --strict clean across 109 production modules, daemon mode for SFTP polling with optional SQLAlchemy persistence, and no licensed code sets embedded in the distribution. What's not in the repo: the partner-specific profiles, the deployment lineage from the middleware era, and the production tuning that kept it standing at enterprise scale.

Also in OPEN

• ROLLTHATUP Rollups across lookups. No code, no master-detail.
• HERMES BRIDGE Autonomy with the brakes wired in first.