Note that this server is configured to be a reference implementation (RI) for subscriptions .
FHIR R4 endpoint at
As a reference implementation for subscriptions, this endpoint contains some immutable records for testing:
Patient/example: An example patient, loaded from the FHIR examples.
An example topic as a
Basic resource, using cross-version extensions (equivalent
to the R4B and R5
The topic triggers when an encounter is either created with a
or updated from any other status to
If you are getting started with topic-based subscriptions, there is a deatiled tour available here.
If you are building or testing a topic-based subscription server implementation, there is a client available here.
FHIR Contents: FHIR resources in this tenant
Local Subscriptions: outgoing Subscription notifications from this server
Received Notifications: incoming notifications received by this server
The endpoint also exposes a system-level operation,
which can be used as a notification endpoint for FHIR R4 notifications (e.g.,
if you are developing a server that sends notifications, you can point it here).
Any received notification bundles are stored as resources locally, and the notifications will appear on
Note that the server will NOT send notifications to addresses rooted in
For example, a REST-Hook pointing at
http://example.org/endpoints/test will trigger
the notifications and be visible on the
page, but not actually attempt to send the notification to the endpoint.