Implementierungsleitfaden ISiK-Basismodul (4.0.1)

Subscription patient-merge (R5 Backport Subscription)

Patient Merge Subscription

Motivation

Subscription ist eine FHIR Ressource, um als Client-System Benachrichtigungen über Events auf dem FHIR Server anzufragen. Der Subscription Mechanismus in FHIR R4 ist nicht geeignet, um alle relevanten Events (hier im Speziellen das Mergen von Patienten) zu unterstützen. Daher basiert das ISiK Subscription-Profil auf dem Subscriptions R5 Backport Profil von HL7.

Siehe auch: Use Case Patient-merge

Um als Subsystem über ein Patienten-Merge-Event informiert zu werden, KANN der FHIR Subscription Mechanismus gemäß des Subscriptions R5 Backport IGs von HL7 genutzt werden.

Kompatibilität

Das Profil PatientMergeSubscription basiert auf dem Backport-Subscription Profil.
Der SubscriptionStatus, sowie das Subscription Notification Bundle werden unverändert direkt aus dem Subscriptions R5 Backport IG genutzt.

Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden.

Metadaten

Canonical	https://gematik.de/fhir/isik/StructureDefinition/patient-merge-subscription
Status	active
Version	4.0.1
Basis	http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription

Inhalt

PatientMergeSubscription (Subscription)	I			There are no (further) constraints on this element Element id Subscription Short description Server push subscription criteria Alternate names WebHook, Hook, Routing Rule Definition The subscription resource is used to define a push-based subscription from a server to another system. Once a subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined "channel" so that another system can take an appropriate action. Data type Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource `contained.where((('#'+id in (%resource.descendants().reference \| %resource.descendants().as(canonical) \| %resource.descendants().as(uri) \| %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()` dom-6: A resource should have narrative for robust management text.`div`.exists() dom-5: If a resource is contained in another resource, it SHALL NOT have a security label `contained.meta.security.empty()` Mappings rim: Entity. Role, or Act rim: N/A
id	Σ	0..1	string	There are no (further) constraints on this element Element id Subscription.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 Subscription.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())` Mappings rim: n/a rim: N/A
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id Subscription.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())` Mappings rim: n/a
language		0..1	codeBinding	There are no (further) constraints on this element Element id Subscription.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())` Mappings rim: n/a
text		0..1	Narrative	There are no (further) constraints on this element Element id Subscription.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display Definition A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Comments 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. Data type Narrative Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id Subscription.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources Definition These 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. Comments This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. Data type Resource Mappings rim: Entity. Role, or Act rim: N/A
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Subscription.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 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. 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 Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url 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 rim: N/A
modifierExtension	?! I	0..*	Extension	There are no (further) constraints on this element Element id Subscription.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and 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). 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 Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url 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 rim: N/A
status	S Σ ?!	1..1	codeBinding	Element id Subscription.status Short description requested \| active \| error \| off Definition The status of the subscription, which marks the server state for managing the subscription. Comments Bedeutung: Der Status der Subscription, der den Serverstatus der Subscription angibt. Neue Subscriptions werden immer mit dem Status `requested` an den Server übergeben. Der Server ändert im Anschluss den Status auf `active` oder im Fehlerfall auf `error`. Hinweise: Siehe R4 Subscriptions Data type code Binding The status of a subscription. SubscriptionStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a w5: FiveWs.status
contact	Σ I	0..*	ContactPoint	There are no (further) constraints on this element Element id Subscription.contact Short description Contact details for source (e.g. troubleshooting) Definition Contact details for a human to contact about the subscription. The primary use of this for system administrator troubleshooting. Data type ContactPoint Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` cpt-2: A system is required if a value is provided. `value.empty() or system.exists()` Mappings rim: n/a v2: XTN rim: TEL servd: ContactPoint w5: FiveWs.subject[x] w5: FiveWs.subject
end	Σ	0..1	instant	There are no (further) constraints on this element Element id Subscription.end Short description When to automatically delete the subscription Definition The time for the server to turn the subscription off. Comments The server is permitted to deviate from this time but should observe it. Data type instant Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a w5: FiveWs.done[x]
reason	S Σ	1..1	string	Element id Subscription.reason Short description Description of why this subscription was created Definition A description of why this subscription is defined. Comments Bedeutung: Beschreibung wieso diese Subscription erstellt wurde. Hinweise: Siehe R4 Subscriptions Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a w5: FiveWs.why[x]
criteria	S Σ	1..1	stringPattern	Element id Subscription.criteria Short description Canonical URL for the topic used to generate events Definition When using topic-based subscriptions, the primary criteria is always the topic, indicated by its canonical URL. Comments The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading "/". Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Subscription.criteria.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 Subscription.criteria.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 Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url 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 rim: N/A
filterCriteria	S Σ I	0..*	Extension(string)	There are no (further) constraints on this element Element id Subscription.criteria.extension:filterCriteria Short description Filtering critiera applied to events Alternate names extensions, user content Definition Search-style filters to be applied to narrow the subscription topic stream. Keys can be either search parameters appropriate to the filtering resource or keys defined within the subscription topic. Comments When multiple filters are applied, evaluates to true if all the conditions are met; otherwise it returns false. (i.e., logical AND). Data type Extension(string) Extension URL http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-filter-criteria 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 rim: N/A
value		0..1	System.String	There are no (further) constraints on this element Element id Subscription.criteria.value Short description Primitive value for string Definition Primitive value for string Data type System.String Maximum string length 1048576
error	Σ	0..1	string	There are no (further) constraints on this element Element id Subscription.error Short description Latest error note Definition A record of the last error that occurred when the server processed a notification. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
channel	S Σ	1..1	BackboneElement	There are no (further) constraints on this element Element id Subscription.channel Short description The channel on which to report matches to the criteria Definition Details where to send notifications when resources are received that meet the criteria. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Subscription.channel.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 Subscription.channel.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 Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url 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 rim: N/A
heartbeatPeriod	I	0..1	Extension(unsignedInt)	There are no (further) constraints on this element Element id Subscription.channel.extension:heartbeatPeriod Short description Interval in seconds to send 'heartbeat' notification Alternate names extensions, user content Definition If present, a 'hearbeat' notification (keepalive) is sent via this channel with an the interval period equal to this elements integer value in seconds. If not present, a heartbeat notification is not sent. 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(unsignedInt) Extension URL http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-heartbeat-period 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 rim: N/A
timeout	I	0..1	Extension(unsignedInt)	There are no (further) constraints on this element Element id Subscription.channel.extension:timeout Short description Timeout in seconds to attempt notification delivery Alternate names extensions, user content Definition If present, the maximum amount of time a server will allow before failing a notification attempt. 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(unsignedInt) Extension URL http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-timeout 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 rim: N/A
maxCount	I	0..1	Extension(positiveInt)	There are no (further) constraints on this element Element id Subscription.channel.extension:maxCount Short description Maximum number of triggering resources included in notification bundles Alternate names extensions, user content Definition If present, the maximum number of triggering resources that will be included in a notification bundle (e.g., a server will not include more than this number of trigger resources in a single notification). Note that this is not a strict limit on the number of entries in a bundle, as dependent resources can be included. 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(positiveInt) Extension URL http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-max-count 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 rim: N/A
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Subscription.channel.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 rim: N/A
type	S Σ	1..1	codeBinding	Element id Subscription.channel.type Short description rest-hook \| websocket \| email \| sms \| message Definition The type of channel to send notifications on. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type code Binding The type of method used to execute a subscription. RestAndWSSubscriptionChannelType (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Subscription.channel.type.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 Subscription.channel.type.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 Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url 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 rim: N/A
customChannelType	S Σ I	0..1	Extension(Coding)	There are no (further) constraints on this element Element id Subscription.channel.type.extension:customChannelType Short description Extended channel type for notifications Alternate names extensions, user content Definition The type of channel to send notifications on. Comments This extension allows for the use of additional channel types that were not defined in the FHIR R4 subscription definition. Data type Extension(Coding) Extension URL http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-channel-type 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 rim: N/A
value		0..1	System.String	There are no (further) constraints on this element Element id Subscription.channel.type.value Short description Primitive value for code Definition Primitive value for code Data type System.String Maximum string length 1048576
endpoint	S Σ	0..1	url	Element id Subscription.channel.endpoint Short description Where the channel points to Definition The url that describes the actual end-point to send messages to. Comments Bedeutung: Adresse des Kommunikationskanals/ Endpunkts, an den Subscription-Benachrichtigungen gesendet werden sollen. Dies ist nur für rest-hook Subscriptions relevant. Hinweise: Siehe R4 Subscriptions Data type url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
payload	S Σ	1..1	codeBinding	Element id Subscription.channel.payload Short description MIME type to send, or omit for no payload Definition The mime type to send the payload in - either application/fhir+xml, or application/fhir+json. If the payload is not present, then there is no payload in the notification, just a notification. The mime type "text/plain" may also be used for Email and SMS subscriptions. Comments Bedeutung: Format in dem Subscription Notifications versendet werden sollen (JSON oder XML) Hinweise: Siehe R4 Subscriptions Data type code Binding The mime type of an attachment. Any valid mime type is allowed. FhirMimeTypeVS (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Subscription.channel.payload.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	1..*	Extension	There are no (further) constraints on this element Element id Subscription.channel.payload.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 Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url 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 rim: N/A
content	S Σ I	1..1	Extension(code)	There are no (further) constraints on this element Element id Subscription.channel.payload.extension:content Short description Notification content level Alternate names extensions, user content Definition How much of the resource content to deliver in the notification payload. The choices are an empty payload, only the resource id, or the full resource content. Comments Sending the payload has obvious security implications. The server is responsible for ensuring that the content is appropriately secured. Data type Extension(code) Extension URL http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-payload-content 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 rim: N/A
value		0..1	System.String	There are no (further) constraints on this element Element id Subscription.channel.payload.value Short description Primitive value for code Definition Primitive value for code Data type System.String Maximum string length 1048576
header	S Σ	0..*	string	Element id Subscription.channel.header Short description Falls eine REST-Enpunkt einen Authorization-Header benötigt, kann dieser hier gesetzt werden Definition Additional headers / information to send as part of the notification. Comments Bedeutung: http-Header welcher dazu genutzt werden kann einen Authorization-header zu setzen. Dies ist nur für rest-hook Subscriptions relevant. Hinweise: ACHTUNG: dieses Datenfeld muss bei READ-Interaktionen maskiert werden! Siehe R4 Subscriptions Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a

<StructureDefinition xmlns="http://hl7.org/fhir">
    <id value="patient-merge-subscription" />
    <url value="https://gematik.de/fhir/isik/StructureDefinition/patient-merge-subscription" />
    <version value="4.0.1" />
    <name value="PatientMergeSubscription" />
    <title value="Patient Merge Subscription" />
    <status value="active" />
    <experimental value="false" />
    <date value="2024-11-25" />
    <publisher value="gematik GmbH" />
    <description value="Patient Merge Subscription  \n### Motivation\n\nSubscription ist eine FHIR Ressource, um als Client-System Benachrichtigungen &#252;ber Events auf dem FHIR Server anzufragen. Der Subscription Mechanismus in FHIR R4 ist nicht geeignet, um alle relevanten Events (hier im Speziellen das Mergen von Patienten) zu unterst&#252;tzen. Daher basiert das ISiK Subscription-Profil auf dem [Subscriptions R5 Backport Profil von HL7](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription.html).\n\nSiehe auch: {{pagelink:Patient-merge, text:Use Case Patient-merge}}\n\nUm als Subsystem &#252;ber ein Patienten-Merge-Event informiert zu werden, KANN der FHIR Subscription Mechanismus gem&#228;&#223; des [Subscriptions R5 Backport IGs von HL7](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/index.html) genutzt werden.\n\n### Kompatibilit&#228;t\n\nDas Profil PatientMergeSubscription basiert auf dem [Backport-Subscription Profil](https://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription.html).  \nDer [SubscriptionStatus](https://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription-status-r4.html), sowie das [Subscription Notification Bundle](https://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription-notification-r4.html) werden unver&#228;ndert direkt aus dem [Subscriptions R5 Backport IG](https://hl7.org/fhir/uv/subscriptions-backport/index.html) genutzt.  \n\nHinweise zu Inkompatibilit&#228;ten k&#246;nnen &#252;ber die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden." />
    <fhirVersion value="4.0.1" />
    <kind value="resource" />
    <abstract value="false" />
    <type value="Subscription" />
    <baseDefinition value="http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription" />
    <derivation value="constraint" />
    <differential>
        <element id="Subscription.status">
            <path value="Subscription.status" />
            <comment value="**Bedeutung:** Der Status der Subscription, der den Serverstatus der Subscription angibt. \n  Neue Subscriptions werden immer mit dem Status `requested` an den Server &#252;bergeben. \n  Der Server &#228;ndert im Anschluss den Status auf `active` oder im Fehlerfall auf `error`.  \n  **Hinweise:** Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)" />
            <mustSupport value="true" />
        </element>
        <element id="Subscription.reason">
            <path value="Subscription.reason" />
            <comment value="**Bedeutung:** Beschreibung wieso diese Subscription erstellt wurde.  \n  **Hinweise:** Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)" />
            <mustSupport value="true" />
        </element>
        <element id="Subscription.criteria">
            <path value="Subscription.criteria" />
            <patternString value="https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge" />
        </element>
        <element id="Subscription.channel">
            <path value="Subscription.channel" />
            <mustSupport value="true" />
        </element>
        <element id="Subscription.channel.type">
            <path value="Subscription.channel.type" />
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="https://gematik.de/fhir/isik/ValueSet/RestAndWSSubscriptionChannelType" />
            </binding>
        </element>
        <element id="Subscription.channel.endpoint">
            <path value="Subscription.channel.endpoint" />
            <comment value="**Bedeutung:** Adresse des Kommunikationskanals/ Endpunkts, an den Subscription-Benachrichtigungen gesendet werden sollen. Dies ist nur f&#252;r rest-hook Subscriptions relevant.  \n    **Hinweise:** Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)" />
            <mustSupport value="true" />
        </element>
        <element id="Subscription.channel.payload">
            <path value="Subscription.channel.payload" />
            <comment value="**Bedeutung:** Format in dem Subscription Notifications versendet werden sollen (JSON oder XML)\n    **Hinweise:** Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)" />
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="https://gematik.de/fhir/isik/ValueSet/FhirMimeTypeVS" />
            </binding>
        </element>
        <element id="Subscription.channel.header">
            <path value="Subscription.channel.header" />
            <short value="Falls eine REST-Enpunkt einen Authorization-Header ben&#246;tigt, kann dieser hier gesetzt werden" />
            <comment value="**Bedeutung:** http-Header welcher dazu genutzt werden kann einen Authorization-header zu setzen. Dies ist nur f&#252;r rest-hook Subscriptions relevant.  \n    **Hinweise:** ACHTUNG: dieses Datenfeld muss bei READ-Interaktionen maskiert werden! Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)" />
            <mustSupport value="true" />
        </element>
    </differential>
</StructureDefinition>

{
    "resourceType": "StructureDefinition",
    "id": "patient-merge-subscription",
    "url": "https://gematik.de/fhir/isik/StructureDefinition/patient-merge-subscription",
    "version": "4.0.1",
    "name": "PatientMergeSubscription",
    "title": "Patient Merge Subscription",
    "status": "active",
    "experimental": false,
    "date": "2024-11-25",
    "publisher": "gematik GmbH",
    "description": "Patient Merge Subscription  \n### Motivation\n\nSubscription ist eine FHIR Ressource, um als Client-System Benachrichtigungen über Events auf dem FHIR Server anzufragen. Der Subscription Mechanismus in FHIR R4 ist nicht geeignet, um alle relevanten Events (hier im Speziellen das Mergen von Patienten) zu unterstützen. Daher basiert das ISiK Subscription-Profil auf dem [Subscriptions R5 Backport Profil von HL7](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription.html).\n\nSiehe auch: {{pagelink:Patient-merge, text:Use Case Patient-merge}}\n\nUm als Subsystem über ein Patienten-Merge-Event informiert zu werden, KANN der FHIR Subscription Mechanismus gemäß des [Subscriptions R5 Backport IGs von HL7](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/index.html) genutzt werden.\n\n### Kompatibilität\n\nDas Profil PatientMergeSubscription basiert auf dem [Backport-Subscription Profil](https://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription.html).  \nDer [SubscriptionStatus](https://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription-status-r4.html), sowie das [Subscription Notification Bundle](https://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription-notification-r4.html) werden unverändert direkt aus dem [Subscriptions R5 Backport IG](https://hl7.org/fhir/uv/subscriptions-backport/index.html) genutzt.  \n\nHinweise zu Inkompatibilitäten können über die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden.",
    "fhirVersion": "4.0.1",
    "kind": "resource",
    "abstract": false,
    "type": "Subscription",
    "baseDefinition": "http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription",
    "derivation": "constraint",
    "differential": {
        "element":  [
            {
                "id": "Subscription.status",
                "path": "Subscription.status",
                "short": "",
                "comment": "**Bedeutung:** Der Status der Subscription, der den Serverstatus der Subscription angibt. \n  Neue Subscriptions werden immer mit dem Status `requested` an den Server übergeben. \n  Der Server ändert im Anschluss den Status auf `active` oder im Fehlerfall auf `error`.  \n  **Hinweise:** Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)",
                "mustSupport": true
            },
            {
                "id": "Subscription.reason",
                "path": "Subscription.reason",
                "short": "",
                "comment": "**Bedeutung:** Beschreibung wieso diese Subscription erstellt wurde.  \n  **Hinweise:** Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)",
                "mustSupport": true
            },
            {
                "id": "Subscription.criteria",
                "path": "Subscription.criteria",
                "short": "",
                "comment": "",
                "patternString": "https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge"
            },
            {
                "id": "Subscription.channel",
                "path": "Subscription.channel",
                "short": "",
                "comment": "",
                "mustSupport": true
            },
            {
                "id": "Subscription.channel.type",
                "path": "Subscription.channel.type",
                "short": "",
                "comment": "",
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "https://gematik.de/fhir/isik/ValueSet/RestAndWSSubscriptionChannelType"
                }
            },
            {
                "id": "Subscription.channel.endpoint",
                "path": "Subscription.channel.endpoint",
                "short": "",
                "comment": "**Bedeutung:** Adresse des Kommunikationskanals/ Endpunkts, an den Subscription-Benachrichtigungen gesendet werden sollen. Dies ist nur für rest-hook Subscriptions relevant.  \n    **Hinweise:** Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)",
                "mustSupport": true
            },
            {
                "id": "Subscription.channel.payload",
                "path": "Subscription.channel.payload",
                "short": "",
                "comment": "**Bedeutung:** Format in dem Subscription Notifications versendet werden sollen (JSON oder XML)\n    **Hinweise:** Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)",
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "https://gematik.de/fhir/isik/ValueSet/FhirMimeTypeVS"
                }
            },
            {
                "id": "Subscription.channel.header",
                "path": "Subscription.channel.header",
                "short": "Falls eine REST-Enpunkt einen Authorization-Header benötigt, kann dieser hier gesetzt werden",
                "comment": "**Bedeutung:** http-Header welcher dazu genutzt werden kann einen Authorization-header zu setzen. Dies ist nur für rest-hook Subscriptions relevant.  \n    **Hinweise:** ACHTUNG: dieses Datenfeld muss bei READ-Interaktionen maskiert werden! Siehe [R4 Subscriptions](https://hl7.org/fhir/R4/subscription.html)",
                "mustSupport": true
            }
        ]
    }
}

