Helix AU Core
0.1.0 - ci-build

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

Custom Operations

Overview

Custom operations are used in FHIR as extensions to the standard RESTful interactions, such as Create, Read, Update, and Delete.

Using Custom Operations

These operations are prefixed by a $ (for example, $getSlots) and can be used to:

  • Perform complex logic on the server
  • Operate on multiple resource types
  • Trigger side effects, such as merging records, generating reports
  • Enforce business rules or workflow-specific behavior

Supported Custom Operations

Custom operations are categorised by the level at which they are executed.

They can be used at three different levels:

  • System-Level: The entire FHIR server (for example, POST/$bulk-export)
  • Type-level: Resource of a specific type (for example, POST/Patient/$match)
  • Instance-level: A specific resource instance (for example, POST/Patient/123/$mergeRecords)

You can find more details at: FHIR Operations documentation


$getSlots Custom Operation

Operation Name Type Documentation Link
$getSlots Type-level custom operation Get slots operation
$requestSasToken Type-level custom operation Request SAS Token

This operation retrieves available Slot resources for a given practitioner, location, or service within a specified time window.