A container for a collection of resources.

A persistent identifier for the batch bundle that won't change as a batch bundle is copied from server to server.

Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results, results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.

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

It's possible to use a bundle for other purposes (e.g. a document can be accepted as a transaction). This is primarily defined so that there can be specific rules for some of the bundle types.

The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle.

For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated.

Usage:

• document : the date the document was created. Note: the composition may predate the document, or be associated with multiple documents. The date of the composition - the authoring time - may be earlier than the document assembly time
• message : the date that the content of the message was assembled. This date is not changed by middleware engines unless they add additional data that changes the meaning of the time of the message
• history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates
• searchset : the time that the search set was assembled. Note that different pages MAY have different timestamps but need not. Having different timestamps does not imply that subsequent pages will represent or include changes made since the initial query
• transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning

The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself.

If a set of search matches, this is the total number of matches for entries of type 'match' across all pages in the search (as opposed to search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of results entries in this bundle). the Bundle.

Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources.

A series of links that provide context to this bundle.

Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS ).

Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was read directly.

This specification defines some specific uses of Bundle.link for searching and paging , but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.

A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 .

The reference details for the link.

An entry in a bundle resource - will either contain a resource, resource or information about a resource (transactions and history only).

A series of links that provide context to this entry.

The Absolute URL for the resource. The fullUrl SHALL not NOT disagree with the id in the resource. resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that: *

• fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle) *
• Results from operations might involve resources that are not identified.

fullUrl may might not be unique in the context of a resource . Note that since FHIR resources do not need to be served through the FHIR API , the fullURL might be a URN or an absolute URL may that does not end with the logical id of the resource (Resource.id), (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the regex , then it the 'id' portion of the fullUrl SHALL end with the Resource.id.

Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).

The Resources Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.

Information about the search process that lead to the creation of this entry.

Why this entry is in the result set - whether it's included as a match or because of an _include requirement. requirement, or to convey information or warning information about the search process.

There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.

When searching, the server's search ranking score for the entry.

Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.

See Patient Match for the EMPI search which relates to this element.

Additional information about how this entry should be processed as part of a transaction. transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.

The In a transaction or batch, this is the HTTP verb action to be executed for this entry in either a change history, or entry. In a transaction/ transaction response. history bundle, this indicates the HTTP action that occurred.

The URL for this entry, relative to the root (the address to which the request is posted).

E.g. for a Patient Create, the method would be "POST" "POST" and the URL would be "Patient". "Patient". For a Patient Update, the method would be PUT, PUT and the URL would be "Patient/[id]". "Patient/[id]".

If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read" "Conditional Read" .

Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read" "Conditional Read" .

Only perform the operation if the Etag value matches. For more information, see the API section "Managing "Managing Resource Contention" Contention" .

Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create" "Conditional Create" . This is just the query portion of the URL - what follows the "?" "?" (not including the "?"). "?").

Additional information about how this Indicates the results of processing the corresponding 'request' entry should be processed as part in the batch or transaction being responded to or what the results of a transaction. an operation where when returning history.

The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.

The location header created by processing this operation. operation, populated if the operation returns a location.

The etag Etag for the resource, it if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention ).

Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.

The date/time that the resource was modified on the server.

This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.

An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction.

For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.

This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.

Digital Signature - base64 encoded. XML-DSIg XML-DSig or a JWT.

A Signature holds an electronic representation of a signature and its supporting context in a FHIR accessible form. The signature may either be a cryptographic type (XML DigSig or a JWS), which is able to provide non-repudiation proof, or it may be a graphical image that represents a signature or a signature process. This element allows capturing signatures on documents. It also allows signatures on documents, messages, transactions or even query responses. It may search responses, to support content-authentication, non-repudiation or other business cases. This is primarily relevant where the bundle may travel through multiple hops or via other mechanisms where HTTPS non-repudiation is insufficient.

The signature could be created by the "author" "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.