IP Review

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 it's use carefully. For futher 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 , BulkMemberMatch ... Show 76 more
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
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 : DocumentReference/123456
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® (SNOMED CT®) : Bundle/1000000-1 , Bundle/1000000-2 ... Show 7 more
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
Used by permission of HL7 International, all rights reserved Creative Commons License
Show Usage

IG © 2024+ HL7 International / Financial Management. Package hl7.fhir.us.davinci-pdex#2.1.0 based on FHIR 4.0.1. Generated 2025-04-09 Links: Table of Contents | QA Report | Version History | CC0 | Propose a change ( src )

hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )

At this point we have two solutions that provide an overlapping but different set of information for the members of a health plan. The first is the CARIN IG for Blue Button® which is focused on providing claims information, including the adjudication information, in the form of a FHIR ExplanationOfBenefit (EOB). The second solution is to provide all payer information related to the clinical condition and care of the patient using US Core profiles on FHIR R4 resources. In the latter case, USCDI information coming from claims is represented as US Core resources and includes, at a minimum: encounters, providers, organizations, locations, dates of service, diagnoses (conditions), procedures and observations. This information would also include clinical information from sources other than claims maintained by the payer, such as: ( src )

CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) ( src )

CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Mon, Nov 28, 2022 15:15+0000+00:00) ( src )

CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Tue, Feb 18, 2025 17:31+0000+00:00) ( src )

CARIN Consumer Directed Payer Data Exchange IG (CARIN IG for Blue Button®) ( src )

Code of Federal Regulation 21CFR§1271.290(c) ( src )

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.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 ( src )

Imported by CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (and potentially others) ( src )

The CARIN Alliance focused on replicating the CMS Blue Button 2.0 solution directed at providing beneficiaries access to claims information for Medicare Fee For Service (FFS) in the form of a FHIR based ExplanationOfBenefit (EOB). The CARIN Alliance Consumer-Directed Payer Data Exchange (CARIN IG for Blue Button®) solution was intended to provide the same information based on commercial payer databases, at least for Medicare Advantage products. The CMS Interoperability and Patient Access Final Rule expanded the scope of a Blue Button 2.0 equivalent to include not just Medicare Advantage but also Medicaid HMO, CHIP HMO and QHP's in the federal marketplace. ( src )

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: DocumentReference/123456 ( src )

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/no-consent-1, PDexProviderSharingConsent and Parameters/payer-multi-member-match-in * Consent PolicyRule Codes: Consent/no-consent-1 and PDexProviderSharingConsent * Consent Scope Codes: Consent/no-consent-1, PDexProviderSharingConsent and Parameters/payer-multi-member-match-in * Coverage Class Codes: Parameters/payer-multi-member-match-in * DataAbsentReason: PDexPAInstitutionalProcedureCodes, PDexPAInstitutionalProcedureCodesVS 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 * Process Priority Codes: ExplanationOfBenefit/PDexPriorAuth1 and PdexPriorAuthorization * Provenance participant type: Bundle/1000000-1, Bundle/1000000-2... Show 13 more , Bundle/1000000-3, Bundle/3000003, Consent/no-consent-1, PDexProviderSharingConsent, Parameters/payer-multi-member-match-in, Provenance, Provenance/1000002, Provenance/1000003, Provenance/1000004, Provenance/1000005, Provenance/1000006, Provenance/1000101 and ProvenanceAgentType * SubscriberPolicyholder Relationship Codes: Coverage/883210, Coverage/Coverage1 and Parameters/payer-multi-member-match-in * identifierType: Bundle/1000000-1, Bundle/1000000-2... Show 18 more , Bundle/1000000-3, Coverage/883210, Coverage/Coverage1, 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, Patient/1, Patient/1-2, Patient/100, Patient/1001, Patient/2002, Payer 1, Payer 2, Practitioner/4, Provider 1 and Provider 2 * ActCode: Bundle/1000000-1, Bundle/1000000-2... Show 11 more , Bundle/1000000-3, Bundle/2000002, Bundle/3000002, Consent/no-consent-1, Encounter/6, Encounter/7, Encounter/8, MedicationDispense/1000001, PDexProviderSharingConsent, Parameters/payer-multi-member-match-in and PdexMedicationDispense * ActReason: Provenance/1000101 * 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: Parameters/payer-multi-member-match-in ( src )

