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

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

Genie Solutions eOrders Capability Statement

Requirements for Genie Solutions Diagnostic eOrders

Behavior: Operation Definitions

These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.

Add Placer Subscription Operation

Submits a Subscription resource to one or more SmileCDR partitions mapped from the supplied brand Organization references. This allows a placer system to register a subscription across multiple diagnostic service brand partitions in a single call.

Each Organization reference (literal or logical) is resolved to the corresponding SmileCDR partition. The provided Subscription resource is then submitted to each partition. The operation returns a result per organization indicating success or failure.

Diagnostic Request Claim Operation

This operation is used to claim a request based on a scanned barcode and returns a group Task reference. An Organization reference is also supplied so that a particular brand of service may be required for the transfer of the request.

The transferred request will result in the creation of a new set of Tasks, including a group Task and child Tasks, each of which will be placed in a requested status. To distinguish a request that has been claimed, the businessStatus of the Tasks will be set to claimed-request and a tag will be set to the same claimed-request value. The reason for the tag is that the businessStatus will change over time but the tag is persistent between resource versions.

The original Task will be placed in a cancelled status and the businessStatus will be set to claimed-cancel. To prevent re-discovering Cancelled tasks, the original filler should set the businessStatus to cancel-handled and when searching for new requested or cancelled tasks, explicitly exclude those that have already been handled via the businessStatus.

The operation will return a Coding value that indicates the result of the claim attempt. If the claim is successful, the group Task reference will be returned. If the claim is unsuccessful, an error code will be returned.

Diagnostic Request View Operation

View a diagnostic order based on the group identifier/barcode. This operation allows a patient portal to request a view into a diagnostic request based on the barcode, including a fulfilment history. It is not designed to be used by service providers. An additional operation will be needed by them to support views needed in the booking process where the patient may or may not choose to instigate a claim.

Get Brands Operation

Retrieves a list of diagnostic service brand Organizations (Pathology Laboratories and Imaging Services). This operation enables clients to discover available diagnostic service providers.

Submit Order Operation

Submits a diagnostic order as a transaction Bundle. The Bundle must conform to the EOrdersSubmitOrderBundle profile and contain all resources required for the order including the patient, requester details, service requests, fulfillment tasks and optional consent and communication preferences.

The response body is always a single resource — either a transaction-response Bundle or an OperationOutcome. The caller distinguishes between them by checking resourceType:

  • Bundle (type transaction-response) — the order was directed and successfully processed.
  • OperationOutcome (severity error or fatal) — the order failed validation or could not be processed.
  • OperationOutcome (severity information) — the order was lodged as undirected (no Task.owner); not an error.

Behavior: Search Parameters

These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.

CommunicationRequest About SearchParameter

Search parameter for CommunicationRequest by About reference

Diagnostic Request CopiesTo SearchParameter

Search parameter for ServiceRequest by copiesTo reference

DiagnosticReport ImagingStudy SearchParameter

Search parameter for DiagnosticReport by ImagingStudy reference

Structures: Abstract Profiles

These are profiles on resources or data types that describe patterns used by other profiles, but cannot be instantiated directly. I.e. instances can conform to profiles based on these abstract profiles but do not declare conformance to the abstract profiles themselves.

Diagnostic Report Base

Foundation for pathology and radiology reports.

EBookings Appointment Base

EBookings appointment base that excludes the contained anaesthetic and prosthesis.

EOrders Diagnostic Request Base

An EOrders Diagnostic Service Request Base profile used by Pathology request profile and Radiology request profile. This base profile captures the common elements between the two request profiles, and should not be used directly for requesting. The more specific profiles should be used for requesting to allow for better differentiation between radiology and pathology requests and to allow for more specific terminology bindings on the code element, amongst other things.

Note that all supportingInformation must include a narrative so that fillers that do not understand how to process new structured content can always revert to a narrative interpretation of the content.

EOrders Registry Provenance

Provenance to track the allocation of an EOrder

EOrders Task Fulfillment Request Base

EOrders Task Fulfillment Request Base Profile. status, statusReason, and businessStatus should all be meaningfully updated on status change. If some attributes are not used, they should be cleared to prevent propagation of other status attributes outside of their binding to the original status for which they were intended.

