Submit a Da Vinci CDex attachment bundle at the system level

domain: hl7.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

In-depth guide

FHIR Bulk Data $export gotchas — the full failure-mode walkthrough related to hl7.org, checked against official docs, with linked verified routes.

Steps

  1. Confirm you are implementing the CDex STU2+ $submit-attachment operation — this is a system-level or base-URL operation, not a Claim-instance operation.
  2. Construct a Parameters resource containing: AttachTo (the claim or prior auth reference), request (the X12 277ADRD or payer-assigned TrackingId), payerId, and one or more Attachment parameters each holding a DocumentReference or Binary resource.
  3. POST the Parameters resource to [base]/$submit-attachment where [base] is the payer's FHIR server base URL (e.g., https://payer.example.org/fhir/$submit-attachment) — not [base]/Claim/$submit-attachment.
  4. Handle the HTTP 200 response with a Parameters body; check for OperationOutcome inside the response to detect business-level rejections even on HTTP 200.
  5. Retain the correlation identifiers returned so you can reconcile submission with the eventual adjudication or prior authorization decision.

Known gotchas

Related routes

Implement a Da Vinci CDex Task-based solicited attachment exchange
hl7.org · 5 steps · unrated
Implement the Da Vinci CDex attachment request workflow for both solicited and unsolicited attachments
healthcare-fhir · 6 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans