R4 Ballot #1 (Mixed Normative/Trial use) Current Build
This is the FHIR R4 Mixed Normative/Trial Use Ballot #1, and the version for the Cologne Connectathon in May 2018. The current version is R3 . See the ballot introduction for details about the ballot. For a full list of available versions, see the Directory of published versions and Timelines for an explanation of STU and other statuses.

4.3.1.620 4.4.1.241 Value Set http://hl7.org/fhir/ValueSet/bundle-type

FHIR Infrastructure Work Group   Maturity Level : 5 Normative Use Context : Any

Normative Candidate Note: This page is candidate normative content for R4 in the Infrastructure Package . Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made.

This is a value set defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/ValueSet/bundle-type
Version: 3.6.0
Name: BundleType
Title: BundleType
Definition:

Indicates the purpose of a bundle - how it was is intended to be used.

Committee: FHIR Infrastructure Work Group
OID: 2.16.840.1.113883.4.642.3.620 (for OID based terminology systems)
Source Resource XML / JSON

This value set is used in the following places:

4.3.1.620.1 4.4.1.241.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.1.620.2 4.4.1.241.2 Expansion

This expansion generated 03 Apr 20 Oct 2018

This value set contains 9 concepts

Expansion based on http://hl7.org/fhir/bundle-type version 3.3.0 3.6.0

All codes from system http://hl7.org/fhir/bundle-type
Code Display Definition
document Document The bundle is a document. The first resource is a Composition.
message Message The bundle is a message. The first resource is a MessageHeader.
transaction Transaction The bundle is a transaction - intended to be processed by a server as an atomic commit.
transaction-response Transaction Response The bundle is a transaction response. Because the response is a transaction response, the transaction has succeeded, and all responses are error free.
batch Batch The bundle is a transaction set of actions - intended to be processed by a server as a group of independent actions.
batch-response Batch Response The bundle is a batch response. Note that as a batch, some responses may indicate failure and others success.
history History List The bundle is a list of resources from a history interaction on a server.
searchset Search Results The bundle is a list of resources returned as a result of a search/query interaction, operation, or message.
collection Collection The bundle is a set of resources collected into a single package for ease of distribution. distribution that imposes no processing obligations or behavioral rules beyond persistence.

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
Source 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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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