Extensions for Using Data Elements from FHIR R4B in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR R4 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
{
"resourceType" : "ConceptMap",
"id" : "R4B-Bundle-element-map-to-R4",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ConceptMap R4B-Bundle-element-map-to-R4</b></p><a name=\"R4B-Bundle-element-map-to-R4\"> </a><a name=\"hcR4B-Bundle-element-map-to-R4\"> </a><p>Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Bundle|4.3.0</code> to <a href=\"http://hl7.org/fhir/R4/bundle.html\">Bundleversion: 4.0.1)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Bundle.meta (meta)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.meta</td><td>Element `Bundle.meta` is mapped to FHIR R4 element `Bundle.meta` as `Equivalent`.</td></tr><tr><td>Bundle.implicitRules (implicitRules)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.implicitRules</td><td>Element `Bundle.implicitRules` is mapped to FHIR R4 element `Bundle.implicitRules` as `Equivalent`.\nAsserting 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.</td></tr><tr><td>Bundle.language (language)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.language</td><td>Element `Bundle.language` is mapped to FHIR R4 element `Bundle.language` as `Equivalent`.\nLanguage 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).</td></tr><tr><td>Bundle.identifier (identifier)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.identifier</td><td>Element `Bundle.identifier` is mapped to FHIR R4 element `Bundle.identifier` as `Equivalent`.\nPersistent 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.</td></tr><tr><td>Bundle.type (type)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.type</td><td>Element `Bundle.type` is mapped to FHIR R4 element `Bundle.type` as `Equivalent`.\nIt'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.</td></tr><tr><td>Bundle.timestamp (timestamp)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.timestamp</td><td>Element `Bundle.timestamp` is mapped to FHIR R4 element `Bundle.timestamp` as `Equivalent`.\nFor 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. \n\nUsage:\n\n* 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\n* 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\n* history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates\n* 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\n* transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning\n\nThe 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.</td></tr><tr><td>Bundle.total (total)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.total</td><td>Element `Bundle.total` is mapped to FHIR R4 element `Bundle.total` as `Equivalent`.\nOnly 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.</td></tr><tr><td>Bundle.link (link)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Bundle.link</td><td>Element `Bundle.link` is mapped to FHIR R4 element `Bundle.link` as `Equivalent`.\nBoth 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)). \n\nBundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](https://hl7.org/fhir/http..html#read) directly.\n\nThis specification defines some specific uses of Bundle.link for [searching](https://hl7.org/fhir/search.html#.html#conformance) and [paging](https://hl7.org/fhir/http.ht.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.</td></tr><tr><td>Bundle.link.relation (relation)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.link.relation</td><td>Element `Bundle.link.relation` is mapped to FHIR R4 element `Bundle.link.relation` as `Equivalent`.</td></tr><tr><td>Bundle.link.url (url)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.link.url</td><td>Element `Bundle.link.url` is mapped to FHIR R4 element `Bundle.link.url` as `Equivalent`.</td></tr><tr><td>Bundle.entry (entry)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Bundle.entry</td><td>Element `Bundle.entry` is mapped to FHIR R4 element `Bundle.entry` as `Equivalent`.</td></tr><tr><td>Bundle.entry.link (link)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.link</td><td>Element `Bundle.entry.link` is mapped to FHIR R4 element `Bundle.entry.link` as `Equivalent`.</td></tr><tr><td>Bundle.entry.fullUrl (fullUrl)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.fullUrl</td><td>Element `Bundle.entry.fullUrl` is mapped to FHIR R4 element `Bundle.entry.fullUrl` as `Equivalent`.\nfullUrl might not be [unique in the context of a resource](https://hl7.org/fhir/bundle.html#bu.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](https://hl7.org/fhir/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](https://hl7.org/fhir/refere.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.\n\nNote 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).</td></tr><tr><td>Bundle.entry.resource (resource)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.resource</td><td>Element `Bundle.entry.resource` is mapped to FHIR R4 element `Bundle.entry.resource` as `Equivalent`.</td></tr><tr><td>Bundle.entry.search (search)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Bundle.entry.search</td><td>Element `Bundle.entry.search` is mapped to FHIR R4 element `Bundle.entry.search` as `Equivalent`.</td></tr><tr><td>Bundle.entry.search.mode (mode)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.search.mode</td><td>Element `Bundle.entry.search.mode` is mapped to FHIR R4 element `Bundle.entry.search.mode` as `Equivalent`.\nThere 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.</td></tr><tr><td>Bundle.entry.search.score (score)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.search.score</td><td>Element `Bundle.entry.search.score` is mapped to FHIR R4 element `Bundle.entry.search.score` as `Equivalent`.\nServers 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.\n\nSee [Patient Match](https://hl7.org/fhir/patient-operation-match.html) for the EMPI search which relates to this element.</td></tr><tr><td>Bundle.entry.request (request)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Bundle.entry.request</td><td>Element `Bundle.entry.request` is mapped to FHIR R4 element `Bundle.entry.request` as `Equivalent`.</td></tr><tr><td>Bundle.entry.request.method (method)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.request.method</td><td>Element `Bundle.entry.request.method` is mapped to FHIR R4 element `Bundle.entry.request.method` as `Equivalent`.</td></tr><tr><td>Bundle.entry.request.url (url)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.request.url</td><td>Element `Bundle.entry.request.url` is mapped to FHIR R4 element `Bundle.entry.request.url` as `Equivalent`.\nE.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]".</td></tr><tr><td>Bundle.entry.request.ifNoneMatch (ifNoneMatch)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.request.ifNoneMatch</td><td>Element `Bundle.entry.request.ifNoneMatch` is mapped to FHIR R4 element `Bundle.entry.request.ifNoneMatch` as `Equivalent`.</td></tr><tr><td>Bundle.entry.request.ifModifiedSince (ifModifiedSince)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.request.ifModifiedSince</td><td>Element `Bundle.entry.request.ifModifiedSince` is mapped to FHIR R4 element `Bundle.entry.request.ifModifiedSince` as `Equivalent`.</td></tr><tr><td>Bundle.entry.request.ifMatch (ifMatch)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.request.ifMatch</td><td>Element `Bundle.entry.request.ifMatch` is mapped to FHIR R4 element `Bundle.entry.request.ifMatch` as `Equivalent`.</td></tr><tr><td>Bundle.entry.request.ifNoneExist (ifNoneExist)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.request.ifNoneExist</td><td>Element `Bundle.entry.request.ifNoneExist` is mapped to FHIR R4 element `Bundle.entry.request.ifNoneExist` as `Equivalent`.</td></tr><tr><td>Bundle.entry.response (response)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Bundle.entry.response</td><td>Element `Bundle.entry.response` is mapped to FHIR R4 element `Bundle.entry.response` as `Equivalent`.</td></tr><tr><td>Bundle.entry.response.status (status)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.response.status</td><td>Element `Bundle.entry.response.status` is mapped to FHIR R4 element `Bundle.entry.response.status` as `Equivalent`.</td></tr><tr><td>Bundle.entry.response.location (location)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.response.location</td><td>Element `Bundle.entry.response.location` is mapped to FHIR R4 element `Bundle.entry.response.location` as `Equivalent`.</td></tr><tr><td>Bundle.entry.response.etag (etag)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.response.etag</td><td>Element `Bundle.entry.response.etag` is mapped to FHIR R4 element `Bundle.entry.response.etag` as `Equivalent`.\nEtags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.</td></tr><tr><td>Bundle.entry.response.lastModified (lastModified)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.response.lastModified</td><td>Element `Bundle.entry.response.lastModified` is mapped to FHIR R4 element `Bundle.entry.response.lastModified` as `Equivalent`.\nThis has to match the same time in the meta header (meta.lastUpdated) if a resource is included.</td></tr><tr><td>Bundle.entry.response.outcome (outcome)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.entry.response.outcome</td><td>Element `Bundle.entry.response.outcome` is mapped to FHIR R4 element `Bundle.entry.response.outcome` as `Equivalent`.\nFor 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.\n\nThis 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.</td></tr><tr><td>Bundle.signature (signature)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Bundle.signature</td><td>Element `Bundle.signature` is mapped to FHIR R4 element `Bundle.signature` as `Equivalent`.\nThe 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.</td></tr></table></div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "fhir"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger" : 0,
"_valueInteger" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "trial-use",
"_valueCode" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
}
],
"url" : "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-Bundle-element-map-to-R4",
"version" : "0.1.0",
"name" : "R4BBundleElementMapToR4",
"title" : "Cross-version mapping for FHIR R4B Bundle to FHIR R4 Bundle",
"status" : "active",
"experimental" : false,
"date" : "2026-03-17T16:03:46.1779875-05:00",
"contact" : [
{
"name" : "FHIR Infrastructure",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description" : "This ConceptMap represents cross-version mappings for elements from a FHIR R4B Bundle to FHIR R4.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"sourceCanonical" : "http://hl7.org/fhir/4.3",
"targetUri" : "http://hl7.org/fhir/4.0",
"group" : [
{
"source" : "http://hl7.org/fhir/StructureDefinition/Bundle",
"sourceVersion" : "4.3.0",
"target" : "http://hl7.org/fhir/StructureDefinition/Bundle",
"targetVersion" : "4.0.1",
"element" : [
{
"code" : "Bundle.meta",
"display" : "meta",
"target" : [
{
"code" : "Bundle.meta",
"display" : "Bundle.meta",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.meta` is mapped to FHIR R4 element `Bundle.meta` as `Equivalent`."
}
]
},
{
"code" : "Bundle.implicitRules",
"display" : "implicitRules",
"target" : [
{
"code" : "Bundle.implicitRules",
"display" : "Bundle.implicitRules",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.implicitRules` is mapped to FHIR R4 element `Bundle.implicitRules` as `Equivalent`.\nAsserting 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."
}
]
},
{
"code" : "Bundle.language",
"display" : "language",
"target" : [
{
"code" : "Bundle.language",
"display" : "Bundle.language",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.language` is mapped to FHIR R4 element `Bundle.language` as `Equivalent`.\nLanguage 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)."
}
]
},
{
"code" : "Bundle.identifier",
"display" : "identifier",
"target" : [
{
"code" : "Bundle.identifier",
"display" : "Bundle.identifier",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.identifier` is mapped to FHIR R4 element `Bundle.identifier` as `Equivalent`.\nPersistent 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."
}
]
},
{
"code" : "Bundle.type",
"display" : "type",
"target" : [
{
"code" : "Bundle.type",
"display" : "Bundle.type",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.type` is mapped to FHIR R4 element `Bundle.type` as `Equivalent`.\nIt'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."
}
]
},
{
"code" : "Bundle.timestamp",
"display" : "timestamp",
"target" : [
{
"code" : "Bundle.timestamp",
"display" : "Bundle.timestamp",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.timestamp` is mapped to FHIR R4 element `Bundle.timestamp` as `Equivalent`.\nFor 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. \n\nUsage:\n\n* 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\n* 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\n* history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates\n* 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\n* transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning\n\nThe 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."
}
]
},
{
"code" : "Bundle.total",
"display" : "total",
"target" : [
{
"code" : "Bundle.total",
"display" : "Bundle.total",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.total` is mapped to FHIR R4 element `Bundle.total` as `Equivalent`.\nOnly 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."
}
]
},
{
"code" : "Bundle.link",
"display" : "link",
"target" : [
{
"code" : "Bundle.link",
"display" : "Bundle.link",
"equivalence" : "wider",
"comment" : "Element `Bundle.link` is mapped to FHIR R4 element `Bundle.link` as `Equivalent`.\nBoth 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)). \n\nBundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](https://hl7.org/fhir/http..html#read) directly.\n\nThis specification defines some specific uses of Bundle.link for [searching](https://hl7.org/fhir/search.html#.html#conformance) and [paging](https://hl7.org/fhir/http.ht.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific."
}
]
},
{
"code" : "Bundle.link.relation",
"display" : "relation",
"target" : [
{
"code" : "Bundle.link.relation",
"display" : "Bundle.link.relation",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.link.relation` is mapped to FHIR R4 element `Bundle.link.relation` as `Equivalent`."
}
]
},
{
"code" : "Bundle.link.url",
"display" : "url",
"target" : [
{
"code" : "Bundle.link.url",
"display" : "Bundle.link.url",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.link.url` is mapped to FHIR R4 element `Bundle.link.url` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry",
"display" : "entry",
"target" : [
{
"code" : "Bundle.entry",
"display" : "Bundle.entry",
"equivalence" : "wider",
"comment" : "Element `Bundle.entry` is mapped to FHIR R4 element `Bundle.entry` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.link",
"display" : "link",
"target" : [
{
"code" : "Bundle.entry.link",
"display" : "Bundle.entry.link",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.link` is mapped to FHIR R4 element `Bundle.entry.link` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.fullUrl",
"display" : "fullUrl",
"target" : [
{
"code" : "Bundle.entry.fullUrl",
"display" : "Bundle.entry.fullUrl",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.fullUrl` is mapped to FHIR R4 element `Bundle.entry.fullUrl` as `Equivalent`.\nfullUrl might not be [unique in the context of a resource](https://hl7.org/fhir/bundle.html#bu.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](https://hl7.org/fhir/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](https://hl7.org/fhir/refere.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.\n\nNote 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)."
}
]
},
{
"code" : "Bundle.entry.resource",
"display" : "resource",
"target" : [
{
"code" : "Bundle.entry.resource",
"display" : "Bundle.entry.resource",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.resource` is mapped to FHIR R4 element `Bundle.entry.resource` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.search",
"display" : "search",
"target" : [
{
"code" : "Bundle.entry.search",
"display" : "Bundle.entry.search",
"equivalence" : "wider",
"comment" : "Element `Bundle.entry.search` is mapped to FHIR R4 element `Bundle.entry.search` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.search.mode",
"display" : "mode",
"target" : [
{
"code" : "Bundle.entry.search.mode",
"display" : "Bundle.entry.search.mode",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.search.mode` is mapped to FHIR R4 element `Bundle.entry.search.mode` as `Equivalent`.\nThere 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."
}
]
},
{
"code" : "Bundle.entry.search.score",
"display" : "score",
"target" : [
{
"code" : "Bundle.entry.search.score",
"display" : "Bundle.entry.search.score",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.search.score` is mapped to FHIR R4 element `Bundle.entry.search.score` as `Equivalent`.\nServers 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.\n\nSee [Patient Match](https://hl7.org/fhir/patient-operation-match.html) for the EMPI search which relates to this element."
}
]
},
{
"code" : "Bundle.entry.request",
"display" : "request",
"target" : [
{
"code" : "Bundle.entry.request",
"display" : "Bundle.entry.request",
"equivalence" : "wider",
"comment" : "Element `Bundle.entry.request` is mapped to FHIR R4 element `Bundle.entry.request` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.request.method",
"display" : "method",
"target" : [
{
"code" : "Bundle.entry.request.method",
"display" : "Bundle.entry.request.method",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.request.method` is mapped to FHIR R4 element `Bundle.entry.request.method` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.request.url",
"display" : "url",
"target" : [
{
"code" : "Bundle.entry.request.url",
"display" : "Bundle.entry.request.url",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.request.url` is mapped to FHIR R4 element `Bundle.entry.request.url` as `Equivalent`.\nE.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]\"."
}
]
},
{
"code" : "Bundle.entry.request.ifNoneMatch",
"display" : "ifNoneMatch",
"target" : [
{
"code" : "Bundle.entry.request.ifNoneMatch",
"display" : "Bundle.entry.request.ifNoneMatch",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.request.ifNoneMatch` is mapped to FHIR R4 element `Bundle.entry.request.ifNoneMatch` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.request.ifModifiedSince",
"display" : "ifModifiedSince",
"target" : [
{
"code" : "Bundle.entry.request.ifModifiedSince",
"display" : "Bundle.entry.request.ifModifiedSince",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.request.ifModifiedSince` is mapped to FHIR R4 element `Bundle.entry.request.ifModifiedSince` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.request.ifMatch",
"display" : "ifMatch",
"target" : [
{
"code" : "Bundle.entry.request.ifMatch",
"display" : "Bundle.entry.request.ifMatch",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.request.ifMatch` is mapped to FHIR R4 element `Bundle.entry.request.ifMatch` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.request.ifNoneExist",
"display" : "ifNoneExist",
"target" : [
{
"code" : "Bundle.entry.request.ifNoneExist",
"display" : "Bundle.entry.request.ifNoneExist",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.request.ifNoneExist` is mapped to FHIR R4 element `Bundle.entry.request.ifNoneExist` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.response",
"display" : "response",
"target" : [
{
"code" : "Bundle.entry.response",
"display" : "Bundle.entry.response",
"equivalence" : "wider",
"comment" : "Element `Bundle.entry.response` is mapped to FHIR R4 element `Bundle.entry.response` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.response.status",
"display" : "status",
"target" : [
{
"code" : "Bundle.entry.response.status",
"display" : "Bundle.entry.response.status",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.response.status` is mapped to FHIR R4 element `Bundle.entry.response.status` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.response.location",
"display" : "location",
"target" : [
{
"code" : "Bundle.entry.response.location",
"display" : "Bundle.entry.response.location",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.response.location` is mapped to FHIR R4 element `Bundle.entry.response.location` as `Equivalent`."
}
]
},
{
"code" : "Bundle.entry.response.etag",
"display" : "etag",
"target" : [
{
"code" : "Bundle.entry.response.etag",
"display" : "Bundle.entry.response.etag",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.response.etag` is mapped to FHIR R4 element `Bundle.entry.response.etag` as `Equivalent`.\nEtags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included."
}
]
},
{
"code" : "Bundle.entry.response.lastModified",
"display" : "lastModified",
"target" : [
{
"code" : "Bundle.entry.response.lastModified",
"display" : "Bundle.entry.response.lastModified",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.response.lastModified` is mapped to FHIR R4 element `Bundle.entry.response.lastModified` as `Equivalent`.\nThis has to match the same time in the meta header (meta.lastUpdated) if a resource is included."
}
]
},
{
"code" : "Bundle.entry.response.outcome",
"display" : "outcome",
"target" : [
{
"code" : "Bundle.entry.response.outcome",
"display" : "Bundle.entry.response.outcome",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.entry.response.outcome` is mapped to FHIR R4 element `Bundle.entry.response.outcome` as `Equivalent`.\nFor 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.\n\nThis 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."
}
]
},
{
"code" : "Bundle.signature",
"display" : "signature",
"target" : [
{
"code" : "Bundle.signature",
"display" : "Bundle.signature",
"equivalence" : "equivalent",
"comment" : "Element `Bundle.signature` is mapped to FHIR R4 element `Bundle.signature` as `Equivalent`.\nThe 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."
}
]
}
]
}
]
}
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4b.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change