Exchange a prior coverage decision bundle between payers using the Da Vinci PCDE (Payer Coverage Decision Exchange) IG

domain: hl7.org · 6 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. Review the PCDE Coverage Transition document structure: a FHIR Document Bundle containing a Composition that sections activeTreatment (CarePlan, prior Coverage, supporting Observations/DiagnosticReports) and otherInformation
  2. Confirm the source payer's FHIR server supports the PCDE Composition profile (profile-composition) and that the document can be assembled as a Bundle of type 'document'
  3. Use the Da Vinci HRex Task-based exchange mechanism: the receiving payer POSTs a Task resource to the source payer requesting the Coverage Transition document, referencing the member via a Coverage or Patient identifier
  4. Monitor Task.status polling until it reaches 'completed'; retrieve the document Bundle from Task.output.valueReference
  5. Validate the received Bundle against the PCDE Bundle profile and check that mandatory sections are present before ingesting into the new payer's system
  6. Optionally use the PDex $member-match operation beforehand to confirm member identity across payer systems before initiating the PCDE Task request

Known gotchas

Related routes

Implement Da Vinci PDex payer-to-payer bulk data exchange to transfer a member's clinical data from a prior payer to a new payer
hl7.org/fhir/us/davinci-pdex · 6 steps · unrated
Implement the Da Vinci PDex Payer Data Exchange to enable a new payer to request a member's clinical and claims history from a prior payer during the plan-to-plan data exchange workflow
hl7.org/fhir/us/davinci-pdex · 5 steps · unrated
Implement Da Vinci PDex Provenance for clinical data exchanged between payers and providers
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