Patient Merge Subscription

Constraints/Invarianten

Terminology-Bindings

Element	Staerke	ValueSet
Subscription.channel.type	required	https://gematik.de/fhir/isik/ValueSet/RestAndWSSubscriptionChannelType
Subscription.channel.payload	required	https://gematik.de/fhir/isik/ValueSet/FhirMimeTypeVS

Anmerkungen zu Must-Support-Feldern

Feldname	Kurzbeschreibung	Hinweise
Subscription.status		Bedeutung: Der Status der Subscription, der den Serverstatus der Subscription angibt. Neue Subscriptions werden immer mit dem Status `requested` an den Server übergeben. Der Server ändert im Anschluss den Status auf `active` oder im Fehlerfall auf `error`. Hinweise: Siehe R4 Subscriptions
Subscription.reason		Bedeutung: Beschreibung wieso diese Subscription erstellt wurde. Hinweise: Siehe R4 Subscriptions
Subscription.channel
Subscription.channel.type
Subscription.channel.endpoint		Bedeutung: Adresse des Kommunikationskanals/ Endpunkts, an den Subscription-Benachrichtigungen gesendet werden sollen. Dies ist nur für rest-hook Subscriptions relevant. Hinweise: Siehe R4 Subscriptions
Subscription.channel.payload		Bedeutung: Format in dem Subscription Notifications versendet werden sollen (JSON oder XML) Hinweise: Siehe R4 Subscriptions
Subscription.channel.header	Falls eine REST-Enpunkt einen Authorization-Header benötigt, kann dieser hier gesetzt werden	Bedeutung: http-Header welcher dazu genutzt werden kann einen Authorization-header zu setzen. Dies ist nur für rest-hook Subscriptions relevant. Hinweise: ACHTUNG: dieses Datenfeld muss bei READ-Interaktionen maskiert werden! Siehe R4 Subscriptions

