PathSlice NameAlias(s)LabelMinMaxMust Support?Is Modifier?Is Summary?Type(s)MappingShortDefinitionCommentsRequirementsDefault ValueMeaning When MissingFixed ValuePatternExampleMinimum ValueMaximum ValueMaximum LengthBinding StrengthBinding DescriptionBinding Value SetCodeSlicing DiscriminatorSlicing DescriptionSlicing OrderedSlicing RulesBase PathBase MinBase MaxCondition(s)Constraint(s)Mapping: HL7 v2 MappingMapping: RIM MappingMapping: CDA (R2)Mapping: FiveWs Pattern MappingComments
Bundle0*Contains a collection of resourcesA container for a collection of resources.Bundle0*bdl-7:FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles) {(type = 'history') or entry.where(fullUrl.exists()).select(fullUrl&resource.meta.versionId).isDistinct()} bdl-9:A document must have an identifier with a system and a value {type = 'document' implies (identifier.system.exists() and identifier.value.exists())}bdl-3:entry.request mandatory for batch/transaction/history, otherwise prohibited {entry.all(request.exists() = (%resource.type = 'batch' or %resource.type = 'transaction' or %resource.type = 'history'))}bdl-4:entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited {entry.all(response.exists() = (%resource.type = 'batch-response' or %resource.type = 'transaction-response' or %resource.type = 'history'))}bdl-12:A message must have a MessageHeader as the first resource {type = 'message' implies entry.first().resource.is(MessageHeader)}bdl-1:total only when a search or history {total.empty() or (type = 'searchset') or (type = 'history')}bdl-2:entry.search only when a search {entry.search.empty() or (type = 'searchset')}bdl-11:A document must have a Composition as the first resource {type = 'document' implies entry.first().resource.is(Composition)}bdl-10:A document must have a date {type = 'document' implies (meta.lastUpdated.hasValue())}N/AN/AClinicalDocument, if bundle.type = document
Bundle.id01Yid Logical id of this artifactThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.The only time that a resource does not have an id is when it is being submitted to the server using a create operation.Resource.id01
Bundle.meta01YMeta Metadata about the resourceThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.Resource.meta01
Bundle.meta.id01string Unique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.Element.id01n/a
Bundle.meta.versionId01Yid Version specific identifierThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.Meta.versionId01
Bundle.meta.lastUpdated01Yinstant Timestamp of when the bundle was last modifiedWhen the resource version last changedWhen the resource last changed - e.g. when the version changed.This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http.html#read) interaction.Meta.lastUpdated01This is different than Bundle.timestamp which is actual message timestamp
Bundle.meta.source01Yuri Identifies where the resource comes fromA uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](provenance.html#) information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.Meta.source01Should it be the uri of the system constructing the bundle or reflect data from MSH ?
Bundle.meta.profile0*Ycanonical(StructureDefinition) Profiles this resource claims to conform toA list of profiles (references to [StructureDefinition](structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](structuredefinition-definitions.html#StructureDefinition.url).It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.Meta.profile0*
Bundle.meta.security0*YCoding Security Labels applied to this resourceSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.extensibleSecurity Labels from the Healthcare Privacy and Security Classification System.http://hl7.org/fhir/ValueSet/security-labelsMeta.security0*
Bundle.meta.tag0*YCoding Tags applied to this resourceTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.exampleCodes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".http://hl7.org/fhir/ValueSet/common-tagsMeta.tag0*
Bundle.implicitRules01YYuri A set of rules under which this content was createdA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.Resource.implicitRules01
Bundle.language01code language code (http://hl7.org/fhir/ValueSet/languages)Language of the resource contentThe base language in which the resource is written.Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).preferredA human language.http://hl7.org/fhir/ValueSet/languagesResource.language01
Bundle.identifier01YIdentifier MSH-10Persistent identifier for the bundleA persistent identifier for the bundle that won't change as a 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 and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.Bundle.identifier01ClinicalDocument.idFiveWs.identifier
Bundle.type11Ycode messagedocument | message | transaction | transaction-response | batch | batch-response | history | searchset | collectionIndicates the purpose of this bundle - how it 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.requiredIndicates the purpose of a bundle - how it is intended to be used.http://hl7.org/fhir/ValueSet/bundle-type|4.0.0Bundle.type11FiveWs.class
Bundle.timestamp01Yinstant MSH-7When the bundle was assembledThe 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.Bundle.timestamp01ClinicalDocument.effectiveTimeFiveWs.initTimestamp of the HL7 message.
Bundle.total01YunsignedInt If search, the total number of matchesIf a set of search matches, this is the total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in 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.Bundle.total01bdl-1
Bundle.link0*YBackboneElement Links related to this BundleA 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](http://en.wikipedia.org/wiki/HATEOAS)). Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http.html#read) directly. This specification defines some specific uses of Bundle.link for [searching](search.html#conformance) and [paging](http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.Bundle.link0*ele-1:All FHIR elements must have a @value or children {hasValue() or (children().count() > id.count())}
Bundle.link.id01string Unique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.Element.id01n/a
Bundle.link.extensionextensions user content0*Extension Additional content defined by implementationsMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Element.extension0*n/a
Bundle.link.modifierExtensionextensions user contentmodifiers0*YYExtension Extensions that cannot be ignored even if unrecognizedMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).BackboneElement.modifierExtension0*N/A
Bundle.link.relation11Ystring See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1A name which details the functional use for this link - see [http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1](http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1).Bundle.link.relation11
Bundle.link.url11Yuri Reference details for the linkThe reference details for the link.Bundle.link.url11
Bundle.entry0*YBackboneElement Entry in the bundle - will have a resource or informationAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).Bundle.entry0*ele-1:All FHIR elements must have a @value or children {hasValue() or (children().count() > id.count())} bdl-8:fullUrl cannot be a version specific reference {fullUrl.contains('/_history/').not()}bdl-5:must be a resource unless there's a request or response {resource.exists() or request.exists() or response.exists()}MessageHeader Resource to be the first resource in the bundle
Bundle.entry.id01string Unique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.Element.id01n/a
Bundle.entry.extensionextensions user content0*Extension Additional content defined by implementationsMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Element.extension0*n/a
Bundle.entry.modifierExtensionextensions user contentmodifiers0*YYExtension Extensions that cannot be ignored even if unrecognizedMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).BackboneElement.modifierExtension0*N/A
Bundle.entry.link0*YLinks related to this entryA series of links that provide context to this entry.Bundle.entry.link0*
Bundle.entry.fullUrl01Yuri URI for resource (Absolute URL server address or URI for UUID/OID)The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the 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 might not be [unique in the context of a resource](bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](references.html#regex), then 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).Bundle.entry.fullUrl01
Bundle.entry.resource01YResource A resource in the bundleThe Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.Bundle.entry.resource01
Bundle.entry.search01YBackboneElement N/ASearch related informationInformation about the search process that lead to the creation of this entry.Bundle.entry.search01bdl-2 ele-1:All FHIR elements must have a @value or children {hasValue() or (children().count() > id.count())}
Bundle.entry.search.id01string N/AUnique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.Element.id01n/a
Bundle.entry.search.extensionextensions user content0*Extension N/AAdditional content defined by implementationsMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Element.extension0*n/a
Bundle.entry.search.modifierExtensionextensions user contentmodifiers0*YYExtension N/AExtensions that cannot be ignored even if unrecognizedMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).BackboneElement.modifierExtension0*N/A
Bundle.entry.search.mode01Ycode N/Amatch | include | outcome - why this is in the result setWhy this entry is in the result set - whether it's included as a match or because of an _include 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.requiredWhy an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.http://hl7.org/fhir/ValueSet/search-entry-mode|4.0.0Bundle.entry.search.mode01
Bundle.entry.search.score01Ydecimal N/ASearch ranking (between 0 and 1)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](patient-operation-match.html) for the EMPI search which relates to this element.Bundle.entry.search.score01
Bundle.entry.request01YBackboneElement N/AAdditional execution information (transaction/batch/history)Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.Bundle.entry.request01bdl-3 ele-1:All FHIR elements must have a @value or children {hasValue() or (children().count() > id.count())}
Bundle.entry.request.id01string N/AUnique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.Element.id01n/a
Bundle.entry.request.extensionextensions user content0*Extension N/AAdditional content defined by implementationsMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Element.extension0*n/a
Bundle.entry.request.modifierExtensionextensions user contentmodifiers0*YYExtension N/AExtensions that cannot be ignored even if unrecognizedMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).BackboneElement.modifierExtension0*N/A
Bundle.entry.request.method11Ycode N/AGET | HEAD | POST | PUT | DELETE | PATCHIn a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.requiredHTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details.http://hl7.org/fhir/ValueSet/http-verb|4.0.0Bundle.entry.request.method11
Bundle.entry.request.url11Yuri N/AURL for HTTP equivalent of this entryThe 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" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".Bundle.entry.request.url11
Bundle.entry.request.ifNoneMatch01Ystring N/AFor managing cache currencyIf the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http.html#cread).Bundle.entry.request.ifNoneMatch01
Bundle.entry.request.ifModifiedSince01Yinstant N/AFor managing cache currencyOnly perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http.html#cread).Bundle.entry.request.ifModifiedSince01
Bundle.entry.request.ifMatch01Ystring N/AFor managing update contentionOnly perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http.html#concurrency).Bundle.entry.request.ifMatch01
Bundle.entry.request.ifNoneExist01Ystring N/AFor conditional createsInstruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").Bundle.entry.request.ifNoneExist01
Bundle.entry.response01YBackboneElement N/AResults of execution (transaction/batch/history)Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.Bundle.entry.response01bdl-4 ele-1:All FHIR elements must have a @value or children {hasValue() or (children().count() > id.count())}
Bundle.entry.response.id01string N/AUnique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.Element.id01n/a
Bundle.entry.response.extensionextensions user content0*Extension N/AAdditional content defined by implementationsMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Element.extension0*n/a
Bundle.entry.response.modifierExtensionextensions user contentmodifiers0*YYExtension N/AExtensions that cannot be ignored even if unrecognizedMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).BackboneElement.modifierExtension0*N/A
Bundle.entry.response.status11Ystring N/AStatus response code (text optional)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.Bundle.entry.response.status11
Bundle.entry.response.location01Yuri N/AThe location (if the operation returns a location)The location header created by processing this operation, populated if the operation returns a location.Bundle.entry.response.location01
Bundle.entry.response.etag01Ystring N/AThe Etag for the resource (if relevant)The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http.html#versioning) and [Managing Resource Contention](http.html#concurrency)).Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.Bundle.entry.response.etag01
Bundle.entry.response.lastModified01Yinstant N/AServer's date time modifiedThe 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.Bundle.entry.response.lastModified01
Bundle.entry.response.outcome01YResource N/AOperationOutcome with hints and warnings (for batch/transaction)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.Bundle.entry.response.outcome01
Bundle.signature01YSignature N/ADigital SignatureDigital Signature - base64 encoded. XML-DSig or a JWT.The signature could be created by the "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.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, messages, transactions or even 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.Bundle.signature01