Da Vinci Health Record Exchange (HRex)
1.1.0-ballot - STU 1.1 Ballot United States of America flag

This page is part of the Da Vinci Health Record Exchange (v1.1.0-ballot: STU 1.1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

Home

Official URL: http://hl7.org/fhir/us/davinci-hrex/ImplementationGuide/hl7.fhir.us.davinci-hrex Version: 1.1.0-ballot
IG Standards status: Trial-use Maturity Level: 2 Computable Name: DaVinciHealthRecordExchangeHRex
Other Identifiers: OID:2.16.840.1.113883.4.642.40.19

This IG has undergone a number of changes to support the needs of the different Da Vinci IGs that use it. The most significant is support for USCDI v3, though there are a number of other significant changes as well. Please refer to the History page for a detailed list of substantive changes.

Introduction

The Da Vinci Health Record Exchange (HRex) implementation guide (IG) is a foundational guide for all other Da Vinci guides. It defines FHIR profiles, operations and guidance that are relevant to more than one, and sometimes all, Da Vinci use-case IGs. In the future, it may define additional types of artifacts such as extensions or value sets. All HRex artifacts are intended to be use-case independent, though they are specifically tied to the HRex scope. They may be referenced in RESTful exchanges, passed in CDS Hooks, or manipulated by SMART apps. Because the artifacts defiend here are use-case independent, this IG does not include a use-case or patient stories section. Use-cases may instead be found in the various Da Vinci guides that leverage the artifacts defined here for specific business purposes.

As a supporting IG, HRex is expected to continue to evolve as additional shared content needs are identified as part of the Da Vinci work. Da Vinci use case IGs will derive from this IG and reference specific pages and sections that are relevant to their use-case and mandate the use of the profiles and artifacts defined here, or that are inherited from US Core. Da Vinci IGs may also refine or further constrain content defined here when the use case requirements are tighter than the general 'shared' requirement.

The scope of Da Vinci is US payer and provider data exchange with each other and other covered entities under HIPAA (including their business associates). It includes data exchange with the patient/member. The exchanges are typically ones that are 'of interest' in value-based care. Some of the Da Vinci content may be relevant outside this defined scope (e.g. non-US implementations). However, requests for change should be focused on HRex’s official scope.

Dependencies

At present, HRex is based on FHIR R4. In addition, HRex is dependent on the US Core 3.1 (FHIR R4) and US Core 6.1 (FHIR R4) implementation guides. The former is supported for those systems limited to USCDI 1 capabilities and the latter is supported to meet regulatory requirements mandating support for USCDI 3. Wherever possible, Da Vinci profiles strive to comply with both releases.

In some situations, the payer community requires additional constraints or needs to profile resources that are not yet supported by US Core. In these cases, this IG does not derive from the US Core profiles, though it does align with them as much as possible. It is possible that certain HRex profiles and/or descriptive content may migrate to a future release of US Core, and in some cases, to the base FHIR standard. In certain instances, Da Vinci IGs will also declare conformance with the QI Core, which supplements US Core with additional profiles and constraints for use in quality measurements. This IG is not derived from QI core, but HRex profiles should be generally compliant with the QI Core specification.

In addition, some Da Vinci specifications will make use of content from the following FHIR-related specifications and implementation guides:

The main menu in this IG is categorized into several primary topics with several sub-topics:

  • Background provides supporting information relevant for implementers of this IG or Da Vinci guides in general. These sections may be referenced from other Da Vinci IGs, but do not contain any rules that impact IG conformance. (Nothing in these sections will ever become 'normative' or define functionality that implementer systems must or must not do.) These sections will provide context to implementers to help them understand other parts of the IG and make better and more efficient decisions with respect to FHIR implementation.
    • Da Vinci Overview provides an overview of the Da Vinci project and provides guidance on how to get involved in the project and where to find the use-case specific IGs.
    • FHIR Introduction highlights the key sections of the FHIR core specification that Da Vinci implementers should be familiar with.
    • Approaches to Exchanging FHIR Data provides a detailed overview of all the mechanisms that FHIR supports for exchanging information. Implementers do not need to read this, but Da Vinci use case IGs may refer to this information.
  • Specification content includes pages that define artifacts or include formal conformance rules that apply to this IG and that may be included by reference in other Da Vinci IGs.
    • Conformance Expectations describes conformance language used within the spec and expectations around mustSupport and missing data
    • Security and Privacy provides general expectations to ensure security and privacy of Da Vinci exchanges
    • Dynamic Registration for SMART Apps documents requirements for cross-registration of SMART on FHIR apps
    • Profile Overview gives an overview of the profiles defined in this IG and, where relevant, guidance on the use of US Core profiles
    • Search Parameter Overview gives an overview of the search parameters defined in this IG and a discussion of how those, along with US Core search parameters should be used
    • Member Match describes the process to resolve a member as known by a different payer
  • IG Practices describes best practices for Da Vinci IGs to adhere to. While primarily of interest to IG authors, reviewers may find reading this page helpful when reviewing IGs or understanding the design choices made.
  • Artifacts includes links to artifacts (profiles, operations, etc.) defined both in this specification as well as in the imported US Core implementation guide. This index also includes a list of all of the examples - there are at least two examples for every profile, sometimes more to demonstrate the range of possible content supported. (Examples relevant to a given profile are also linked to from the profile page.)
  • Base Specs includes links to the FHIR core specification as well as the US Core specs that underlie this IG.
  • Support includes various links for support and guidance, as well as download links for this IG and guidance on tools and support for Da Vinci implementers.

The main menu at the top of all IG pages will allow you to jump to any of the main pages in the IG. The breadcrumbs bar (right below the menu bar) will let you navigate 'up' to ancestor pages of whatever page you are looking at. The Table of Contents (TOC) will show you all pages in the IG and the Artifacts list will list all of the artifacts (profiles, extensions, operations, value sets, etc.) defined in this specification. As well, this IG makes heavy use of hyperlinks which will allow navigation to relevant sections of this specification and parent specifications.

Dependencies

This guide is based on the FHIR R4 specification. In addition, this guide also relies on a number of parent implementation guides:

This implementation guide defines additional constraints and usage expectations above and beyond the information found in these base specifications.

Intellectual Property Considerations

This implementation guide and the underlying FHIR specification are licensed as public domain under the FHIR license. The license page also describes rules for the use of the FHIR name and logo.

This publication includes IP covered under the following statements.