Note that we have begun to include some Task output options that can be provided by the filler as part of the fulfilment process. For example,

  • Reference to reflex orders that define a filler nominated change in diagnostic request fulfilment, e.g. when an alternative test or procedure is provided.
  • Indirect references to diagnostic reports that are created as an outcome of fulfilment. These are referenced via a Task as the task allows tracking of the receipt of the report by the original requester.
  • Booking information for the test or procedure which has been created via an independent booking process. This is provided through a Slot reference that, through other contained resources, carries information of time, location, and provider.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Diagnostic Imaging Report CopyTo Task

The Diagnostic Imaging Report CopyTo Task tracks the receiving workflow performed by the PMS for a report CopyTo.

Diagnostic Imaging Report Transaction

Genie Diagnostic Imaging Report Transaction

Diagnostic Imaging Report Transaction Task Entry

The Diagnostic Imaging Report Transaction Task tracks the receiving workflow performed by the PMS.

EBooking Difference Between Appointment Versions

Documents the difference between two versions of a theatre booking. Uses a structured form rather than a string to allow for easier processing.

EBookings Adverse Reaction

Magentus EBookings adverse reaction such as Penicillin or latex.

EBookings Anaesthetic Request

Genie EBookings Anaesthetic ServiceRequest profile

EBookings Appointment

EBookings Appointment Profile

EBookings Appointment Response

Genie EBookings Appointment Response Profile

EBookings ChargeItem

Genie EBookings ChargeItem profile. This supports both MBS codes as well as ADA codes for dental billing items (see ADA ValueSet).

EBookings Consent

Genie EBookings Consent profile. There are three Consent approaches.

  1. Consent agreed and attached: This will have the consent document attached and a status of #active.
  2. Consent to be provided on day of theatre: This will have a status of #proposed, no attachment, and the consent document will be provided on the day of theatre.
  3. No consent decision made: This will have a status of #draft and no consent document is provided.
EBookings Encounter

Genie EBookings Encounter profile

EBookings Infection Risk

Magentus EBookings infection risk such as HIV or Hep-C.

EBookings PDF

EBookings PDF that is used to carry arbitrary PDF attachments for a booking.

EBookings Patient

EBookings Patient profile that enforces a residential address

EBookings Practice Healthcare Service

Healthcare service that is offered by a specialist practice. It covers additional service information not covered by the organisation details, specifically clinical specialities. This can only be a contained resource within a practice Organization resource

EBookings Prosthesis Device

Genie EBookings Prosthesis Device profile

EBookings Related Person

Magentus EBookings Related Person profile used for emergency contact as the next of kin. If applicable, the next of kin and emergency contact codes should be used alongside the coding of the relationship, e.g. mother.

EBookings ServiceRequest

EBookings ServiceRequest Profile

EBookings Theatre List

EBookings theatre list that defines a snapshot of bookings/appointment at a point in time. This will have a status of draft or final. The theatre list may be shared with participants of the appointment or beyond. All listed bookings should be contained copies at the point in time at which the theatre list was created.

EBookings VMO

EBookings VMO core profile

EBookings VMO Organization

EBookings VMO Organization core profile

EOrders Allergy Intolerance

Genie Solutions EOrders Allergy Intolerance describing allergies relevant to supporting clinical information for diagnostic requests. We assume these are active and current allergies.

EOrders Booking HealthcareService

EOrders HealthcareService profile containing service name and location reference.

EOrders Booking Location

EOrders Location profile containing the physical address where services are provided.

EOrders Booking Schedule

EOrders Schedule profile that links to HealthcareService. The Schedule organizes slots for a particular service.

EOrders Booking Slot

EOrders Slot profile for appointment scheduling. Contains the appointment time and links to Schedule resource.

EOrders Communication Request Patient

EOrders diagnostic provider to patient communication. This is only used when preventing communication by the lab/service to the patient, primarily for SMS and email. Typically this is the result of a Do not SMS or Do not email appearing in the clinical UI. Note that this has implications for how a diagnostic request is provided to the patient. If communication via electronic means is restricted, the clinician should always print the corresponding request for the patient.

EOrders Communication Request Provider

EOrders communication request to a clinical provider for the purpose of directing urgent results. This is used when the requesting clinician requires urgent contact relating to the results of a request. The request should be marked as 'urgent' to match the 'urgent' communication request. The profile currently only supports Fax and Phone methods.

EOrders Communication Request Task

EOrders Communication Request Task. This is used to track how a CommunicationRequest was fulfilled. For example, it would indicate if a Practitioner urgent results CommunicationRequest was successful or not.

EOrders CommunicationRequest CopyTo

Copy the imaging report to another recipient within the organisation. The report may or may not be directed to that organisation.

