Exchange payer-to-payer patient data using Da Vinci PDex and resolve member attribution between old and new payers

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

Steps

  1. Initiate the payer-to-payer exchange: the new payer (requestor) must first establish the member's identity at the old payer using a member matching operation — POST to '$member-match' on the old payer's FHIR endpoint with a Parameters resource containing CoverageToMatch and MemberPatient
  2. Receive the '$member-match' response with a matched Patient resource and a new Coverage resource representing the old payer's member identifier; use these to authorize the data request
  3. Request clinical and claims data from the old payer using FHIR bulk export or individual resource queries scoped to the matched patient; PDex specifies ExplanationOfBenefit, Patient, Coverage, MedicationDispense, Observation, Condition, and Procedure as the primary resource types
  4. Map the received data to your internal FHIR model; normalize coding systems (ICD-10, CPT, NDC, RxNorm) and resolve any duplicate or conflicting records against your existing member data
  5. Store the exchanged data in your FHIR server and surface it to providers via your Patient Access API within the timelines required by the CMS interoperability rule
  6. Maintain an audit log of all PDex exchanges including the requesting entity, date, data types exchanged, and member consent status

Known gotchas

Related routes

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
Execute the Da Vinci PDex $member-match operation to identify a member across payer systems during payer-to-payer exchange
hl7.org/fhir/us/davinci-pdex · 6 steps · unrated
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

Give your agent this knowledge — and 15,500+ 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