Quick intro

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 following process will assist mobile intermediary system software developers to connect to Open PDS and/or ASLR Services and declare software conformance with the Agency’s electronic prescribing technical framework. 

1: Connect with a PDS and/or ASLR

A mobile intermediary system may connect to either Open PDS or ASLR Services or both. 

Please contact the Open PDS and/or ASLR Service provider to gain access to test environments and interface technical specifications to connect to their service. Contact details are available below. 

Open PDSeRX Script Exchange E: [email protected]  
ASLR ServicesMy Script ListE: [email protected]

2: Develop your product

Within the Technical Framework Documents, identify the requirements that apply to your product in the Electronic Prescribing – Conformance Profile.

To assist your development and testing, refer to the Electronic Prescribing –Conformance Test Specifications (CTS) and test data. 

Commence developing your product using the interface technical specifications and test environment provided by the PDS and/or ASLR Services provider.

3: Conduct internal testing

Conduct a self-assessment against the applicable requirements and your own internal testing. 

4: Complete the Conformance Test Specification

Complete the CTS and submit to the PDS and/or ASLR Services provider.

Please ensure the CTS for your product is completed in full, with:

  • the relevant test outcomes (pass, fail, N/A) recorded against each test case
  • a corresponding reason documented for any test marked as N/A 
  • completed Test Summary Report worksheet
  • relevant evidence for each test outcome including screenshots, recordings, documentation or other.

5: Conduct conformance assessment

Your PDS or ASLR Services provider will conduct your conformance assessment observation session. 

The purpose of this session is to verify the results recorded in your submitted CTS and validate any further information requested by your PDS or ASLR Services provider. 

Your PDS or ASLR Services provider will help you determine if you are ready to undergo observation and will schedule the session at a mutually agreed time.

In addition to your observed conformance assessment, your PDS or ASLR Services provider may request further evidence for specific test cases to ensure the record of the test is full and accurate.

6: Declare conformance

Complete the Electronic Prescribing – Conformance Vendor Declaration form after the observed conformance assessment is successfully completed. Email your form to [email protected]. Please ensure that:

  • you have completed all relevant information, such as inclusion of companion software details in section 1.3. Companion software may include PDS adaptor(s), workflow engine(s), mobile gateway(s), etc.
  • you include the name of the Open PDS your software product is integrated with in the ‘Connection name’ field, if applicable (e.g. eRx). 
  • you include the name of the ASLR your software product is integrated with in the ‘Connection name’ field, if applicable (e.g. Medication Knowledge).
  • the information in the form matches the information in the Test Summary Report tab in the final CTS.

7: Deploy updated product

Once you have received a notification that your product has been included on the list of conformant products, you may commence deploying electronic prescribing functionality into production.


You should now be able to gain conformance with the Agency’s electronic prescribing technical framework for your mobile intermediary. If you need any further assistance, please contact [email protected].