EOrders Consent Withdrawl

EOrders Withdraw Consent to upload result to MHR. It should be noted that this resource links to the relevant ServiceRequests rather than being referenced from the request itself. This means searches looking to include optional Consent information must add in a reverse include parameter to the search.

MHR consent withdrawals should only be included for countering the policy position that diagnostic reports should be uploaded to MHR by default.

EOrders Copy-To Organization

A profile for representing organization details in the context of a 'copy-to' recipient for diagnostic results. This profile supports the fields captured by Australian clinical systems including Genie and Gentu for address book entries, including HPI-O and address.

EOrders Copy-To Practitioner

A profile for representing practitioner details in the context of a 'copy-to' recipient for diagnostic results. This profile supports the fields captured by Australian clinical systems including Genie and Gentu for address book entries.

EOrders Copy-To PractitionerRole

A profile for representing practitioner role details in the context of a 'copy-to' recipient for diagnostic results. This profile supports the fields captured by Australian clinical systems including Genie and Gentu for address book entries, including secure messaging endpoints and communication preferences.

Examples of this profile are included as contained resources in diagnostic request examples, and a reference to the contained PractitionerRole is used in the result copies-to extension on diagnostic requests. This allows for the inclusion of rich practitioner role information for result recipients, including secure messaging identifiers, while maintaining compatibility with existing systems that may only support a display name for copies-to recipients. See Diagnostic Request, Pathology Request, and Radiology Request profiles and examples for usage of this profile in the context of diagnostic requesting.

EOrders Coverage

EOrders Coverage profile is primarily used to carry payment method codes. Note that this is limited to four types: self funded, bulk billed, concession, and DVA. This should be treated as a requested funding type and not necessarily mandatory for the request to be successful.

EOrders Diagnostic Request

This Diagnostic request profile that should be considered legacy. The Radiology request profile and the Pathology request profile should be used in lieu of this profile.

EOrders Encounter

Minimum Genie Encounter profile for EOrders Diagnostic Request. The sole use at present is to specify that the request is community diagnostic request, i.e. ambulatory, to distinguish it from possible future support for in-patient/hospital diagnostic requesting.

EOrders Medication Statement

Genie Solutions EOrders Medication Statement describing medications relevant to supporting clinical information for diagnostic requests. This is typically current medications.

EOrders Pathology Request

Pathology request leveraging the abstract diagnostic request profile. This Pathology request profile and the Radiology request profile should be used in lieu of the legacy Diagnostic request profile.

EOrders PractitionerRole

EOrders PractitionerRole profile. Adds in identifiers unique to eOrders.

EOrders PractitionerRole Contact

This profile supports a PractitionerRole with communication contact details in the context of Diagnostic Requests

EOrders Radiology Request

Radiology request profile leveraging the abstract diagnostic request profile. This Radiology request profile and the Pathology request profile should be used in lieu of the legacy Diagnostic request profile.

EOrders Registry Claim Provenance

Provenance to track the claim of an EOrder

EOrders Registry Transfer Provenance

Provenance to track the transfer of an EOrder

EOrders Task Fulfillment Request

EOrders Task Fulfillment Request Profile that is associated with each individual request. We also refer to these as child tasks as they are linked to an identified group task thorugh the partOf attribute. Be sure to read the note on the base profile for Task fulfilment that ensures that status, statusReason, and businessStatus are all updated correctly every time a status changes.

EOrders Task Fulfillment Request Group

EOrders Task Fulfillment Request Group Profile. Group tasks do not link to a request but rather represent the collection of fulfilments required to complete the order. The group can carry a child task count to aid accuracy of child task discovery. New order searches should base their discovery on group tasks identified through the group tag.

Genie ChargeItem Base

Genie ChargeItem Base profile

Genie Coverage

Genie Coverage core profile

Genie Estimated Date of Delivery

This profile sets minimum expectations for an Observation resource to record, search, and fetch observations of estimated date of delivery (EDD) related to pregnancy with standard coding. It is based on the core FHIR Observation resource and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Observation resource when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.

Genie Gestational Age

This profile sets minimum expectations for an Observation resource to record, search, and fetch observations of gestational age by scan, or gestational age by last menstrual period (LMP) with standard coding and units. It is based on the core FHIR Observation resource and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Observation resource when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.

Genie HealthcareService

Genie HealthcareService core profile

Genie Hormone Replacement Therapy Flag

