Quick Intro
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.
If your product will support Electronic Prescribing, please be familiar with the conformance process:
Step 1: Connect to an Open Prescription Delivery Service (PDS)
To connect your product to the Open PDS, please contact the Open PDS provider listed below. Your provider will make available specifications and test environment access to enable you to develop and test your product.
| Delivery Services | ||
| Open PDS | eRX Script Exchange | E: [email protected] |
| Active Script List Register | Medication Knowledge | E: [email protected] |
Step 2: Develop Your Product
Review the Electronic Prescribing Conformance Profile here:
Identify the applicable requirements/conformance points that apply to your product. Each requirement identifies if it is applicable to an Open PDS model. Applicable requirements have a “yes” in the “open PDS” column. Where “No” appears in the “Open PDS” column, it means the requirement is not applicable.
If your product is connecting to an open medication chart PDS, the applicable conformance requirements are marked with “yes” in the “Med charts Open PDS” column.
Conformance Test Specifications and test data are available to assist your development and testing here:
Using the specifications and test environment access provided by your PDS provider commence developing your product.
Note:
Please ensure you check the specific requirements of the states and/or territories in which you intend to release your product. Some states and territories have established approval criteria software developers must meet prior to deployment. Details available here:
Step 3: Conduct Internal Testing
Conduct a self assessment against the applicable requirements/conformance points and your own internal testing.
Step 4: Complete the Conformance Test Specification
Complete the Electronic Prescribing Conformance Test Specification (CTS) and submit to the Open PDS Provider unless your product is owned (fully or partially) by the Open PDS (or vice versa) listed, in that case submit to the Australian Digital Health Agency.
Please ensure the CTS for your product, 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 (TSR) worksheet
- relevant evidence for each test outcome including screenshots, recordings, documentation or other.
Step 5: Conduct Conformance Assessment
The Open PDS Provider will conduct your Conformance Assessment observation session unless your product is owned (fully or partially) by the Open PDS (or vice versa) listed, in that case the Australian Digital Health Agency will conduct your observed tests.
The purpose of the observed Conformance Assessment is to verify and confirm the results recorded in your submitted Conformance Test Specification (CTS) and validate any further information requested by the Open PDS provider.
The PDS provider will inform you if you are ready to undergo observation and will schedule the session at a mutually agreeable time.
During and following your observed Conformance Assessment, the PDS provider may request further evidence for specific test cases to ensure the record of the test is full and accurate.
Step 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 (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.
Note: The Conformance ID requested in the form is a string of no more than 36 printable characters containing a text string representing the product name, a single character delimiter (“|”) and an alphanumeric string representing the software product version. As the Conformance ID may help with issue identification and is used to manage participation, it is strongly advised that you declare accurate version information. It is, however, recognised that some software products update version information regularly and in response to changes that do not impact electronic prescribing functionality. For this reason, software vendors may ascertain for themselves the granularity of version information declared in the Conformance ID and the occasions at which it is declared.
If the Agency identifies any issues in your submission, then the Agency will inform you directly. Upon successful processing, you will be notified by the Agency directly and your product will be added to the register of conformance. This register is communicated by the Agency to Services Australia, State and Territory Health departments and PDS providers for operational purposes.
Step 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 and conduct associated training to your end users.
Conclusion
You should now be able to gain product conformance with the Agency’s Electronic Prescribing Technical Framework for your CIS product/s connecting to the Open PDS. If you need any further assistance please contact [email protected].