External References

Type	Reference	Content
web	www.x12.org	The Vocabulary, Value Sets and codings used to express data in this IG are subject to review and will be reconciled with X12 .
web	diamond.1.onyxhealth.io	telecom : https://diamond.1.onyxhealth.io
web	valueset.x12.org	Value of extension Binding: https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 ( required ): Codes specifying the level of service rendered. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.
web	valueset.x12.org	Healthcare Services Outcome URL: http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/extension-reviewActionCode Binding: https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 ( required ): Codes indicating type of action. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.
web	valueset.x12.org	Value of extension Binding: https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 ( required ): Codes indicating type of action. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.
web	valueset.x12.org	A code specifying the level of service being requested (UM06) URL: http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/extension-levelOfServiceCode Binding: https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 ( required ): Codes specifying the level of service rendered. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.
web	github.com	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.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
web	x12.org	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
web	x12.org	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
web	x12.org	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
web	x12.org	https://x12.org/products/licensing-program
web	www.iso.org	ISO Maintains the copyright on the country codes, and controls it's use carefully. For futher 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 , BulkMemberMatch ... Show 76 more
web	fhir.github.io	FHIR Validator
web	valueset.x12.org	The codes SHALL be taken from For codes, see https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 ( required to `https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338` )
web	valueset.x12.org	The codes SHALL be taken from https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 ( required to `https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338` )
web	valueset.x12.org	Value of extension Binding: https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 ( required ): Codes specifying the level of service rendered. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.
web	valueset.x12.org	https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 `https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338`
web	valueset.x12.org	The codes SHALL be taken from For codes, see https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 ( required to `https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306` )
web	valueset.x12.org	The codes SHALL be taken from https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 ( required to `https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306` )
web	valueset.x12.org	Value of extension Binding: https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 ( required ): Codes indicating type of action. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.
web	valueset.x12.org	https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 `https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306`
web	en.wikipedia.org	Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS ).
web	www.omg.org	Mappings for ServD ( http://www.omg.org/spec/ServD/1.0/ )
web	valueset.x12.org	A code specifying the level of service being requested (UM06) URL: http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/extension-levelOfServiceCode Binding: https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 ( required ): Codes specifying the level of service rendered. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions. ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
web	info.commerce.ama-assn.org	To obtain CPT, please see the license request form here
web	x12.org	Additional IP information can be found here: https://x12.org/products/ip-use
web	x12.org	https://x12.org/codes
web	www.wpc-edi.com	Click on the name of any external code list to access more information about the code list, view the codes, or submit a maintenance request. These external code lists were previously published on either www.wpc-edi.com/reference or www.x12.org/codes .
web	www.x12.org	Click on the name of any external code list to access more information about the code list, view the codes, or submit a maintenance request. These external code lists were previously published on either www.wpc-edi.com/reference or www.x12.org/codes .
web	github.com	Feedback on CDS Hooks should be posted to the CDS Hooks GitHub Issue List
web	oauth.net	The authorization method uses the OAuth 2.0 protocol to issue a token to an authorized application or service. The authorized application can then use the token to enable interaction with the FHIR REST API.
web	cds-hooks.org	The PDex guide is based on the HL7 FHIR 4.0.1 standard, as well as the CDS Hooks , SMART on FHIR and OAuth2.0 standards, which build additional capabilities on top of FHIR. This architecture is intended to maximize the number of clinical systems that conform to this guide as well as to allow for easy growth and extensibility of system capabilities in the future.
web	docs.smarthealthit.org	The PDex guide is based on the HL7 FHIR 4.0.1 standard, as well as the CDS Hooks , SMART on FHIR and OAuth2.0 standards, which build additional capabilities on top of FHIR. This architecture is intended to maximize the number of clinical systems that conform to this guide as well as to allow for easy growth and extensibility of system capabilities in the future.
web	oauth.net	The PDex guide is based on the HL7 FHIR 4.0.1 standard, as well as the CDS Hooks , SMART on FHIR and OAuth2.0 standards, which build additional capabilities on top of FHIR. This architecture is intended to maximize the number of clinical systems that conform to this guide as well as to allow for easy growth and extensibility of system capabilities in the future.
web	github.com	For Payers to establish a secure mTLS connection with another Payer there needs to be a discovery service. In the absence of a Trusted Exchange Framework and Common Agreement (TEFCA) or National Endpoint Directory service for Payers an interim solution is required. For this purpose, a public git repository will be established that will be used to store signed mTLS endpoint bundles. A test version of that repository has been established here: https://github.com/HL7-DaVinci/pdex-payer-payer . The repository includes some supporting tools and documentation relating to mTLS discovery.
web	github.com	PDex SMART-on-FHIR+CDS-Hook Patient Import App
web	github.com	PDex Payer-to-Payer Patient Import App .

Type

Reference

Content

web

www.x12.org

The Vocabulary, Value Sets and codings used to express data in this IG are subject to review and will be reconciled with X12 .

web

diamond.1.onyxhealth.io

telecom : https://diamond.1.onyxhealth.io

web

valueset.x12.org

Value of extension
Binding: https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 ( required ): Codes specifying the level of service rendered. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.

web

valueset.x12.org

Healthcare Services Outcome
URL: http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/extension-reviewActionCode
Binding: https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 ( required ): Codes indicating type of action. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.

web

valueset.x12.org

Value of extension
Binding: https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 ( required ): Codes indicating type of action. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.

web

valueset.x12.org

A code specifying the level of service being requested (UM06)
URL: http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/extension-levelOfServiceCode
Binding: https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 ( required ): Codes specifying the level of service rendered. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.

web

github.com

web

x12.org

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

web

x12.org

Show Usage

web

x12.org

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

web

x12.org

https://x12.org/products/licensing-program

web

www.iso.org

ISO Maintains the copyright on the country codes, and controls it's use carefully. For futher details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html

Show Usage

web

fhir.github.io

FHIR Validator

web

valueset.x12.org

The codes SHALL be taken from For codes, see https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338
( required to https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 )

web

valueset.x12.org

The codes SHALL be taken from https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338
( required to https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338 )

web

valueset.x12.org

web

valueset.x12.org

https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338

https://valueset.x12.org/x217/005010/request/2000E/UM/1/06/00/1338

web

valueset.x12.org

The codes SHALL be taken from For codes, see https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306
( required to https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 )

web

valueset.x12.org

The codes SHALL be taken from https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306
( required to https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306 )

web

valueset.x12.org

web

valueset.x12.org

https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306

https://valueset.x12.org/x217/005010/response/2000F/HCR/1/01/00/306

web

en.wikipedia.org

Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS ).