This profile sets minimum expectations for an Observation resource to record, search, and fetch observations of hormone replacement therapy flags with standard coding and units. It is based on the core FHIR Observation resource and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Observation resource when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.

Genie Invoice

Genie Invoice profile

Genie Last Menstrual Period

This profile sets minimum expectations for an Observation resource to record, search, and fetch observations that represent the date of a patient’s last known menstrual period at a point in time with standard coding and value. It is based on the core FHIR Observation resource and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Observation resource when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.

Genie Location

Genie Location core profile

Genie Organization

Genie Organization core profile

Genie Patient

Genie Patient core profile

Genie Payment Basic Resource

Genie Invoice Payment Basic Resource profile

Genie Practitioner

Genie Practitioner core profile

Genie PractitionerRole

Genie PractitionerRole core profile

Magentus Imaging Study

Imaging study to carry the date images were scanned.

Pathology Report

Pathology Report

Radiology Report

Radiology report based on a common report base and including an imaging study date.

Referral Fulfilment Task

Referral fulfilment task complted by the PMS as a referral is processed.

Referral Request

Magentus Referral Request for a clinical referral to a specialist.

eOrders Organisation Diagnostic Parent

An extension of the Genie Organization resource to represent a diagnostic parent organisation. These are defining the hierarchy of Organizations where a parent organisation may cover a number of brand Organizations. Fillers can choose to discover new orders based on individual Task.owner brands or instead discover orders based on the Task.owner part-of relationship.

eOrders Organisation Imaging Service

An extension of the Genie Organization resource to represent an imaging service. The imaging service must be linked to a parent Organization.

eOrders Organisation Pathology Laboratory

An extension of the Genie Organization resource to represent a pathology laboratory. The lab must be linked to a parent Organization.

eOrders Submit Order Transaction Bundle

A transaction Bundle profile for submitting a diagnostic order (pathology or imaging/radiology). This bundle contains the full set of resources required to create an order, including the patient, requesting practitioner, organisation, service requests, fulfillment tasks and optional consent, coverage, communication and filler organisation resources.

The bundle must be of type transaction and contain at minimum:

  • A Patient resource
  • At least one Organization resource (requesting organisation, and optionally filler brand organisations)
  • A requesting Practitioner resource
  • A requesting PractitionerRole resource
  • At least one diagnostic ServiceRequest (EOrdersDiagnosticRequest, EOrdersPathologyRequest or EOrdersRadiologyRequest)
  • A fulfillment group Task (EOrdersTaskFulfillmentGroup)
  • At least one fulfillment request Task per ServiceRequest (EOrdersTaskFulfillmentRequest)

Optional entries include consent withdrawals, communication requests, communication request tasks and filler brand organisations.

Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

Australian Hospital Provider Number

Australian Hospital Provider Number profile

EOrders ArgusConnect Identifier

Identifier for ArgusConnect secure messaging endpoint in the context of EOrders Copy-To PractitionerRole profile. This information may be available from the PMS address book.

EOrders Doctor Number

Genie EOrders Doctor Number profile. These identifiers are allocated by pathology providers to give explicit direction to the filler for how a practice or practitioner wants the report to be returned. A practitioner may have multiple doctor numbers for different delivery approaches. This is really a legacy feature that should not be needed if guidance in CommunicationRequests carries such information.

EOrders Healthlink Identifier

Identifier for Healthlink secure messaging endpoint in the context of EOrders Copy-To PractitionerRole profile. This information may be available from the PMS address book.

EOrders Medical Objects Identifier

Identifier for Medical Objects secure messaging endpoint in the context of EOrders Copy-To PractitionerRole profile. This information may be available from the PMS address book.

EOrders Placer Group Number

EOrders Placer Group Number profile. This is the main barcode used to identify all parts of a diagnostic order/request.

EOrders ReferralNet Identifier

Identifier for ReferralNet secure messaging endpoint in the context of EOrders Copy-To PractitionerRole profile. This information may be available from the PMS address book.

Genie Organization Local Identifier

Genie Organization local identifier profile

Genie Practice Local Identifier

Genie Practice local identifier profile

Genie Practitioner Local Identifier

Genie Practitioner local identifier profile

Genie PractitionerRole Local Identifier

Genie PractitionerRole local identifier profile

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

ChargeItem Category

ChargeItem Category Extension

Count of Sub-Tasks for a Group Task

Count of Sub-Tasks for a Group Task. Note that this should include both CommunicationRequest Tasks and ServiceRequest Tasks.

Diagnostic Request Display Sequence

