Implement Da Vinci HRex member attribution (member-match) and consent exchange to authorize payer-to-payer data sharing before initiating a PDex data request
domain: hl7.org/fhir/us/davinci-hrex · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to /Patient/$member-match on the old payer's FHIR server with a Parameters resource containing MemberPatient (demographic + coverage identifiers) and CoverageToMatch
Extract the matched member identifier from the single-match response Parameters resource; a multi-match or no-match returns OperationOutcome — handle both error cases
Create a FHIR Consent resource on the new payer's system documenting the member's authorization for data exchange, referencing the matched patient and payer as actors
Include the Consent resource reference when constructing the PDex data request so the old payer can verify authorization before returning data
Verify the returned Consent status is active before proceeding with data retrieval
Known gotchas
$member-match is defined in HRex and reused by PDex; confirm you are calling it on the correct payer endpoint — the new payer calls the old payer's endpoint, not its own
Demographic matching tolerance is implementation-specific; a fuzzy match that returns multiple candidates results in a 422 OperationOutcome, not multiple results — the caller must refine the query
The Consent resource must reference the specific coverage period being exchanged; a Consent without date scoping may be rejected by the old payer's authorization layer
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