Review the Da Vinci HRex IG (hl7.org/fhir/us/davinci-hrex) to understand the role of Consent and Provenance profiles in authorizing and documenting payer-to-payer data exchange.
Construct a HRex Consent resource representing the member's consent to share data between payers, setting Consent.status to 'active', Consent.scope to the appropriate value, and Consent.patient to the member's Patient resource.
Populate Consent.performer (the consenting member or their representative), Consent.organization (the payer receiving consent), and Consent.dateTime (the date consent was given), using the HRex Consent profile constraints.
Transmit the Consent resource to the prior payer as part of the payer-to-payer data exchange request (e.g., via $member-match input Parameters) to authorize the data release.
For data received from another payer, construct a HRex Provenance resource to document the data origin: set Provenance.target to the received resources, Provenance.agent to the prior payer's Organization, and Provenance.recorded to the exchange timestamp.
Store the Provenance resources alongside the ingested clinical and claims data so that downstream consumers can identify which data originated from a prior payer and distinguish it from data generated by the current payer.
Known gotchas
HRex Consent is not a full clinical consent management system — it is a lightweight mechanism for authorizing a specific payer-to-payer exchange; organizations with complex consent requirements may need to supplement HRex Consent with their own consent infrastructure.
Provenance.agent.type must use codes from the appropriate value set to correctly categorize the payer as the data source — using a generic agent type (e.g., 'author') when the agent is a transmitter loses important provenance context.
The HRex IG is a foundational IG that other Da Vinci IGs build upon — some HRex profiles may be further constrained by PDex, PAS, or other IGs; always check the derived IG's constraints in addition to HRex base constraints.
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