Interaktionen

Interaktion	Verbindlichkeit
read	MAY
create	MAY
update	MAY
delete	MAY

(Reverse-)Include

Name	Spezifikation	Verbindlichkeit
$get-ws-binding-token	http://hl7.org/fhir/uv/subscriptions-backport/OperationDefinition/backport-subscription-get-ws-binding-token	MAY

CapabilityStatement

Subscription:

Subscription

id : PatientMergeSubscriptionExample

meta

profile : https://gematik.de/fhir/isik/StructureDefinition/patient-merge-subscription

status : requested

reason : Patient merge subscription

criteria : https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge

channel

type : rest-hook

endpoint : http://localhost:8081/fhir/Bundle

payload : application/fhir+json

extension

url : http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-payload-content

value : full-resource

header : Authorization: Bearer xxxxxxxxxx

<Subscription xmlns="http://hl7.org/fhir">
    <id value="PatientMergeSubscriptionExample" />
    <meta>
        <profile value="https://gematik.de/fhir/isik/StructureDefinition/patient-merge-subscription" />
    </meta>
    <status value="requested" />
    <reason value="Patient merge subscription" />
    <criteria value="https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge" />
    <channel>
        <type value="rest-hook" />
        <endpoint value="http://localhost:8081/fhir/Bundle" />
        <payload value="application/fhir+json">
            <extension url="http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-payload-content">
                <valueCode value="full-resource" />
            </extension>
        </payload>
        <header value="Authorization: Bearer xxxxxxxxxx" />
    </channel>
