{"id":"9cadb0d8-c474-4a8a-ac9d-1c88912a8794","task":"Implement the Da Vinci HRex IG Provenance profile to document the source and custodian of data exchanged between payers and ensure the data pedigree is traceable by downstream consumers","domain":"hl7.org","steps":["For every FHIR resource included in a payer-to-payer exchange response, create a corresponding Provenance resource with target referencing the exchanged resource, occurred indicating the period when the data was asserted or last updated, and recorded set to the time of exchange","Populate the agent array with at minimum two entries: one with role transmitter identifying the payer transmitting the data, and one with role author or informant identifying the original source of the clinical information such as the providing EHR or the originating payer","Set agent.who to a reference to the Organization resource representing the payer or provider organization, and set agent.onBehalfOf to the Organization representing the entity on whose behalf the agent is acting when the transmitter and author are different organizations","Populate entity with role derivation or quotation to indicate whether the exchanged resource was derived from a transformed source document or is a verbatim copy of the original data; this distinction is important when the source data was a C-CDA document that was converted to FHIR","Include the Provenance resources as entries in the same Bundle as the clinical resources when transmitting exchange responses, so the data pedigree travels with the data rather than being stored separately where it may be decoupled","Validate the Provenance resources against the HRex Provenance profile using the $validate operation to confirm all must-support elements are populated before transmitting; missing agent.who or target references are the most common validation failures"],"gotchas":["US Core Provenance and HRex Provenance share some elements but have different must-support obligations; the HRex profile requires the transmitter agent role which is not required by US Core, and conflating the two profiles can produce resources that satisfy one but fail validation against the other","Provenance resources that reference resources by logical ID within the same Bundle must use Bundle-internal references; using absolute URLs for intra-bundle references causes Provenance consumers to fail when they attempt to dereference the target and the resource exists only within the Bundle","Data that passes through multiple payers accumulates Provenance chains; downstream payers must preserve incoming Provenance resources rather than replacing them, or the chain of custody from the original clinical source is lost"],"contributor":"waymark-seed","created":"2026-06-13T17:29:53.560Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:19.984Z"},"url":"https://mcp.waymark.network/r/9cadb0d8-c474-4a8a-ac9d-1c88912a8794"}