Implementierungsleitfaden ISiK-Medikation

ISiK Medikation TransactionBundle-Response

Hinweis: Die Regeln aus dem Modul ISiK Basis Stufe 4 für die Verarbeitung Document-Bundles, treffen hier nicht zu, da es sich um den Bundle-Typ Transaction handelt.

Dieses Profil definiert die Server-Antwort auf Transaktions-Bundles im Rahmen von ISiK-Medikations-Szenarien.

Metadaten

Canonical	https://gematik.de/fhir/isik/StructureDefinition/ISiKMedikationTransactionResponse
Status	active
Version	4.0.3
Basis	http://hl7.org/fhir/StructureDefinition/Bundle

Inhalt

ISiKMedikationTransactionResponse (Bundle)	I		Bundle	There are no (further) constraints on this element Element id Bundle Short description Contains a collection of resources Definition A container for a collection of resources. Data type Bundle Constraints bdl-1: total only when a search or history `total.empty() or (type = 'searchset') or (type = 'history')` bdl-2: entry.search only when a search `entry.search.empty() or (type = 'searchset')` bdl-3: entry.request mandatory for batch/transaction/history, otherwise prohibited `entry.all(request.exists() = (%resource.type = 'batch' or %resource.type = 'transaction' or %resource.type = 'history'))` bdl-4: entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited `entry.all(response.exists() = (%resource.type = 'batch-response' or %resource.type = 'transaction-response' or %resource.type = 'history'))` bdl-7: FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles) `(type = 'history') or entry.where(fullUrl.exists()).select(fullUrl&resource.meta.versionId).isDistinct()` bdl-9: A document must have an identifier with a system and a value `type = 'document' implies (identifier.system.exists() and identifier.value.exists())` bdl-10: A document must have a date `type = 'document' implies (timestamp.hasValue())` bdl-11: A document must have a Composition as the first resource `type = 'document' implies entry.first().resource.is(Composition)` bdl-12: A message must have a MessageHeader as the first resource `type = 'message' implies entry.first().resource.is(MessageHeader)` Mappings rim: Entity. Role, or Act v2: N/A rim: N/A cda: ClinicalDocument, if bundle.type = document
id	Σ	0..1	string	There are no (further) constraints on this element Element id Bundle.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type string
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id Bundle.meta Short description Metadata about the resource Definition The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. Data type Meta Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id Bundle.implicitRules Short description A set of rules under which this content was created Definition A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Comments Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
language		0..1	codeBinding	There are no (further) constraints on this element Element id Bundle.language Short description Language of the resource content Definition The base language in which the resource is written. Comments Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). Data type code Binding A human language. CommonLanguages (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id Bundle.identifier Short description Persistent identifier for the bundle Definition A persistent identifier for the bundle that won't change as a bundle is copied from server to server. Comments Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.identifier cda: ClinicalDocument.id
type	S Σ	1..1	codeBindingFixed Value	Element id Bundle.type Short description Type des Bundles Definition Indicates the purpose of this bundle - how it is intended to be used. Comments fix: transaction-response Data type code Binding Indicates the purpose of a bundle - how it is intended to be used. BundleType (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Fixed value transaction-response Mappings w5: FiveWs.class
timestamp	Σ	0..1	instant	There are no (further) constraints on this element Element id Bundle.timestamp Short description When the bundle was assembled Definition The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. Comments For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated. Usage: document : the date the document was created. Note: the composition may predate the document, or be associated with multiple documents. The date of the composition - the authoring time - may be earlier than the document assembly time message : the date that the content of the message was assembled. This date is not changed by middleware engines unless they add additional data that changes the meaning of the time of the message history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates searchset : the time that the search set was assembled. Note that different pages MAY have different timestamps but need not. Having different timestamps does not imply that subsequent pages will represent or include changes made since the initial query transaction \| transaction-response \| batch \| batch-response \| collection : no particular assigned meaning The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself. Data type instant Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.init cda: ClinicalDocument.effectiveTime
total	Σ I	0..1	unsignedInt	There are no (further) constraints on this element Element id Bundle.total Short description If search, the total number of matches Definition If 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. Comments Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources. Data type unsignedInt Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
link	Σ	0..*	BackboneElement	There are no (further) constraints on this element Element id Bundle.link Short description Links related to this Bundle Definition A series of links that provide context to this bundle. Comments Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS). Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was read directly. This specification defines some specific uses of Bundle.link for searching and paging, but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
id		0..1	string	There are no (further) constraints on this element Element id Bundle.link.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Bundle.link.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Bundle.link.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and 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). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A
relation	Σ	1..1	string	There are no (further) constraints on this element Element id Bundle.link.relation Short description See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 Definition A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
url	Σ	1..1	uri	There are no (further) constraints on this element Element id Bundle.link.url Short description Reference details for the link Definition The reference details for the link. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
entry	S Σ I	1..*	BackboneElement	Element id Bundle.entry Short description Der einzelne Eintrag zur Interaktion Definition An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). Data type BackboneElement Constraints bdl-5: must be a resource unless there's a request or response `resource.exists() or request.exists() or response.exists()` bdl-8: fullUrl cannot be a version specific reference `fullUrl.contains('/_history/').not()` ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
id		0..1	string	There are no (further) constraints on this element Element id Bundle.entry.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Bundle.entry.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Bundle.entry.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and 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). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A
link	Σ	0..0	see (link)	There are no (further) constraints on this element Element id Bundle.entry.link Short description Links related to this entry Definition A series of links that provide context to this entry. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
fullUrl	S Σ	0..1	uri	Element id Bundle.entry.fullUrl Short description vollständige URL der Ressource Definition The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that: fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle) Results from operations might involve resources that are not identified. Comments fullUrl might not be unique in the context of a resource. Note that since FHIR resources do not need to be served through the FHIR API, the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the regex, then the 'id' portion of the fullUrl SHALL end with the Resource.id. Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL). Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
resource	S Σ	0..1	Resource	Element id Bundle.entry.resource Short description Die Ressourcen-Instanz der Interaktion Definition The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. Data type Resource
search	Σ I	0..0	BackboneElement	There are no (further) constraints on this element Element id Bundle.entry.search Short description Search related information Definition Information about the search process that lead to the creation of this entry. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
request	Σ I	0..0	BackboneElement	There are no (further) constraints on this element Element id Bundle.entry.request Short description Additional execution information (transaction/batch/history) Definition Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
response	S Σ I	1..1	BackboneElement	Element id Bundle.entry.response Short description HTTP-Response des Servers innerhalb der Transaktions-Antwort Definition Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
id		0..1	string	There are no (further) constraints on this element Element id Bundle.entry.response.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Bundle.entry.response.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Bundle.entry.response.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and 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). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A
status	S Σ	1..1	string	Element id Bundle.entry.response.status Short description HTTP-Statuscode Definition The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
location	S Σ	0..1	uri	Element id Bundle.entry.response.location Short description Location der Ressource (URL) auf dem Server Definition The location header created by processing this operation, populated if the operation returns a location. Comments Gemäß FHIR-Spezifikation MUSS hier der Pfad zur exakten Version (History) enthalten sein, wenn der Server History unterstützt. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
etag	Σ	0..1	string	There are no (further) constraints on this element Element id Bundle.entry.response.etag Short description The Etag for the resource (if relevant) Definition The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). Comments Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
lastModified	Σ	0..1	instant	There are no (further) constraints on this element Element id Bundle.entry.response.lastModified Short description Server's date time modified Definition The date/time that the resource was modified on the server. Comments This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. Data type instant Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
outcome	S Σ	0..1	Resource	Element id Bundle.entry.response.outcome Short description OperationOutcome-Ressource zur Rückgabe von Fehler-Details sowie Informationen. Definition An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. Comments For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned. This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error. Data type Resource
signature	Σ	0..1	Signature	There are no (further) constraints on this element Element id Bundle.signature Short description Digital Signature Definition Digital Signature - base64 encoded. XML-DSig or a JWT. Requirements A Signature holds an electronic representation of a signature and its supporting context in a FHIR accessible form. The signature may either be a cryptographic type (XML DigSig or a JWS), which is able to provide non-repudiation proof, or it may be a graphical image that represents a signature or a signature process. This element allows capturing signatures on documents, messages, transactions or even search responses, to support content-authentication, non-repudiation or other business cases. This is primarily relevant where the bundle may travel through multiple hops or via other mechanisms where HTTPS non-repudiation is insufficient. Comments The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific. Data type Signature Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`

<StructureDefinition xmlns="http://hl7.org/fhir">
    <id value="ISiKMedikationTransactionResponse" />
    <url value="https://gematik.de/fhir/isik/StructureDefinition/ISiKMedikationTransactionResponse" />
    <version value="4.0.3" />
    <name value="ISiKMedikationTransactionResponse" />
    <title value="ISiK Medikation TransactionBundle-Response" />
    <status value="active" />
    <experimental value="false" />
    <date value="2025-03-17" />
    <publisher value="gematik GmbH" />
    <description value="Dieses Profil definiert die Server-Antwort auf Transaktions-Bundles im Rahmen von ISiK-Medikations-Szenarien." />
    <fhirVersion value="4.0.1" />
    <kind value="resource" />
    <abstract value="false" />
    <type value="Bundle" />
    <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Bundle" />
    <derivation value="constraint" />
    <differential>
        <element id="Bundle.type">
            <path value="Bundle.type" />
            <short value="Type des Bundles" />
            <comment value="fix: transaction-response" />
            <fixedCode value="transaction-response" />
            <mustSupport value="true" />
        </element>
        <element id="Bundle.entry">
            <path value="Bundle.entry" />
            <short value="Der einzelne Eintrag zur Interaktion" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Bundle.entry.link">
            <path value="Bundle.entry.link" />
            <max value="0" />
        </element>
        <element id="Bundle.entry.fullUrl">
            <path value="Bundle.entry.fullUrl" />
            <short value="vollst&#228;ndige URL der Ressource" />
            <mustSupport value="true" />
        </element>
        <element id="Bundle.entry.resource">
            <path value="Bundle.entry.resource" />
            <short value="Die Ressourcen-Instanz der Interaktion" />
            <mustSupport value="true" />
        </element>
        <element id="Bundle.entry.search">
            <path value="Bundle.entry.search" />
            <max value="0" />
        </element>
        <element id="Bundle.entry.request">
            <path value="Bundle.entry.request" />
            <max value="0" />
        </element>
        <element id="Bundle.entry.response">
            <path value="Bundle.entry.response" />
            <short value="HTTP-Response des Servers innerhalb der Transaktions-Antwort" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Bundle.entry.response.status">
            <path value="Bundle.entry.response.status" />
            <short value="HTTP-Statuscode" />
            <mustSupport value="true" />
        </element>
        <element id="Bundle.entry.response.location">
            <path value="Bundle.entry.response.location" />
            <short value="Location der Ressource (URL) auf dem Server" />
            <comment value="Gem&#228;&#223; FHIR-Spezifikation MUSS hier der Pfad zur exakten Version (History) enthalten sein, wenn der Server History unterst&#252;tzt." />
            <mustSupport value="true" />
        </element>
        <element id="Bundle.entry.response.outcome">
            <path value="Bundle.entry.response.outcome" />
            <short value="OperationOutcome-Ressource zur R&#252;ckgabe von Fehler-Details sowie Informationen." />
            <mustSupport value="true" />
        </element>
    </differential>
</StructureDefinition>

{
    "resourceType": "StructureDefinition",
    "id": "ISiKMedikationTransactionResponse",
    "url": "https://gematik.de/fhir/isik/StructureDefinition/ISiKMedikationTransactionResponse",
    "version": "4.0.3",
    "name": "ISiKMedikationTransactionResponse",
    "title": "ISiK Medikation TransactionBundle-Response",
    "status": "active",
    "experimental": false,
    "date": "2025-03-17",
    "publisher": "gematik GmbH",
    "description": "Dieses Profil definiert die Server-Antwort auf Transaktions-Bundles im Rahmen von ISiK-Medikations-Szenarien.",
    "fhirVersion": "4.0.1",
    "kind": "resource",
    "abstract": false,
    "type": "Bundle",
    "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Bundle",
    "derivation": "constraint",
    "differential": {
        "element":  [
            {
                "id": "Bundle.type",
                "path": "Bundle.type",
                "short": "Type des Bundles",
                "comment": "fix: transaction-response",
                "fixedCode": "transaction-response",
                "mustSupport": true
            },
            {
                "id": "Bundle.entry",
                "path": "Bundle.entry",
                "short": "Der einzelne Eintrag zur Interaktion",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Bundle.entry.link",
                "path": "Bundle.entry.link",
                "max": "0"
            },
            {
                "id": "Bundle.entry.fullUrl",
                "path": "Bundle.entry.fullUrl",
                "short": "vollständige URL der Ressource",
                "mustSupport": true
            },
            {
                "id": "Bundle.entry.resource",
                "path": "Bundle.entry.resource",
                "short": "Die Ressourcen-Instanz der Interaktion",
                "mustSupport": true
            },
            {
                "id": "Bundle.entry.search",
                "path": "Bundle.entry.search",
                "max": "0"
            },
            {
                "id": "Bundle.entry.request",
                "path": "Bundle.entry.request",
                "max": "0"
            },
            {
                "id": "Bundle.entry.response",
                "path": "Bundle.entry.response",
                "short": "HTTP-Response des Servers innerhalb der Transaktions-Antwort",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Bundle.entry.response.status",
                "path": "Bundle.entry.response.status",
                "short": "HTTP-Statuscode",
                "mustSupport": true
            },
            {
                "id": "Bundle.entry.response.location",
                "path": "Bundle.entry.response.location",
                "short": "Location der Ressource (URL) auf dem Server",
                "comment": "Gemäß FHIR-Spezifikation MUSS hier der Pfad zur exakten Version (History) enthalten sein, wenn der Server History unterstützt.",
                "mustSupport": true
            },
            {
                "id": "Bundle.entry.response.outcome",
                "path": "Bundle.entry.response.outcome",
                "short": "OperationOutcome-Ressource zur Rückgabe von Fehler-Details sowie Informationen.",
                "mustSupport": true
            }
        ]
    }
}

ISiK Medikation TransactionBundle-Response

Constraints/Invarianten

Terminology-Bindings

Interaktionen

TransactionResponse-Bundles werden nicht persistiert, sondern ausschließlich im Kontext von FHIR-Transaktionen verwendet, vgl. FHIR RESTful API - Batch/Transaction.