FHIR R4 endpoint at https://subscriptions.argo.run/fhir/payer

This endpoint uses FHIR R4 and Subscriptions via the Subscriptions Backport IG

• 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, https://subscriptions.argo.run/fhir/payer/$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 Received Notifications page.

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 Local Subscriptions page, but not actually attempt to send the notification to the endpoint.

FHIR R4 endpoint at https://subscriptions.argo.run/fhir/provider

Based on loaded packages, this server also implements the following pages:

This endpoint uses FHIR R4 and Subscriptions via the Subscriptions Backport IG

• 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, https://subscriptions.argo.run/fhir/provider/$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 Received Notifications page.

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 Local Subscriptions page, but not actually attempt to send the notification to the endpoint.