A display sequence number for an individual test/service that matches the sequence as seen on a paper order form. This more easily allows for reconciliation of paper and digital requesting data by the filler. Sequence numbers do to need to be contiguous and sequence is low to high.

Diagnostic Request Rule 3 Exemption

Extension to request rule 3 exemption. This is currently a placeholder for more extensive Rule 3 Exemption support that will need to support multiple request fulfilment and the timing of fulfilment.

Digital Only

Indicates that the diagnostic request is digital only and will not have a paper copy. This is important for fillers to know when deciding their SMS notification strategy for new requests.

EBooking Difference Addition

Additional resource added to the theatre booking

EBooking Difference Deletion

Removed resource from the theatre booking. Must be a string as the resource doesn't exist anymore and referential integrity is not possible.

EBooking Difference Modification

Resource modified in the theatre booking

EBookings Appointment lastModified Extension

The lastModified extension should be updated for every meaningful change to an appointment or its network of linked resource. This enables a hospital to subscribe to Appointment changes to pick up Appointment changes.

EBookings Fasting Time Element

EBookings Fasting Time Element

EBookings Fasting Time Precondition

EBookings Fasting Precondition for ServiceRequest, indicating the fasting time requirement for a procedure.

EBookings Theatre List Hospital Extension

Theatre list hospital.

EBookings Theatre List Period Extension

Theatre list period.

EBookings Theatre List Status Extension

Theatre list status.

EBookings Theatre List VMO Extension

Theatre list VMO.

Invoice Item Balance

Invoice Item Balance Extension

Invoice Item Payment

Invoice Item Payment Extension

Organization Test List Extension

Test List Extension for Organization. This directly references the ValueSet that holds the test list.

Payment Date

Payment Date Extension

Payment Gross Amount

Payment Gross Amount Extension

Payment Invoice

Payment Invoice Extension

Payment Invoice Line Item

Payment Invoice Line Item Extension

Payment Method

Payment Method Extension

Preferred Contact Method

The practitioner's preferred method of communication for receiving results and correspondence. Can indicate a secure messaging system (via identifier) or a telecom contact type.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

ADA Dental Terms ValueSet

An Australian Glossary of Dental Terms was first published by the Australian Dental Association (ADA) in 1986. The Fifth Edition was expanded to The Australian Schedule of Dental Services and Glossary (the Schedule) in 1996. Since its inception, it has been universally accepted as the definitive coding system of dental treatment across the sector. The Australian Classification of Health Interventions (ACHI) Dental Services chapter is based on the most recent edition (at the time of development) of ADA's The Australian Schedule of Dental Services and Glossary.

Add Placer Subscription Result ValueSet

Result codes for the add placer subscription operation.

Brand Service Type ValueSet

Value set for filtering brand organizations by service type.

EBookings Body Side ValueSet

EBookings Body Side ValueSet

EBookings Consent Status ValueSet

EBookings Consent Status ValueSet.

  1. Consent agreed and attached: This will have the consent document attached and a status of #active.
  2. Consent to be provided on day of theatre: This will have a status of #proposed, no attachment, and the consent document will be provided on the day of theatre.
  3. No consent decision made: This will have a status of #draft and no consent document is provided.
EBookings Encounter Class ValueSet

EBookings Encounter Class ValueSet

EBookings Location Code ValueSet

EBookings Location Code ValueSet

EOrders Communication Request Category

EOrders Communication Request Category

EOrders Communication Urgent Medium codes

Codes for urgent Diagnostic Communication Request from filler back to the clinician

EOrders Coverage Type and Self Pay codes

EOrders Coverage Type and Self Pay codes

EOrders Placer Tag Value Set

EOrders Placer Tag Value Set

EOrders Priority codes

EOrders Priority codes

EOrders Service Request Category codes

EOrders Service Request Category codes

EOrders Service Request Intent codes

EOrders Service Request Intent codes. For diagnostic requesting, this will always be order but for an order created by the filler, it should be filler-order. These filler orders may be included as output in a fulfilment Task. See Fulfilment Task Base

EOrders Service Request Status codes

EOrders Service Request Status codes. Normally active but may be moved to revoked if request cancelled.

EOrders Task Status codes

EOrders Task Status codes

EOrders Task codes

EOrders Task codes

EOrders claimed tag value set

EOrders claimed tag value set

EOrders communication medium values

EOrders communication medium values

EOrders reason codes ValueSet

