XS SM MD LG XL XXL
Guide
DG-3084
Status
Active
Version
1.0
Created
Updated

Quick Intro

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.

If your product will not provide NPDS/ASLR functionality, please check the other options available here:

Step 1: Contact the Agency

Please contact [email protected] if you are developing National Prescription Delivery Service (NPDS) or Active Script List Registry (ASLR) functionality.

Step 2: Develop Your Product

Review the latest version of the Electronic Prescribing Conformance Profile within the Technical Framework documentation available here:

Identify the applicable requirements/conformance points that apply to your product. National Prescription Delivery Service System requirements are in section 3.1 of the Conformance Profile. Active Script List requirements are in section 3.2.

Each requirement identifies if it is applicable to the NPDS model. Applicable requirements have a “yes” in the “National PDS” column. Where “No” appears in the “National PDS” column, it means the requirement is not applicable.

Conformance Test Specifications and test data are available to assist your development and testing 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 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 Australian Digital Health Agency will conduct your Conformance Assessment observation session.

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 Australian Digital Health Agency.

You will be informed by the Australian Digital Health Agency if you are ready to undergo observation and will schedule the session at a mutually agreeable time. The observation session will be conducted with the NPDS and ASLR together to ensure interfacing functionality can be demonstrated.

During and following your observed Conformance Assessment, the Australian Digital Health Agency 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.
  • the information in the form matches the information in the Test Summary Report tab in the final CTS.

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 functionality into production.

Conclusion

You should now be able to gain product conformance with the Agency’s Electronic Prescribing Technical Framework for your PDS/ASLR. If you need any further assistance please contact [email protected].

Back to: Electronic Prescribing Conformance Process