Magentus Practice Management FHIR® Implementation Guide
1.3.2 - Release
Australia
Magentus Practice Management FHIR® Implementation Guide
1.3.2 - Release
Australia
Magentus Practice Management FHIR® Implementation Guide - Downloaded Version 1.3.2 See the Directory of published versions
| Official URL: http://fhir.geniesolutions.io/ImplementationGuide/geniesolutions.fhir | Version: 1.3.2 | ||||
| Active as of 2026-10-02 | Computable Name: MagentusPracticeManagement | ||||
This FHIR Implementation Guide provides FHIR profiles for the Magentus FHIR Interoperability Platform.
The Implementation Guide includes the following profile domains:
Start by choosing the solution you are integrating with, then follow the guide for your role within that solution.
| Role | Start here |
|---|---|
| Placer — practice management system submitting orders | Placer Integration |
| Filler — pathology or radiology system fulfilling orders | Filler Integration |
| Patient portal — providing patients access to their orders | Patient Integration |
| Role | Start here |
|---|---|
| VMO / Practice Management System — creating and managing theatre bookings | Bookings |
| Hospital — receiving booking requests and responding to them | Bookings — Responding to a Booking |
| Role | Start here |
|---|---|
| Filler / Diagnostic service — sending pathology or radiology reports to a PMS | Reports |
| PMS / Placer — receiving diagnostic reports from a filler | Reports |
| Role | Start here |
|---|---|
| Referring practice — sending a referral to a specialist | Referrals |
| Specialist — receiving and managing incoming referrals | Referrals |
| Term | Definition |
|---|---|
| Placer | A system (typically a practice management system) that creates and submits diagnostic orders on behalf of a requesting clinician. |
| Filler | A diagnostic service provider (pathology laboratory or imaging service) that receives and fulfils diagnostic orders. |
| Brand | A named filler organisation — a Pathology Laboratory or Imaging Service — that is discoverable via the $get_brands operation. Brands belong to a Parent Diagnostic Organization. |
| Directed order | An order where all fulfillment Tasks carry a Task.owner identifying the intended filler brand. |
| Undirected order | An order where no fulfillment Task has a Task.owner. The order is lodged in the registry for any eligible filler to claim. |
| Requisition | The group identifier (ServiceRequest.requisition) shared by all ServiceRequests and Tasks in a single order — typically the barcode printed on the request form. |
| Group Task | An EOrdersTaskFulfillmentGroup Task that coordinates all individual fulfillment Tasks for an order. Placers and fillers subscribe to group Task status changes. |
| VMO | Visiting Medical Officer — the surgeon or specialist who creates and manages a theatre booking. |
This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (geniesolutions.fhir.r4) and R4B (geniesolutions.fhir.r4b) are available.
This IG Contains the following dependencies on other IGs.
Package hl7.fhir.uv.extensions.r4#5.3.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, May 16, 2026 18:32+1000+10:00) |
Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00) |
Package hl7.fhir.au.base#6.0.0 This implementation guide is provided to support the use of FHIR®© in an Australian context. (built Thu, Jan 15, 2026 22:19+0000+00:00) |
Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00) |
Package hl7.fhir.uv.ipa#1.1.0 This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Wed, Mar 19, 2025 14:34+0000+00:00) |
Package hl7.fhir.au.core#2.0.0 This implementation guide is provided to support the use of FHIR®© in an Australian context, and defines the minimum set of constraints on the FHIR resources to create the AU Core profiles. This implementation guide forms the foundation to build future AU Realm FHIR implementation guides and its content will continue to grow to meet the needs of AU implementers. (built Wed, Jan 28, 2026 05:31+0000+00:00) |
Package hl7.fhir.au.ereq#1.0.1 This implementation guide is provided to support the use of FHIR®© for clinical requesting and ordering in an Australian context. , and defines the minimum set of constraints on the FHIR resources to create the AU eRequesting profiles. (built Thu, Sep 10, 2026 12:21+0000+00:00) |
Package hl7.fhir.uv.tools.r4#1.1.2 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Mar 24, 2026 11:13+1100+11:00) |
There are no Global profiles defined
This work is licensed under CC BY 4.0
This publication includes IP covered under the following statements.
