Site search

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…

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 walk through the process to get patient clinical documents from the My Health Record system and display them to your users using a generic style sheet

This guide will look at retrieving all clinical document data (including these 2, but excluding MBS documents)

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 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.

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 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.

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…

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…

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.

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

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

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

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

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

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…

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…

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 guide will describe the steps to remove a Clinical Document

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 provides an implementable technical interface specification for the document exchange services using IHE’s Cross-Enterprise Document Sharing-b (XDS-b) specification and accompanying bespoke web services.