Consumer-Directed Payer Data Exchange
- Release 0.1.0

Consumer-Directed Payer Data Exchange, published by CARIN Alliance. This is not an authorized publication; it is the continuous build for version 0.1.0). This version is based on the current content of https://github.com/HL7/carin-bb/ and changes regularly. See the Directory of published versions

General Guidance

Previous Page

Conformance Verbs

The conformance verbs - SHALL, SHOULD, MAY - used in this guide are defined in FHIR Conformance Rules.

Must Support

For profiles defined in other IGs, the meaning of Must Support is established in the defining IG.

For profiles defined in this IG, Must Support means the following:

When querying and reading CARIN BB Profiles, Must Support on any profile data element SHALL be interpreted as follows:

  • Health Plan API actors SHALL be capable of populating all data elements as part of the query results as specified by the CARINBlueButtonHealthPlanAPICapabilityStatement.
  • Consumer App actors SHALL be capable of processing resource instances containing the data elements without generating an error or causing the application to fail. In other words, Consumer App actors SHOULD be capable of displaying the data elements for human use or storing the information for other purposes.
  • In situations where information on a particular data element is not present and the reason for absence is unknown, Health Plan API actors SHALL NOT include the data elements in the resource instance returned as part of the query results.
  • When querying Health Plan API actors, Consumer App actors SHALL interpret missing data elements within resource instances as data not present in the Health Plan API actors system.
  • In situations where information on a particular data element is missing and the Health Plan API actor knows the precise reason for the absence of data, Health Plan API actors SHALL send the reason for the missing information using values (such as nullFlavors) from the value set where they exist or use the dataAbsentReason extension.
  • Consumer App actors SHALL be able to process resource instances containing data elements asserting missing information.
  • NOTE: The above definition of Must Support is derived from HL7v2 concept Required but may be empty - RE described in HL7v2 V28_CH02B_Conformance.doc.
  • NOTE: Readers are advised to understand FHIR Terminology requirements, FHIR RESTful API based on the HTTP protocol, along with FHIR Data Types, FHIR Search and FHIR Resource formats before implementing CARIN BB IG requirements.

Missing Data

If the source system does not have data for a Must Support data element with minimum cardinality = 0, the data element is omitted from the resource. If the source system does not have data for a required data element (in other words, where the minimum cardinality is > 0), follow guidance defined in the core FHIR specification and summarized in the US Core IG.

Conformance to US Core Profiles

Any actor acting as a Health Plan API actor in this IG SHALL:

  • Be able to populate all profile data elements that have a minimum cardinality >= 1 and/or flagged as Must Support as defined by that profiles StructureDefinition.
  • Conform to the US Core Server Capability Statement expectations for that profiles type.
  • Any actor acting a FHIR Client in this IG SHALL:
  • Be able to process and retain all profile data elements that have a minimum cardinality >= 1 and/or flagged as Must Support as defined by that profiles StructureDefinition.
  • Conform to the US Core Client Capability Statement expectations for that profiles type.

U.S. Core Data for Interoperability and 2015 Edition Common Clinical Data Set

The US Core Profiles were originally designed to meet the 2015 Edition certification criterion for Patient Selection 170.315(g)(7), and Application Access - Data Category Request 170.315(g)(8). They were created for each item in the 2015 Edition Common Clinical Data Set (CCDS). The 3.1.0 version of the US Core Profiles IG includes new requirements from the latest proposed ONC U.S. Core Data for Interoperability (USCDI) and includes all the API Resource Collection in Health (ARCH) resources.

Access to Licensed Code Systems

The Industry Standard Code Systems defined by this IG align with claims submission standards adopted by the Department of Health and Human Services. Some of the codes require licenses; others are available for use. The CARIN team will be submitting proposed additions to the set of Externally Published code systems for any Industry Standard Code Systems not in the published list. https://www.hl7.org/fhir/terminologies-systems.html

Licensed Industry Standard Code Systems

This IG includes value set bindings to industry standard codes that reference Code Systems which require implementers to purchase a license before the coded concepts can be used. HL7 presently addresses similar license requirements for LOINC and SNOMED CT codes, which although are not used by this IG, are required for other IGs. The following information summarizes the set of licensed Code Systems required by this IG and provides links to the information about where to go to purchase a license.

Available Industry Standard Code Systems

This IG includes value set bindings to industry standard codes that are available for use without licenses. An example is the ICD-10 procedure codes ICD-10-PCS codes which are defined in US Core Procedure Profile. (However, the US Core Procedure Profile cannot be used by this IG as it includes LOINC and SNOMED CT codes, which are not are not defined by HHS for claims submissions). The following information summarizes the set of Code Systems required by this IG that are available for use and provides links to the location of the information.

Next Page