web

www.omg.org

Mappings for ServD ( http://www.omg.org/spec/ServD/1.0/ )

web

valueset.x12.org

web

info.commerce.ama-assn.org

To obtain CPT, please see the license request form here

web

x12.org

Additional IP information can be found here: https://x12.org/products/ip-use

web

x12.org

https://x12.org/codes

web

www.wpc-edi.com

Click on the name of any external code list to access more information about the code list, view the codes, or submit a maintenance request. These external code lists were previously published on either www.wpc-edi.com/reference or www.x12.org/codes .

web

www.x12.org

web

github.com

Feedback on CDS Hooks should be posted to the CDS Hooks GitHub Issue List

web

oauth.net

The authorization method uses the OAuth 2.0 protocol to issue a token to an authorized application or service. The authorized application can then use the token to enable interaction with the FHIR REST API.

web

cds-hooks.org

The PDex guide is based on the HL7 FHIR 4.0.1 standard, as well as the CDS Hooks , SMART on FHIR and OAuth2.0 standards, which build additional capabilities on top of FHIR. This architecture is intended to maximize the number of clinical systems that conform to this guide as well as to allow for easy growth and extensibility of system capabilities in the future.

web

docs.smarthealthit.org

web

oauth.net

web

github.com

For Payers to establish a secure mTLS connection with another Payer there needs to be a discovery service. In the absence of a Trusted Exchange Framework and Common Agreement (TEFCA) or National Endpoint Directory service for Payers an interim solution is required. For this purpose, a public git repository will be established that will be used to store signed mTLS endpoint bundles. A test version of that repository has been established here: https://github.com/HL7-DaVinci/pdex-payer-payer . The repository includes some supporting tools and documentation relating to mTLS discovery.

web

github.com

PDex SMART-on-FHIR+CDS-Hook Patient Import App

web

github.com

PDex Payer-to-Payer Patient Import App .

Internal Images

MappingFromV2toFHIR.png