Exportobjekt (Bundle)
Die App bietet Patient die Möglichkeit Daten maschienenlesbar als JSON-Datei zu exportieren. Diese Datei enthält ein Bundle vom Typ collection; FHIR-Bundle (http://hl7.org/fhir/StructureDefinition/Bundle). Das Bundle enthält als ersten Eintrag ein Patientenprofil (http://hl7.org/fhir/StructureDefinition/Patient). Weiter werden Beobachtungsdaten in Form von Observations exportiert; FHIR-Observation (http://hl7.org/fhir/StructureDefinition/Observation). Die enthaltenen Ressourcen werden im Folgenden näher beschrieben.
FHIR-Profil (Bundle)
Bundle | I | http://hl7.org/fhir/StructureDefinition/Resource | Element idBundle Contains a collection of resources DefinitionA container for a collection of resources. http://hl7.org/fhir/StructureDefinition/Resource Constraints
| |
id | Σ | 0..1 | id | There are no (further) constraints on this element Element idBundle.id 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. id |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idBundle.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. Meta |
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idBundle.implicitRules 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. 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. uri |
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idBundle.language 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). code BindingA human language. ?? (extensible) | |
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idBundle.identifier Persistent identifier for the bundle DefinitionA persistent identifier for the batch that won't change as a batch 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. Identifier Mappings
|
type | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idBundle.type document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection DefinitionIndicates the purpose of this bundle - how it was 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. code BindingIndicates the purpose of a bundle - how it was intended to be used. ?? (required)Mappings
|
total | Σ I | 0..1 | unsignedInt | There are no (further) constraints on this element Element idBundle.total If search, the total number of matches DefinitionIf a set of search matches, this is the total number of matches for the search (as opposed to the number of results in this 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. unsignedInt |
link | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.link Links related to this Bundle DefinitionA series of links that provide context to this bundle. BackboneElement |
entry | Σ I | 0..* | BackboneElement | There are no (further) constraints on this element Element idBundle.entry 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). BackboneElement Constraints
|
signature | Σ | 0..1 | Signature | There are no (further) constraints on this element Element idBundle.signature Digital Signature DefinitionDigital Signature - base64 encoded. XML-DSIg or a JWT. This element allows capturing signatures on documents. It also allows signatures on messages, transactions or even query responses. It may 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. Signature |