Execute Da Vinci PDex $member-match to locate a member across payer systems
domain: hl7.org/fhir/us/davinci-pdex · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Construct the $member-match Parameters resource with the MemberPatient parameter (Patient demographic data) and the CoverageToMatch parameter (old payer coverage details)
POST the Parameters to the new payer's Patient/$member-match endpoint using SMART Backend Services credentials
Parse the response Parameters resource to extract the matched member identifier returned by the new payer
Use the matched identifier to request the member's prior coverage data via the PDex member history operation
Store the matched identifier for subsequent data retrieval requests within the payer-to-payer exchange flow
Known gotchas
$member-match is defined on the Patient resource type endpoint, not on a specific Patient instance; posting to a patient instance URL is incorrect
The operation may return HTTP 422 if the member cannot be uniquely matched; implement handling for both no-match and multiple-match error conditions described in the OperationOutcome
CoverageToMatch must include the subscriberId as it appeared on the prior plan; mismatched formatting (leading zeros, hyphens) frequently causes match failures
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?