Attachments have a long-standing wire format and a newer FHIR one, and both carry the same clinical evidence. This card is about the FHIR path and how it sits beside the X12 baseline.
The X12 baseline. CMS-0053-F adopts X12N 275/277 (v6020) as the HIPAA transaction for claims attachments — the 277 requests the additional documentation, the 275 carries it, with HL7 C-CDA / Attachments IG content inside. This is the administrative-transaction lineage EDI clearinghouses have run for years.
The FHIR cousin. Da Vinci's Clinical Data Exchange (CDex) defines a $submit-attachment operation: a payer or intermediary asks for supporting documentation and the provider system returns it as FHIR resources — solicited or unsolicited, tied to a claim or a prior-auth request. It is the same evidence problem PAS and DTR target, expressed as a FHIR operation instead of an EDI transaction.
The transport-variance lesson. The payload is the clinical evidence; the transport is a choice — X12 275/277 on one path, CDex $submit-attachment on the other, with C-CDA or FHIR content riding inside. The mandate fixes the X12 transaction; the FHIR path is where the burden-reduction IGs are converging. Which one a given payer actually implements is the variance worth watching — and the mandate-stack-9115-0057-0053 and why-payers-are-moving cards frame why both exist at once. The dated compliance milestone lives on the watch-list.
What ImOnFHIR does with it: we exercise PAS/DTR-shaped evidence payloads on the FHIR path and note X12 275 as a future inbound shape for attachment metadata. We name the transaction sets (275/277 v6020) and point, don't host: no licensed X12 TR3, C-CDA, or CPT bytes ship here.