| Type |
Standard / Implementation Specification |
Standards Process Maturity |
Implementation Maturity |
Adoption Level |
Federally required |
Cost |
Test Tool Availability |
|
Implementation Specification
|
|
Final
|
Production
|
 |
No
|
Free
|
Yes
Yes
|
|
Implementation Specification
|
|
Final
|
Production
|
 |
No
|
Free
|
Yes
Yes
|
|
Implementation Specification
|
|
Final
|
Production
|
 |
No
|
Free
|
Yes
Yes
|
|
Implementation Specification
|
|
Balloted Draft
|
Pilot
|
 |
No
|
Free
|
No
|
|
Implementation Specification
|
|
Balloted Draft
|
Pilot
|
 |
Yes
|
Free
|
Yes
|
|
Emerging Implementation Specification
|
|
Balloted Draft
|
Pilot
|
 |
No
|
Free
|
Yes
|
|
Emerging Implementation Specification
|
|
Balloted Draft
|
Pilot
|
 |
No
|
Free
|
No
|
|
Emerging Implementation Specification
|
|
Balloted Draft
|
Pilot
|
 |
No
|
Free
|
No
|
|
Emerging Implementation Specification
|
|
Balloted Draft
|
Pilot
|
Feedback Requested |
No
|
Free
|
No
|
= Federal FHIR Action Plan: Marks standards for coordinated federal adoption. See Appendix V: Federal FHIR Action Plan for more details.
| Federal FHIR Action Plan Alignment |
HL7® FHIR® Da Vinci Da Vinci Clinical Data Exchange Implementation Guide (CDex IG) - This Implementation specification provides a framework for data exchange between providers and payers, as well as provider-to-provider and payer-to-payer workflows, for patient EHR data. The CDex IG supports query-based, task-based, and documents-based data exchange workflows.
- The CDex IG is not intended to replace other HL7 FHIR Da Vinci specifications required by the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F). Instead, it focuses on specific workflows at the provider-payer interface, particularly when there is a need for manual review of received data query requests from external providers or payers. It is important to note that the CDex IG should not be implemented for workflows requiring real-time responses. Instead, it is suitable for scenarios where manual review of data query responses is necessary before delivering the data to partner providers or payers.
- Certified Health IT developers, providers, and payers are encouraged to consider the CDex IG as a starting point for supporting data exchange at the provider-payer interface. This specification enables controlled and structured data sharing while allowing manual oversight to ensure accuracy and compliance in data exchange workflows.
HL7® FHIR® Da Vinci Payer Data Exchange Implementation Guide (PDex IG) - This implementation specification provides a framework for payers and health plans to create a member’s health history using clinical resources based on the US Core IG. This health history can be shared with providers in a format that is understandable and can be integrated into their Certified Health IT systems. The PDex IG includes components for both payers and providers, enabling providers to access timely and comprehensive clinical information. This supports more informed treatment decisions, better adherence to care plans, and improved quality of care for patients.
- ONC and the Centers for Medicare & Medicaid Services (CMS) have identified PDex IG version 2.0 as ready for adoption in Certified Health IT. Developed by the Da Vinci Project Accelerator, the PDex IG is available for implementation without licensing requirements.
- Payers and providers should consider adopting the PDex IG for use cases that involve exchanging clinical information between payers and providers, as well as enabling patients to access their clinical information from their payers.
- Referenced in Federal Rulemaking: CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)
|
| Limitations, Dependencies, and Preconditions for Consideration |
Applicable Security Patterns for Consideration
|
- IHE-PIX and IHE-PDQ are used for the purposes of patient matching and to support this interoperability need along with IHE-XDS.
- The MHD Supplement Revision 2.2 published in April 2016 is based on FHIR DSTU2.
- IHE-PIXm and IHE-PDQm are used for the purposes of patient matching and to support this interoperability need along with MHD.
- The Document Sharing exchange infrastructure is a family of implementation guides specifically designed to support this setting. This includes the FHIR based Mobile Health Document Sharing (MHDS) comprehensive community exchange. Both XDS and MHDS enable the automation of discovery and retrieve of document content by more advanced health information systems.
|
- Secure Communication – Create a secure channel for client-to-server and server-to-server communication.
- Secure Message Router – Securely route and enforce policy on inbound and outbound messages without interruption of delivery.
- Authentication Enforcer – Centralized authentication processes.
- Authorization Enforcer – Specifies access control policies.
- Credential Tokenizer – Encapsulate credentials as a security token for reuse (e.g., SAML, Kerberos).
- Assertion Builder – Define processing logic for identity, authorization and attribute statements.
- User Role – Identifies the role asserted by the individual initiating the transaction.
- Purpose of Use – Identifies the purpose for the transaction.
|
Submitted by John Moehrke on
IHE - Document Sharing
The Document Sharing exchange infrastructure is a family of implementation guides specifically designed to support this setting.
https://profiles.ihe.net/ITI/HIE-Whitepaper/index.html
This includes the FHIR based Mobile Health Document Sharing (MHDS) comprehensive community exchange.
Both XDS and MHDS enable the automation of discovery and retrieve of document content by more advanced health information systems.