FHIR Candle
Development Server This is an open FHIR endpoint for development, testing, and educational purposes only. Uploading real patient data is strictly prohibited.
Reference Implementation

Note that this server is configured to be a reference implementation (RI) for subscriptions .

FHIR Endpoints
r4

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

As a reference implementation for subscriptions, this endpoint contains some immutable records for testing:

  • Patient/example : An example patient, loaded from the FHIR examples.
  • Basic/encounter-complete : An example topic as a 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:

Directive
Name
Description
subscriptionsSubscriptions RI TourThis page contains a tour of topic-based subscriptions.
subscriptionsSubscriptions US Core HTI-2 TestingThis page contains a testing utilites for proposed US Core subscriptions.

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/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 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.

r4b

FHIR R4B endpoint at https://subscriptions.argo.run/fhir/r4b

As a reference implementation for subscriptions, this endpoint contains some immutable records for testing:

  • Patient/example : An example patient, loaded from the FHIR examples.
  • SubscriptionTopic/encounter-complete : An example 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:

Directive
Name
Description
subscriptionsSubscriptions RI TourThis page contains a tour of topic-based subscriptions.
subscriptionsSubscriptions US Core HTI-2 TestingThis page contains a testing utilites for proposed US Core subscriptions.

This endpoint uses FHIR R4B 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/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 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.

r5

FHIR R5 endpoint at https://subscriptions.argo.run/fhir/r5

As a reference implementation for subscriptions, this endpoint contains some immutable records for testing:

  • Patient/example : An example patient, loaded from the FHIR examples.
  • SubscriptionTopic/encounter-complete : An example 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:

Directive
Name
Description
subscriptionsSubscriptions RI TourThis page contains a tour of topic-based subscriptions.
subscriptionsSubscriptions US Core HTI-2 TestingThis page contains a testing utilites for proposed US Core subscriptions.

This endpoint uses FHIR R5 and Subscriptions via the Subscriptions Framework

  • 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/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 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.

Description Link
GitHub Repository for this software github.com
FHIR R5 Subscriptions Framework hl7.org
FHIR R4/R4B Subscriptions Backport IG hl7.org
FHIR R4 Specification hl7.org
FHIR R4B Specification hl7.org
An unhandled error has occurred. Reload 🗙