</Subscription>

{
    "resourceType": "Subscription",
    "id": "PatientMergeSubscriptionExample",
    "meta": {
        "profile":  [
            "https://gematik.de/fhir/isik/StructureDefinition/patient-merge-subscription"
        ]
    },
    "criteria": "https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge",
    "channel": {
        "type": "rest-hook",
        "endpoint": "http://localhost:8081/fhir/Bundle",
        "payload": "application/fhir+json",
        "_payload": {
            "extension":  [
                {
                    "url": "http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-payload-content",
                    "valueCode": "full-resource"
                }
            ]
        },
        "header":  [
            "Authorization: Bearer xxxxxxxxxx"
        ]
    },
    "status": "requested",
    "reason": "Patient merge subscription"
}

Subscription

SubscriptionNotification-Bundle

Bundle

id : SubscriptionNotificationBundleExample

type : history

entry

fullUrl : urn:uuid:9bb6fcbd-8391-4e35-bd4c-620a2db47af0

resource

id : SubscriptionNotification

meta

profile : http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription-status-r4

parameter

name : subscription

value

reference : Subscription/1

parameter

name : topic

value : https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge

parameter

name : status

value : active

parameter

name : type

value : event-notification

parameter

name : events-since-subscription-start

value : 1

parameter

