Da Vinci Payer Data Exchange
2.1.1 - STU 2.1

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.1.1 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

## PDex Implementation Guide

Page standards status: Informative

Previous Page - Introduction

Official URL: http://hl7.org/fhir/us/davinci-pdex | Version: 2.1.0
NPM package name: hl7.fhir.us.davinci-pdex | ComputableName: DaVinciPayerDataExchange
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License |
Other Identifiers: OID:2.16.840.1.113883.4.642.40.8 |

- XML
- JSON

### Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.us.davinci-pdex.r4) and R4B (hl7.fhir.us.davinci-pdex.r4b) are available.

### IG Dependencies

This IG Contains the following dependencies on other IGs.

IG | Package | FHIR | Comment
--- | --- | --- | ---
Da Vinci Payer Data Exchange | hl7.fhir.us.davinci-pdex#2.1.1 | R4 |
US Core Implementation Guide | hl7.fhir.us.core#7.0.0 | R4 | Defines USCDI v4 EHR expectations on a range of resources that will be passed to and/or queried by CRD servers.
HL7 Terminology (THO) | hl7.terminology.r4#5.5.0 | R4 |
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.0.0 | R4 |
VSAC | us.nlm.vsac#0.18.0 | R4 |
Structured Data Capture | hl7.fhir.uv.sdc#3.0.0 | R4 |
PHINVads | us.cdc.phinvads#0.12.0 | R4 |
US Core (Reuse Wrapper) | hl7.fhir.us.core.v610#6.1.0 | R4 | Defines USCDI v3 EHR expectations on a range of resources that will be passed to and/or queried by CRD servers
US Core Implementation Guide | hl7.fhir.us.core#6.1.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#5.0.0 | R4 |
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#1.0.0 | R4 |
Bulk Data Access IG | hl7.fhir.uv.bulkdata#2.0.0 | R4 |
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.1.0 | R4 |
VSAC | us.nlm.vsac#0.11.0 | R4 |
IHE FormatCode Vocabulary | ihe.formatcode.fhir#1.1.0 | R4 |
US Core (Reuse Wrapper) | hl7.fhir.us.core.3.1.1#3.1.1 | R4 | Defines USCDI v1 EHR expectations on a range of resources that will be passed to and/or queried by CRD servers.
US Core | hl7.fhir.us.core#3.1.1 | R4 |
Da Vinci Health Record Exchange (HRex) | hl7.fhir.us.davinci-hrex#1.1.0 | R4 | Defines common conformance rules across all Da Vinci IGs, as well as additional constraints and profiles beyond U.S. Core
HL7 Terminology (THO) | hl7.terminology.r4#6.1.0 | R4 |
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#5.1.0 | R4 |
US Core (Reuse Wrapper) | hl7.fhir.us.core.v311#3.1.1 | R4 |
VSAC | us.nlm.vsac#0.19.0 | R4 |
CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) | hl7.fhir.us.carin-bb#2.1.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#6.2.0 | R4 |
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#5.2.0 | R4 |
VSAC | us.nlm.vsac#0.21.0 | R4 |
Da Vinci - Coverage Requirements Discovery | hl7.fhir.us.davinci-crd#2.1.0 | R4 |
Da Vinci Prior Authorization Support (PAS) FHIR IG | hl7.fhir.us.davinci-pas#2.1.0 | R4 |
Da Vinci - Coverage Requirements Discovery | hl7.fhir.us.davinci-crd#2.0.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#5.3.0 | R4 |
Da Vinci Health Record Exchange (HRex) | hl7.fhir.us.davinci-hrex#1.0.0 | R4 |
Security for Scalable Registration, Authentication, and Authorization | hl7.fhir.us.udap-security#0.1.0 | R4 |
Subscriptions R5 Backport | hl7.fhir.uv.subscriptions-backport.r4#1.1.0 | R4 |
CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) | hl7.fhir.us.carin-bb#2.0.0 | R4 |
VSAC | us.nlm.vsac#0.7.0 | R4 |
Da Vinci - Member Attribution (ATR) List | hl7.fhir.us.davinci-atr#2.1.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#6.3.0 | R4 |
Da Vinci PDex Plan Net | hl7.fhir.us.davinci-pdex-plan-net#1.2.0 | R4 |
Da Vinci Clinical Data Exchange (CDex) | hl7.fhir.us.davinci-cdex#2.1.0 | R4 |
Da Vinci - Documentation Templates and Rules | hl7.fhir.us.davinci-dtr#2.1.0 | R4 |
National Directory of Healthcare Providers & Services (NDH) Implementation Guide | hl7.fhir.us.ndh#1.0.0 | R4 |
Security for Scalable Registration, Authentication, and Authorization | hl7.fhir.us.udap-security#1.0.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#4.0.0 | R4 |
FHIR Tooling Extensions IG | hl7.fhir.uv.tools.r4#0.9.0 | R4 | for example references

Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. This includes two components: * Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains. *Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:32+0000+00:00)