EOrders reason codes ValueSet. This is not complete nor extensive and is used to support existing PMS behaviours.

EOrders tag value set

EOrders tag value set

Genie Anaesthetic type ValueSet

Genie Anaesthetic type ValueSet

Genie ChargeItem Category ValueSet

Genie ChargeItem Category ValueSet

Genie Coverage Status values

Genie Coverage Status values

Genie Coverage Type and Self Pay codes

Genie Coverage Type and Self Pay codes

Genie DVA Entitlement ValueSet

Genie DVA Entitlement ValueSet

Genie Invoice Type ValueSet

Genie Invoice Type ValueSet

Genie Payment Method ValueSet

Genie Payment Method ValueSet

Healthcare Specialty Target Codes

ValueSet containing all target healthcare specialty SNOMED CT codes from the ANZSCO to Healthcare Specialty ConceptMap. Codes are sourced from multiple clinical specialty classifications including Clinical-Specialty-1.0.0, Snomed_Service_ValueSet, C80 Practice Codes, and EBookings specialty codes.

Preferred Contact Method Value Set

Methods of communication for result delivery, including secure messaging systems and traditional contact methods.

Request Claim Result Type ValueSet

Request Claim Result Type ValueSet

Theatre list status valueSet

Theatre list status valueSet

eOrders Task Business Status

eOrders Task Business Status ValueSet

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

ADA Dental Terms

An Australian Glossary of Dental Terms was first published by the Australian Dental Association (ADA) in 1986. The Fifth Edition was expanded to The Australian Schedule of Dental Services and Glossary (the Schedule) in 1996. Since its inception, it has been universally accepted as the definitive coding system of dental treatment across the sector. The Australian Classification of Health Interventions (ACHI) Dental Services chapter is based on the most recent edition (at the time of development) of ADA's The Australian Schedule of Dental Services and Glossary.

Add Placer Subscription Result CodeSystem

Result codes for the add placer subscription operation.

Brand Service Type CodeSystem

Code system for filtering brand organizations by service type.

CommunicationRequest Reason

Reason codes for a communication request used in the Australian context.

Copy To Identifier Code System

Code system for copy-to identifiers including secure messaging endpoints

EOrders Placer Tag Code System

EOrders Placer Tag Code System

EOrders Registry Claim CodeSystem

CodeSystem for EOrders Registry Claim Provenance

EOrders reason local codes CodeSystem

EOrders reason local codes CodeSystem. This is not complete nor extensive and is used to support existing PMS behaviours.

EOrders tag code system

EOrders tag code system

Genie Anaesthetic type CodeSystem

Genie Anaesthetic type CodeSystem

Genie Basic Resource Types

Genie Basic Resource Types

Genie ChargeItem Category CodeSystem

Genie ChargeItem Category CodeSystem

Genie Invoice Type CodeSystem

Genie Invoice Type CodeSystem

Genie Payment Methods

Genie Payment Methods

Genie Systems local identifier types

Genie Systems local identifier types to expose Organization, Practitioner, and PractitionRole

Preferred Contact Method Code System

Code system for preferred contact methods including secure messaging endpoints

Request Claim Result Type CodeSystem

Request Claim Result Type CodeSystem

Theatre list Status CodeSystem

Theatre list status codesystem

eOrders Task Business Status CodeSystem

eOrder Task Business Status CodeSystem

Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming to this implementation guide.

DICOM NamingSystem

NamingSystem for DICOM

ElectronicHealth NamingSystem

NamingSystem for ElectronicHealth

HL7 AU NamingSystem

NamingSystem for HL7 AU

HealthGovAu NamingSystem

NamingSystem for HealthGovAu

Magentus NamingSystem

NamingSystem for Magentus

PrivateHealth NamingSystem

NamingSystem for PrivateHealth

RSNA NamingSystem

NamingSystem for RSNA

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Active account

Sample account instance where it only records active.

Diagnostic Imaging Report Transaction

Inbound Diagnostic Imaging Report Transaction

Diagnostic Pathology Request Transaction

Diagnostic Pathology Request Transaction - Genie Generated example

EBookings Anaesthetic Request Example

EBookings Anaesthetic Request Example

EBookings Consent - Active with attachment URL

EBookings Consent - Active with consent form URL

EBookings Consent Active, permit transfusion

EBookings Consent Active, permit transfusion - no attachment

EBookings Consent Proposed

EBookings Consent Proposed

EBookings Create Booking Transaction

EBookings Create Booking Transaction

EBookings PDF Example

