Release 5 4

This page is part of the FHIR Specification (v5.0.0: R5 (v4.0.1: R4 - Mixed Normative and STU ). This is the ) in it's permanent home (it will always be available at this URL). The current published version. version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

4.4.1.137 4.4.1.243 ValueSet Value Set http://hl7.org/fhir/ValueSet/bundle-type

FHIR Infrastructure Work Group   Maturity Level : N Normative (from v4.0.0) Use Context : Country: World Any
This page has been approved as part of an ANSI Narrative standard. See the Infrastructure Package for further details.

This is a value set defined by the FHIR project.

Summary

XML JSON TTL Official URL : http://hl7.org/fhir/ValueSet/bundle-type active as of 2020-12-28 Flags : Immutable OID :
Defining URL: http://hl7.org/fhir/ValueSet/bundle-type
Version: 4.0.1
Name: BundleType
Title: BundleType
Definition: Version : 5.0.0

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

Committee: Computable Name : BundleType 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:


This value set includes codes from the following code systems:

 

This expansion generated 26 Mar 2023 01 Nov 2019


This value set contains 10 9 concepts

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

All codes from system Bundle Type v5.0.0 (CodeSystem) http://hl7.org/fhir/bundle-type

Code System Display Definition
   document http://hl7.org/fhir/bundle-type Document The bundle is a document. The first resource is a Composition.
   message http://hl7.org/fhir/bundle-type Message The bundle is a message. The first resource is a MessageHeader.
   transaction http://hl7.org/fhir/bundle-type Transaction The bundle is a transaction - intended to be processed by a server as an atomic commit.
   transaction-response http://hl7.org/fhir/bundle-type 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 http://hl7.org/fhir/bundle-type Batch The bundle is a set of actions - intended to be processed by a server as a group of independent actions.
   batch-response http://hl7.org/fhir/bundle-type Batch Response The bundle is a batch response. Note that as a batch, some responses may indicate failure and others success.
   history http://hl7.org/fhir/bundle-type History List The bundle is a list of resources from a history interaction on a server.
   searchset http://hl7.org/fhir/bundle-type Search Results The bundle is a list of resources returned as a result of a search/query interaction, operation, or message.
   collection http://hl7.org/fhir/bundle-type Collection 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.    subscription-notification http://hl7.org/fhir/bundle-type Subscription Notification The bundle has been generated by a Subscription to communicate information to a client.

 

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