Package hl7.fhir.us.core#7.0.0 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Wed, May 8, 2024 15:33+0000+00:00)

Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Package hl7.fhir.uv.bulkdata#2.0.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00)

Package ihe.formatcode.fhir#1.1.0 Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00)

Package hl7.fhir.us.core#6.1.0 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Fri, Jun 30, 2023 14:02+0000+00:00)

Package hl7.fhir.uv.extensions.r4#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.us.davinci-hrex#1.1.0 The Da Vinci Payer Health Record exchange (HRex) Framework/library specifies the FHIR elements used in multiple Da Vinci implementation guides. This includes FHIR profiles, functions, operations, and constraints on other specifications such as CDS-Hooks and other aspects of Da Vinci Use Cases that are common across more than a single use case.\n\nDa Vinci HRex Implementation Guide (IG) will make use of US Core profiles that are based on the FHIR R4 specification wherever practical. The HRex IG will use the HL7 FHIR Release 4/US Core STU3 specification as its base but will provide additional guidance and documentation to support implementations that follow the HL7 FHIR STU3/US Core STU2 and HL7 FHIR DSTU2/Argonaut specifications.\n\nThe HRex profiles documented in this IG will be used to exchange data between providers systems (e.g. EHRs) and other providers, payers, and third-party applications where appropriate. In addition, exchanges from payer systems to providers, other payers, and third-party applications are supported by the HRex profiles and operations.\n\nHRex may define new extensions, profiles, value sets, constraints/extension to other specification (e.g. specific CDS-Hooks) that are specific Da Vinci requirements. Where appropriate these Da Vinci specific artifacts will be promoted for incorporation into the future versions of existing standards (e.g. R4 US Core profiles) and deprecated in this guide on publication in the updated standard. (built Tue, Dec 10, 2024 16:43+0000+00:00)

Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)

Package hl7.fhir.us.carin-bb#2.1.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Tue, Feb 18, 2025 17:31+0000+00:00)

Package hl7.fhir.us.davinci-crd#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Dec 11, 2024 18:43+0000+00:00)

Package hl7.fhir.us.udap-security#0.1.0 This implementation guide describes how to extend OAuth 2.0 to support secure and scalable workflows for business-to-business (B2B) apps that implement the client credentials flow or authorization code flow. (built Fri, Aug 6, 2021 15:57+0000+00:00)

Package hl7.fhir.us.davinci-hrex#1.0.0 The Da Vinci Payer Health Record exchange (HRex) Framework/library specifies the FHIR elements used in multiple Da Vinci implementation guides. This includes FHIR profiles, functions, operations, and constraints on other specifications such as CDS-Hooks and other aspects of Da Vinci Use Cases that are common across more than a single use case. Da Vinci HRex Implementation Guide (IG) will make use of US Core profiles that are based on the FHIR R4 specification wherever practical. The HRex IG will use the HL7 FHIR Release 4/US Core STU3 specification as its base but will provide additional guidance and documentation to support implementations that follow the HL7 FHIR STU3/US Core STU2 and HL7 FHIR DSTU2/Argonaut specifications. The HRex profiles documented in this IG will be used to exchange data between providers systems (e.g. EHRs) and other providers, payers, and third-party applications where appropriate. In addition, exchanges from payer systems to providers, other payers, and third-party applications are supported by the HRex profiles and operations. HRex may define new extensions, profiles, value sets, constraints/extension to other specification (e.g. specific CDS-Hooks) that are specific Da Vinci requirements. Where appropriate these Da Vinci specific artifacts will be promoted for incorporation into the future versions of existing standards (e.g. R4 US Core profiles) and deprecated in this guide on publication in the updated standard. (built Wed, Mar 23, 2022 18:55+0000+00:00)

