Bundles
- Air filter replaced
- Wild Cycle
- Test Strip Bottle Enrolled
- Water Filter Replaced
- HLD Replaced
- Disinfection Cycle
- Firmware Replaced
- Annual Calibration and Conductivity Probe Replaced
Air filter replaced
AirFilterReplacedBundle (Bundle) | C | Bundle | |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
identifier | Σ C | 0..1 | Identifier |
type | Σ C | 1..1 | codeBindingFixed Value |
timestamp | Σ C | 0..1 | instant |
total | Σ C | 0..1 | unsignedInt |
link | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
relation | Σ C | 1..1 | codeBinding |
url | Σ C | 1..1 | uri |
entry | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
link | Σ | 0..* | see (link) |
fullUrl | Σ C | 0..1 | uri |
resource | Σ C | 0..1 | Procedure, Device, Practitioner |
id | 0..1 | string | |
extension | C | 0..* | Extension |
Procedure | |||
Device | |||
search | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
mode | Σ | 0..1 | codeBinding |
score | Σ | 0..1 | decimal |
request | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
method | Σ C | 1..1 | codeBinding |
url | Σ | 1..1 | uri |
ifNoneMatch | Σ | 0..1 | string |
ifModifiedSince | Σ | 0..1 | instant |
ifMatch | Σ | 0..1 | string |
ifNoneExist | Σ | 0..1 | string |
response | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
status | Σ | 1..1 | string |
location | Σ | 0..1 | uri |
etag | Σ | 0..1 | string |
lastModified | Σ | 0..1 | instant |
outcome | Σ | 0..1 | Resource |
signature | Σ | 0..1 | Signature |
issues | Σ C | 0..1 | OperationOutcome |
identifier |
Bundle | |
Short | Contains a collection of resources |
Definition | A container for a collection of resources. |
Cardinality | 0..* |
Constraints |
|
Mappings |
|
Bundle.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.identifier | |
Short | Persistent identifier for the bundle |
Definition | A persistent identifier for the bundle that won't change as a bundle is copied from server to server. |
Cardinality | 0..1 |
Type | Identifier |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-9 |
Constraints |
|
Mappings |
|
Bundle.type | |
Short | document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection | subscription-notification |
Definition | Indicates the purpose of this bundle - how it is intended to be used. |
Cardinality | 1..1 |
Type | code |
Binding | Indicates the purpose of a bundle - how it is intended to be used. |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1, bdl-2, bdl-3a, bdl-3b, bdl-3c, bdl-3d, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, bdl-13, bdl-14, bdl-15, bdl-17, bdl-18 |
Constraints |
|
Fixed Value | collection |
Mappings |
|
Bundle.timestamp | |
Short | When the bundle was assembled |
Definition | The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | 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:
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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-10 |
Constraints |
|
Mappings |
|
Bundle.total | |
Short | If search, the total number of matches |
Definition | If a set of search matches, this is the (potentially estimated) 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. |
Cardinality | 0..1 |
Type | unsignedInt |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1 |
Constraints |
|
Bundle.link | |
Short | Links related to this Bundle |
Definition | A series of links that provide context to this bundle. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Comments | 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. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.link.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.relation | |
Short | See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 |
Definition | A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. |
Cardinality | 1..1 |
Type | code |
Binding | |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.url | |
Short | Reference details for the link |
Definition | The reference details for the link. |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.entry | |
Short | Entry in the bundle - will have a resource or information |
Definition | An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Bundle.entry.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.link | |
Short | Links related to this entry |
Definition | A series of links that provide context to this entry. |
Cardinality | 0..* |
Type | see (link) |
Summary | True |
Constraints |
|
Bundle.entry.fullUrl | |
Short | URI for resource (e.g. the absolute URL server address, URI for UUID/OID, etc.) |
Definition | The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. 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. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
|
Cardinality | 0..1 |
Type | uri |
Summary | True |
Comments | fullUrl 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 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, 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). |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-7, bdl-15, bdl-8 |
Constraints |
|
Bundle.entry.resource | |
Short | A resource in the bundle |
Definition | The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning. |
Cardinality | 0..1 |
Type | Procedure, Device, Practitioner |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3c, bdl-7, bdl-11, bdl-12, bdl-13, bdl-5 |
Bundle.entry.resource.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.resource.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url |
Constraints |
|
Mappings |
|
Bundle.entry.resource.Procedure | |
Bundle.entry.resource.Device | |
Bundle.entry.search | |
Short | Search related information |
Definition | Information about the search process that lead to the creation of this entry. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-2 |
Constraints |
|
Bundle.entry.search.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.search.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.mode | |
Short | match | include - why this is in the result set |
Definition | Why 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. |
Cardinality | 0..1 |
Type | code |
Binding | Why 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. |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.search.score | |
Short | Search ranking (between 0 and 1) |
Definition | When searching, the server's search ranking score for the entry. |
Cardinality | 0..1 |
Type | decimal |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.request | |
Short | Additional execution information (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-5 |
Constraints |
|
Bundle.entry.request.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.request.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.method | |
Short | GET | HEAD | POST | PUT | DELETE | PATCH |
Definition | In 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. |
Cardinality | 1..1 |
Type | code |
Binding | HTTP verbs (in the HTTP command line). See HTTP rfc for details. |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3b, bdl-3c, bdl-14, bdl-15 |
Constraints |
|
Bundle.entry.request.url | |
Short | URL for HTTP equivalent of this entry |
Definition | The URL for this entry, relative to the root (the address to which the request is posted). |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | 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]". |
Constraints |
|
Bundle.entry.request.ifNoneMatch | |
Short | For managing cache validation |
Definition | If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifModifiedSince | |
Short | For managing cache currency |
Definition | Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Constraints |
|
Bundle.entry.request.ifMatch | |
Short | For managing update contention |
Definition | Only perform the operation if the Etag value matches. For more information, see the API section "Managing Resource Contention". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifNoneExist | |
Short | For conditional creates |
Definition | Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?"). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response | |
Short | Results of execution (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3d, bdl-5 |
Constraints |
|
Bundle.entry.response.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.response.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.status | |
Short | Status response code (text optional) |
Definition | 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. |
Cardinality | 1..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response.location | |
Short | The location (if the operation returns a location) |
Definition | The location header created by processing this operation, populated if the operation returns a location. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Constraints |
|
Bundle.entry.response.etag | |
Short | The Etag for the resource (if relevant) |
Definition | The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. |
Constraints |
|
Bundle.entry.response.lastModified | |
Short | Server's date time modified |
Definition | The date/time that the resource was modified on the server. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. |
Constraints |
|
Bundle.entry.response.outcome | |
Short | OperationOutcome with hints and warnings (for batch/transaction) |
Definition | An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. |
Cardinality | 0..1 |
Type | Resource |
Summary | True |
Comments | 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.signature | |
Short | Digital Signature |
Definition | Digital Signature - base64 encoded. XML-DSig or a JWS. |
Cardinality | 0..1 |
Type | Signature |
Summary | True |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Bundle.issues | |
Short | Issues with the Bundle |
Definition | Captures issues and warnings that relate to the construction of the Bundle and the content within it. |
Cardinality | 0..1 |
Type | OperationOutcome |
Summary | True |
Comments | Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-16, bdl-17 |
Bundle.identifier |
Wild Cycle
WildCycleBundle (Bundle) | C | Bundle | |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
identifier | Σ C | 0..1 | Identifier |
type | Σ C | 1..1 | codeBindingFixed Value |
timestamp | Σ C | 0..1 | instant |
total | Σ C | 0..1 | unsignedInt |
link | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
relation | Σ C | 1..1 | codeBinding |
url | Σ C | 1..1 | uri |
entry | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
link | Σ | 0..* | see (link) |
fullUrl | Σ C | 0..1 | uri |
resource | Σ C | 0..1 | Procedure, Observation, Practitioner, Device |
id | 0..1 | string | |
extension | C | 0..* | Extension |
Procedure | |||
Observation | |||
Device | |||
search | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
mode | Σ | 0..1 | codeBinding |
score | Σ | 0..1 | decimal |
request | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
method | Σ C | 1..1 | codeBinding |
url | Σ | 1..1 | uri |
ifNoneMatch | Σ | 0..1 | string |
ifModifiedSince | Σ | 0..1 | instant |
ifMatch | Σ | 0..1 | string |
ifNoneExist | Σ | 0..1 | string |
response | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
status | Σ | 1..1 | string |
location | Σ | 0..1 | uri |
etag | Σ | 0..1 | string |
lastModified | Σ | 0..1 | instant |
outcome | Σ | 0..1 | Resource |
signature | Σ | 0..1 | Signature |
issues | Σ C | 0..1 | OperationOutcome |
identifier |
Bundle | |
Short | Contains a collection of resources |
Definition | A container for a collection of resources. |
Cardinality | 0..* |
Constraints |
|
Mappings |
|
Bundle.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.identifier | |
Short | Persistent identifier for the bundle |
Definition | A persistent identifier for the bundle that won't change as a bundle is copied from server to server. |
Cardinality | 0..1 |
Type | Identifier |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-9 |
Constraints |
|
Mappings |
|
Bundle.type | |
Short | document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection | subscription-notification |
Definition | Indicates the purpose of this bundle - how it is intended to be used. |
Cardinality | 1..1 |
Type | code |
Binding | Indicates the purpose of a bundle - how it is intended to be used. |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1, bdl-2, bdl-3a, bdl-3b, bdl-3c, bdl-3d, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, bdl-13, bdl-14, bdl-15, bdl-17, bdl-18 |
Constraints |
|
Fixed Value | collection |
Mappings |
|
Bundle.timestamp | |
Short | When the bundle was assembled |
Definition | The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | 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:
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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-10 |
Constraints |
|
Mappings |
|
Bundle.total | |
Short | If search, the total number of matches |
Definition | If a set of search matches, this is the (potentially estimated) 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. |
Cardinality | 0..1 |
Type | unsignedInt |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1 |
Constraints |
|
Bundle.link | |
Short | Links related to this Bundle |
Definition | A series of links that provide context to this bundle. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Comments | 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. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.link.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.relation | |
Short | See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 |
Definition | A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. |
Cardinality | 1..1 |
Type | code |
Binding | |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.url | |
Short | Reference details for the link |
Definition | The reference details for the link. |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.entry | |
Short | Entry in the bundle - will have a resource or information |
Definition | An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Bundle.entry.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.link | |
Short | Links related to this entry |
Definition | A series of links that provide context to this entry. |
Cardinality | 0..* |
Type | see (link) |
Summary | True |
Constraints |
|
Bundle.entry.fullUrl | |
Short | URI for resource (e.g. the absolute URL server address, URI for UUID/OID, etc.) |
Definition | The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. 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. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
|
Cardinality | 0..1 |
Type | uri |
Summary | True |
Comments | fullUrl 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 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, 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). |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-7, bdl-15, bdl-8 |
Constraints |
|
Bundle.entry.resource | |
Short | A resource in the bundle |
Definition | The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning. |
Cardinality | 0..1 |
Type | Procedure, Observation, Practitioner, Device |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3c, bdl-7, bdl-11, bdl-12, bdl-13, bdl-5 |
Bundle.entry.resource.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.resource.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url |
Constraints |
|
Mappings |
|
Bundle.entry.resource.Procedure | |
Bundle.entry.resource.Observation | |
Bundle.entry.resource.Device | |
Bundle.entry.search | |
Short | Search related information |
Definition | Information about the search process that lead to the creation of this entry. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-2 |
Constraints |
|
Bundle.entry.search.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.search.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.mode | |
Short | match | include - why this is in the result set |
Definition | Why 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. |
Cardinality | 0..1 |
Type | code |
Binding | Why 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. |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.search.score | |
Short | Search ranking (between 0 and 1) |
Definition | When searching, the server's search ranking score for the entry. |
Cardinality | 0..1 |
Type | decimal |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.request | |
Short | Additional execution information (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-5 |
Constraints |
|
Bundle.entry.request.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.request.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.method | |
Short | GET | HEAD | POST | PUT | DELETE | PATCH |
Definition | In 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. |
Cardinality | 1..1 |
Type | code |
Binding | HTTP verbs (in the HTTP command line). See HTTP rfc for details. |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3b, bdl-3c, bdl-14, bdl-15 |
Constraints |
|
Bundle.entry.request.url | |
Short | URL for HTTP equivalent of this entry |
Definition | The URL for this entry, relative to the root (the address to which the request is posted). |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | 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]". |
Constraints |
|
Bundle.entry.request.ifNoneMatch | |
Short | For managing cache validation |
Definition | If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifModifiedSince | |
Short | For managing cache currency |
Definition | Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Constraints |
|
Bundle.entry.request.ifMatch | |
Short | For managing update contention |
Definition | Only perform the operation if the Etag value matches. For more information, see the API section "Managing Resource Contention". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifNoneExist | |
Short | For conditional creates |
Definition | Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?"). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response | |
Short | Results of execution (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3d, bdl-5 |
Constraints |
|
Bundle.entry.response.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.response.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.status | |
Short | Status response code (text optional) |
Definition | 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. |
Cardinality | 1..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response.location | |
Short | The location (if the operation returns a location) |
Definition | The location header created by processing this operation, populated if the operation returns a location. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Constraints |
|
Bundle.entry.response.etag | |
Short | The Etag for the resource (if relevant) |
Definition | The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. |
Constraints |
|
Bundle.entry.response.lastModified | |
Short | Server's date time modified |
Definition | The date/time that the resource was modified on the server. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. |
Constraints |
|
Bundle.entry.response.outcome | |
Short | OperationOutcome with hints and warnings (for batch/transaction) |
Definition | An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. |
Cardinality | 0..1 |
Type | Resource |
Summary | True |
Comments | 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.signature | |
Short | Digital Signature |
Definition | Digital Signature - base64 encoded. XML-DSig or a JWS. |
Cardinality | 0..1 |
Type | Signature |
Summary | True |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Bundle.issues | |
Short | Issues with the Bundle |
Definition | Captures issues and warnings that relate to the construction of the Bundle and the content within it. |
Cardinality | 0..1 |
Type | OperationOutcome |
Summary | True |
Comments | Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-16, bdl-17 |
Bundle.identifier |
Test Strip Bottle Enrolled
TestStripBottleEnrolled (Bundle) | C | Bundle | |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
identifier | Σ C | 0..1 | Identifier |
type | Σ C | 1..1 | codeBindingFixed Value |
timestamp | Σ C | 0..1 | instant |
total | Σ C | 0..1 | unsignedInt |
link | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
relation | Σ C | 1..1 | codeBinding |
url | Σ C | 1..1 | uri |
entry | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
link | Σ | 0..* | see (link) |
fullUrl | Σ C | 0..1 | uri |
resource | Σ C | 0..1 | Procedure, Device, Practitioner, Observation, Substance, Organization |
id | 0..1 | string | |
extension | C | 0..* | Extension |
Procedure | |||
Device | |||
Observation | |||
Substance | |||
Organization | |||
search | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
mode | Σ | 0..1 | codeBinding |
score | Σ | 0..1 | decimal |
request | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
method | Σ C | 1..1 | codeBinding |
url | Σ | 1..1 | uri |
ifNoneMatch | Σ | 0..1 | string |
ifModifiedSince | Σ | 0..1 | instant |
ifMatch | Σ | 0..1 | string |
ifNoneExist | Σ | 0..1 | string |
response | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
status | Σ | 1..1 | string |
location | Σ | 0..1 | uri |
etag | Σ | 0..1 | string |
lastModified | Σ | 0..1 | instant |
outcome | Σ | 0..1 | Resource |
signature | Σ | 0..1 | Signature |
issues | Σ C | 0..1 | OperationOutcome |
identifier |
Bundle | |
Short | Contains a collection of resources |
Definition | A container for a collection of resources. |
Cardinality | 0..* |
Constraints |
|
Mappings |
|
Bundle.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.identifier | |
Short | Persistent identifier for the bundle |
Definition | A persistent identifier for the bundle that won't change as a bundle is copied from server to server. |
Cardinality | 0..1 |
Type | Identifier |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-9 |
Constraints |
|
Mappings |
|
Bundle.type | |
Short | document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection | subscription-notification |
Definition | Indicates the purpose of this bundle - how it is intended to be used. |
Cardinality | 1..1 |
Type | code |
Binding | Indicates the purpose of a bundle - how it is intended to be used. |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1, bdl-2, bdl-3a, bdl-3b, bdl-3c, bdl-3d, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, bdl-13, bdl-14, bdl-15, bdl-17, bdl-18 |
Constraints |
|
Fixed Value | collection |
Mappings |
|
Bundle.timestamp | |
Short | When the bundle was assembled |
Definition | The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | 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:
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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-10 |
Constraints |
|
Mappings |
|
Bundle.total | |
Short | If search, the total number of matches |
Definition | If a set of search matches, this is the (potentially estimated) 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. |
Cardinality | 0..1 |
Type | unsignedInt |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1 |
Constraints |
|
Bundle.link | |
Short | Links related to this Bundle |
Definition | A series of links that provide context to this bundle. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Comments | 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. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.link.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.relation | |
Short | See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 |
Definition | A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. |
Cardinality | 1..1 |
Type | code |
Binding | |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.url | |
Short | Reference details for the link |
Definition | The reference details for the link. |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.entry | |
Short | Entry in the bundle - will have a resource or information |
Definition | An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Bundle.entry.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.link | |
Short | Links related to this entry |
Definition | A series of links that provide context to this entry. |
Cardinality | 0..* |
Type | see (link) |
Summary | True |
Constraints |
|
Bundle.entry.fullUrl | |
Short | URI for resource (e.g. the absolute URL server address, URI for UUID/OID, etc.) |
Definition | The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. 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. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
|
Cardinality | 0..1 |
Type | uri |
Summary | True |
Comments | fullUrl 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 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, 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). |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-7, bdl-15, bdl-8 |
Constraints |
|
Bundle.entry.resource | |
Short | A resource in the bundle |
Definition | The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning. |
Cardinality | 0..1 |
Type | Procedure, Device, Practitioner, Observation, Substance, Organization |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3c, bdl-7, bdl-11, bdl-12, bdl-13, bdl-5 |
Bundle.entry.resource.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.resource.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url |
Constraints |
|
Mappings |
|
Bundle.entry.resource.Procedure | |
Bundle.entry.resource.Device | |
Bundle.entry.resource.Observation | |
Bundle.entry.resource.Substance | |
Bundle.entry.resource.Organization | |
Bundle.entry.search | |
Short | Search related information |
Definition | Information about the search process that lead to the creation of this entry. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-2 |
Constraints |
|
Bundle.entry.search.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.search.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.mode | |
Short | match | include - why this is in the result set |
Definition | Why 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. |
Cardinality | 0..1 |
Type | code |
Binding | Why 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. |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.search.score | |
Short | Search ranking (between 0 and 1) |
Definition | When searching, the server's search ranking score for the entry. |
Cardinality | 0..1 |
Type | decimal |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.request | |
Short | Additional execution information (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-5 |
Constraints |
|
Bundle.entry.request.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.request.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.method | |
Short | GET | HEAD | POST | PUT | DELETE | PATCH |
Definition | In 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. |
Cardinality | 1..1 |
Type | code |
Binding | HTTP verbs (in the HTTP command line). See HTTP rfc for details. |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3b, bdl-3c, bdl-14, bdl-15 |
Constraints |
|
Bundle.entry.request.url | |
Short | URL for HTTP equivalent of this entry |
Definition | The URL for this entry, relative to the root (the address to which the request is posted). |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | 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]". |
Constraints |
|
Bundle.entry.request.ifNoneMatch | |
Short | For managing cache validation |
Definition | If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifModifiedSince | |
Short | For managing cache currency |
Definition | Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Constraints |
|
Bundle.entry.request.ifMatch | |
Short | For managing update contention |
Definition | Only perform the operation if the Etag value matches. For more information, see the API section "Managing Resource Contention". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifNoneExist | |
Short | For conditional creates |
Definition | Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?"). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response | |
Short | Results of execution (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3d, bdl-5 |
Constraints |
|
Bundle.entry.response.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.response.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.status | |
Short | Status response code (text optional) |
Definition | 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. |
Cardinality | 1..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response.location | |
Short | The location (if the operation returns a location) |
Definition | The location header created by processing this operation, populated if the operation returns a location. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Constraints |
|
Bundle.entry.response.etag | |
Short | The Etag for the resource (if relevant) |
Definition | The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. |
Constraints |
|
Bundle.entry.response.lastModified | |
Short | Server's date time modified |
Definition | The date/time that the resource was modified on the server. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. |
Constraints |
|
Bundle.entry.response.outcome | |
Short | OperationOutcome with hints and warnings (for batch/transaction) |
Definition | An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. |
Cardinality | 0..1 |
Type | Resource |
Summary | True |
Comments | 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.signature | |
Short | Digital Signature |
Definition | Digital Signature - base64 encoded. XML-DSig or a JWS. |
Cardinality | 0..1 |
Type | Signature |
Summary | True |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Bundle.issues | |
Short | Issues with the Bundle |
Definition | Captures issues and warnings that relate to the construction of the Bundle and the content within it. |
Cardinality | 0..1 |
Type | OperationOutcome |
Summary | True |
Comments | Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-16, bdl-17 |
Bundle.identifier |
Water Filter Replaced
WaterFilterReplaced (Bundle) | C | Bundle | |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
identifier | Σ C | 0..1 | Identifier |
type | Σ C | 1..1 | codeBindingFixed Value |
timestamp | Σ C | 0..1 | instant |
total | Σ C | 0..1 | unsignedInt |
link | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
relation | Σ C | 1..1 | codeBinding |
url | Σ C | 1..1 | uri |
entry | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
link | Σ | 0..* | see (link) |
fullUrl | Σ C | 0..1 | uri |
resource | Σ C | 0..1 | Procedure, Device, Practitioner |
id | 0..1 | string | |
extension | C | 0..* | Extension |
Procedure | |||
Device | |||
Practitioner | |||
search | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
mode | Σ | 0..1 | codeBinding |
score | Σ | 0..1 | decimal |
request | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
method | Σ C | 1..1 | codeBinding |
url | Σ | 1..1 | uri |
ifNoneMatch | Σ | 0..1 | string |
ifModifiedSince | Σ | 0..1 | instant |
ifMatch | Σ | 0..1 | string |
ifNoneExist | Σ | 0..1 | string |
response | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
status | Σ | 1..1 | string |
location | Σ | 0..1 | uri |
etag | Σ | 0..1 | string |
lastModified | Σ | 0..1 | instant |
outcome | Σ | 0..1 | Resource |
signature | Σ | 0..1 | Signature |
issues | Σ C | 0..1 | OperationOutcome |
identifier |
Bundle | |
Short | Contains a collection of resources |
Definition | A container for a collection of resources. |
Cardinality | 0..* |
Constraints |
|
Mappings |
|
Bundle.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.identifier | |
Short | Persistent identifier for the bundle |
Definition | A persistent identifier for the bundle that won't change as a bundle is copied from server to server. |
Cardinality | 0..1 |
Type | Identifier |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-9 |
Constraints |
|
Mappings |
|
Bundle.type | |
Short | document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection | subscription-notification |
Definition | Indicates the purpose of this bundle - how it is intended to be used. |
Cardinality | 1..1 |
Type | code |
Binding | Indicates the purpose of a bundle - how it is intended to be used. |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1, bdl-2, bdl-3a, bdl-3b, bdl-3c, bdl-3d, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, bdl-13, bdl-14, bdl-15, bdl-17, bdl-18 |
Constraints |
|
Fixed Value | collection |
Mappings |
|
Bundle.timestamp | |
Short | When the bundle was assembled |
Definition | The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | 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:
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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-10 |
Constraints |
|
Mappings |
|
Bundle.total | |
Short | If search, the total number of matches |
Definition | If a set of search matches, this is the (potentially estimated) 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. |
Cardinality | 0..1 |
Type | unsignedInt |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1 |
Constraints |
|
Bundle.link | |
Short | Links related to this Bundle |
Definition | A series of links that provide context to this bundle. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Comments | 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. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.link.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.relation | |
Short | See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 |
Definition | A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. |
Cardinality | 1..1 |
Type | code |
Binding | |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.url | |
Short | Reference details for the link |
Definition | The reference details for the link. |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.entry | |
Short | Entry in the bundle - will have a resource or information |
Definition | An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Bundle.entry.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.link | |
Short | Links related to this entry |
Definition | A series of links that provide context to this entry. |
Cardinality | 0..* |
Type | see (link) |
Summary | True |
Constraints |
|
Bundle.entry.fullUrl | |
Short | URI for resource (e.g. the absolute URL server address, URI for UUID/OID, etc.) |
Definition | The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. 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. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
|
Cardinality | 0..1 |
Type | uri |
Summary | True |
Comments | fullUrl 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 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, 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). |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-7, bdl-15, bdl-8 |
Constraints |
|
Bundle.entry.resource | |
Short | A resource in the bundle |
Definition | The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning. |
Cardinality | 0..1 |
Type | Procedure, Device, Practitioner |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3c, bdl-7, bdl-11, bdl-12, bdl-13, bdl-5 |
Bundle.entry.resource.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.resource.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url |
Constraints |
|
Mappings |
|
Bundle.entry.resource.Procedure | |
Bundle.entry.resource.Device | |
Bundle.entry.resource.Practitioner | |
Bundle.entry.search | |
Short | Search related information |
Definition | Information about the search process that lead to the creation of this entry. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-2 |
Constraints |
|
Bundle.entry.search.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.search.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.mode | |
Short | match | include - why this is in the result set |
Definition | Why 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. |
Cardinality | 0..1 |
Type | code |
Binding | Why 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. |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.search.score | |
Short | Search ranking (between 0 and 1) |
Definition | When searching, the server's search ranking score for the entry. |
Cardinality | 0..1 |
Type | decimal |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.request | |
Short | Additional execution information (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-5 |
Constraints |
|
Bundle.entry.request.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.request.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.method | |
Short | GET | HEAD | POST | PUT | DELETE | PATCH |
Definition | In 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. |
Cardinality | 1..1 |
Type | code |
Binding | HTTP verbs (in the HTTP command line). See HTTP rfc for details. |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3b, bdl-3c, bdl-14, bdl-15 |
Constraints |
|
Bundle.entry.request.url | |
Short | URL for HTTP equivalent of this entry |
Definition | The URL for this entry, relative to the root (the address to which the request is posted). |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | 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]". |
Constraints |
|
Bundle.entry.request.ifNoneMatch | |
Short | For managing cache validation |
Definition | If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifModifiedSince | |
Short | For managing cache currency |
Definition | Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Constraints |
|
Bundle.entry.request.ifMatch | |
Short | For managing update contention |
Definition | Only perform the operation if the Etag value matches. For more information, see the API section "Managing Resource Contention". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifNoneExist | |
Short | For conditional creates |
Definition | Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?"). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response | |
Short | Results of execution (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3d, bdl-5 |
Constraints |
|
Bundle.entry.response.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.response.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.status | |
Short | Status response code (text optional) |
Definition | 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. |
Cardinality | 1..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response.location | |
Short | The location (if the operation returns a location) |
Definition | The location header created by processing this operation, populated if the operation returns a location. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Constraints |
|
Bundle.entry.response.etag | |
Short | The Etag for the resource (if relevant) |
Definition | The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. |
Constraints |
|
Bundle.entry.response.lastModified | |
Short | Server's date time modified |
Definition | The date/time that the resource was modified on the server. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. |
Constraints |
|
Bundle.entry.response.outcome | |
Short | OperationOutcome with hints and warnings (for batch/transaction) |
Definition | An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. |
Cardinality | 0..1 |
Type | Resource |
Summary | True |
Comments | 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.signature | |
Short | Digital Signature |
Definition | Digital Signature - base64 encoded. XML-DSig or a JWS. |
Cardinality | 0..1 |
Type | Signature |
Summary | True |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Bundle.issues | |
Short | Issues with the Bundle |
Definition | Captures issues and warnings that relate to the construction of the Bundle and the content within it. |
Cardinality | 0..1 |
Type | OperationOutcome |
Summary | True |
Comments | Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-16, bdl-17 |
Bundle.identifier |
HLD Replaced
HLDReplaced (Bundle) | C | Bundle | |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
identifier | Σ C | 0..1 | Identifier |
type | Σ C | 1..1 | codeBindingFixed Value |
timestamp | Σ C | 0..1 | instant |
total | Σ C | 0..1 | unsignedInt |
link | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
relation | Σ C | 1..1 | codeBinding |
url | Σ C | 1..1 | uri |
entry | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
link | Σ | 0..* | see (link) |
fullUrl | Σ C | 0..1 | uri |
resource | Σ C | 0..1 | Procedure, Device, Practitioner, Substance, Organization |
id | 0..1 | string | |
extension | C | 0..* | Extension |
Procedure | |||
Device | |||
Substance | |||
Organization | |||
search | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
mode | Σ | 0..1 | codeBinding |
score | Σ | 0..1 | decimal |
request | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
method | Σ C | 1..1 | codeBinding |
url | Σ | 1..1 | uri |
ifNoneMatch | Σ | 0..1 | string |
ifModifiedSince | Σ | 0..1 | instant |
ifMatch | Σ | 0..1 | string |
ifNoneExist | Σ | 0..1 | string |
response | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
status | Σ | 1..1 | string |
location | Σ | 0..1 | uri |
etag | Σ | 0..1 | string |
lastModified | Σ | 0..1 | instant |
outcome | Σ | 0..1 | Resource |
signature | Σ | 0..1 | Signature |
issues | Σ C | 0..1 | OperationOutcome |
identifier |
Bundle | |
Short | Contains a collection of resources |
Definition | A container for a collection of resources. |
Cardinality | 0..* |
Constraints |
|
Mappings |
|
Bundle.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.identifier | |
Short | Persistent identifier for the bundle |
Definition | A persistent identifier for the bundle that won't change as a bundle is copied from server to server. |
Cardinality | 0..1 |
Type | Identifier |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-9 |
Constraints |
|
Mappings |
|
Bundle.type | |
Short | document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection | subscription-notification |
Definition | Indicates the purpose of this bundle - how it is intended to be used. |
Cardinality | 1..1 |
Type | code |
Binding | Indicates the purpose of a bundle - how it is intended to be used. |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1, bdl-2, bdl-3a, bdl-3b, bdl-3c, bdl-3d, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, bdl-13, bdl-14, bdl-15, bdl-17, bdl-18 |
Constraints |
|
Fixed Value | collection |
Mappings |
|
Bundle.timestamp | |
Short | When the bundle was assembled |
Definition | The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | 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:
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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-10 |
Constraints |
|
Mappings |
|
Bundle.total | |
Short | If search, the total number of matches |
Definition | If a set of search matches, this is the (potentially estimated) 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. |
Cardinality | 0..1 |
Type | unsignedInt |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1 |
Constraints |
|
Bundle.link | |
Short | Links related to this Bundle |
Definition | A series of links that provide context to this bundle. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Comments | 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. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.link.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.relation | |
Short | See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 |
Definition | A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. |
Cardinality | 1..1 |
Type | code |
Binding | |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.url | |
Short | Reference details for the link |
Definition | The reference details for the link. |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.entry | |
Short | Entry in the bundle - will have a resource or information |
Definition | An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Bundle.entry.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.link | |
Short | Links related to this entry |
Definition | A series of links that provide context to this entry. |
Cardinality | 0..* |
Type | see (link) |
Summary | True |
Constraints |
|
Bundle.entry.fullUrl | |
Short | URI for resource (e.g. the absolute URL server address, URI for UUID/OID, etc.) |
Definition | The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. 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. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
|
Cardinality | 0..1 |
Type | uri |
Summary | True |
Comments | fullUrl 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 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, 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). |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-7, bdl-15, bdl-8 |
Constraints |
|
Bundle.entry.resource | |
Short | A resource in the bundle |
Definition | The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning. |
Cardinality | 0..1 |
Type | Procedure, Device, Practitioner, Substance, Organization |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3c, bdl-7, bdl-11, bdl-12, bdl-13, bdl-5 |
Bundle.entry.resource.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.resource.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url |
Constraints |
|
Mappings |
|
Bundle.entry.resource.Procedure | |
Bundle.entry.resource.Device | |
Bundle.entry.resource.Substance | |
Bundle.entry.resource.Organization | |
Bundle.entry.search | |
Short | Search related information |
Definition | Information about the search process that lead to the creation of this entry. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-2 |
Constraints |
|
Bundle.entry.search.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.search.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.mode | |
Short | match | include - why this is in the result set |
Definition | Why 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. |
Cardinality | 0..1 |
Type | code |
Binding | Why 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. |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.search.score | |
Short | Search ranking (between 0 and 1) |
Definition | When searching, the server's search ranking score for the entry. |
Cardinality | 0..1 |
Type | decimal |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.request | |
Short | Additional execution information (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-5 |
Constraints |
|
Bundle.entry.request.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.request.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.method | |
Short | GET | HEAD | POST | PUT | DELETE | PATCH |
Definition | In 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. |
Cardinality | 1..1 |
Type | code |
Binding | HTTP verbs (in the HTTP command line). See HTTP rfc for details. |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3b, bdl-3c, bdl-14, bdl-15 |
Constraints |
|
Bundle.entry.request.url | |
Short | URL for HTTP equivalent of this entry |
Definition | The URL for this entry, relative to the root (the address to which the request is posted). |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | 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]". |
Constraints |
|
Bundle.entry.request.ifNoneMatch | |
Short | For managing cache validation |
Definition | If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifModifiedSince | |
Short | For managing cache currency |
Definition | Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Constraints |
|
Bundle.entry.request.ifMatch | |
Short | For managing update contention |
Definition | Only perform the operation if the Etag value matches. For more information, see the API section "Managing Resource Contention". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifNoneExist | |
Short | For conditional creates |
Definition | Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?"). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response | |
Short | Results of execution (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3d, bdl-5 |
Constraints |
|
Bundle.entry.response.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.response.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.status | |
Short | Status response code (text optional) |
Definition | 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. |
Cardinality | 1..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response.location | |
Short | The location (if the operation returns a location) |
Definition | The location header created by processing this operation, populated if the operation returns a location. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Constraints |
|
Bundle.entry.response.etag | |
Short | The Etag for the resource (if relevant) |
Definition | The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. |
Constraints |
|
Bundle.entry.response.lastModified | |
Short | Server's date time modified |
Definition | The date/time that the resource was modified on the server. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. |
Constraints |
|
Bundle.entry.response.outcome | |
Short | OperationOutcome with hints and warnings (for batch/transaction) |
Definition | An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. |
Cardinality | 0..1 |
Type | Resource |
Summary | True |
Comments | 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.signature | |
Short | Digital Signature |
Definition | Digital Signature - base64 encoded. XML-DSig or a JWS. |
Cardinality | 0..1 |
Type | Signature |
Summary | True |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Bundle.issues | |
Short | Issues with the Bundle |
Definition | Captures issues and warnings that relate to the construction of the Bundle and the content within it. |
Cardinality | 0..1 |
Type | OperationOutcome |
Summary | True |
Comments | Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-16, bdl-17 |
Bundle.identifier |
Disinfection Cycle
DisinfectionCycle (Bundle) | C | Bundle | |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
identifier | Σ C | 1..1 | Identifier |
type | Σ C | 1..1 | codeBindingFixed Value |
timestamp | Σ C | 0..1 | instant |
total | Σ C | 0..1 | unsignedInt |
link | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
relation | Σ C | 1..1 | codeBinding |
url | Σ C | 1..1 | uri |
entry | Σ C | 1..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
link | Σ | 0..* | see (link) |
fullUrl | Σ C | 1..1 | uri |
resource | Σ C | 1..1 | DeviceDefinition |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | C | 0..1 | Narrative |
contained | C | 0..* | Resource |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
identifier | Σ | 0..* | Identifier |
instantiatesCanonical | Σ | 0..* | canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) |
instantiatesUri | Σ | 0..* | uri |
basedOn | Σ | 0..* | Reference(CarePlan | ServiceRequest) |
partOf | Σ | 0..* | Reference(Procedure | Observation | MedicationAdministration) |
status | Σ ?! | 1..1 | codeBinding |
statusReason | Σ | 0..1 | CodeableConcept |
category | Σ | 0..* | CodeableConcept |
code | Σ | 0..1 | CodeableConcept |
subject | Σ | 1..1 | Reference(Patient | Group | Device | Practitioner | Organization | Location) |
focus | Σ | 0..1 | Reference(Patient | Group | RelatedPerson | Practitioner | Organization | CareTeam | PractitionerRole | Specimen) |
encounter | Σ | 0..1 | Reference(Encounter) |
occurrence[x] | Σ | 0..1 | |
occurrenceDateTime | dateTime | ||
occurrencePeriod | Period | ||
occurrenceString | string | ||
occurrenceAge | Age | ||
occurrenceRange | Range | ||
occurrenceTiming | Timing | ||
recorded | Σ | 0..1 | dateTime |
recorder | Σ | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) |
reported[x] | Σ | 0..1 | |
reportedBoolean | boolean | ||
reportedReference | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization) | ||
performer | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
function | Σ | 0..1 | CodeableConcept |
actor | Σ C | 1..1 | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device | CareTeam | HealthcareService) |
onBehalfOf | C | 0..1 | Reference(Organization) |
period | 0..1 | Period | |
location | Σ | 0..1 | Reference(Location) |
reason | Σ | 0..* | CodeableReference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference) |
bodySite | Σ | 0..* | CodeableConcept |
outcome | Σ | 0..1 | CodeableConcept |
report | 0..* | Reference(DiagnosticReport | DocumentReference | Composition) | |
complication | 0..* | CodeableReference(Condition) | |
followUp | 0..* | CodeableConcept | |
note | 0..* | Annotation | |
focalDevice | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
action | 0..1 | CodeableConceptBinding | |
manipulated | 1..1 | Reference(Device) | |
used | 0..* | CodeableReference(Device | Medication | Substance | BiologicallyDerivedProduct) | |
supportingInfo | 0..* | Reference(Resource) | |
Procedure | |||
Substance | |||
Device | |||
Observation | |||
DeviceDefinition | |||
search | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
mode | Σ | 0..1 | codeBinding |
score | Σ | 0..1 | decimal |
request | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
method | Σ C | 1..1 | codeBinding |
url | Σ | 1..1 | uri |
ifNoneMatch | Σ | 0..1 | string |
ifModifiedSince | Σ | 0..1 | instant |
ifMatch | Σ | 0..1 | string |
ifNoneExist | Σ | 0..1 | string |
response | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
status | Σ | 1..1 | string |
location | Σ | 0..1 | uri |
etag | Σ | 0..1 | string |
lastModified | Σ | 0..1 | instant |
outcome | Σ | 0..1 | Resource |
signature | Σ | 0..1 | Signature |
issues | Σ C | 0..1 | OperationOutcome |
Bundle | |
Short | Contains a collection of resources |
Definition | A container for a collection of resources. |
Cardinality | 0..* |
Constraints |
|
Mappings |
|
Bundle.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.identifier | |
Short | Persistent identifier for the bundle |
Definition | A persistent identifier for the bundle that won't change as a bundle is copied from server to server. |
Cardinality | 1..1 |
Type | Identifier |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-9 |
Constraints |
|
Mappings |
|
Bundle.type | |
Short | document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection | subscription-notification |
Definition | Indicates the purpose of this bundle - how it is intended to be used. |
Cardinality | 1..1 |
Type | code |
Binding | Indicates the purpose of a bundle - how it is intended to be used. |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1, bdl-2, bdl-3a, bdl-3b, bdl-3c, bdl-3d, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, bdl-13, bdl-14, bdl-15, bdl-17, bdl-18 |
Constraints |
|
Fixed Value | collection |
Mappings |
|
Bundle.timestamp | |
Short | When the bundle was assembled |
Definition | The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | 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:
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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-10 |
Constraints |
|
Mappings |
|
Bundle.total | |
Short | If search, the total number of matches |
Definition | If a set of search matches, this is the (potentially estimated) 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. |
Cardinality | 0..1 |
Type | unsignedInt |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1 |
Constraints |
|
Bundle.link | |
Short | Links related to this Bundle |
Definition | A series of links that provide context to this bundle. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Comments | 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. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.link.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.relation | |
Short | See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 |
Definition | A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. |
Cardinality | 1..1 |
Type | code |
Binding | |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.url | |
Short | Reference details for the link |
Definition | The reference details for the link. |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.entry | |
Short | Entry in the bundle - will have a resource or information |
Definition | An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). |
Cardinality | 1..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Bundle.entry.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.link | |
Short | Links related to this entry |
Definition | A series of links that provide context to this entry. |
Cardinality | 0..* |
Type | see (link) |
Summary | True |
Constraints |
|
Bundle.entry.fullUrl | |
Short | URI for resource (e.g. the absolute URL server address, URI for UUID/OID, etc.) |
Definition | The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. 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. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
|
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | fullUrl 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 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, 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). |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-7, bdl-15, bdl-8 |
Constraints |
|
Bundle.entry.resource | |
Short | A resource in the bundle |
Definition | The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning. |
Cardinality | 1..1 |
Type | DeviceDefinition |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3c, bdl-7, bdl-11, bdl-12, bdl-13, bdl-5 |
Bundle.entry.resource.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.entry.resource.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.entry.resource.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.entry.resource.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.entry.resource.text | |
Short | Text summary of the resource, for human interpretation |
Definition | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. |
Cardinality | 0..1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. |
Conditions | The cardinality or value of this element may be affected by these constraints: dom-6 |
Constraints |
|
Mappings |
|
Bundle.entry.resource.contained | |
Short | Contained, inline Resources |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. |
Cardinality | 0..* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. |
Conditions | The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 |
Mappings |
|
Bundle.entry.resource.extension | |
Short | Additional content defined by implementations |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.modifierExtension | |
Short | Extensions that cannot be ignored |
Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.identifier | |
Short | External Identifiers for this procedure |
Definition | Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server. |
Cardinality | 0..* |
Type | Identifier |
Summary | True |
Requirements | Allows identification of the procedure as it is known by various participating systems and in a way that remains consistent across servers. |
Comments | This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and Person resource instances might share the same social insurance number. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.instantiatesCanonical | |
Short | Instantiates FHIR protocol or definition |
Definition | The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. |
Cardinality | 0..* |
Type | canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.instantiatesUri | |
Short | Instantiates external protocol or definition |
Definition | The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. |
Cardinality | 0..* |
Type | uri |
Summary | True |
Comments | This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.basedOn | |
Short | A request for this procedure |
Definition | A reference to a resource that contains details of the request for this procedure. |
Cardinality | 0..* |
Type | Reference(CarePlan | ServiceRequest) |
Summary | True |
Alias | fulfills |
Constraints |
|
Mappings |
|
Bundle.entry.resource.partOf | |
Short | Part of referenced event |
Definition | A larger event of which this particular procedure is a component or step. |
Cardinality | 0..* |
Type | Reference(Procedure | Observation | MedicationAdministration) |
Summary | True |
Alias | container |
Comments | The MedicationAdministration resource has a partOf reference to Procedure, but this is not a circular reference. For example, the anesthesia MedicationAdministration is part of the surgical Procedure (MedicationAdministration.partOf = Procedure). For example, the procedure to insert the IV port for an IV medication administration is part of the medication administration (Procedure.partOf = MedicationAdministration). |
Constraints |
|
Mappings |
|
Bundle.entry.resource.status | |
Short | preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown |
Definition | A code specifying the state of the procedure. Generally, this will be the in-progress or completed state. |
Cardinality | 1..1 |
Type | code |
Binding | A code specifying the state of the procedure. |
Modifier | True |
Summary | True |
Comments | The "unknown" code is not to be used to convey other statuses. The "unknown" code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.statusReason | |
Short | Reason for current status |
Definition | Captures the reason for the current state of the procedure. |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | A code that identifies the reason a procedure was not performed. |
Summary | True |
Alias | Suspended Reason, Cancelled Reason |
Comments | This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.category | |
Short | Classification of the procedure |
Definition | A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). |
Cardinality | 0..* |
Type | CodeableConcept |
Binding | A code that classifies a procedure for searching, sorting and display purposes. |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.code | |
Short | Identification of the procedure |
Definition | The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy"). |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | A code to identify a specific procedure . |
Summary | True |
Alias | type |
Requirements | 0..1 to account for primarily narrative only resources. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.subject | |
Short | Individual or entity the procedure was performed on |
Definition | On whom or on what the procedure was performed. This is usually an individual human, but can also be performed on animals, groups of humans or animals, organizations or practitioners (for licensing), locations or devices (for safety inspections or regulatory authorizations). If the actual focus of the procedure is different from the subject, the focus element specifies the actual focus of the procedure. |
Cardinality | 1..1 |
Type | Reference(Patient | Group | Device | Practitioner | Organization | Location) |
Summary | True |
Alias | patient |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focus | |
Short | Who is the target of the procedure when it is not the subject of record only |
Definition | Who is the target of the procedure when it is not the subject of record only. If focus is not present, then subject is the focus. If focus is present and the subject is one of the targets of the procedure, include subject as a focus as well. If focus is present and the subject is not included in focus, it implies that the procedure was only targeted on the focus. For example, when a caregiver is given education for a patient, the caregiver would be the focus and the procedure record is associated with the subject (e.g. patient). For example, use focus when recording the target of the education, training, or counseling is the parent or relative of a patient. |
Cardinality | 0..1 |
Type | Reference(Patient | Group | RelatedPerson | Practitioner | Organization | CareTeam | PractitionerRole | Specimen) |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.encounter | |
Short | The Encounter during which this Procedure was created |
Definition | The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated. |
Cardinality | 0..1 |
Type | Reference(Encounter) |
Summary | True |
Comments | This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.occurrence[x] | |
Short | When the procedure occurred or is occurring |
Definition | Estimated or actual date, date-time, period, or age when the procedure did occur or is occurring. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured. |
Cardinality | 0..1 |
Type | dateTime, Period, string, Age, Range, Timing |
Summary | True |
Comments | This indicates when the procedure actually occurred or is occurring, not when it was asked/requested/ordered to occur. For the latter, look at the occurence element of the Request this Procedure is "basedOn". The status code allows differentiation of whether the timing reflects a historic event or an ongoing event. Ongoing events should not include an upper bound in the Period or Timing.bounds. Age is generally used when the patient reports an age at which the procedure was performed. Range is generally used when the patient reports an age range when the procedure was performed, such as sometime between 20-25 years old. dateTime supports a range of precision due to some procedures being reported as past procedures that might not have millisecond precision while other procedures performed and documented during the encounter might have more precise UTC timestamps with timezone. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.recorded | |
Short | When the procedure was first captured in the subject's record |
Definition | The date the occurrence of the procedure was first captured in the record regardless of Procedure.status (potentially after the occurrence of the event). |
Cardinality | 0..1 |
Type | dateTime |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.recorder | |
Short | Who recorded the procedure |
Definition | Individual who recorded the record and takes responsibility for its content. |
Cardinality | 0..1 |
Type | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.reported[x] | |
Short | Reported rather than primary record |
Definition | Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report. |
Cardinality | 0..1 |
Type | boolean, Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization) |
Summary | True |
Alias | informer |
Requirements | Reported data may have different rules on editing and may be visually distinguished from primary data. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer | |
Short | Who performed the procedure and what they did |
Definition | Indicates who or what performed the procedure and how they were involved. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.resource.performer.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.function | |
Short | Type of performance |
Definition | Distinguishes the type of involvement of the performer in the procedure. For example, surgeon, anaesthetist, endoscopist. |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | A code that identifies the role of a performer of the procedure. |
Summary | True |
Requirements | Allows disambiguation of the types of involvement of different performers. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.actor | |
Short | Who performed the procedure |
Definition | Indicates who or what performed the procedure. |
Cardinality | 1..1 |
Type | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device | CareTeam | HealthcareService) |
Summary | True |
Requirements | A reference to Device supports use cases, such as pacemakers. |
Conditions | The cardinality or value of this element may be affected by these constraints: prc-1 |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.onBehalfOf | |
Short | Organization the device or practitioner was acting for |
Definition | The Organization the Patient, RelatedPerson, Device, CareTeam, and HealthcareService was acting on behalf of. |
Cardinality | 0..1 |
Type | Reference(Organization) |
Requirements | Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action. |
Comments | Organization, Patient, RelatedPerson, Device, CareTeam, and HealthcareService can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action. |
Conditions | The cardinality or value of this element may be affected by these constraints: prc-1 |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.period | |
Short | When the performer performed the procedure |
Definition | Time period during which the performer performed the procedure. |
Cardinality | 0..1 |
Type | Period |
Constraints |
|
Bundle.entry.resource.location | |
Short | Where the procedure happened |
Definition | The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant. |
Cardinality | 0..1 |
Type | Reference(Location) |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.reason | |
Short | The justification that the procedure was performed |
Definition | The coded reason or reference why the procedure was performed. This may be a coded entity of some type, be present as text, or be a reference to one of several resources that justify the procedure. |
Cardinality | 0..* |
Type | CodeableReference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference) |
Binding | A code that identifies the reason a procedure is required. |
Summary | True |
Comments | Use Procedure.reason.concept when a code sufficiently describes the reason. Use Procedure.reason.reference when referencing a resource, which allows more information to be conveyed, such as onset date. For a single Procedure.reason, if both Procedure.reason.concept and Procedure.reason.reference are present, they are expected to be consistent with each other. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.bodySite | |
Short | Target body sites |
Definition | Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. |
Cardinality | 0..* |
Type | CodeableConcept |
Binding | SNOMED CT Body site concepts |
Summary | True |
Comments | If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension http://hl7.org/fhir/StructureDefinition/procedure-targetBodyStructure. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.outcome | |
Short | The result of procedure |
Definition | The outcome of the procedure - did it resolve the reasons for the procedure being performed? |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | An outcome of a procedure - whether it was resolved or otherwise. |
Summary | True |
Comments | If outcome contains narrative text only, it can be captured using the CodeableConcept.text. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.report | |
Short | Any report resulting from the procedure |
Definition | This could be a histology result, pathology report, surgical report, etc. |
Cardinality | 0..* |
Type | Reference(DiagnosticReport | DocumentReference | Composition) |
Comments | There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.complication | |
Short | Complication following the procedure |
Definition | Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues. |
Cardinality | 0..* |
Type | CodeableReference(Condition) |
Binding | Codes describing complications that resulted from a procedure. |
Comments | If complications are only expressed by the narrative text, they can be captured using the CodeableReference.concept.text. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.followUp | |
Short | Instructions for follow up |
Definition | If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used. |
Cardinality | 0..* |
Type | CodeableConcept |
Binding | Specific follow up required for a procedure e.g. removal of sutures. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.note | |
Short | Additional information about the procedure |
Definition | Any other notes and comments about the procedure. |
Cardinality | 0..* |
Type | Annotation |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice | |
Short | Manipulated, implanted, or removed device |
Definition | A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure. |
Cardinality | 0..* |
Type | BackboneElement |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.resource.focalDevice.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice.action | |
Short | Kind of change to device |
Definition | The kind of change that happened to the device during the procedure. |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | A kind of change that happened to the device during the procedure. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice.manipulated | |
Short | Device that was changed |
Definition | The device that was manipulated (changed) during the procedure. |
Cardinality | 1..1 |
Type | Reference(Device) |
Constraints |
|
Mappings |
|
Bundle.entry.resource.used | |
Short | Items used during procedure |
Definition | Identifies medications, devices and any other substance used as part of the procedure. |
Cardinality | 0..* |
Type | CodeableReference(Device | Medication | Substance | BiologicallyDerivedProduct) |
Binding | Codes describing items used during a procedure. |
Requirements | Used for tracking contamination, etc. |
Comments | For devices actually implanted or removed, use Procedure.focalDevice.manipulated. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.supportingInfo | |
Short | Extra information relevant to the procedure |
Definition | Other resources from the patient record that may be relevant to the procedure. The information from these resources was either used to create the instance or is provided to help with its interpretation. This extension should not be used if more specific inline elements or extensions are available. |
Cardinality | 0..* |
Type | Reference(Resource) |
Constraints |
|
Mappings |
|
Bundle.entry.resource.Procedure | |
Bundle.entry.resource.Substance | |
Bundle.entry.resource.Device | |
Bundle.entry.resource.Observation | |
Bundle.entry.resource.DeviceDefinition | |
Bundle.entry.search | |
Short | Search related information |
Definition | Information about the search process that lead to the creation of this entry. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-2 |
Constraints |
|
Bundle.entry.search.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.search.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.mode | |
Short | match | include - why this is in the result set |
Definition | Why 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. |
Cardinality | 0..1 |
Type | code |
Binding | Why 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. |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.search.score | |
Short | Search ranking (between 0 and 1) |
Definition | When searching, the server's search ranking score for the entry. |
Cardinality | 0..1 |
Type | decimal |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.request | |
Short | Additional execution information (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-5 |
Constraints |
|
Bundle.entry.request.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.request.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.method | |
Short | GET | HEAD | POST | PUT | DELETE | PATCH |
Definition | In 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. |
Cardinality | 1..1 |
Type | code |
Binding | HTTP verbs (in the HTTP command line). See HTTP rfc for details. |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3b, bdl-3c, bdl-14, bdl-15 |
Constraints |
|
Bundle.entry.request.url | |
Short | URL for HTTP equivalent of this entry |
Definition | The URL for this entry, relative to the root (the address to which the request is posted). |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | 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]". |
Constraints |
|
Bundle.entry.request.ifNoneMatch | |
Short | For managing cache validation |
Definition | If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifModifiedSince | |
Short | For managing cache currency |
Definition | Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Constraints |
|
Bundle.entry.request.ifMatch | |
Short | For managing update contention |
Definition | Only perform the operation if the Etag value matches. For more information, see the API section "Managing Resource Contention". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifNoneExist | |
Short | For conditional creates |
Definition | Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?"). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response | |
Short | Results of execution (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3d, bdl-5 |
Constraints |
|
Bundle.entry.response.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.response.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.status | |
Short | Status response code (text optional) |
Definition | 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. |
Cardinality | 1..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response.location | |
Short | The location (if the operation returns a location) |
Definition | The location header created by processing this operation, populated if the operation returns a location. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Constraints |
|
Bundle.entry.response.etag | |
Short | The Etag for the resource (if relevant) |
Definition | The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. |
Constraints |
|
Bundle.entry.response.lastModified | |
Short | Server's date time modified |
Definition | The date/time that the resource was modified on the server. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. |
Constraints |
|
Bundle.entry.response.outcome | |
Short | OperationOutcome with hints and warnings (for batch/transaction) |
Definition | An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. |
Cardinality | 0..1 |
Type | Resource |
Summary | True |
Comments | 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.signature | |
Short | Digital Signature |
Definition | Digital Signature - base64 encoded. XML-DSig or a JWS. |
Cardinality | 0..1 |
Type | Signature |
Summary | True |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Bundle.issues | |
Short | Issues with the Bundle |
Definition | Captures issues and warnings that relate to the construction of the Bundle and the content within it. |
Cardinality | 0..1 |
Type | OperationOutcome |
Summary | True |
Comments | Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-16, bdl-17 |
Firmware Replaced
FirmwareReplaced (Bundle) | C | Bundle | |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
identifier | Σ C | 1..1 | Identifier |
id | 0..1 | id | |
extension | C | 0..* | Extension |
use | Σ ?! | 0..1 | codeBinding |
type | Σ | 1..1 | CodeableConceptBindingFixed Value |
system | Σ | 0..1 | uri |
value | Σ C | 0..1 | string |
period | Σ | 0..1 | Period |
assigner | Σ | 0..1 | Reference(Organization) |
type | Σ C | 1..1 | codeBindingFixed Value |
timestamp | Σ C | 0..1 | instant |
total | Σ C | 0..1 | unsignedInt |
link | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
relation | Σ C | 1..1 | codeBinding |
url | Σ C | 1..1 | uri |
entry | Σ C | 1..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
link | Σ | 0..* | see (link) |
fullUrl | Σ C | 1..1 | uri |
resource | Σ C | 1..1 | Device |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | C | 0..1 | Narrative |
contained | C | 0..* | Resource |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
identifier | Σ | 0..* | Identifier |
instantiatesCanonical | Σ | 0..* | canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) |
instantiatesUri | Σ | 0..* | uri |
basedOn | Σ | 0..* | Reference(CarePlan | ServiceRequest) |
partOf | Σ | 0..* | Reference(Procedure | Observation | MedicationAdministration) |
status | Σ ?! | 1..1 | codeBinding |
statusReason | Σ | 0..1 | CodeableConcept |
category | Σ | 0..* | CodeableConcept |
code | Σ | 0..1 | CodeableConcept |
subject | Σ | 1..1 | Reference(Patient | Group | Device | Practitioner | Organization | Location) |
focus | Σ | 0..1 | Reference(Patient | Group | RelatedPerson | Practitioner | Organization | CareTeam | PractitionerRole | Specimen) |
encounter | Σ | 0..1 | Reference(Encounter) |
occurrence[x] | Σ | 0..1 | |
occurrenceDateTime | dateTime | ||
occurrencePeriod | Period | ||
occurrenceString | string | ||
occurrenceAge | Age | ||
occurrenceRange | Range | ||
occurrenceTiming | Timing | ||
recorded | Σ | 0..1 | dateTime |
recorder | Σ | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) |
reported[x] | Σ | 0..1 | |
reportedBoolean | boolean | ||
reportedReference | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization) | ||
performer | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
function | Σ | 0..1 | CodeableConcept |
actor | Σ C | 1..1 | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device | CareTeam | HealthcareService) |
onBehalfOf | C | 0..1 | Reference(Organization) |
period | 0..1 | Period | |
location | Σ | 0..1 | Reference(Location) |
reason | Σ | 0..* | CodeableReference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference) |
bodySite | Σ | 0..* | CodeableConcept |
outcome | Σ | 0..1 | CodeableConcept |
report | 0..* | Reference(DiagnosticReport | DocumentReference | Composition) | |
complication | 0..* | CodeableReference(Condition) | |
followUp | 0..* | CodeableConcept | |
note | 0..* | Annotation | |
focalDevice | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
action | 0..1 | CodeableConceptBinding | |
manipulated | 1..1 | Reference(Device) | |
used | 0..* | CodeableReference(Device | Medication | Substance | BiologicallyDerivedProduct) | |
supportingInfo | 0..* | Reference(Resource) | |
Procedure | |||
Device | |||
search | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
mode | Σ | 0..1 | codeBinding |
score | Σ | 0..1 | decimal |
request | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
method | Σ C | 1..1 | codeBinding |
url | Σ | 1..1 | uri |
ifNoneMatch | Σ | 0..1 | string |
ifModifiedSince | Σ | 0..1 | instant |
ifMatch | Σ | 0..1 | string |
ifNoneExist | Σ | 0..1 | string |
response | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
status | Σ | 1..1 | string |
location | Σ | 0..1 | uri |
etag | Σ | 0..1 | string |
lastModified | Σ | 0..1 | instant |
outcome | Σ | 0..1 | Resource |
signature | Σ | 0..1 | Signature |
issues | Σ C | 0..1 | OperationOutcome |
Bundle | |
Short | Contains a collection of resources |
Definition | A container for a collection of resources. |
Cardinality | 0..* |
Constraints |
|
Mappings |
|
Bundle.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.identifier | |
Short | An identifier for the Bundle |
Definition | A persistent identifier for the bundle that won't change as a bundle is copied from server to server. |
Cardinality | 1..1 |
Type | Identifier |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-9 |
Constraints |
|
Mappings |
|
Bundle.identifier.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | id |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.identifier.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url |
Constraints |
|
Mappings |
|
Bundle.identifier.use | |
Short | usual | official | temp | secondary | old (If known) |
Definition | The purpose of this identifier. |
Cardinality | 0..1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Constraints |
|
Mappings |
|
Bundle.identifier.type | |
Short | Description of identifier |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 1..1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Constraints |
|
Fixed Value | { "text": "Firmware Replaced" } |
Mappings |
|
Bundle.identifier.system | |
Short | The namespace for the identifier value |
Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Constraints |
|
Examples | Generalhttp://www.acme.com/identifiers/patient |
Mappings |
|
Bundle.identifier.value | |
Short | The value that is unique |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 |
Constraints |
|
Examples | General123456 |
Mappings |
|
Bundle.identifier.period | |
Short | Time period when id is/was valid for use |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0..1 |
Type | Period |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.identifier.assigner | |
Short | Organization that issued id (may be just text) |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0..1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Constraints |
|
Mappings |
|
Bundle.type | |
Short | Must be of type 'collection' |
Definition | Indicates the purpose of this bundle - how it is intended to be used. |
Cardinality | 1..1 |
Type | code |
Binding | Indicates the purpose of a bundle - how it is intended to be used. |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1, bdl-2, bdl-3a, bdl-3b, bdl-3c, bdl-3d, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, bdl-13, bdl-14, bdl-15, bdl-17, bdl-18 |
Constraints |
|
Fixed Value | collection |
Mappings |
|
Bundle.timestamp | |
Short | When the bundle was assembled |
Definition | The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | 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:
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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-10 |
Constraints |
|
Mappings |
|
Bundle.total | |
Short | If search, the total number of matches |
Definition | If a set of search matches, this is the (potentially estimated) 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. |
Cardinality | 0..1 |
Type | unsignedInt |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1 |
Constraints |
|
Bundle.link | |
Short | Links related to this Bundle |
Definition | A series of links that provide context to this bundle. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Comments | 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. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.link.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.relation | |
Short | See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 |
Definition | A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. |
Cardinality | 1..1 |
Type | code |
Binding | |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.url | |
Short | Reference details for the link |
Definition | The reference details for the link. |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.entry | |
Short | Entries in the bundle |
Definition | An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). |
Cardinality | 1..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Bundle.entry.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.link | |
Short | Links related to this entry |
Definition | A series of links that provide context to this entry. |
Cardinality | 0..* |
Type | see (link) |
Summary | True |
Constraints |
|
Bundle.entry.fullUrl | |
Short | Full URL for the entry |
Definition | The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. 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. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
|
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | fullUrl 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 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, 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). |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-7, bdl-15, bdl-8 |
Constraints |
|
Bundle.entry.resource | |
Short | A resource in the bundle |
Definition | The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning. |
Cardinality | 1..1 |
Type | Device |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3c, bdl-7, bdl-11, bdl-12, bdl-13, bdl-5 |
Bundle.entry.resource.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.entry.resource.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.entry.resource.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.entry.resource.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.entry.resource.text | |
Short | Text summary of the resource, for human interpretation |
Definition | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. |
Cardinality | 0..1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. |
Conditions | The cardinality or value of this element may be affected by these constraints: dom-6 |
Constraints |
|
Mappings |
|
Bundle.entry.resource.contained | |
Short | Contained, inline Resources |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. |
Cardinality | 0..* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. |
Conditions | The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 |
Mappings |
|
Bundle.entry.resource.extension | |
Short | Additional content defined by implementations |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.modifierExtension | |
Short | Extensions that cannot be ignored |
Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.identifier | |
Short | External Identifiers for this procedure |
Definition | Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server. |
Cardinality | 0..* |
Type | Identifier |
Summary | True |
Requirements | Allows identification of the procedure as it is known by various participating systems and in a way that remains consistent across servers. |
Comments | This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and Person resource instances might share the same social insurance number. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.instantiatesCanonical | |
Short | Instantiates FHIR protocol or definition |
Definition | The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. |
Cardinality | 0..* |
Type | canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.instantiatesUri | |
Short | Instantiates external protocol or definition |
Definition | The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. |
Cardinality | 0..* |
Type | uri |
Summary | True |
Comments | This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.basedOn | |
Short | A request for this procedure |
Definition | A reference to a resource that contains details of the request for this procedure. |
Cardinality | 0..* |
Type | Reference(CarePlan | ServiceRequest) |
Summary | True |
Alias | fulfills |
Constraints |
|
Mappings |
|
Bundle.entry.resource.partOf | |
Short | Part of referenced event |
Definition | A larger event of which this particular procedure is a component or step. |
Cardinality | 0..* |
Type | Reference(Procedure | Observation | MedicationAdministration) |
Summary | True |
Alias | container |
Comments | The MedicationAdministration resource has a partOf reference to Procedure, but this is not a circular reference. For example, the anesthesia MedicationAdministration is part of the surgical Procedure (MedicationAdministration.partOf = Procedure). For example, the procedure to insert the IV port for an IV medication administration is part of the medication administration (Procedure.partOf = MedicationAdministration). |
Constraints |
|
Mappings |
|
Bundle.entry.resource.status | |
Short | preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown |
Definition | A code specifying the state of the procedure. Generally, this will be the in-progress or completed state. |
Cardinality | 1..1 |
Type | code |
Binding | A code specifying the state of the procedure. |
Modifier | True |
Summary | True |
Comments | The "unknown" code is not to be used to convey other statuses. The "unknown" code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.statusReason | |
Short | Reason for current status |
Definition | Captures the reason for the current state of the procedure. |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | A code that identifies the reason a procedure was not performed. |
Summary | True |
Alias | Suspended Reason, Cancelled Reason |
Comments | This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.category | |
Short | Classification of the procedure |
Definition | A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). |
Cardinality | 0..* |
Type | CodeableConcept |
Binding | A code that classifies a procedure for searching, sorting and display purposes. |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.code | |
Short | Identification of the procedure |
Definition | The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy"). |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | A code to identify a specific procedure . |
Summary | True |
Alias | type |
Requirements | 0..1 to account for primarily narrative only resources. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.subject | |
Short | Individual or entity the procedure was performed on |
Definition | On whom or on what the procedure was performed. This is usually an individual human, but can also be performed on animals, groups of humans or animals, organizations or practitioners (for licensing), locations or devices (for safety inspections or regulatory authorizations). If the actual focus of the procedure is different from the subject, the focus element specifies the actual focus of the procedure. |
Cardinality | 1..1 |
Type | Reference(Patient | Group | Device | Practitioner | Organization | Location) |
Summary | True |
Alias | patient |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focus | |
Short | Who is the target of the procedure when it is not the subject of record only |
Definition | Who is the target of the procedure when it is not the subject of record only. If focus is not present, then subject is the focus. If focus is present and the subject is one of the targets of the procedure, include subject as a focus as well. If focus is present and the subject is not included in focus, it implies that the procedure was only targeted on the focus. For example, when a caregiver is given education for a patient, the caregiver would be the focus and the procedure record is associated with the subject (e.g. patient). For example, use focus when recording the target of the education, training, or counseling is the parent or relative of a patient. |
Cardinality | 0..1 |
Type | Reference(Patient | Group | RelatedPerson | Practitioner | Organization | CareTeam | PractitionerRole | Specimen) |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.encounter | |
Short | The Encounter during which this Procedure was created |
Definition | The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated. |
Cardinality | 0..1 |
Type | Reference(Encounter) |
Summary | True |
Comments | This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.occurrence[x] | |
Short | When the procedure occurred or is occurring |
Definition | Estimated or actual date, date-time, period, or age when the procedure did occur or is occurring. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured. |
Cardinality | 0..1 |
Type | dateTime, Period, string, Age, Range, Timing |
Summary | True |
Comments | This indicates when the procedure actually occurred or is occurring, not when it was asked/requested/ordered to occur. For the latter, look at the occurence element of the Request this Procedure is "basedOn". The status code allows differentiation of whether the timing reflects a historic event or an ongoing event. Ongoing events should not include an upper bound in the Period or Timing.bounds. Age is generally used when the patient reports an age at which the procedure was performed. Range is generally used when the patient reports an age range when the procedure was performed, such as sometime between 20-25 years old. dateTime supports a range of precision due to some procedures being reported as past procedures that might not have millisecond precision while other procedures performed and documented during the encounter might have more precise UTC timestamps with timezone. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.recorded | |
Short | When the procedure was first captured in the subject's record |
Definition | The date the occurrence of the procedure was first captured in the record regardless of Procedure.status (potentially after the occurrence of the event). |
Cardinality | 0..1 |
Type | dateTime |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.recorder | |
Short | Who recorded the procedure |
Definition | Individual who recorded the record and takes responsibility for its content. |
Cardinality | 0..1 |
Type | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.reported[x] | |
Short | Reported rather than primary record |
Definition | Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report. |
Cardinality | 0..1 |
Type | boolean, Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization) |
Summary | True |
Alias | informer |
Requirements | Reported data may have different rules on editing and may be visually distinguished from primary data. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer | |
Short | Who performed the procedure and what they did |
Definition | Indicates who or what performed the procedure and how they were involved. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.resource.performer.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.function | |
Short | Type of performance |
Definition | Distinguishes the type of involvement of the performer in the procedure. For example, surgeon, anaesthetist, endoscopist. |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | A code that identifies the role of a performer of the procedure. |
Summary | True |
Requirements | Allows disambiguation of the types of involvement of different performers. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.actor | |
Short | Who performed the procedure |
Definition | Indicates who or what performed the procedure. |
Cardinality | 1..1 |
Type | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device | CareTeam | HealthcareService) |
Summary | True |
Requirements | A reference to Device supports use cases, such as pacemakers. |
Conditions | The cardinality or value of this element may be affected by these constraints: prc-1 |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.onBehalfOf | |
Short | Organization the device or practitioner was acting for |
Definition | The Organization the Patient, RelatedPerson, Device, CareTeam, and HealthcareService was acting on behalf of. |
Cardinality | 0..1 |
Type | Reference(Organization) |
Requirements | Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action. |
Comments | Organization, Patient, RelatedPerson, Device, CareTeam, and HealthcareService can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action. |
Conditions | The cardinality or value of this element may be affected by these constraints: prc-1 |
Constraints |
|
Mappings |
|
Bundle.entry.resource.performer.period | |
Short | When the performer performed the procedure |
Definition | Time period during which the performer performed the procedure. |
Cardinality | 0..1 |
Type | Period |
Constraints |
|
Bundle.entry.resource.location | |
Short | Where the procedure happened |
Definition | The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant. |
Cardinality | 0..1 |
Type | Reference(Location) |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.entry.resource.reason | |
Short | The justification that the procedure was performed |
Definition | The coded reason or reference why the procedure was performed. This may be a coded entity of some type, be present as text, or be a reference to one of several resources that justify the procedure. |
Cardinality | 0..* |
Type | CodeableReference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference) |
Binding | A code that identifies the reason a procedure is required. |
Summary | True |
Comments | Use Procedure.reason.concept when a code sufficiently describes the reason. Use Procedure.reason.reference when referencing a resource, which allows more information to be conveyed, such as onset date. For a single Procedure.reason, if both Procedure.reason.concept and Procedure.reason.reference are present, they are expected to be consistent with each other. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.bodySite | |
Short | Target body sites |
Definition | Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. |
Cardinality | 0..* |
Type | CodeableConcept |
Binding | SNOMED CT Body site concepts |
Summary | True |
Comments | If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension http://hl7.org/fhir/StructureDefinition/procedure-targetBodyStructure. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.outcome | |
Short | The result of procedure |
Definition | The outcome of the procedure - did it resolve the reasons for the procedure being performed? |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | An outcome of a procedure - whether it was resolved or otherwise. |
Summary | True |
Comments | If outcome contains narrative text only, it can be captured using the CodeableConcept.text. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.report | |
Short | Any report resulting from the procedure |
Definition | This could be a histology result, pathology report, surgical report, etc. |
Cardinality | 0..* |
Type | Reference(DiagnosticReport | DocumentReference | Composition) |
Comments | There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.complication | |
Short | Complication following the procedure |
Definition | Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues. |
Cardinality | 0..* |
Type | CodeableReference(Condition) |
Binding | Codes describing complications that resulted from a procedure. |
Comments | If complications are only expressed by the narrative text, they can be captured using the CodeableReference.concept.text. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.followUp | |
Short | Instructions for follow up |
Definition | If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used. |
Cardinality | 0..* |
Type | CodeableConcept |
Binding | Specific follow up required for a procedure e.g. removal of sutures. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.note | |
Short | Additional information about the procedure |
Definition | Any other notes and comments about the procedure. |
Cardinality | 0..* |
Type | Annotation |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice | |
Short | Manipulated, implanted, or removed device |
Definition | A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure. |
Cardinality | 0..* |
Type | BackboneElement |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.resource.focalDevice.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice.action | |
Short | Kind of change to device |
Definition | The kind of change that happened to the device during the procedure. |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | A kind of change that happened to the device during the procedure. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.focalDevice.manipulated | |
Short | Device that was changed |
Definition | The device that was manipulated (changed) during the procedure. |
Cardinality | 1..1 |
Type | Reference(Device) |
Constraints |
|
Mappings |
|
Bundle.entry.resource.used | |
Short | Items used during procedure |
Definition | Identifies medications, devices and any other substance used as part of the procedure. |
Cardinality | 0..* |
Type | CodeableReference(Device | Medication | Substance | BiologicallyDerivedProduct) |
Binding | Codes describing items used during a procedure. |
Requirements | Used for tracking contamination, etc. |
Comments | For devices actually implanted or removed, use Procedure.focalDevice.manipulated. |
Constraints |
|
Mappings |
|
Bundle.entry.resource.supportingInfo | |
Short | Extra information relevant to the procedure |
Definition | Other resources from the patient record that may be relevant to the procedure. The information from these resources was either used to create the instance or is provided to help with its interpretation. This extension should not be used if more specific inline elements or extensions are available. |
Cardinality | 0..* |
Type | Reference(Resource) |
Constraints |
|
Mappings |
|
Bundle.entry.resource.Procedure | |
Bundle.entry.resource.Device | |
Bundle.entry.search | |
Short | Search related information |
Definition | Information about the search process that lead to the creation of this entry. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-2 |
Constraints |
|
Bundle.entry.search.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.search.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.mode | |
Short | match | include - why this is in the result set |
Definition | Why 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. |
Cardinality | 0..1 |
Type | code |
Binding | Why 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. |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.search.score | |
Short | Search ranking (between 0 and 1) |
Definition | When searching, the server's search ranking score for the entry. |
Cardinality | 0..1 |
Type | decimal |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.request | |
Short | Additional execution information (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-5 |
Constraints |
|
Bundle.entry.request.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.request.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.method | |
Short | GET | HEAD | POST | PUT | DELETE | PATCH |
Definition | In 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. |
Cardinality | 1..1 |
Type | code |
Binding | HTTP verbs (in the HTTP command line). See HTTP rfc for details. |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3b, bdl-3c, bdl-14, bdl-15 |
Constraints |
|
Bundle.entry.request.url | |
Short | URL for HTTP equivalent of this entry |
Definition | The URL for this entry, relative to the root (the address to which the request is posted). |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | 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]". |
Constraints |
|
Bundle.entry.request.ifNoneMatch | |
Short | For managing cache validation |
Definition | If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifModifiedSince | |
Short | For managing cache currency |
Definition | Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Constraints |
|
Bundle.entry.request.ifMatch | |
Short | For managing update contention |
Definition | Only perform the operation if the Etag value matches. For more information, see the API section "Managing Resource Contention". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifNoneExist | |
Short | For conditional creates |
Definition | Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?"). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response | |
Short | Results of execution (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3d, bdl-5 |
Constraints |
|
Bundle.entry.response.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.response.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.status | |
Short | Status response code (text optional) |
Definition | 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. |
Cardinality | 1..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response.location | |
Short | The location (if the operation returns a location) |
Definition | The location header created by processing this operation, populated if the operation returns a location. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Constraints |
|
Bundle.entry.response.etag | |
Short | The Etag for the resource (if relevant) |
Definition | The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. |
Constraints |
|
Bundle.entry.response.lastModified | |
Short | Server's date time modified |
Definition | The date/time that the resource was modified on the server. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. |
Constraints |
|
Bundle.entry.response.outcome | |
Short | OperationOutcome with hints and warnings (for batch/transaction) |
Definition | An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. |
Cardinality | 0..1 |
Type | Resource |
Summary | True |
Comments | 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.signature | |
Short | Digital Signature |
Definition | Digital Signature - base64 encoded. XML-DSig or a JWS. |
Cardinality | 0..1 |
Type | Signature |
Summary | True |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Bundle.issues | |
Short | Issues with the Bundle |
Definition | Captures issues and warnings that relate to the construction of the Bundle and the content within it. |
Cardinality | 0..1 |
Type | OperationOutcome |
Summary | True |
Comments | Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-16, bdl-17 |
Annual Calibration and Conductivity Probe Replaced
AnnualCalibrationConductivityProbeReplaced (Bundle) | C | Bundle | |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
identifier | Σ C | 0..1 | Identifier |
id | 0..1 | id | |
extension | C | 0..* | Extension |
use | Σ ?! | 0..1 | codeBinding |
type | Σ | 0..1 | CodeableConceptBinding |
id | 0..1 | id | |
extension | C | 0..* | Extension |
coding | Σ | 0..* | Coding |
text | Σ | 1..1 | stringFixed Value |
system | Σ | 0..1 | uri |
value | Σ C | 0..1 | string |
period | Σ | 0..1 | Period |
assigner | Σ | 0..1 | Reference(Organization) |
type | Σ C | 1..1 | codeBindingFixed Value |
timestamp | Σ C | 0..1 | instant |
total | Σ C | 0..1 | unsignedInt |
link | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
relation | Σ C | 1..1 | codeBinding |
url | Σ C | 1..1 | uri |
entry | Σ C | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
link | Σ | 0..* | see (link) |
fullUrl | Σ C | 0..1 | uri |
resource | Σ C | 0..1 | Resource |
id | Σ | 0..1 | id |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
resourceType | Pattern | ||
Procedure | |||
Device | |||
search | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
mode | Σ | 0..1 | codeBinding |
score | Σ | 0..1 | decimal |
request | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
method | Σ C | 1..1 | codeBinding |
url | Σ | 1..1 | uri |
ifNoneMatch | Σ | 0..1 | string |
ifModifiedSince | Σ | 0..1 | instant |
ifMatch | Σ | 0..1 | string |
ifNoneExist | Σ | 0..1 | string |
response | Σ C | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
status | Σ | 1..1 | string |
location | Σ | 0..1 | uri |
etag | Σ | 0..1 | string |
lastModified | Σ | 0..1 | instant |
outcome | Σ | 0..1 | Resource |
signature | Σ | 0..1 | Signature |
issues | Σ C | 0..1 | OperationOutcome |
Bundle | |
Short | Contains a collection of resources |
Definition | A container for a collection of resources. |
Cardinality | 0..* |
Constraints |
|
Mappings |
|
Bundle.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.identifier | |
Short | Persistent identifier for the bundle |
Definition | A persistent identifier for the bundle that won't change as a bundle is copied from server to server. |
Cardinality | 0..1 |
Type | Identifier |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-9 |
Constraints |
|
Mappings |
|
Bundle.identifier.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | id |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.identifier.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url |
Constraints |
|
Mappings |
|
Bundle.identifier.use | |
Short | usual | official | temp | secondary | old (If known) |
Definition | The purpose of this identifier. |
Cardinality | 0..1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Constraints |
|
Mappings |
|
Bundle.identifier.type | |
Short | Description of identifier |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 0..1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Constraints |
|
Mappings |
|
Bundle.identifier.type.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | id |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.identifier.type.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url |
Constraints |
|
Mappings |
|
Bundle.identifier.type.coding | |
Short | Code defined by a terminology system |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0..* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Constraints |
|
Mappings |
|
Bundle.identifier.type.text | |
Short | Plain text representation of the concept |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 1..1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Constraints |
|
Fixed Value | Annual Calibration and Conductivity Probe Replaced |
Mappings |
|
Bundle.identifier.system | |
Short | The namespace for the identifier value |
Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Constraints |
|
Examples | Generalhttp://www.acme.com/identifiers/patient |
Mappings |
|
Bundle.identifier.value | |
Short | The value that is unique |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 |
Constraints |
|
Examples | General123456 |
Mappings |
|
Bundle.identifier.period | |
Short | Time period when id is/was valid for use |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0..1 |
Type | Period |
Summary | True |
Constraints |
|
Mappings |
|
Bundle.identifier.assigner | |
Short | Organization that issued id (may be just text) |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0..1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Constraints |
|
Mappings |
|
Bundle.type | |
Short | document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection | subscription-notification |
Definition | Indicates the purpose of this bundle - how it is intended to be used. |
Cardinality | 1..1 |
Type | code |
Binding | Indicates the purpose of a bundle - how it is intended to be used. |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1, bdl-2, bdl-3a, bdl-3b, bdl-3c, bdl-3d, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, bdl-13, bdl-14, bdl-15, bdl-17, bdl-18 |
Constraints |
|
Fixed Value | collection |
Mappings |
|
Bundle.timestamp | |
Short | When the bundle was assembled |
Definition | The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | 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:
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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-10 |
Constraints |
|
Mappings |
|
Bundle.total | |
Short | If search, the total number of matches |
Definition | If a set of search matches, this is the (potentially estimated) 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. |
Cardinality | 0..1 |
Type | unsignedInt |
Summary | True |
Comments | 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. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1 |
Constraints |
|
Bundle.link | |
Short | Links related to this Bundle |
Definition | A series of links that provide context to this bundle. |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Comments | 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. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.link.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.link.relation | |
Short | See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 |
Definition | A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. |
Cardinality | 1..1 |
Type | code |
Binding | |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.link.url | |
Short | Reference details for the link |
Definition | The reference details for the link. |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 |
Constraints |
|
Bundle.entry | |
Short | Entry in the bundle - will have a resource or information |
Definition | An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). |
Cardinality | 0..* |
Type | BackboneElement |
Summary | True |
Constraints |
|
Bundle.entry.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.link | |
Short | Links related to this entry |
Definition | A series of links that provide context to this entry. |
Cardinality | 0..* |
Type | see (link) |
Summary | True |
Constraints |
|
Bundle.entry.fullUrl | |
Short | URI for resource (e.g. the absolute URL server address, URI for UUID/OID, etc.) |
Definition | The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. 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. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
|
Cardinality | 0..1 |
Type | uri |
Summary | True |
Comments | fullUrl 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 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, 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). |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-7, bdl-15, bdl-8 |
Constraints |
|
Bundle.entry.resource | |
Short | A resource in the bundle |
Definition | The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning. |
Cardinality | 0..1 |
Type | Resource |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3c, bdl-7, bdl-11, bdl-12, bdl-13, bdl-5 |
Bundle.entry.resource.id | |
Short | Logical id of this artifact |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0..1 |
Type | id |
Summary | True |
Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
Bundle.entry.resource.meta | |
Short | Metadata about the resource |
Definition | The 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. |
Cardinality | 0..1 |
Type | Meta |
Summary | True |
Constraints |
|
Bundle.entry.resource.implicitRules | |
Short | A set of rules under which this content was created |
Definition | A 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. |
Cardinality | 0..1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 its narrative along with other profiles, value sets, etc. |
Constraints |
|
Bundle.entry.resource.language | |
Short | Language of the resource content |
Definition | The base language in which the resource is written. |
Cardinality | 0..1 |
Type | code |
Binding | IETF language tag for a human language |
Comments | 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). |
Constraints |
|
Bundle.entry.resource.resourceType | |
Pattern | Procedure | Device |
Bundle.entry.resource.Procedure | |
Bundle.entry.resource.Device | |
Bundle.entry.search | |
Short | Search related information |
Definition | Information about the search process that lead to the creation of this entry. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-2 |
Constraints |
|
Bundle.entry.search.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.search.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.search.mode | |
Short | match | include - why this is in the result set |
Definition | Why 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. |
Cardinality | 0..1 |
Type | code |
Binding | Why 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. |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.search.score | |
Short | Search ranking (between 0 and 1) |
Definition | When searching, the server's search ranking score for the entry. |
Cardinality | 0..1 |
Type | decimal |
Summary | True |
Comments | 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. |
Constraints |
|
Bundle.entry.request | |
Short | Additional execution information (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-5 |
Constraints |
|
Bundle.entry.request.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.request.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.request.method | |
Short | GET | HEAD | POST | PUT | DELETE | PATCH |
Definition | In 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. |
Cardinality | 1..1 |
Type | code |
Binding | HTTP verbs (in the HTTP command line). See HTTP rfc for details. |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3b, bdl-3c, bdl-14, bdl-15 |
Constraints |
|
Bundle.entry.request.url | |
Short | URL for HTTP equivalent of this entry |
Definition | The URL for this entry, relative to the root (the address to which the request is posted). |
Cardinality | 1..1 |
Type | uri |
Summary | True |
Comments | 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]". |
Constraints |
|
Bundle.entry.request.ifNoneMatch | |
Short | For managing cache validation |
Definition | If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifModifiedSince | |
Short | For managing cache currency |
Definition | Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read". |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Constraints |
|
Bundle.entry.request.ifMatch | |
Short | For managing update contention |
Definition | Only perform the operation if the Etag value matches. For more information, see the API section "Managing Resource Contention". |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.request.ifNoneExist | |
Short | For conditional creates |
Definition | Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?"). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response | |
Short | Results of execution (transaction/batch/history) |
Definition | 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. |
Cardinality | 0..1 |
Type | BackboneElement |
Summary | True |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3d, bdl-5 |
Constraints |
|
Bundle.entry.response.id | |
Short | Unique id for inter-element referencing |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0..1 |
Type | string |
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 |
Mappings |
|
Bundle.entry.response.extension | |
Short | Additional content defined by implementations |
Definition | May 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 managable, 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. |
Cardinality | 0..* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.modifierExtension | |
Short | Extensions that cannot be ignored even if unrecognized |
Definition | May 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 managable, 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). |
Cardinality | 0..* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Mappings |
|
Bundle.entry.response.status | |
Short | Status response code (text optional) |
Definition | 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. |
Cardinality | 1..1 |
Type | string |
Summary | True |
Constraints |
|
Bundle.entry.response.location | |
Short | The location (if the operation returns a location) |
Definition | The location header created by processing this operation, populated if the operation returns a location. |
Cardinality | 0..1 |
Type | uri |
Summary | True |
Constraints |
|
Bundle.entry.response.etag | |
Short | The Etag for the resource (if relevant) |
Definition | The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). |
Cardinality | 0..1 |
Type | string |
Summary | True |
Comments | Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. |
Constraints |
|
Bundle.entry.response.lastModified | |
Short | Server's date time modified |
Definition | The date/time that the resource was modified on the server. |
Cardinality | 0..1 |
Type | instant |
Summary | True |
Comments | This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. |
Constraints |
|
Bundle.entry.response.outcome | |
Short | OperationOutcome with hints and warnings (for batch/transaction) |
Definition | An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. |
Cardinality | 0..1 |
Type | Resource |
Summary | True |
Comments | 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.signature | |
Short | Digital Signature |
Definition | Digital Signature - base64 encoded. XML-DSig or a JWS. |
Cardinality | 0..1 |
Type | Signature |
Summary | True |
Requirements | 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. |
Comments | 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. |
Constraints |
|
Bundle.issues | |
Short | Issues with the Bundle |
Definition | Captures issues and warnings that relate to the construction of the Bundle and the content within it. |
Cardinality | 0..1 |
Type | OperationOutcome |
Summary | True |
Comments | Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle. |
Conditions | The cardinality or value of this element may be affected by these constraints: bdl-16, bdl-17 |