Da Vinci Payer Data Exchange
2.1.0 - STU2 United States of America flag

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

ValueSet: mTLS Bundle Type Value Set (Experimental)

Official URL: http://hl7.org/fhir/us/davinci-pdex/ValueSet/BundleTypeVS Version: 2.1.0
Active as of 2024-03-01 Computable Name: BundleTypeVS

Categories of bundle.


Logical Definition (CLD)

This value set includes codes based on the following rules:



Expansion based on codesystem BundleType v4.0.1 (CodeSystem)

This value set contains 9 concepts.


The bundle is a document. The first resource is a Composition.


The bundle is a message. The first resource is a MessageHeader.


The bundle is a transaction - intended to be processed by a server as an atomic commit.

  transaction-responsehttp://hl7.org/fhir/bundle-typeTransaction Response

The bundle is a transaction response. Because the response is a transaction response, the transaction has succeeded, and all responses are error free.


The bundle is a set of actions - intended to be processed by a server as a group of independent actions.

  batch-responsehttp://hl7.org/fhir/bundle-typeBatch Response

The bundle is a batch response. Note that as a batch, some responses may indicate failure and others success.

  historyhttp://hl7.org/fhir/bundle-typeHistory List

The bundle is a list of resources from a history interaction on a server.

  searchsethttp://hl7.org/fhir/bundle-typeSearch Results

The bundle is a list of resources returned as a result of a search/query interaction, operation, or message.


The bundle is a set of resources collected into a single package for ease of distribution that imposes no processing obligations or behavioral rules beyond persistence.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code