Package hl7.fhir.us.davinci-crd#2.0.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Fri, Oct 20, 2023 14:17+0000+00:00)

Package hl7.fhir.uv.subscriptions-backport.r4#1.1.0 The Subscription R5 Backport Implementation Guide enables servers running versions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Wed, Jan 11, 2023 15:34+1100+11:00)

Package hl7.fhir.us.carin-bb#2.0.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Mon, Nov 28, 2022 15:15+0000+00:00)

Package hl7.fhir.us.davinci-pas#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, Dec 20, 2024 21:03+0000+00:00)

Package hl7.fhir.us.davinci-pdex-plan-net#1.2.0 Da Vinci PDex Plan Net (built Tue, Feb 25, 2025 19:12+0000+00:00)

Package hl7.fhir.us.davinci-dtr#2.1.0 The Documentation Templates and Rules (DTR) Implementation Guide (IG) specifies how payer rules can be executed in a provider context to ensure that documentation requirements are met. The IG is a companion to the Coverage Requirements Discovery (CRD) IG, which uses CDS Hooks to query payers to determine if there are documentation requirements for a proposed medication, procedure or other service. (built Sat, Dec 21, 2024 15:48+0000+00:00)

Package hl7.fhir.us.davinci-cdex#2.1.0 This IG provides detailed guidance that helps implementers use FHIR-based interactions to support specific exchanges of clinical data between providers and payers (or other providers). (built Tue, Feb 11, 2025 03:51+1100+11:00)

Package hl7.fhir.us.davinci-atr#2.1.0 Exchange of member attribution list between payers and providers (built Fri, May 16, 2025 16:00+0000+00:00)

Package hl7.fhir.us.udap-security#1.0.0 This implementation guide describes how to extend OAuth 2.0 to support secure and scalable workflows for business-to-business (B2B) apps that implement the client credentials flow or authorization code flow. (built Tue, Sep 27, 2022 18:31+0000+00:00)

Package hl7.fhir.uv.tools.r4#0.9.0 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Dec 16, 2025 23:18+1100+11:00)

### Global Profiles

There are no Global profiles defined

### Copyrights

This publication includes IP covered under the following statements.

- All X12 products are subject to this IP policy, including published and draft works.X12 is the only organization authorized to grant permission for use of X12 products. Users of all X12 products should make sure that they understand the permissible uses, as well as the limitations on such usage, as outlined below.Additional IP information can be found here Send an email to ip@x12.org to request permission to reproduce X12 IP. Include your name, organization, title, address, city, state, zip, email, a detailed description of the Submitted Artifact, including the underlying or cited X12 Product, and a detailed description of the intended audience and planned distribution method for the Artifact.Additional information on X12 licensing program can be found here To purchase code list subscriptions call (425) 562-2245 or email admin@wpc-edi.com.
  Show Usage
  - X12 Claim Adjustment Reason Codes: PdexPriorAuthorization and X12ClaimAdjustmentReasonCodesCMSRemittanceAdviceRemarkCodes
- All X12 work products are copyrighted. Any use of any X12 work product must be compliant with US Copyright laws and X12 Intellectual Property policies.Please see https://x12.org/products/licensing-program
  Show Usage
  - X12 Service Type Codes: ExplanationOfBenefit/PDexPriorAuth1, PdexPriorAuthorization and PriorAuthServiceTypeCodes
- CMS maintains HIPPS. There are no known constraints on the use of HIPPS.
  Show Usage
  - Health Insurance Prospective Payment System (HIPPS): ExplanationOfBenefit/PDexPriorAuth1, PDexPAInstitutionalProcedureCodes, PDexPAInstitutionalProcedureCodesVS and PdexPriorAuthorization
- ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
  Show Usage
  - ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code: AssociatedServers, AttestationProvisionTypeValueSet... Show 102 more, AttestationStatusValueSet, BulkMemberMatch, BulkMemberMatchDataExport, ContactPointAvailableTime, DaVinciPayerDataExchange, DispenseRefill, DynamicRegistration, EndpointAccessControlMechanism, EndpointPayloadTypeCS, EndpointPayloadTypeVS, EndpointRank, EndpointUsecase, ExplanationOfBenefit_Identifier, ExplanationOfBenefit_Patient, ExplanationOfBenefit_ServiceDate, ExplanationOfBenefit_Type, ExplanationOfBenefit_Use, FDANationalDrugCode, FhirIg, Group_Code, IdentifierStatus, LastFilters, LastTransmission, LastTypes, LevelOfServiceCode, MatchParameters, MemberOptOut, MemberProviderTreatmentRelationship, MembersOptedOut, MtlsBundle, MtlsEndpoint, MtlsObjectCodeCS, MtlsObjectTypeVS, MtlsOrganization, MtlsSignedObject, OptOutDetails, OptOutReason, OptOutReasonCodeSystem, OptOutReasonValueSet, OptOutScopeCodeSystem, OptOutScopeValueSet, OrgTypeCS, OrgTypeVS, PDexAdjudication, PDexAdjudicationCategoryDiscriminator, PDexAdjudicationDiscriminator, PDexIdentifierType, PDexMemberCharacteristicCode, PDexMemberMatchGroup, PDexMemberNoMatchGroup, PDexMultiMemberMatchRequestParameters, PDexMultiMemberMatchResponseParameters, PDexMultiMemberMatchResultVS, PDexPAInstitutionalProcedureCodes, PDexPAInstitutionalProcedureCodesVS, PDexPayerAdjudicationStatus, PDexPayerBenefitPaymentStatus, PDexProviderGroup, PDexProviderSharingConsent, PDexServerCapabilityStatement61, PDexSupportingInfoType, PDexSupportingInfoTypeCS, PdexDevice, PdexMedicationDispense, PdexMedicationDispensePatient, PdexMedicationDispenseStatus, PdexMemberAttributionCS, PdexMultiMemberMatchResultCS, PdexPayerAccessServerCapabilityStatement, PdexPriorAuthorization, PdexProviderAccessServerCapabilityStatement, PdexServerCapabilityStatement, PriorAuthServiceTypeCodes, PriorAuthorizationAmounts, PriorAuthorizationUtilization, PriorAuthorizationValueCodes, Provenance, ProvenanceAgentRoleType, ProvenanceAgentType, ProvenancePayerDataSource, ProvenancePayerSourceFormat, ProvenanceSourceFrom, ProviderMemberMatch, ProviderMemberMatchGroup, ProviderMemberNoMatchGroup, ProviderMultiMemberMatchRequestParameters, ProviderMultiMemberMatchResponseParameters, ProviderTreatmentAttestation, ReviewAction, ReviewActionCode, SecureExchangeArtifacts, TreatmentRelationshipDetails, TreatmentRelationshipTypeCodeSystem, TreatmentRelationshipTypeValueSet, TrustFramework, TrustFrameworkTypeCS, TrustFrameworkTypeVS, TrustProfileCS, VerificationStatus, WhenAdjudicated, X12278ReviewDecisionReasonCode and X12ClaimAdjustmentReasonCodesCMSRemittanceAdviceRemarkCodes
- These codes are excerpted from ASTM Standard, E1762-95(2013) - Standard Guide for Electronic Authentication of Health Care Information, Copyright by ASTM International, 100 Barr Harbor Drive, West Conshohocken, PA 19428. Copies of this standard are available through the ASTM Web Site at www.astm.org.
  Show Usage
  - Signature Type Codes: Bundle/example-mtls-endpoint-bundle
- This CodeSystem is not copyrighted.
  Show Usage
  - C4BB Adjudication Code System: PDexAdjudication, PDexAdjudicationCategoryDiscriminator and PdexPriorAuthorization
  - PDex Adjudication Discriminator: PDexAdjudicationCategoryDiscriminator and PdexPriorAuthorization
  - PDex Payer Adjudication Status: PDexPayerBenefitPaymentStatus
  - PDex Supporting Info Type: PDexSupportingInfoType
- This is an example set based on ASTM Standard, E1762-95 (2013) HL7 RoleClass OID 2.16.840.1.113883.5.110, HL7 Role Code 2.16.840.1.113883.5.111, HL7 ParticipationType OID: 2.16.840.1.113883.5.90, HL7 ParticipationFunction codes at OID: 2.16.840.1.113883.5.88, and HL7 Security and Privacy Domain Analysis Model roles classes.
  Show Usage
  - Contract Signer Type Codes: Bundle/1000000-1, Bundle/1000000-2, Bundle/1000000-3 and Provenance/1000017
