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 update includes an editorial split to existing Electronic Prescribing - Conformance Profile v2.3 and v3.0.1 documents. There are no changes to the conformance requirements in each profile. Electronic Prescribing – Conformance Profile v2.3 will be replaced by the following products on their effective date (30 November 2023): Electronic…

This update includes an editorial split to existing Electronic Prescribing - Conformance Profile v2.3 and v3.0.1 documents. There are no changes to the conformance requirements in each profile. Electronic Prescribing – Conformance Profile v2.3 will be replaced by the following products on their effective date (30 November 2023): Electronic…

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.

The prescribe and dispense personas file contains a list of medical practitioners that may be a part of the electronic prescribing lifecycle.

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.

These test cases have been written against the specified requirements in the Electronic Prescribing - Software Conformance Profile v3.0.1 document.

This release of the end product EP-3726:2022 updates Conformance Test Specifications and test data for electronic prescribing software vendors. It also includes instructions for Transitional eNRMC software vendors. The test cases in the worksheets have been written against the specified requirements in the Electronic Prescribing Conformance Profile version…

The following steps will assist Clinical Information System (CIS) software developers with a direct Prescription Delivery Service (PDS), declare software conformance with the Agency’s Electronic Prescribing technical framework.

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

The Electronic Prescribing - Declaration of Conformance v2.0 has been developed in consultation with key participants in the Electronic Prescribing community to better address the requirements of the contemporary Conformance Assessment Scheme (CAS), and to clearly articulate vendor roles and responsibilities. It was redesigned as a form that can be filled,…

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 Australian Digital Health Agency (the Agency) has published a series of Electronic Prescribing (EP) Conformance Profiles (CP) with incremental increases in functionality.

The Australian Digital Health Agency provides the following documents relating to Electronic Prescribing. Software Vendor Welcome Pack In the welcome pack you will find the latest versions of the following: Notification of intent to operate as an Open Prescription Delivery Service or Active Script List Registry Service Developer contact list which outlines…

A mobile application or web-based application is used by a subject of care or carer to manage prescriptions and to present an electronic prescription token to a pharmacy.

The Electronic Prescribing - Declaration of Conformance v2.0 has been developed in consultation with key participants in the Electronic Prescribing community to better address the requirements of the contemporary Conformance Assessment Scheme (CAS), and to clearly articulate vendor roles and responsibilities. It was redesigned as a form that can be filled,…

This document summarises the functional and non-functional requirements for connecting system software that supports participation in electronic prescribing. This includes software used by: Authorised prescribers Authorised dispensers Subjects of Care (SoC), or their Agents, using mobile devices to access their prescriptions through URIs sent to them via…

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…

A mobile intermediary system is a software product that a mobile application uses to connect to, and interact with, Open Prescription Delivery Services (PDS) and/or Active Script List Registry (ASLR) Services. 

The Healthcare Provider Identifier-Organisation (HPI-O) Test Data file contains a comprehensive list of HPI-O test data for use by software vendors wishing to test their electronic prescribing functionality. This document is superseded by Electronic Prescribing - Test Data - Subject of Care, HPI-I and HPI-O v3.0.

The subjects of care test data file contains a comprehensive list of subjects of care (Patient) test data for use by  software vendors wishing to test their electronic prescribing functionality. This document is superseded by Electronic Prescribing - Test Data - Subject of Care, HPI-I and HPI-O v3.0.

The Electronic Prescribing developer contact list provides a list of key contacts that are useful for software developers throughout the development and implementation of electronic prescribing functionality.

The Individual Healthcare Identifier (IHI) Test Data file contains a comprehensive list of IHI test data for use by software vendors wishing to test their electronic prescribing functionality. This document is superseded by Electronic Prescribing - Test Data - Subject of Care, HPI-I and HPI-O v3.0.

The purpose of the solution architecture is to provide an overview of the architectural components of the end-to-end national electronic prescribing system. It reflects: the scope of the project as defined by the Electronic Prescribing Working Group (EPWG); agreed overarching principles of the project that have informed development of the architecture;…