- Shipped
- October 25, 2026 at 3:30 PM UTC
- Author
- Kamo
- Commit
- bc783e1
No clearinghouse contract exists, so practices upload X12 files to a portal by hand. This builds that path end to end: - 837P (005010X222A1) for one or many ready claims: 1000A/B, 2000A/2010AA with NPI, tax id and a street (never PO box) address with ZIP+4, 2000B/2010BA/BB, 2000C/2010CA for a dependant, 2300 CLM/HI with CLM01 = our claim number, 2310B rendering, 2400 SV1/DTP/REF*6R. Pure writer pinned by golden files. - Validation before building, in plain language naming where to fix it; a file with a known problem is never built and spends no control number. - ISA13/GS06/ST02 from a per-practice atomic counter (REQUIRES_NEW bean). - Batches stored byte for byte with SHA-256; re-download is the identical file; confirming the upload moves claims to SENT via CLEARINGHOUSE_FILE with the file as the reference; a never-uploaded file is set aside, not deleted. - 999 and 277CA imports mark files and claims accepted/rejected with reasons. - 835 import creates one remittance per payment (trace unique), review shows matched/unmatched/patient responsibility, posting is additive (reversals), matched by REF*6R then code+modifiers, PLB and unmatched money stay unapplied, posted once (conditional UPDATE). - Small X12 tokenizer/writer with separators from the ISA; files never logged; builds and downloads audited fail-closed per claim as PAYMENT exports.