- This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
  Show Usage
  - LOINC: Consent/provider-treatment-attestation-1, Consent/treatment-attestation-ex1... Show 6 more, Consent/treatment-attestation-ex2, DocumentReference/123456, DocumentReference/provider-attestation-doc-1, Parameters/provider-bulk-member-match-in, Parameters/provider-member-match-request-001 and ProviderTreatmentAttestation
- This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  - SNOMED Clinical Terms&reg; (SNOMED CT&reg;): Bundle/1000000-1, Bundle/1000000-2... Show 7 more, Bundle/1000000-3, Bundle/3000003, Device/543210, Encounter/6, Encounter/7, Encounter/8 and PdexDevice
- This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  - Adjudication Value Codes: ExplanationOfBenefit/PDexPriorAuth1, PDexAdjudication and PdexPriorAuthorization
  - Claim Type Codes: ExplanationOfBenefit/PDexPriorAuth1
  - Condition Category Codes: Bundle/3000003
  - Condition Clinical Status Codes: Bundle/3000003
  - ConditionVerificationStatus: Bundle/3000003
  - Consent Action Codes: Consent/consent-2, Consent/no-consent-1, PDexProviderSharingConsent and Parameters/payer-multi-member-match-in
  - Consent Category Codes: Consent/provider-treatment-attestation-1, Consent/treatment-attestation-ex1... Show 5 more, Consent/treatment-attestation-ex2, DocumentReference/provider-attestation-doc-1, Parameters/provider-bulk-member-match-in, Parameters/provider-member-match-request-001 and ProviderTreatmentAttestation
  - Consent PolicyRule Codes: Consent/no-consent-1 and PDexProviderSharingConsent
  - Consent Scope Codes: Consent/consent-2, Consent/no-consent-1... Show 8 more, Consent/provider-treatment-attestation-1, Consent/treatment-attestation-ex1, Consent/treatment-attestation-ex2, PDexProviderSharingConsent, Parameters/payer-multi-member-match-in, Parameters/provider-bulk-member-match-in, Parameters/provider-member-match-request-001 and ProviderTreatmentAttestation
  - Coverage Class Codes: Coverage/CoverageLinkExample1, Coverage/CoverageMatchExample1... Show 5 more, Coverage/CoverageMatchExample2, Coverage/coverage-2, Parameters/payer-multi-member-match-in, Parameters/provider-bulk-member-match-in and Parameters/provider-member-match-request-001
  - DataAbsentReason: Bundle/example-mtls-endpoint-bundle, MtlsEndpoint... Show 4 more, PDexPAInstitutionalProcedureCodes, PDexPAInstitutionalProcedureCodesVS, Payer-Payer Exchange and PdexPriorAuthorization
  - Endpoint Connection Type: Bundle/example-mtls-endpoint-bundle, MtlsEndpoint and Payer-Payer Exchange
  - Example Diagnosis Type Codes: ExplanationOfBenefit/PDexPriorAuth1
  - Example Related Claim Relationship Codes: ExplanationOfBenefit/PDexPriorAuth1
  - Funds Reservation Codes: ExplanationOfBenefit/PDexPriorAuth1
  - Organization type: DiamondOnyxHealth
  - Process Priority Codes: ExplanationOfBenefit/PDexPriorAuth1 and PdexPriorAuthorization
  - Professional Credential Status: IdentifierStatus
  - SubscriberPolicyholder Relationship Codes: Coverage/883210, Coverage/Coverage1... Show 8 more, Coverage/CoverageLinkExample1, Coverage/CoverageMatchExample1, Coverage/CoverageMatchExample2, Coverage/coverage-2, Coverage/coverage-link-2, Parameters/payer-multi-member-match-in, Parameters/provider-bulk-member-match-in and Parameters/provider-member-match-request-001
  - identifierType: Bundle/1000000-1, Bundle/1000000-2... Show 28 more, Bundle/1000000-3, Coverage/883210, Coverage/Coverage1, Coverage/coverage-2, Coverage/coverage-link-2, Group/example-pdex-member-consent-constraint-group, Group/example-pdex-member-no-match-group, Matched Members, Parameters/payer-multi-member-match-in, Parameters/payer-multi-member-match-out, Parameters/provider-bulk-member-match-in, Parameters/provider-bulk-member-match-out, Parameters/provider-member-match-request-001, Patient/1, Patient/1-2, Patient/100, Patient/1001, Patient/2002, Patient/PatientMemberMatchExample1, Patient/PatientMemberMatchExample2, Patient/patient-2, Patient/payer-patient-1001, Patient/payer-patient-2002, Payer 1, Payer 2, Practitioner/4, Provider 1 and Provider 2
  - ActCode: Bundle/1000000-1, Bundle/1000000-2... Show 16 more, Bundle/1000000-3, Bundle/2000002, Bundle/3000002, Consent/consent-2, Consent/no-consent-1, Coverage/CoverageLinkExample1, Coverage/CoverageMatchExample1, Coverage/CoverageMatchExample2, Encounter/6, Encounter/7, Encounter/8, MedicationDispense/1000001, PDexProviderSharingConsent, Parameters/payer-multi-member-match-in, Parameters/provider-member-match-request-001 and PdexMedicationDispense
  - ActReason: Consent/provider-treatment-attestation-1, Consent/treatment-attestation-ex1... Show 5 more, Consent/treatment-attestation-ex2, Parameters/provider-bulk-member-match-in, Parameters/provider-member-match-request-001, Provenance/1000101 and ProviderTreatmentAttestation
  - DataOperation: Provenance/1000101
  - NullFlavor: Bundle/1000000-1, Bundle/1000000-2... Show 4 more, Bundle/1000000-3, Patient/1, Patient/1-2 and Patient/100
  - ParticipationType: Consent/consent-2, Consent/provider-treatment-attestation-1... Show 5 more, Consent/treatment-attestation-ex1, Consent/treatment-attestation-ex2, Parameters/payer-multi-member-match-in, Parameters/provider-bulk-member-match-in and Parameters/provider-member-match-request-001
  - RoleClass: Consent/provider-treatment-attestation-1 and Parameters/provider-bulk-member-match-in
