Note that this server is configured to be a reference implementation (RI) for subscriptions .
FHIR R4 endpoint at https://subscriptions.argo.run/fhir/r4
As a reference implementation for subscriptions, this endpoint contains some immutable records for testing:
Basic
resource, using cross-version extensions (equivalent
to the R4B and R5 encounter-complete
topics).
The topic triggers when an encounter is either created with a status
of finished
or updated from any other status to finished
.
Based on loaded packages, this server also implements the following pages:
This endpoint uses
The endpoint also exposes a system-level operation, https://subscriptions.argo.run/fhir/r4/$subscription-hook
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
the
Note that the server will NOT send notifications to addresses rooted in example.org
.
For example, a REST-Hook pointing at http://example.org/endpoints/test
will trigger
the notifications and be visible on the
FHIR R4B endpoint at https://subscriptions.argo.run/fhir/r4b
As a reference implementation for subscriptions, this endpoint contains some immutable records for testing:
SubscriptionTopic
.
The topic triggers when an encounter is either created with a status
of finished
or updated from any other status to finished
.
Based on loaded packages, this server also implements the following pages:
This endpoint uses
The endpoint also exposes a system-level operation, https://subscriptions.argo.run/fhir/r4b/$subscription-hook
which can be used as a notification endpoint for FHIR R4B 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
the
Note that the server will NOT send notifications to addresses rooted in example.org
.
For example, a REST-Hook pointing at http://example.org/endpoints/test
will trigger
the notifications and be visible on the
FHIR R5 endpoint at https://subscriptions.argo.run/fhir/r5
As a reference implementation for subscriptions, this endpoint contains some immutable records for testing:
SubscriptionTopic
.
The topic triggers when an encounter is either created with a status
of complete
or updated from any other status to complete
.
Based on loaded packages, this server also implements the following pages:
This endpoint uses
The endpoint also exposes a system-level operation, https://subscriptions.argo.run/fhir/r5/$subscription-hook
which can be used as a notification endpoint for FHIR R5 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
the
Note that the server will NOT send notifications to addresses rooted in example.org
.
For example, a REST-Hook pointing at http://example.org/endpoints/test
will trigger
the notifications and be visible on the