Skip to main content

The following steps will assist software developers who wish to build products that support electronic prescribing.

The Agency offers a range of support services including consultative support and scheduled information sessions. If you require any support to understand the Agency’s conformance requirements or other technical specifications please contact [email protected].

Step 1: Gain HI Service conformance

Conformance to the Healthcare Identifier Service (HI) is a prerequisite for prescribing and dispensing systems to participate in electronic prescribing. If your product is not conformant with the HI Service, please develop this capability first. For instructions please go to the following page: 

If your product is already HI Service conformant please proceed to step 2. 

Step 2: Learn how Electronic Prescribing works

To gain an understanding of how electronic prescribing works, read the Electronic Prescribing Technical Framework documents located here:

The Conformance Test Specification is located here:

Once you have read these documents, proceed to step 3. 

Step 3: Identify your product type

Determine the functions your product will perform in the electronic prescribing process and if your product will need to connect to the National Prescription Delivery Service (NPDS) to enable end-to-end electronic prescription transactions.

To access capabilities provided in an Active Script List you will need to connect to the National PDS, this functionality is not available in a direct PDS model.

national-prescription-delivery-service-model-v1.png
National Prescription Delivery Service Model v1

Most prescribing and dispensing CIS products will connect to the NPDS.

Hospital CIS solutions may provide their own direct PDS solution.

You will need to complete the conformance process with the National Prescription Delivery Service (NPDS) and the Agency. The process will vary depending on the type of product you are developing. The average time required to complete the process with the Agency is currently 20 business days. This is in addition to the time required to develop your product, conduct your testing and self-assessment, and complete the observed testing session with the NPDS. An overview of the process steps, who performs each step, and the average time taken to complete is shown in the diagram.

Conformance process timeline

Conducted by Prescription Delivery Service (PDS)

Contact PDS provider to confirm timeframe.

2 to 4 business days

3 to 5 business days

1 to 2 business days

The Agency will advise PDS (and other relevant infrastructure operators) and Services Australia of conformance outcome. Conformance outcome registered in PBS online systems.

3 to 5 business days

Conducted by Prescription Delivery Service (PDS)

The Agency will also publish the updated conformance register on its website to conclude the conformance process.

3 to 5 business days

For detailed information on the conformance process for your product type, please select the relevant option:

No items created. No items created.No items created.No items created.No items created.

Developer guides

Electronic Prescribing - CIS to NPDS or ASLR

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

Electronic Prescribing - NPDS and ASLR

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

Electronic Prescribing - CIS with a Direct PDS

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.

NASH SHA-2 Certificates - Developer Guide

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.

Resources

eHealth Prescription Record v1.2.1

Product
EP-2689:2018
Version
1.2.1
Status
Active
eHealth prescription record documents can be used to share information about prescribed medications via the individual’s digital health record. Documents of this type do not represent actual prescriptions, but merely support the sharing of information about medication prescriptions via the individual’s digital health record.

Electronic Prescribing - Conformance Test Specifications v3.0.3

Product
EP-3726:2022
Version
3.0.3
Status
Active
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…

Electronic Prescribing - Declaration of Conformance v2.0

Product
EP-3757:2023
Version
2.0
Status
Active
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,…

Electronic Prescribing - State and Territory Legislative Readiness and Technical Requirements v2.3

Product
EP-3285:2020
Version
2.3
Status
Archived
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…

Electronic Prescribing - Technical Framework Documents v3.4

Product
EP-3880:2024
Version
3.4
Status
Active
These technical framework documents are provided to software vendors and demonstrate what is required to enable electronic prescribing. This release of the end-product EP-3880:2024 provides the following updates: DH-3878:2024 Electronic Prescribing – Prescription Delivery Services and Active Script List Registry Conformance Profile v3.1 replaces the…

Electronic Transfer of Prescription v1.1

Product
EP-0938:2010
Version
1.1
Status
Archived
ETP 1.1, published in December 2010, contributed to Standards Australia’s publication process, along with effort from the Agency subject matter experts working collaboratively within the IT-014 informatics community. On 20 May 2013, Standards Australia released Australian Technical Specification 4888.x for Electronic Transfer of Prescription …

eMedications Management Functional Framework v1.1

Product
EP-2121:2015
Version
1.1
Status
Active
The eMedications Management (eMM) Functional Framework outlines the key capabilities within medications management business systems. It can be used to identify opportunities and gaps in medications management process automation, system integration, information quality and terminology standardisation.

Pharmacist Shared Medicines List v1.1.1

Product
EP-2924:2020
Version
1.1.1
Status
Active
PSML documents help ensure the continuity of medicine management for consumers across different care settings. PSML documents allow pharmacists in both hospital and community pharmacy settings to record the outcome of consumer consultations regarding their current medications for upload to the My Health Record system. This specification references or…