Magentus Practice Management FHIR Implementation Guide
1.2.60 - ci-build Australia flag

Magentus Practice Management FHIR Implementation Guide - Local Development build (v1.2.60) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Reports

The Magentus Reports Service accepts a transaction with a constrained set of FHIR Resources, including DiagnosticReport, based on AU Core R4 profiles. The Magentus Diagnostic Report transactions and associated AU Core Profiles are described below.

A Task needs to be included to request tracking of DiagnosticReport receipt by the PMS and to indicate that the report receipt is being requested. This status will be updated by the PMS based on the receiving workflow. See Magentus Imaging Task Entry for more detail.

In addition to the DiagnosticReport, the report service can be asked to accept a CopyTo of a report to a Magentus PMS user. This is specified using a CommunicationRequest and a Task placed in a requested state to track the workflow of delivery as with report delivery.

Magentus Profile FHIR® Resource
Diagnostic Imaging Report Transaction Bundle
Magentus Imaging Report Task Task
Magentus Imaging Report DiagnosticReport
Magentus Imaging Study ImagingStudy
Magentus Patient Patient
Magentus Imaging Request ServiceRequest
Magentus Organization Organization
Magentus PractitionerRole PractitionerRole
Diagnostic Imaging Report CopyTo CommunicationRequest CommunicationRequest
Diagnostic Imaging Report CopyTo Task Task

Below are a list of example instances of Magentus Diagnostic Report transactions.

Example Instance
Pathology Report
Inbound Imaging Diagnostic Report Transaction