FHIR International Patient Summary (IPS)
Introduction
The FHIR International Patient Summary (IPS) is a standardized clinical document used to exchange essential patient health information across healthcare systems and countries.
IPS enables safe and efficient sharing of patient summaries for:
- Emergency care
- Cross-border treatment
- Care continuity
- Health information exchange
What is IPS?
IPS is a minimal yet clinically relevant dataset that provides a snapshot of a patient's health status.
Typical information includes:
- Demographics
- Allergies
- Medical conditions
- Medications
- Immunizations
- Procedures
- Diagnostic results
- Vital signs
IPS Architecture
FHIR IPS is implemented as a FHIR Document Bundle and the Composition resource acts as the table of contents referencing all clinical resources. R4 version is used.
| BundleUvIps (Bundle) | C | Bundle | Element idBundleShort description International Patient Summary Bundle DefinitionInternational Patient Summary Bundle. A container for a collection of resources in the patient summary document.
| |||||||||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idBundle.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||||||||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idBundle.metaShort description Metadata about the resource DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idBundle.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idBundle.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||
| identifier | SO Σ | 1..1 | Identifier | Element idBundle.identifierShort description Persistent identifier for the bundle DefinitionA persistent identifier for the bundle that won't change as a bundle is copied from server to server. Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| type | Σ | 1..1 | codeBindingFixed Value | Element idBundle.typeShort description document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection DefinitionIndicates the purpose of this bundle - how it is intended to be used. It's possible to use a bundle for other purposes (e.g. a document can be accepted as a transaction). This is primarily defined so that there can be specific rules for some of the bundle types. Indicates the purpose of a bundle - how it is intended to be used. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
documentMappings
| ||||||||
| timestamp | SO Σ | 1..1 | instant | Element idBundle.timestampShort description When the bundle was assembled DefinitionThe date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated. Usage:
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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| total | Σ C | 0..1 | unsignedInt | There are no (further) constraints on this element Element idBundle.totalShort description If search, the total number of matches DefinitionIf a set of search matches, this is the total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle. Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-1 Constraints
| ||||||||
| link | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.linkShort description Links related to this Bundle DefinitionA series of links that provide context to this bundle. Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS). Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was read directly. This specification defines some specific uses of Bundle.link for searching and paging, but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.link.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.link.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.link.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| relation | Σ | 1..1 | string | There are no (further) constraints on this element Element idBundle.link.relationShort description See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 DefinitionA name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| url | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.link.urlShort description Reference details for the link DefinitionThe reference details for the link. see http://en.wikipedia.org/wiki/Uniform_resource_identifier The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| entry | Σ C | 2..* | BackboneElement | Element idBundle.entryShort description Entry resource in the patient summary bundle DefinitionAn entry resource included in the patient summary document bundle resource. Must contain the IPS Composition as the first entry (only a single Composition resource instance may be included) and a Patient resource. Additional constraints are specified in the IPS Composition profile. Unordered, Open, by resource(Type), resource(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| (All Slices) | The requirements in this element apply to all slices | |||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ | 0..1 | Resource | There are no (further) constraints on this element Element idBundle.entry.resourceShort description A resource in the bundle DefinitionThe Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| composition | SO Σ C | 1..1 | BackboneElement | Element idBundle.entry:compositionShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:composition.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:composition.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:composition.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:composition.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:composition.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | CompositionUvIps | Element idBundle.entry:composition.resourceShort description International Patient Summary composition DefinitionInternational Patient Summary composition. A composition is a set of healthcare-related information that is assembled together into a single logical document that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:composition.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:composition.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:composition.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| patient | Σ C | 1..1 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:patientShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:patient.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:patient.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:patient.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:patient.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:patient.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | PatientUvIps | Element idBundle.entry:patient.resourceShort description Information about an individual or animal receiving health care services Alternate namesSubjectOfCare Client Resident DefinitionDemographics and other administrative information about an individual or animal receiving care or other health-related services.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:patient.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:patient.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:patient.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| allergyintolerance | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:allergyintoleranceShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:allergyintolerance.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:allergyintolerance.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:allergyintolerance.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:allergyintolerance.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:allergyintolerance.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | AllergyIntoleranceUvIps | Element idBundle.entry:allergyintolerance.resourceShort description Allergy or Intolerance (generally: Risk of adverse reaction to a substance) Alternate namesAllergy, Intolerance, Adverse Reaction DefinitionRisk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. Substances include, but are not limited to: a therapeutic substance administered correctly at an appropriate dosage for the individual; food; material derived from plants or animals; or venom from insect stings.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:allergyintolerance.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:allergyintolerance.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:allergyintolerance.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| careplan | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:careplanShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:careplan.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:careplan.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:careplan.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:careplan.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:careplan.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ | 1..1 | CarePlan | Element idBundle.entry:careplan.resourceShort description A resource in the bundle DefinitionThe Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:careplan.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:careplan.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:careplan.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| clinicalimpression | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:clinicalimpressionShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:clinicalimpression.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:clinicalimpression.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:clinicalimpression.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:clinicalimpression.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:clinicalimpression.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ | 1..1 | ClinicalImpression | Element idBundle.entry:clinicalimpression.resourceShort description A resource in the bundle DefinitionThe Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:clinicalimpression.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:clinicalimpression.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:clinicalimpression.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| condition | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:conditionShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:condition.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:condition.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:condition.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:condition.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:condition.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ConditionUvIps | Element idBundle.entry:condition.resourceShort description Documentation of a health problem of the patient DefinitionA clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:condition.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:condition.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:condition.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| consent | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:consentShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:consent.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:consent.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:consent.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:consent.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:consent.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ | 1..1 | Consent | Element idBundle.entry:consent.resourceShort description A resource in the bundle DefinitionThe Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:consent.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:consent.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:consent.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| device | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:deviceShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:device.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:device.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:device.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:device.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:device.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ | 1..1 | Device | Element idBundle.entry:device.resourceShort description A resource in the bundle DefinitionThe Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:device.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:device.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:device.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| deviceusestatement | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:deviceusestatementShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:deviceusestatement.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:deviceusestatement.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:deviceusestatement.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:deviceusestatement.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:deviceusestatement.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | DeviceUseStatementUvIps | Element idBundle.entry:deviceusestatement.resourceShort description Record of use of a device DefinitionA record of a device being used by a patient where the record is the result of a report from the patient or another clinician.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:deviceusestatement.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:deviceusestatement.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:deviceusestatement.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| diagnosticreport | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:diagnosticreportShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:diagnosticreport.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:diagnosticreport.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:diagnosticreport.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:diagnosticreport.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:diagnosticreport.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | DiagnosticReportUvIps | Element idBundle.entry:diagnosticreport.resourceShort description A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports Alternate namesReport, Test, Result, Results, Labs, Laboratory DefinitionThe findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:diagnosticreport.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:diagnosticreport.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:diagnosticreport.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| documentreference | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:documentreferenceShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:documentreference.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:documentreference.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:documentreference.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:documentreference.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:documentreference.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ | 1..1 | DocumentReference | Element idBundle.entry:documentreference.resourceShort description A resource in the bundle DefinitionThe Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:documentreference.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:documentreference.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:documentreference.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| flag | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:flagShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:flag.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:flag.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:flag.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:flag.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:flag.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | FlagAlertUvIps | Element idBundle.entry:flag.resourceShort description Key information to flag to healthcare providers Alternate namesBarriers to Care, Alert, Warning DefinitionProspective warnings of potential issues when providing care to the patient.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:flag.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:flag.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:flag.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| imagingstudy | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:imagingstudyShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:imagingstudy.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:imagingstudy.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:imagingstudy.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:imagingstudy.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:imagingstudy.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ImagingStudyUvIps | Element idBundle.entry:imagingstudy.resourceShort description A set of images produced in single study (one or more series of references images) DefinitionRepresentation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:imagingstudy.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:imagingstudy.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:imagingstudy.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| immunization | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:immunizationShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:immunization.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:immunization.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:immunization.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:immunization.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:immunization.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ImmunizationUvIps | Element idBundle.entry:immunization.resourceShort description Immunization event information DefinitionDescribes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:immunization.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:immunization.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:immunization.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| immunizationrecommendation | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:immunizationrecommendationShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:immunizationrecommendation.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:immunizationrecommendation.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:immunizationrecommendation.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:immunizationrecommendation.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:immunizationrecommendation.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ | 1..1 | ImmunizationRecommendation | Element idBundle.entry:immunizationrecommendation.resourceShort description A resource in the bundle DefinitionThe Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:immunizationrecommendation.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:immunizationrecommendation.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:immunizationrecommendation.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| medication | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medicationShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:medication.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:medication.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:medication.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:medication.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:medication.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | MedicationIPS | Element idBundle.entry:medication.resourceShort description Definition of a Medication DefinitionThis resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use. IPS Medication
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medication.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medication.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medication.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| medicationrequest | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medicationrequestShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:medicationrequest.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:medicationrequest.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:medicationrequest.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:medicationrequest.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:medicationrequest.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | MedicationRequestIPS | Element idBundle.entry:medicationrequest.resourceShort description Ordering of medication for patient or group Alternate namesPrescription, Order DefinitionAn order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medicationrequest.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medicationrequest.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medicationrequest.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| medicationstatement | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medicationstatementShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:medicationstatement.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:medicationstatement.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:medicationstatement.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:medicationstatement.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:medicationstatement.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | MedicationStatementIPS | Element idBundle.entry:medicationstatement.resourceShort description Record of medication being taken by a patient DefinitionA record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains. The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medication statement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the medication statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information. When interpreting a medicationStatement, the value of the status and NotTaken needed to be considered: MedicationStatement.status + MedicationStatement.wasNotTaken Status=Active + NotTaken=T = Not currently taking Status=Completed + NotTaken=T = Not taken in the past Status=Intended + NotTaken=T = No intention of taking Status=Active + NotTaken=F = Taking, but not as prescribed Status=Active + NotTaken=F = Taking Status=Intended +NotTaken= F = Will be taking (not started) Status=Completed + NotTaken=F = Taken in past Status=In Error + NotTaken=N/A = In Error.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medicationstatement.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medicationstatement.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:medicationstatement.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| practitioner | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:practitionerShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:practitioner.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:practitioner.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:practitioner.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:practitioner.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:practitioner.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | PractitionerUvIps | Element idBundle.entry:practitioner.resourceShort description A person with a formal responsibility in the provisioning of healthcare or related services DefinitionA person who is directly or indirectly involved in the provisioning of healthcare.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:practitioner.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:practitioner.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:practitioner.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| practitionerrole | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:practitionerroleShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:practitionerrole.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:practitionerrole.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:practitionerrole.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:practitionerrole.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:practitionerrole.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | PractitionerRoleUvIps | Element idBundle.entry:practitionerrole.resourceShort description Roles/organizations the practitioner is associated with DefinitionA specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:practitionerrole.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:practitionerrole.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:practitionerrole.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| procedure | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:procedureShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:procedure.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:procedure.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:procedure.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:procedure.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:procedure.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ProcedureUvIps | Element idBundle.entry:procedure.resourceShort description An action that is being or was performed on a patient DefinitionAn action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:procedure.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:procedure.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:procedure.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| observation-pregnancy-edd | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-eddShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-edd.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-edd.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-edd.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-edd.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-edd.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ObservationPregnancyEddUvIps | Element idBundle.entry:observation-pregnancy-edd.resourceShort description Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-edd.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-edd.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-edd.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| observation-pregnancy-outcome | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-outcomeShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-outcome.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-outcome.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-outcome.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-outcome.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-outcome.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ObservationPregnancyOutcomeUvIps | Element idBundle.entry:observation-pregnancy-outcome.resourceShort description Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc. ObservationPregnancyOutcomeUvIps Constraints
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-outcome.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-outcome.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-outcome.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| observation-pregnancy-status | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-statusShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-status.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-status.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-status.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-status.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-status.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ObservationPregnancyStatusUvIps | Element idBundle.entry:observation-pregnancy-status.resourceShort description Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc. ObservationPregnancyStatusUvIps Constraints
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-status.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-status.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-pregnancy-status.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| observation-alcohol-use | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-alcohol-useShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:observation-alcohol-use.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-alcohol-use.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-alcohol-use.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:observation-alcohol-use.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:observation-alcohol-use.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ObservationAlcoholUseUvIps | Element idBundle.entry:observation-alcohol-use.resourceShort description Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-alcohol-use.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-alcohol-use.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-alcohol-use.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| observation-tobacco-use | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-tobacco-useShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:observation-tobacco-use.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-tobacco-use.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-tobacco-use.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:observation-tobacco-use.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:observation-tobacco-use.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ObservationTobaccoUseUvIps | Element idBundle.entry:observation-tobacco-use.resourceShort description Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-tobacco-use.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-tobacco-use.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-tobacco-use.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| observation-results-laboratory-pathology | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-results-laboratory-pathologyShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:observation-results-laboratory-pathology.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-results-laboratory-pathology.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-results-laboratory-pathology.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:observation-results-laboratory-pathology.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:observation-results-laboratory-pathology.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ObservationResultsLaboratoryPathologyUvIps | Element idBundle.entry:observation-results-laboratory-pathology.resourceShort description Laboratory (including Pathology) result for a simple test or for a panel/study Alternate namesVital Signs, Measurement, Results, Tests DefinitionThis observation may represent the result of a simple laboratory or pathology test such as hematocrit, or it may group the set of results produced by a multi-test study or panel such as a complete blood count, a dynamic function test, or a urine specimen study. In the latter case, the observation carries the overall conclusion of the study and references the atomic results of the study as "has-member" child observations Represents either a lab simple observation or the group of observations produced by a laboratory study. ObservationResultsLaboratoryPathologyUvIps Constraints
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-results-laboratory-pathology.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-results-laboratory-pathology.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-results-laboratory-pathology.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| observation-results-radiology | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-results-radiologyShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:observation-results-radiology.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-results-radiology.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-results-radiology.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:observation-results-radiology.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:observation-results-radiology.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | ObservationResultsRadiologyUvIps | Element idBundle.entry:observation-results-radiology.resourceShort description Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc. ObservationResultsRadiologyUvIps Constraints
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-results-radiology.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-results-radiology.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-results-radiology.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| observation-vital-signs | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-vital-signsShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:observation-vital-signs.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-vital-signs.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:observation-vital-signs.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:observation-vital-signs.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:observation-vital-signs.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | observation-vitalsigns | Element idBundle.entry:observation-vital-signs.resourceShort description FHIR Vital Signs Profile Alternate namesVital Signs, Measurement, Results, Tests DefinitionThe FHIR Vitals Signs profile sets minimum expectations for the Observation Resource to record, search and fetch the vital signs associated with a patient. Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-vital-signs.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-vital-signs.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:observation-vital-signs.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| organization | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:organizationShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:organization.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:organization.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:organization.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:organization.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:organization.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | OrganizationUvIps | Element idBundle.entry:organization.resourceShort description A grouping of people or organizations with a common purpose DefinitionA formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:organization.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:organization.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:organization.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| specimen | Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:specimenShort description Entry in the bundle - will have a resource or information DefinitionAn entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idBundle.entry:specimen.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:specimen.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idBundle.entry:specimen.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| link | Σ | 0..* | see (link) | There are no (further) constraints on this element Element idBundle.entry:specimen.linkShort description Links related to this entry DefinitionA series of links that provide context to this entry. | ||||||||
| fullUrl | Σ | 1..1 | uri | There are no (further) constraints on this element Element idBundle.entry:specimen.fullUrlShort description URI for resource (Absolute URL server address or URI for UUID/OID) DefinitionThe Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
fullUrl 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||
| resource | Σ C | 1..1 | SpecimenUvIps | Element idBundle.entry:specimen.resourceShort description Sample for analysis DefinitionA sample to be used for analysis.
| ||||||||
| search | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:specimen.searchShort description Search related information DefinitionInformation about the search process that lead to the creation of this entry. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-2 Constraints
| ||||||||
| request | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:specimen.requestShort description Additional execution information (transaction/batch/history) DefinitionAdditional 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-3 Constraints
| ||||||||
| response | Σ C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idBundle.entry:specimen.responseShort description Results of execution (transaction/batch/history) DefinitionIndicates 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. The cardinality or value of this element may be affected by these constraints: ele-1, bdl-4 Constraints
| ||||||||
| signature | Σ | 0..1 | Signature | There are no (further) constraints on this element Element idBundle.signatureShort description Digital Signature DefinitionDigital Signature - base64 encoded. XML-DSig or a JWT. A Signature holds an electronic representation of a signature and its supporting context in a FHIR accessible form. The signature may either be a cryptographic type (XML DigSig or a JWS), which is able to provide non-repudiation proof, or it may be a graphical image that represents a signature or a signature process. This element allows capturing signatures on documents, 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
| CompositionUvIps (Composition) | C | Composition | Element idCompositionShort description International Patient Summary composition DefinitionInternational Patient Summary composition. A composition is a set of healthcare-related information that is assembled together into a single logical document that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.
| |||||||||||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||||||||||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idComposition.metaShort description Metadata about the resource DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.meta.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.meta.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| versionId | Σ | 0..1 | id | There are no (further) constraints on this element Element idComposition.meta.versionIdShort description Version specific identifier DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| lastUpdated | Σ | 0..1 | instant | There are no (further) constraints on this element Element idComposition.meta.lastUpdatedShort description When the resource version last changed DefinitionWhen the resource last changed - e.g. when the version changed. This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| source | Σ | 0..1 | uri | There are no (further) constraints on this element Element idComposition.meta.sourceShort description Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| profile | SO Σ | 0..* | canonical(StructureDefinition) | Element idComposition.meta.profileShort description The conformance of this Composition to a specific IPS version. DefinitionThe conformance of this Composition to a specific version of the IPS (e.g. http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips|2.0.0 for 2.0.0) It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idComposition.meta.securityShort description Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.meta.tagShort description Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idComposition.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| text | SO | 0..1 | Narrative | Element idComposition.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. Contained resources do not have 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idComposition.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. 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.
| |||||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 manageable, 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). 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| identifier | SO Σ | 0..1 | Identifier | Element idComposition.identifierShort description Version-independent identifier for the Composition DefinitionA version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time. Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| status | SO Σ ?! | 1..1 | codeBinding | Element idComposition.statusShort description preliminary | final | amended | entered-in-error DefinitionThe workflow/clinical status of this composition. The status is a marker for the clinical standing of the document. Need to be able to mark interim, amended, or withdrawn compositions or documents. If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements. Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required. The workflow/clinical status of the composition. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| type | SO Σ | 1..1 | CodeableConceptIPSBindingPattern | Element idComposition.typeShort description Kind of composition ("Patient Summary") DefinitionSpecifies that this composition refers to a Patient Summary (Loinc "60591-5") Key metadata element describing the composition, used in searching/filtering. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Type of a composition. FHIRDocumentTypeCodes (preferred) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "60591-5"
}
]
}Mappings
| ||||||||||
| category | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idComposition.categoryShort description Categorization of Composition DefinitionA categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type. Helps humans to assess whether the composition is of interest when viewing an index of compositions or documents. This is a metadata field from XDS/MHD. High-level kind of a clinical document at a macro level. DocumentClassValueSet (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| subject | SO Σ C | 1..1 | Reference(PatientUvIps) | Element idComposition.subjectShort description Who and/or what the composition is about DefinitionWho or what the composition is about. In general a composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). For the IPS the subject is always the patient. Essential metadata for searching for the composition. Identifies who and/or what the composition/document is about. For clinical documents, this is usually the patient. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.subject.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.subject.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| reference | SO Σ C | 1..1 | string | Element idComposition.subject.referenceShort description Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. The cardinality or value of this element may be affected by these constraints: ele-1, ref-1 Constraints
| ||||||||||
| type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element idComposition.subject.typeShort description Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idComposition.subject.identifierShort description Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.subject.displayShort description Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| encounter | Σ C | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idComposition.encounterShort description Context of the Composition DefinitionDescribes the clinical encounter or type of care this documentation is associated with. Provides context for the composition and supports searching. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| date | SO Σ | 1..1 | dateTime | Element idComposition.dateShort description Composition editing time DefinitionThe composition editing time, when the composition was last logically changed by the author. dateTime is used for tracking, organizing versions and searching. Note that this is the time of authoring. When packaged in a document, Bundle.timestamp is the date of packaging. The Last Modified Date on the composition may be after the date of the document was attested without being changed. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| author | SO Σ C | 1..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | Element idComposition.authorShort description Who and/or what authored the IPS DefinitionIdentifies who is responsible for the information in the composition, not necessarily who typed it in. Identifies who is responsible for the content. The distinction between the two types of IPS, "human-curated" or "software-assembled", is based on the authors recorded in this field: the author refers to humans (i.e. Practitioner, PractitionerRole, Patient, and/or RelatedPerson) if the IPS provenance is "human-curated", or devices (i.e. Device) if the IPS provenance is "software-assembled". In the case of a software-assembled IPS that is then verified by a human, the author would be the device that constructed the IPS document, but additional attesters would identity the humans who performed this check. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO Σ | 1..1 | string | Element idComposition.titleShort description The title of this patient summary. This may include information like the patient name and time generated DefinitionOfficial human-readable label for the composition. This would typically include a label of "International Patient Summary" or any equivalent translation and other relevant document information For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| confidentiality | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.confidentialityShort description As defined by affinity domain DefinitionThe code specifying the level of confidentiality of the Composition. The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not. Codes specifying the level of confidentiality of the composition. v3.ConfidentialityClassification (required) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| attester | SO | 0..* | BackboneElement | Element idComposition.attesterShort description Attests to accuracy of composition DefinitionA participant who has attested to the accuracy of the composition/document. Identifies responsibility for the accuracy of the composition content. Only list each attester once. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.attester.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.attester.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.attester.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| mode | SO | 1..1 | codeBinding | Element idComposition.attester.modeShort description personal | professional | legal | official DefinitionThe type of attestation the authenticator offers. Indicates the level of authority of the attestation. Note that FHIR strings SHALL NOT exceed 1MB in size The way in which a person authenticated a composition. CompositionAttestationMode (required) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| time | SO | 0..1 | dateTime | Element idComposition.attester.timeShort description When the composition was attested DefinitionWhen the composition was attested by the party. Identifies when the information in the composition was deemed accurate. (Things may have changed since then.). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| party | SO C | 0..1 | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | Element idComposition.attester.partyShort description Who attested the composition DefinitionWho attested the composition in the specified way. Identifies who has taken on the responsibility for accuracy of the composition content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| custodian | SO Σ C | 0..1 | Reference(Organization) | Element idComposition.custodianShort description Organization which maintains the composition DefinitionIdentifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. Identifies where to go to find the current version, where to report issues, etc. This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| relatesTo | 0..* | BackboneElement | There are no (further) constraints on this element Element idComposition.relatesToShort description Relationships to other compositions/documents DefinitionRelationships that this composition has with other compositions or documents that already exist. A document is a version specific composition. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.relatesTo.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.relatesTo.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.relatesTo.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | 1..1 | codeBinding | There are no (further) constraints on this element Element idComposition.relatesTo.codeShort description replaces | transforms | signs | appends DefinitionThe type of relationship that this composition has with anther composition or document. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document. The type of relationship between documents. DocumentRelationshipType (required) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| target[x] | 1..1 | There are no (further) constraints on this element Element idComposition.relatesTo.target[x]Short description Target of the relationship DefinitionThe target composition/document of this relationship. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||||
| targetIdentifier | Identifier | Data type | ||||||||||||
| targetReference | Reference(Composition | CompositionUvIps) | Data type | ||||||||||||
| event | Σ | 0..* | BackboneElement | Element idComposition.eventShort description The clinical service(s) being documented DefinitionThe main activity being described by a IPS is the provision of healthcare over a period of time. In the CDA representation of the IPS this is shown by setting the value of serviceEvent/@classCode to “PCPR” (care provision) and indicating the duration over which care was provided in serviceEvent/effectiveTime. In the FHIR representation at least one event should be used to record this information. Additional data from outside this duration may also be included if it is relevant to care provided during that time range (e.g., reviewed during the stated time range). For example if the IPS is generated by a GP based on information recorded in his/her EHR-S, then the start value should represent the date when the treatment relationship between the patient and the GP started; and the end value the date of the latest care event. Provides context for the composition and creates a linkage between a resource describing an event and the composition created describing the event. The event needs to be consistent with the type element, though can provide further information if desired. Unordered, Open, by code(Value) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| (All Slices) | The requirements in this element apply to all slices | |||||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.event.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.event.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.event.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idComposition.event.codeShort description Code(s) that apply to the event being documented DefinitionThis list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries. This list of codes represents the main clinical acts being documented. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| period | Σ C | 0..1 | Period | There are no (further) constraints on this element Element idComposition.event.periodShort description The period covered by the documentation DefinitionThe period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| detail | Σ C | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idComposition.event.detailShort description The event(s) being documented DefinitionThe description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| careProvisioningEvent | SO Σ | 0..1 | BackboneElement | Element idComposition.event:careProvisioningEventShort description The care provisioning being documented DefinitionThe provision of healthcare over a period of time this IPS is documenting. Provides context for the composition and creates a linkage between a resource describing an event and the composition created describing the event. The event needs to be consistent with the type element, though can provide further information if desired. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.event:careProvisioningEvent.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.event:careProvisioningEvent.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.event:careProvisioningEvent.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO Σ | 1..1 | CodeableConceptPattern | Element idComposition.event:careProvisioningEvent.codeShort description Code(s) that apply to the event being documented DefinitionThis list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries. This list of codes represents the main clinical acts being documented. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActClass",
"code": "PCPR"
}
]
}Mappings
| ||||||||||
| period | SO Σ C | 0..1 | Period | Element idComposition.event:careProvisioningEvent.periodShort description The period covered by the documentation DefinitionThe period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| detail | Σ C | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idComposition.event:careProvisioningEvent.detailShort description The event(s) being documented DefinitionThe description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section | SO C | 3..* | BackboneElement | Element idComposition.sectionShort description Sections composing the IPS DefinitionThe root of the sections that make up the IPS composition. Unordered, Open, by code(Value) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| (All Slices) | The requirements in this element apply to all slices | |||||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConcept | Element idComposition.section.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section.entryShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionProblems | SO C | 1..1 | BackboneElement | Element idComposition.section:sectionProblemsShort description IPS Problems Section DefinitionThe IPS problem section lists and describes clinical problems or conditions currently being monitored for the patient. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionProblems.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionProblems.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionProblems.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionProblems.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionProblems.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionProblems.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "11450-4"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionProblems.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionProblems.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionProblems.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionProblems.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionProblems.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(Condition | DocumentReference) | Element idComposition.section:sectionProblems.entryShort description Clinical problems or conditions currently being monitored for the patient. DefinitionIt lists and describes clinical problems or conditions currently being monitored for the patient. This entry shall be used to document that no information about problems is available, or that no relevant problems are known. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(Condition | DocumentReference) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| problem | SO C | 0..* | Reference(ConditionUvIps) | Element idComposition.section:sectionProblems.entry:problemShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | SO C | 0..1 | CodeableConceptBinding | Element idComposition.section:sectionProblems.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionProblems.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionAllergies | SO C | 1..1 | BackboneElement | Element idComposition.section:sectionAllergiesShort description IPS Allergies and Intolerances Section DefinitionThis section documents the relevant allergies or intolerances for that patient, describing the kind of reaction (e.g. rash, anaphylaxis,..); preferably the agents that cause it; and optionally the criticality and the certainty of the allergy. At a minimum, it should list currently active and any relevant historical allergies and adverse reactions. If no information about allergies is available, or if no allergies are known this should be clearly documented in the section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionAllergies.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionAllergies.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionAllergies.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionAllergies.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionAllergies.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionAllergies.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "48765-2"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionAllergies.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionAllergies.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionAllergies.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionAllergies.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionAllergies.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(AllergyIntolerance | DocumentReference) | Element idComposition.section:sectionAllergies.entryShort description Relevant allergies or intolerances for that patient. DefinitionIt lists the relevant allergies or intolerances for that patient, describing the kind of reaction (e.g. rash, anaphylaxis,..); preferably the agents that cause it; and optionally the criticality and the certainty of the allergy. At a minimum, it should list currently active and any relevant historical allergies and adverse reactions. This entry shall be used to document that no information about allergies is available, or that no allergies are known . If there are no entries in the list, an emptyReason SHOULD be provided. Reference(AllergyIntolerance | DocumentReference) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| allergyOrIntolerance | SO C | 0..* | Reference(AllergyIntoleranceUvIps) | Element idComposition.section:sectionAllergies.entry:allergyOrIntoleranceShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(AllergyIntoleranceUvIps) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | SO C | 0..1 | CodeableConceptBinding | Element idComposition.section:sectionAllergies.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionAllergies.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionMedications | SO C | 1..1 | BackboneElement | Element idComposition.section:sectionMedicationsShort description IPS Medication Summary Section DefinitionThe medication summary section contains a description of the patient's medications relevant for the scope of the patient summary. The actual content could depend on the jurisdiction, it could report:
In those cases medications are documented in the Patient Summary as medication statements or medication requests. This section requires either an entry indicating the subject is known not to be on any relevant medication; either an entry indicating that no information is available about medications; or entries summarizing the subject's relevant medications. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionMedications.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionMedications.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionMedications.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionMedications.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionMedications.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionMedications.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "10160-0"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionMedications.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionMedications.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionMedications.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionMedications.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionMedications.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(DocumentReference | MedicationAdministration | MedicationDispense | MedicationRequest | MedicationStatement) | Element idComposition.section:sectionMedications.entryShort description Medications relevant for the scope of the patient summary DefinitionThis list the medications relevant for the scope of the patient summary or it is used to indicate that the subject is known not to be on any relevant medication; either that no information is available about medications. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DocumentReference | MedicationAdministration | MedicationDispense | MedicationRequest | MedicationStatement) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| medicationStatementOrRequest | SO C | 0..* | Reference(MedicationRequestIPS | MedicationStatementIPS) | Element idComposition.section:sectionMedications.entry:medicationStatementOrRequestShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(MedicationRequestIPS | MedicationStatementIPS) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | SO C | 0..1 | CodeableConceptBinding | Element idComposition.section:sectionMedications.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionMedications.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionImmunizations | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionImmunizationsShort description IPS Immunizations Section DefinitionThe Immunizations Section defines a patient's current immunization status and pertinent immunization history. The primary use case for the Immunization Section is to enable communication of a patient's immunization status. The section includes the current immunization status, and may contain the entire immunization history that is relevant to the period of time being summarized. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionImmunizations.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionImmunizations.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionImmunizations.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionImmunizations.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionImmunizations.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionImmunizations.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "11369-6"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionImmunizations.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionImmunizations.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionImmunizations.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionImmunizations.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionImmunizations.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(DocumentReference | Immunization) | Element idComposition.section:sectionImmunizations.entryShort description Patient's immunization status and pertinent history. DefinitionIt defines the patient's current immunization status and pertinent immunization history. The primary use case for the Immunization Section is to enable communication of a patient's immunization status. It may contain the entire immunization history that is relevant to the period of time being summarized. This entry shall be used to document that no information about immunizations is available, or that no immunizations are known. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DocumentReference | Immunization) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| immunization | SO C | 0..* | Reference(ImmunizationUvIps) | Element idComposition.section:sectionImmunizations.entry:immunizationShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionImmunizations.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionImmunizations.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionResults | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionResultsShort description IPS Results Section DefinitionThis section assembles relevant observation results collected on the patient or produced on in-vitro biologic specimens collected from the patient. Some of these results may be laboratory results, others may be anatomic pathology results, others, radiology results, and others, clinical results. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionResults.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionResults.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionResults.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionResults.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionResults.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionResults.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "30954-2"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionResults.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionResults.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionResults.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionResults.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionResults.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(DiagnosticReport | DocumentReference | Observation) | Element idComposition.section:sectionResults.entryShort description Relevant observation results collected on the patient or produced on in-vitro biologic specimens collected from the patient. DefinitionRelevant observation results collected on the patient or produced on in-vitro biologic specimens collected from the patient. Some of these results may be laboratory results, others may be anatomic pathology results, others, radiology results, and others, clinical results. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DiagnosticReport | DocumentReference | Observation) SlicingUnordered, Open, by resolve()(Type), resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| results-observation-laboratory-pathology | SO C | 0..* | Reference(ObservationResultsLaboratoryPathologyUvIps) | Element idComposition.section:sectionResults.entry:results-observation-laboratory-pathologyShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(ObservationResultsLaboratoryPathologyUvIps) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| results-observation-radiology | SO C | 0..* | Reference(ObservationResultsRadiologyUvIps) | Element idComposition.section:sectionResults.entry:results-observation-radiologyShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(ObservationResultsRadiologyUvIps) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| results-diagnosticReport | SO C | 0..* | Reference(DiagnosticReportUvIps) | Element idComposition.section:sectionResults.entry:results-diagnosticReportShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DiagnosticReportUvIps) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionResults.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionResults.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionProceduresHx | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionProceduresHxShort description IPS History of Procedures Section DefinitionThe History of Procedures Section contains a description of the patient past procedures that are pertinent to the scope of this document. Procedures may refer for example to:
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionProceduresHx.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionProceduresHx.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionProceduresHx.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionProceduresHx.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionProceduresHx.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionProceduresHx.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "47519-4"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionProceduresHx.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionProceduresHx.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionProceduresHx.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionProceduresHx.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionProceduresHx.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(DocumentReference | Procedure) | Element idComposition.section:sectionProceduresHx.entryShort description Patient past procedures pertinent to the scope of this document. DefinitionIt lists the patient past procedures that are pertinent to the scope of this document. Procedures may refer for example to:
If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DocumentReference | Procedure) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| procedure | SO C | 0..* | Reference(ProcedureUvIps) | Element idComposition.section:sectionProceduresHx.entry:procedureShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionProceduresHx.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionProceduresHx.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionMedicalDevices | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionMedicalDevicesShort description IPS Medical Devices Section DefinitionThe medical devices section contains narrative text and coded entries describing the patient history of medical device use. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionMedicalDevices.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionMedicalDevices.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionMedicalDevices.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionMedicalDevices.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionMedicalDevices.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionMedicalDevices.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "46264-8"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionMedicalDevices.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionMedicalDevices.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionMedicalDevices.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionMedicalDevices.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionMedicalDevices.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(DeviceUseStatement | DocumentReference) | Element idComposition.section:sectionMedicalDevices.entryShort description Patient history of medical device use. DefinitionIt describes the patient history of medical device use. This entry shall be used to document that no information about medical device use is available, or that no relevant medical device use is known. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DeviceUseStatement | DocumentReference) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| deviceStatement | SO C | 0..* | Reference(DeviceUseStatementUvIps) | Element idComposition.section:sectionMedicalDevices.entry:deviceStatementShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DeviceUseStatementUvIps) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionMedicalDevices.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionMedicalDevices.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionAdvanceDirectives | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionAdvanceDirectivesShort description IPS Advance Directives Section DefinitionThe advance directives section contains a narrative description of patient's advance directive. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionAdvanceDirectives.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionAdvanceDirectives.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionAdvanceDirectives.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionAdvanceDirectives.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionAdvanceDirectives.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionAdvanceDirectives.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "42348-3"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionAdvanceDirectives.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionAdvanceDirectives.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionAdvanceDirectives.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionAdvanceDirectives.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionAdvanceDirectives.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(Consent | DocumentReference) | Element idComposition.section:sectionAdvanceDirectives.entryShort description Narrative description of the patient's advance directive. DefinitionContains a narrative description or a Consent entry with information about the patient's advance directive. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(Consent | DocumentReference) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| advanceDirectivesConsent | C | 0..* | Reference(Consent) | Element idComposition.section:sectionAdvanceDirectives.entry:advanceDirectivesConsentShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionAdvanceDirectives.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionAdvanceDirectives.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionAlerts | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionAlertsShort description IPS Alerts Section DefinitionThe alerts section flags potential concerns and/or dangers to/from the patient and may also include obstacles to care. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionAlerts.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionAlerts.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionAlerts.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionAlerts.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionAlerts.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionAlerts.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "104605-1"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionAlerts.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionAlerts.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionAlerts.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionAlerts.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionAlerts.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(DocumentReference | Flag) | Element idComposition.section:sectionAlerts.entryShort description Alert information. DefinitionContains alert information to be communicated. May optionally reference other resources in IPS. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DocumentReference | Flag) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| alertsFlag | C | 0..* | Reference(FlagAlertUvIps) | Element idComposition.section:sectionAlerts.entry:alertsFlagShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionAlerts.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionAlerts.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionFunctionalStatus | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionFunctionalStatusShort description IPS Functional Status DefinitionThe functional status section shall contain a narrative description of capability of the patient to perform acts of daily living, including possible needs of the patient to be continuously assessed by third parties. The invalidity status may in fact influence decisions about how to administer treatments. Profiles to express disabilities and functional assessments will be specified by future versions of this guide. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionFunctionalStatus.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionFunctionalStatus.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionFunctionalStatus.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionFunctionalStatus.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionFunctionalStatus.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionFunctionalStatus.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "47420-5"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionFunctionalStatus.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionFunctionalStatus.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionFunctionalStatus.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionFunctionalStatus.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionFunctionalStatus.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(ClinicalImpression | Condition | DocumentReference) | Element idComposition.section:sectionFunctionalStatus.entryShort description Optional entry used to represent disabilities and functional assessments DefinitionIt describes capabilities of the patient to perform acts of daily living, including possible needs of the patient to be continuously assessed by third parties. The invalidity status may in fact influence decisions about how to administer treatments. Profiles to express disabilities and functional assessments will be specified by future versions of this guide. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(ClinicalImpression | Condition | DocumentReference) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| disability | C | 0..* | Reference(ConditionUvIps) | Element idComposition.section:sectionFunctionalStatus.entry:disabilityShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| functionalAssessment | C | 0..* | Reference(ClinicalImpression) | Element idComposition.section:sectionFunctionalStatus.entry:functionalAssessmentShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionFunctionalStatus.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionFunctionalStatus.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionPastProblems | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionPastProblemsShort description IPS History of Past Problems Section DefinitionThe History of Past Problems section contains a description of the conditions the patient suffered in the past but no longer tracked in the Problem List. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionPastProblems.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionPastProblems.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionPastProblems.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionPastProblems.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionPastProblems.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionPastProblems.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "11348-0"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionPastProblems.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionPastProblems.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionPastProblems.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionPastProblems.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionPastProblems.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(Condition | DocumentReference) | Element idComposition.section:sectionPastProblems.entryShort description Conditions the patient suffered in the past. DefinitionIt contains a description of the conditions the patient suffered in the past. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(Condition | DocumentReference) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| pastProblem | C | 0..* | Reference(ConditionUvIps) | Element idComposition.section:sectionPastProblems.entry:pastProblemShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionPastProblems.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionPastProblems.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionPregnancyHx | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionPregnancyHxShort description IPS History of Pregnancy Section DefinitionThe history of pregnancy section shall contain information about whether the patient is currently pregnant or not. It may contain addition summarizing information about the outcome of earlier pregnancies. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionPregnancyHx.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionPregnancyHx.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionPregnancyHx.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionPregnancyHx.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionPregnancyHx.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionPregnancyHx.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "10162-6"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionPregnancyHx.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionPregnancyHx.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionPregnancyHx.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionPregnancyHx.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionPregnancyHx.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(DocumentReference | Observation) | Element idComposition.section:sectionPregnancyHx.entryShort description Current pregnancy status and, optionally, information about the outcome of earlier pregnancies. DefinitionIt contains information about whether the patient is currently pregnant or not. It may contain addition summarizing information about the outcome of earlier pregnancies. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DocumentReference | Observation) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| pregnancyStatus | C | 0..* | Reference(ObservationPregnancyStatusUvIps) | Element idComposition.section:sectionPregnancyHx.entry:pregnancyStatusShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(ObservationPregnancyStatusUvIps) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| pregnancyOutcome | C | 0..* | Reference(ObservationPregnancyOutcomeUvIps) | Element idComposition.section:sectionPregnancyHx.entry:pregnancyOutcomeShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(ObservationPregnancyOutcomeUvIps) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionPregnancyHx.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionPregnancyHx.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionPatientStory | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionPatientStoryShort description IPS Patient Story Section DefinitionThe section contains narrative text along with optional resources that express what matters to a patient. This may include needs, strengths, values, concerns and preferences to others providing support and care. The patient’s story, provided here, may be told by the patient or by a proxy. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionPatientStory.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionPatientStory.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionPatientStory.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionPatientStory.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionPatientStory.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionPatientStory.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "81338-6"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionPatientStory.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionPatientStory.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionPatientStory.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionPatientStory.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionPatientStory.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(Resource) | Element idComposition.section:sectionPatientStory.entryShort description Patient Story resources. DefinitionContains resources to support the Patient Story. Instances of DocumentReference or any other suitable resource type may be used. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionPatientStory.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionPatientStory.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionPlanOfCare | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionPlanOfCareShort description IPS Plan of Care Section DefinitionThe plan of care section contains a narrative description of the expectations for care including proposals, goals, and order requests for monitoring, tracking, or improving the condition of the patient. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionPlanOfCare.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionPlanOfCare.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionPlanOfCare.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionPlanOfCare.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionPlanOfCare.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionPlanOfCare.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "18776-5"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionPlanOfCare.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionPlanOfCare.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionPlanOfCare.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionPlanOfCare.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionPlanOfCare.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(CarePlan | DocumentReference | ImmunizationRecommendation) | Element idComposition.section:sectionPlanOfCare.entryShort description Optional entry used to represent structured care plans DefinitionDynamic, personalized plan including identified needed healthcare activity, health objectives and healthcare goals, relating to one or more specified health issues in a healthcare process [Source EN ISO 13940] If there are no entries in the list, an emptyReason SHOULD be provided. Reference(CarePlan | DocumentReference | ImmunizationRecommendation) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| carePlan | C | 0..* | Reference(CarePlan) | Element idComposition.section:sectionPlanOfCare.entry:carePlanShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| immunizationRecommendation | C | 0..* | Reference(ImmunizationRecommendation) | Element idComposition.section:sectionPlanOfCare.entry:immunizationRecommendationShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(ImmunizationRecommendation) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionPlanOfCare.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionPlanOfCare.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionSocialHistory | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionSocialHistoryShort description IPS Social History Section DefinitionThe social history section contains a description of the person’s Health related "lifestyle factors" or "lifestyle observations" (e.g. smoke habits; alcohol consumption; diets, risky habits.) The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionSocialHistory.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionSocialHistory.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionSocialHistory.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionSocialHistory.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionSocialHistory.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionSocialHistory.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "29762-2"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionSocialHistory.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionSocialHistory.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionSocialHistory.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionSocialHistory.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionSocialHistory.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(DocumentReference | Observation) | Element idComposition.section:sectionSocialHistory.entryShort description Health related "lifestyle factors" or "lifestyle observations" (e.g. smoke habits; alcohol consumption; diets, risky habits.) DefinitionDescription of the person’s Health related “lifestyle factors" or "lifestyle observations" (e.g. smoke habits; alcohol consumption; diets, risky habits.) If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DocumentReference | Observation) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| smokingTobaccoUse | C | 0..1 | Reference(ObservationTobaccoUseUvIps) | Element idComposition.section:sectionSocialHistory.entry:smokingTobaccoUseShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(ObservationTobaccoUseUvIps) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| alcoholUse | C | 0..1 | Reference(ObservationAlcoholUseUvIps) | Element idComposition.section:sectionSocialHistory.entry:alcoholUseShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(ObservationAlcoholUseUvIps) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionSocialHistory.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionSocialHistory.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
| ||||||||||
| sectionVitalSigns | SO C | 0..1 | BackboneElement | Element idComposition.section:sectionVitalSignsShort description IPS Vital Signs Section DefinitionThe Vital signs section includes blood pressure, body temperature, heart rate, and respiratory rate. It may also include other clinical findings, such as height, weight, body mass index, head circumference, and pulse oximetry. In particular, notable vital signs or physical findings such as the most recent, maximum and/or minimum, baseline, or relevant trends may be included The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sectionVitalSigns.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||||||||||
| extension | C | 0..* | Extension | Element idComposition.section:sectionVitalSigns.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| section-note | C | 0..* | Extension | Element idComposition.section:sectionVitalSigns.extension:section-noteShort description Additional notes that apply to the section (but not to specific resource). Alternate namesextensions, user content DefinitionAdditional notes that apply to the section (but not to specific resource). This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element http://hl7.org/fhir/StructureDefinition/note|5.3.0-ballot-tc1 ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sectionVitalSigns.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| title | SO | 1..1 | string | Element idComposition.section:sectionVitalSigns.titleShort description Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| code | SO | 1..1 | CodeableConceptPattern | Element idComposition.section:sectionVitalSigns.codeShort description Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Classification of a section of a composition/document. DocumentSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
{
"coding": [
{
"system": "http://loinc.org",
"code": "8716-3"
}
]
}Mappings
| ||||||||||
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idComposition.section:sectionVitalSigns.authorShort description Who and/or what authored the section DefinitionIdentifies who is responsible for the information in this section, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| focus | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sectionVitalSigns.focusShort description Who/what the section is about, when it is not about the subject of composition DefinitionThe actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||||||||
| text | SO C | 1..1 | Narrative | Element idComposition.section:sectionVitalSigns.textShort description Text summary of the section, for human interpretation DefinitionA human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 Constraints
| ||||||||||
| mode | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sectionVitalSigns.modeShort description working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be misunderstood as a complete list. The processing mode that applies to this section. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionVitalSigns.orderedByShort description Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. What order applies to the items in the entry. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||||||||||
| entry | C | 0..* | Reference(DocumentReference | Observation) | Element idComposition.section:sectionVitalSigns.entryShort description Notable vital signs or physical findings. DefinitionNotable vital signs or physical findings as: blood pressure, body temperature, heart rate, and respiratory rate. It may also include other clinical findings, such as height, weight, body mass index, head circumference, and pulse oximetry. In particular, notable vital signs or physical findings such as the most recent, maximum and/or minimum, baseline, or relevant trends may be included If there are no entries in the list, an emptyReason SHOULD be provided. Reference(DocumentReference | Observation) SlicingUnordered, Open, by resolve()(Profile) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| vitalSign | C | 0..* | Reference(observation-vitalsigns) | Element idComposition.section:sectionVitalSigns.entry:vitalSignShort description A reference to data that supports this section DefinitionA reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided. Reference(observation-vitalsigns) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| emptyReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sectionVitalSigns.emptyReasonShort description Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. If a section is empty, why it is empty. The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 Constraints
| ||||||||||
| section | C | 0..0 | see (section) | There are no (further) constraints on this element Element idComposition.section:sectionVitalSigns.sectionShort description Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. The cardinality or value of this element may be affected by these constraints: cmp-1 Mappings
|
Sample IPS Bundle
Design Principles
most slicing is open, meaning predefined slices guide expected data structures but additional elements or profiles not explicitly defined can still be included as long as overall profile constraints are met.
human-readable narrative in every Composition section to ensure patient safety, legal attestation, and reliable understanding during cross-border exchange—even when structured data or language translations cannot be fully processed by receiving systems.
Composition sections may be empty, but required sections must state why data is missing using
emptyReason(populated using ListEmptyReasons or an explicit “no information available” clinical statement, while all included sections must still provide human-readable narrative text.IPS documents are generated as FHIR Bundles and can be accessed either via a
$summaryoperation on the Patient resource for on-demand summary Bundles, or via a$docrefoperation on DocumentReference to create and retrieve persisted IPS Bundles; future guides may provide additional generation methods.IPS documents support cross-border and lifetime patient care, but only current and relevant data—especially allergies, medications, and problems—are required, while other historical data may be selectively included based on clinical relevance.
IPS creation can leverage FHIR
Resource.meta.securitytags to identify and exclude highly sensitive or restricted health data based on patient consent or system policies, ensuring privacy while sharing summaries with authorized recipients.
Future Development
Explore the adoption of the Provenance resource with the IPS (bundle level, composition level, or entry level) to document the IPS curation as documented in the first known issue above (see also the "International Patient Summary: Use Cases" Confluence page)
Include additional guidance or references on approaches for selecting appropriate summary content, documenting algorithmic vs. human curation of data, and generating narrative representations. A draft page on the various Methods for IPS generation has been drafted on HL7 Confluence and may be a consideration for future version of this IPS FHIR Implementation Guide.
Gather feedback on the IPS $summary operation introduced in STU1.1 of this guide.
Gather feedback on how Provenance could be used in IPS FHIR-40610
Loosen Observation profile for alcohol usage FHIR-40802
Provide IPS viewing requirements FHIR-41630
Remove identifying information requirements in IPS FHIR-43721
Check value Set OID alignment between FHIR and CDA IPS IGs FHIR-46169
Add NutritionIntake Observation profile in Social History FHIR-46923
Add Patient Travel History FHIR-47930
Add NUVA as additional vaccine binding FHIR-49146
Add 'disability' to ValueSet: Problem Type - IPS FHIR-49218
Add CarePlan (IPS) Profile, based on ISO 27269 FHIR-49905
Guidance on laterality in IPS FHIR-50042
Add a CareTeam section, and describe how to use it for patient advocate / legal power of attorney FHIR-50098
Include more detail in section about identifier usage FHIR-51507
Clarify intent and possible rules for separation between Current and Past problems FHIR-51511