Subscribing to changes
It is often important to be notified of changes to specific resources. Within Koppeltaal it is possible to be notified of changes on a very accurate level.
Last updated
It is often important to be notified of changes to specific resources. Within Koppeltaal it is possible to be notified of changes on a very accurate level.
Last updated
The notification mechanism has a maturity level 3. We know that FHIR is working hard to improve the notification mechanism. In the future version, it is very likely that this functionality will change. For example, currently there is no notification when a resource is deleted.
Applications can create their own notification using the resource. This must adhere to the . The Subscription
, like the other resources, can be managed through the .
The Subscription.criteria
field can be filled by applications themselves. With each change, the Koppeltaal server will check if there are Subscriptions
where the criteria matches the created/changed Resource
. If so, a POST
notification will be sent to the Subscription.channel.endpoint
for the matched subscriptions.
It's possible to subscribe to custom search criteria added by Koppeltaal. This is done by defining SearchParameter
resources. Koppeltaal provides SearchParameters
that are likely to be used. Information on these can be found on .
The Subscription.channel
is used to specify how and where the notification should go. In the POC, Koppeltaal will only support the rest-hook
type without a payload.
There are differences between the FHIR Subscription
and the Koppeltaal 2.0 profile. For example, Koppeltaal does not allow the creation of a Subscription
where the Subscription.payload
is turned on. This way, the notification is purely a "ping" to indicate that something has changed, but not WHAT content has changed. This choice was made to avoid accidentally sending sensitive information to the wrong endpoint.