name : notification-event

part

name : event-number

value : 1

part

name : timestamp

value : 2024-02-22T18:30:05+01:00

part

name : focus

value

reference : Patient/DorisQuelle

request

method : GET

url : https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge/$status

response

status : 200

entry

fullUrl : http://example.org/fhir/Patient/DorisQuelle

resource

id : DorisQuelle

meta

profile : https://gematik.de/fhir/isik/StructureDefinition/ISiKPatient

identifier

type

coding

system : http://terminology.hl7.org/CodeSystem/v2-0203

code : MR

system : https://fhir.krankenhaus.example/sid/PID

value : 654321

identifier

type

coding

system : http://fhir.de/CodeSystem/identifier-type-de-basis

code : KVZ10

system : http://fhir.de/sid/gkv/kvid-10

value : A123456789

active : False

name

use : official

family : Duplikat

given : Doris

gender : female

birthDate : 1964-08-12

request

method : PUT

url : Patient

response

status : 201

<Bundle xmlns="http://hl7.org/fhir">
    <id value="SubscriptionNotificationBundleExample" />
    <type value="history" />
    <entry>
        <fullUrl value="urn:uuid:9bb6fcbd-8391-4e35-bd4c-620a2db47af0" />
        <resource>
            <Parameters>
                <id value="SubscriptionNotification" />
                <meta>
                    <profile value="http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription-status-r4" />
                </meta>
                <parameter>
                    <name value="subscription" />
                    <valueReference>
                        <reference value="Subscription/1" />
                    </valueReference>
                </parameter>
                <parameter>
                    <name value="topic" />
                    <valueCanonical value="https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge" />
                </parameter>
                <parameter>
                    <name value="status" />
                    <valueCode value="active" />
                </parameter>
                <parameter>
                    <name value="type" />
                    <valueCode value="event-notification" />
                </parameter>
                <parameter>
                    <name value="events-since-subscription-start" />
                    <valueString value="1" />
                </parameter>
                <parameter>
                    <name value="notification-event" />
                    <part>
                        <name value="event-number" />
                        <valueString value="1" />
                    </part>
                    <part>
                        <name value="timestamp" />
                        <valueInstant value="2024-02-22T18:30:05+01:00" />
                    </part>
                    <part>
                        <name value="focus" />
                        <valueReference>
                            <reference value="Patient/DorisQuelle" />
                        </valueReference>
                    </part>
                </parameter>
            </Parameters>
        </resource>
        <request>
            <method value="GET" />
            <url value="https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge/$status" />
        </request>
        <response>
            <status value="200" />
        </response>
    </entry>
    <entry>
        <fullUrl value="http://example.org/fhir/Patient/DorisQuelle" />
        <resource>
            <Patient>
                <id value="DorisQuelle" />
                <meta>
                    <profile value="https://gematik.de/fhir/isik/StructureDefinition/ISiKPatient" />
                </meta>
                <identifier>
                    <type>
                        <coding>
                            <system value="http://terminology.hl7.org/CodeSystem/v2-0203" />
                            <code value="MR" />
                        </coding>
                    </type>
                    <system value="https://fhir.krankenhaus.example/sid/PID" />
                    <value value="654321" />
                </identifier>
                <identifier>
                    <type>
                        <coding>
                            <system value="http://fhir.de/CodeSystem/identifier-type-de-basis" />
                            <code value="KVZ10" />
                        </coding>
                    </type>
                    <system value="http://fhir.de/sid/gkv/kvid-10" />
                    <value value="A123456789" />
                </identifier>
                <active value="false" />
                <name>
                    <use value="official" />
                    <family value="Duplikat" />
                    <given value="Doris" />
                </name>
                <gender value="female" />
                <birthDate value="1964-08-12" />
            </Patient>
        </resource>
        <request>
            <method value="PUT" />
            <url value="Patient" />
        </request>
        <response>
            <status value="201" />
        </response>
    </entry>
</Bundle>

{
    "resourceType": "Bundle",
    "id": "SubscriptionNotificationBundleExample",
    "type": "history",
    "entry":  [
        {
            "fullUrl": "urn:uuid:9bb6fcbd-8391-4e35-bd4c-620a2db47af0",
            "resource": {
                "resourceType": "Parameters",
                "id": "SubscriptionNotification",
                "meta": {
                    "profile":  [
                        "http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription-status-r4"
                    ]
                },
                "parameter":  [
                    {
                        "name": "subscription",
                        "valueReference": {
                            "reference": "Subscription/1"
                        }
                    },
                    {
                        "name": "topic",
                        "valueCanonical": "https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge"
                    },
                    {
                        "name": "status",
                        "valueCode": "active"
                    },
                    {
                        "name": "type",
                        "valueCode": "event-notification"
                    },
                    {
                        "name": "events-since-subscription-start",
                        "valueString": "1"
                    },
                    {
                        "name": "notification-event",
                        "part":  [
                            {
                                "name": "event-number",
                                "valueString": "1"
                            },
                            {
                                "name": "timestamp",
                                "valueInstant": "2024-02-22T18:30:05+01:00"
                            },
                            {
                                "name": "focus",
                                "valueReference": {
                                    "reference": "Patient/DorisQuelle"
                                }
                            }
                        ]
                    }
                ]
            },
            "request": {
                "method": "GET",
                "url": "https://gematik.de/fhir/isik/SubscriptionTopic/patient-merge/$status"
            },
            "response": {
                "status": "200"
            }
        },
        {
            "fullUrl": "http://example.org/fhir/Patient/DorisQuelle",
            "resource": {
                "resourceType": "Patient",
                "id": "DorisQuelle",
                "meta": {
                    "profile":  [
                        "https://gematik.de/fhir/isik/StructureDefinition/ISiKPatient"
                    ]
                },
                "identifier":  [
                    {
                        "type": {
                            "coding":  [
                                {
                                    "code": "MR",
                                    "system": "http://terminology.hl7.org/CodeSystem/v2-0203"
                                }
                            ]
                        },
                        "system": "https://fhir.krankenhaus.example/sid/PID",
                        "value": "654321"
                    },
                    {
                        "system": "http://fhir.de/sid/gkv/kvid-10",
                        "type": {
                            "coding":  [
                                {
                                    "code": "KVZ10",
                                    "system": "http://fhir.de/CodeSystem/identifier-type-de-basis"
                                }
                            ]
                        },
                        "value": "A123456789"
                    }
                ],
                "name":  [
                    {
                        "use": "official",
                        "family": "Duplikat",
                        "given":  [
                            "Doris"
                        ]
                    }
                ],
                "active": false,
                "gender": "female",
                "birthDate": "1964-08-12"
            },
            "request": {
                "method": "PUT",
                "url": "Patient"
            },
            "response": {
                "status": "201"
            }
        }
    ]
}

SubscriptionNotificationBundleExample

Patientenobjekte

Zum Beispiel für den Merge auf Ebene der Patient-Instanzen siehe Übergreifende Festlegungen Patient-merge.