- Used by permission of HL7 International, all rights reserved Creative Commons License
  Show Usage
  - US Core DocumentReferences Category Codes: DocumentReference/123456
  - US Core Provenance Participant Type Extension Codes: Bundle/1000000-1, Bundle/1000000-2... Show 8 more, Bundle/1000000-3, Bundle/3000002, Provenance, Provenance/1000001, Provenance/1000016, Provenance/1000017, Provenance/1000101 and ProvenanceAgentType
  - Endpoint Payload Types Code System: EndpointPayloadTypeVS
  - mTLS Object Type Code: MtlsObjectTypeVS, MtlsSignedObject and Payer-Payer Exchange
  - Organization Type: Acme of CT and OrgTypeVS
  - PDex Provider Access API Attribution Code System: Attributed List of Health Plan Members for Practitioner 1122334455., MemberOptOut... Show 7 more, MemberProviderTreatmentRelationship, PDexMemberMatchGroup, PDexMemberNoMatchGroup, PDexMultiMemberMatchResultVS, PDexProviderGroup, ProviderMemberMatchGroup and ProviderMemberNoMatchGroup
  - PDex Multi-Member Match Result Code System: Group/example-pdex-member-consent-constraint-group, Group/example-pdex-member-no-match-group... Show 11 more, Matched Members, MemberOptOut, MemberProviderTreatmentRelationship, PDexMemberMatchGroup, PDexMemberNoMatchGroup, PDexMultiMemberMatchResultVS, PDexProviderGroup, Parameters/payer-multi-member-match-out, Parameters/provider-bulk-member-match-out, ProviderMemberMatchGroup and ProviderMemberNoMatchGroup
  - Prior Authorization Values: ExplanationOfBenefit/PDexPriorAuth1, PdexPriorAuthorization and PriorAuthorizationAmounts
  - Provenance Roles: Provenance and ProvenanceAgentType
  - Provenance Payer Data Source Format: Bundle/1000000-1, Bundle/1000000-2... Show 13 more, Bundle/1000000-3, Bundle/3000002, Bundle/3000003, Provenance, Provenance/1000001, Provenance/1000002, Provenance/1000003, Provenance/1000004, Provenance/1000005, Provenance/1000006, Provenance/1000016, ProvenancePayerSourceFormat and ProvenanceSourceFrom
  - Trust FrameworkType Code System: TrustFramework and TrustFrameworkTypeVS
  - Opt-Out Reason: OptOutReason and OptOutReasonValueSet
  - Opt-Out Scope: MemberOptOut and OptOutScopeValueSet
  - Treatment Relationship Type: TreatmentRelationshipTypeValueSet

Next Page - Security and Privacy