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
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'
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
Monitor Task.status polling until it reaches 'completed'; retrieve the document Bundle from Task.output.valueReference
Validate the received Bundle against the PCDE Bundle profile and check that mandatory sections are present before ingesting into the new payer's system
Optionally use the PDex $member-match operation beforehand to confirm member identity across payer systems before initiating the PCDE Task request
Known gotchas
PCDE is built on top of HRex and PDex — you need the HRex member attribution and OAuth 2.0 payer-to-payer authorization in place before the Task-based document request can succeed
The Coverage Transition document is a FHIR Document Bundle (type='document'), not a transaction or collection Bundle — servers that don't support document Bundles will reject it
PCDE STU 1 is based on FHIR R4 and is distinct from PDex payer-to-payer bulk exchange; do not conflate the two — PCDE carries a structured coverage-decision document, not raw clinical NDJSON
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp