Site search

Electronic Prescribing Frequently Asked Questions covering topics such as Prescribing Systems, Dispensing Systems, Mobile Applications, Mobile Intermediaries, Transitional eNRMC and Conformance Profile 3.0 and more. 

This guide will discuss potential changes which are required in your software.

This guide will walk through the steps to create and upload clinical documents

This Developer Guide is for the use of developers whose products connect to the Healthcare Identifiers (HI) Service, My Health Record, Electronic Prescribing and Secure Messaging with a National Authentication Service for Health (NASH) PKI Certificate.

OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.

In this guide, we will be accessing Prescription and Dispense List and Allergies List contained in a patient’s clinical document service

This document describes the structured document template for a prescription request, from a clinical communication perspective. This specification references or contains excerpts of intellectual property (IP) owned by the Regenstrief Institute, IHTSDO, or HL7 International. Applicable IP constraints apply: This material contains content from LOINCTM …

This document summarises the functional and non-functional requirements for software that acts as infrastructure in electronic prescribing. This document lists the specific conformance requirements for Prescription Delivery Services and Active Script List Registry Services that must or should be met to support participation in electronic prescribing. These…

This document describes the structured document template for a prescription request, from a clinical communication perspective. This specification references or contains excerpts of intellectual property (IP) owned by the Regenstrief Institute, IHTSDO, or HL7 International. Applicable IP constraints apply: This material contains content from…

This guide will use the My Health Record getView web service to download collated information from a My Health Record in a ‘View’

This document provides a guide to implementing the 'logical' model detailed by the eHealth Prescription and Dispense View Structured Content Specification as an HL7 Clinical Document Architecture Release 2 (CDA) XML document. The guide contains descriptions of both constraints on the CDA and, where necessary, custom extensions to the CDA, for the purposes…

The National Requirements for Electronic Prescriptions provide a set of key principles for a safe system to support prescribing and dispensing of prescriptions in the electronic environment within the relevant legislative framework.

The Australian Digital Health Agency aims to increase the adoption of the My Health Record by connecting the My Health Record platform to mobile applications through industry-standard APIs.

Each software developer needs to consider the jurisdictions they think their software will operate in and consider the legal obligations for those jurisdictions. Software developers are responsible for contacting their relevant state and territory regulation authorities to attain this information. This document has been developed and is maintained by the…

This document provides a guide to implementing the 'logical' model detailed by the Agency's PCEHR Prescription and Dispense View Structured Content Specification as an HL7 Clinical Document Architecture Release 2 (CDA) XML document. The guide contains descriptions of both constraints on the CDA and, where necessary, custom extensions to the CDA, for the…

Each software developer needs to consider the jurisdictions they think their software will operate in and consider the legal obligations for those jurisdictions. Software developers are responsible for contacting their relevant state and territory regulation authorities to attain this information. This document has been developed and is maintained by the…

eHealth Prescription and Dispense View documents represent an electronic summary of information about medication prescriptions and dispensations contained in an individual’s My Health Record. NOTES The Conformance Test Specification for PCEHR Views provides conformance tests for implementing eHealth Prescription and Dispense View and is available in…

Software products must pass testing requirements before gaining access to the My Health Record production system.

This release introduces updates to the conformance profile for eHealth Prescription and Dispense View documents, as mandated by approved change request CCB-0314. This change request mandated that the rendering of eHealth Prescription and Dispense View documents conforms to the PCEHR Prescription and Dispense View Presentation Guide, in alignment with advice…

The following steps will assist software developers who provide open Prescription Delivery Service (PDS) and/or Active Script List Registry capabilities to declare software conformance with the Agency’s Electronic Prescribing technical framework.

The following steps will assist prescribing and dispensing Clinical Information System (CIS) software developers connect to the national Prescription Delivery Service (PDS) and declare software conformance with the Agency’s Electronic Prescribing technical framework.

We will use the token received from MyGov to access the patient’s My Health Record