Example of an EBookings PDF attachment that might be added to a booking.

EBookings Prosthetic Example

EBookings Prosthetic Example

EBookings SearchSet Bundle Example

EBookings SearchSet Bundle example

EBookingsAppointmentExample

Example of a theatre appointment.

EBookingsAppointmentResponseExample

Example of a booking request response from the hospital.

EBookingsChargeItemAssistant

Example of a charge for an assistant to an operation.

EBookingsChargeItemCustomCode

Example of custom code for a ChargeItem.

EBookingsChargeItemDescriptionOnly

Example of a custom ChargeItem with only a description.

EBookingsChargeItemKneeReplacement

Example of a charge for a knee replacement operation.

EBookingsEncounterSoreStomach

Example of a theatre booking encounter where the booking was established.

EBookingsServiceRequestExample

Example of a ServiceRequest specifying the surgery to be performed in the theatre booking.

EBookingsVMOTrevorWright

Example PractitionerRole binding a Practitioner to an Organization.

EOrders Allergy Intolerance - Erythromycin Example

Example of EOrders Allergy Intolerance profile showing Erythromycin allergy with rash reaction from Genie data.

EOrders Allergy Intolerance - No Known Allergy Example

Example of EOrders Allergy Intolerance profile showing no known allergy from Genie data.

EOrders Allergy Intolerance - Penicillin Example

Example of EOrders Allergy Intolerance profile showing Penicillin allergy with anaphylactoid reaction from Genie data.

EOrders Booking Slot Example

Example of an EOrders Booking Slot resource that could be referenced in the output of an EOrders Task Fulfillment resource. The Slot references a Schedule that references a HealthcareService that could be referenced in the output of an EOrders Task Fulfillment resource.

EOrders Coverage Example

EOrders Coverage Example

EOrders Diagnostic Request

EOrders Diagnostic Request example

EOrders Encounter Example

EOrders Encounter Example

EOrders Medication Statement - Crestor Example

Example of EOrders Medication Statement profile showing current Crestor prescription from Genie data.

EOrders Medication Statement - Eliquis Example

Example of EOrders Medication Statement profile showing current Eliquis prescription from Genie data.

EOrders Medication Statement - Forxiga Example

Example of EOrders Medication Statement profile showing current Forxiga prescription from Genie data.

EOrders Pathology Request

EOrders Pathology Request example

EOrders PractitionerRole Contact

EOrders PractitionerRole Contact

EOrders Radiology Request

EOrders Radiology Request example

EOrdersCommunicationRequestDoNotSendSMS

Diagnostic Communication Request Do Not Perform SMS

EOrdersCommunicationRequestUrgentFax

EOrders Communication Request Urgent Fax

EOrdersCommunicationRequestUrgentPhone

EOrders Communication Request Urgent Phone Call

EOrdersCoverageMarySmith

Example of eOrders Coverage.

EOrdersRegistryClaimProvenanceInstance

Provenance to track the claim of an EOrder to a filler through Task.owner

EOrdersRegistryTransferProvenanceInstance

Provenance to track the allocation of an EOrder to a filler through Task.owner

EOrdersTaskCommunicationRequestDoNotPerformSMS

Communication Request Task Do Not Perform SMS

EOrdersTaskCommunicationRequestUrgentPhone

EOrders Communication Request Task Urgent Phone Call

Estimated Date of Delivery

Estimated Date of Delivery

Example Diagnostic Parent Organisation

An example of a diagnostic parent organisation.

Example Imaging Service

An example of an imaging service organisation.

Example Imaging Study

Example Imaging Study

Example Pathology Laboratory

An example of a pathology laboratory organisation.

Example of ChargeItem

Example instance of ChargeItem that might be part of a Theatre Booking difference.

Example of a successful response from the $view operation

This example of a $view output provides the request information and the fulfilment data from a single filler.

Example of an invoice

Example of an invoice.

GSHRTExample

An example instance of a Hormone Replacement Therapy Observation

GSHealthcareServiceAshfordPrivateHospital

Example hospital as participant in theatre booking.

GSOrganizationJonathanportPractice

Example practice that would be instigating a theatre booking.

GSPaymentExample

Example payment information.

GSPractitionerRoleTrevorWright

Example PractitionerRole binding a Practitioner to an Organization.

GSPractitionerTrevorWright

Example of a practitioner to be performing surgery.

Genie ChargeItem Example

Genie ChargeItem Example

Gestational Age

Gestational Age

