Helix AU Core - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Architecture

Overview

Use Helix FHIR API to send your requests to the server.

Rate Limiting

Helix FHIR API uses rate limiting to ensure fair use of the API and to adhere to security principles. Rate limiting is per IP address. Telstra Health reserves the right to modify rate-limiting parameters at any time without prior notice; however, you will be notified of any changes that may have a significant impact.

If you have specific rate requirements, discuss them with Telstra Health support team.

Be prepared to manage transient HTTP errors that may result from rate limiting. This includes but is not limited to 429 and 503 response codes.

Transient HTTP Errors & Error Handling

Be prepared to manage transient HTTP errors and retry the operations as required. Errors may be returned from any layer of the system not just the FHIR server. Design your integration to manage the full range of HTTP and network error conditions.

Scenarios and suggestions:

• Retry requests that cause transient errors to ensure reliable delivery.
• Implement robust monitoring to trigger alerts in the event of permanent failures.
• Ensure that permanent failures do not result in cascading failures and infinite retries.

Polling vs Change Notifications

Use the change notification mechanisms such as Subscriptions to avoid polling operations.

• Note: Polling for changes is not acceptable due to the unnecessary additional load imposed on systems.