Da Vinci Payer Data Exchange, published by HL7 International / Financial Management. This guide is not an authorized publication; it is the continuous build for version 2.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-epdx/ and changes regularly. See the Directory of published versions

Handling Data Provenance

Previous Page - PDex Implementation, Actors, Interactions, Data Payloads and Methods

Handling Provenance is an essential element in establishing confidence and trust as data is exchanged with other parties. The Provenance resource is used to document the source and handling of data. It documents the chain of custody of the information.

The PDex IG will define PDex Provenance examples that meet the needs of Health Plans. The value sets, including any new codes required, used to enable Health Plans to express Provenance Records will be supplied to the Security Work Group and others developing Provenance profiles as examples of real-world requirements.

Provenance requirements for the Payer Community may be a super-set of those of the Provider-focused Argonaut community.

pdex-84: Health Plans SHOULD accept and retain Provenance records received with data based on Member-authorized Payer-to-Payer exchange. ^§21

pdex-85: Health Plans SHOULD accept and retain Provenance records received with data from sources other than Member-authorized Payer-to-Payer exchange. ^§22

pdex-86: When a Health Plan forwards information as a FHIR Resource it SHOULD create related Provenance record(s) to reflect the original source of the data. ^§23

A Provenance resource describing the upstream origin (Author or Source) of each member-related resource SHOULD be provided with that resource when the Health Plan's FHIR API serves it — particularly when the requester adds the _revinclude=Provenance:target parameter to a search query. ^§pdex-87 This per-resource Provenance is in addition to the per-exchange Transmitter Provenance required by pdex-127 (see Overview and PDex Provenance for the full distinction); it is not a substitute for pdex-127.

This guide provides a pdex-provenance resource that is customized to the needs of the payer by focusing on their role as a transmitter and not originator of data.

Next Page - Provider Access API (v1)