Imaging Report Patient

Imaging Report Patient

Instance of EBookingsAdverseReaction

Example instance of EBookingsAdverseReaction

Instance of EBookingsDifference

Example instance of EBookingsDifference

Instance of EBookingsInfectionRisk - HIV

Example instance of EBookingsInfectionRisk for HIV

Instance of EBookingsInfectionRisk - Hepatitis B

Example instance of EBookingsInfectionRisk for Hepatitis B

Instance of EBookingsInfectionRisk - Hepatitis C

Example instance of EBookingsInfectionRisk for Hepatitis C

Instance of EBookingsInfectionRisk - MRSA

Example instance of EBookingsInfectionRisk for MRSA

Instance of EBookingsRelatedPerson

Example instance of EBookingsRelatedPerson

Instance of EBookingsVMOOrganization

Example instance of EBookings VMO Organization which contains the practice healthcare service.

Last Menstrual Period

Last Menstrual Period

Magentus Location Example

Magentus location example.

Pathology Report

Pathology Report

Pathology Report Organization

Pathology Report Organization

Pathology Request Bundle Example

Diagnostic Pathology Request Bundle example

Pathology Request with Rule 3 Exemption

Pathology Request with Rule 3 Exemption

PathologyRequestTask

Example of an assigned Task for a pathology request.

ReferralPatient

Example patient who is the subject of a referral.

ReferralPerformerIndividual

An individual practitioner who is the nominated filler for a referral.

ReferralRequestExample

Example of a specialist referral.

ReferralRequester

Practitioner who requested the referral.

ReferralRequesterOrganization

Example organization for a practitioner creating a referral.

ReferralRequesterPractitioner

Requester practitioner identity for a referral creator.

ReferralTaskExample

Example of a specialist referral fulfilment task.

Sample EOrders Task Status Patch

EOrders Task status PATCH to update fulfilment of an order. This makes all Tasks received and removes any businessStatus or statusReason attributes if they are set.

Sample EOrders Task Status Patch

EOrders Task status PATCH to update fulfilment of an order. This makes all Tasks accepted, and removes any businessStatus or statusReason attributes if they are set.

Sample Patient

Sample patient.

Sample Patient Bob Smith

Sample patient Bob Smith.

Sample eRequest

Sample eRequest.

Submit Order Response — Directed Order Success

Example transaction-response Bundle returned by the $submit_order operation when all fulfillment Tasks have an owner and the order is successfully processed against the filler partition.

Each entry mirrors the corresponding entry in the submitted transaction Bundle and carries a response element with the HTTP status and assigned server URL.

Submit Order Response — Error

Example OperationOutcome returned by the $submit_order operation when the submitted Bundle fails validation or cannot be processed. The caller should not retry without correcting the reported issues.

Submit Order Response — Undirected Order

Example OperationOutcome returned by the $submit_order operation when all fulfillment Tasks in the submitted Bundle have no owner. The order has been lodged as an undirected order and will be routed to a filler partition later. This is not an error; no corrective action is required by the caller.

Theatre List of Appointment Entries

Theatre List of Appointment Entries.

eOrders Consent withdraw upload MHR

eOrders Consent to indicate do not upload to MHR

eOrders Consent withdraw upload MHR FBC LFT

eOrders Consent to indicate do not upload to MHR

eOrders Create FBC LFT Laboratory Request Transaction

eOrders Create Laboratory Request Transaction with multiple coded tests (FBC LFT), fulfillment task group and 'do not send SMS' CommunicationRequest

eOrders Create Order Transaction

eOrders Create Order Transaction with text ServiceRequest and Task

eOrders FBC LFT Fulfillment Task Group

Example of a Task group for a combination of FBC and LFT pathology tests.

eOrders Organization Acme Filler

Example of a filler Organization.

eOrders Organization Other Filler

Example of a filler Organization.

eOrders Organization Placer

Example of a placer Organization.

eOrders Pathology Request FBC

Example of a pathology request for a Full Blood Count.

eOrders Pathology Request LFT

Example of a Liver Function Test as a pathology request.

eOrders Pathology Request Task FBC

Example of a Full Blood Count diagnostic request.

eOrders Pathology Request Task LFT

Example of a Liver Function Test as a diagnostic request.

eOrders Pathology Request text

eOrders Pathology Request - free text test name

eOrders Practitioner Placer

Example placer Practitioner.

eOrders PractitionerRole Placer

Example placer PractitionerRole binding a Practitioner to an Organization.