Early Access
Can Your System Use the Attachment It Received?
Redix checks the transaction, verifies the received attachment payload, and records the evidence used to associate it with the related claim or review.
Choose a Synthetic Scenario
Curated, synthetic X12 275 scenarios. Each runs the real pipeline end to end — validate, extract each attachment, build the Processing Manifest, and (for X314 claims) evaluate association against the related transaction context:
Runs on the native Redix AnyToAny engine (v9.1) for this early-access demonstration; production deployments use the supported production release appropriate to their environment. Content-neutral: the demo shows each attachment's metadata and hash, never the document bytes.
275 Attachment Processing Report —
275 Attachment Processing Report
One report. Three operational checks. — did the 275 pass structural validation, does the received payload match what was declared, and do the identifiers/context support association with the related transaction.
Source transactions — what went in
Display copy only — the
BDS03 Base64 payload is elided for readability (its declared length is preserved). The pipeline processed the complete synthetic payload. The 277/837 are separate synthetic transactions supplied to the correlation service, not inferred from the 275.Validation (X12)
-
Extraction
-
Attachments
-
Correlation
-
Engine
-
Standard extraction — validation & content-neutral attachment recovery
| LX | Attachment control # | Reported type | Decoded bytes | SHA-256 | Extraction | Security |
|---|
Successful extraction confirms Redix recovered the embedded bytes. It does not establish clinical validity, payer acceptance, delivery, or adjudication. “Reported type” is the declared/observed type, not a verified file signature.
Standard processing completes above. Managed processing adds the Processing Manifest (Redix M5) and the receive-side correlation results below.
Managed — receive-side association
Association is receive-side only. A match does not mean the attachment was accepted, adjudicated, or will be paid. Every PARTIAL / AMBIGUOUS / UNMATCHED result routes to a human exception queue.
The Processing Manifest is Redix's structured, machine-readable record of the transaction and each attachment — declared vs. actual size, SHA-256 fingerprint, extraction result, and captured association context — that downstream systems use for automation, troubleshooting, and operational review.
The native X12 999 Implementation Acknowledgment (
USE999=1; IK5/IK3/IK4) is the machine-readable acknowledgment supporting the validation result above.Technical scope & limitations
Supports 006020X314 claim attachments and 006020X316 services-review attachments. X314 is adopted under CMS-0053-F, with compliance required by May 26, 2028. X316 is an adjacent prior-authorization documentation profile and is not part of the CMS-0053-F mandate. This is an Early Access prototype; broader profile regression testing is in progress.
Built from licensed X12 TR3 specifications and capable of producing native X12 999 acknowledgments. Redix healthcare transaction technology has supported a Fortune 500 provider relationship for approximately two decades.