Magentus Practice Management FHIR® Implementation Guide
1.3.2 - Release
Australia
Magentus Practice Management FHIR® Implementation Guide
1.3.2 - Release
Australia
This page is part of the Magentus Practice Management FHIR Implementation Guide (v1.3.2: Releases Draft) based on FHIR (HL7® FHIR® Standard) R4. No current official version has been published yet. For a full list of available versions, see the Directory of published versions
| Official URL: http://fhir.geniesolutions.io/CapabilityStatement/ebookings-capability | Version: 1.3.2 | ||||
| Active as of 2026-09-30 | Computable Name: EBookingsCapability | ||||
Requirements for Genie Solutions Electronic Theatre Bookings
The capability statement below describes the FHIR resources, profiles, and search parameters that the eBookings FHIR server supports. Use this as a reference when implementing a VMO practice management system or hospital integration to understand which interactions are available and which are mandatory (SHALL) vs. recommended (SHOULD).
Raw OpenAPI-Swagger Definition file | Download
Language: en
json, xmlNote to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.
serverRequirements for Genie Solutions Electronic Theatre Bookings
transactioninteraction.The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revincluderead, create, update, search-typepatchUsed by the Magentus platform to change status after a hospital response, and to cancel a booking. A hospital does not change the Appointment. It responds with an AppointmentResponse.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | status | token | |
| SHALL | _lastUpdated | date | |
| SHALL | _id | token |
read, create, updatesearch-typeUsed by a placer to find the latest response to a booking, for example to detect a booking that has stalled at tentative: AppointmentResponse?appointment=Appointment/[id]&_sort=-_lastUpdated&_count=1. The server SHALL support _sort on _lastUpdated.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | appointment | reference | |
| SHALL | _lastUpdated | date | |
| SHOULD | identifier | token | Lets a hospital find a response that it created by its own business identifier, for example to recover after a create whose result it did not receive. |
read, create, update.read, createupdateThe hospital updates Encounter.status as the admission progresses, and sets finished and period.end when the patient is discharged. A practice may take finished to mean that the booked procedure was performed, unless the booking was cancelled.
read, create.read, create.read, create.read, create.read, createupdateThe platform keeps one Consent per booking. It writes each change of consent option as a new version of that resource with PUT (same id, new meta.versionId). See EBookingsConsent.
read, create, search-typedeleteThe platform deletes a ChargeItem when the practice removes the item from the booking. A consumer that keeps a copy of the booking should compare the ChargeItems in each retrieval with its copy, and remove the ones that are no longer present.
read, create.read, create.read, create.read, create, search-type.| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | subject | reference |
read, create.search-type.read.search-type.