Oexa's Managed Intermediary is an API gateway to eScripts, enabling secure and efficient integration with the National Prescription Delivery Service (NPDS) and the Active Script List (ASL). It acts as the backend solution, providing the infrastructure needed to support eScripts functionality in your mobile app or website.

Oexa MI does not handle front-end development or user interface design for apps or websites. Instead, we provide the backend API that powers your platform’s ability to manage eScripts. This allows you, as the vendor, to build a custom front-end experience that aligns with your brand and user needs, leveraging the robust and compliant foundation our API offers.

If you need detailed technical insights about the API or assistance with backend integration, our team is here to help.

To connect to our Managed Intermediary, the process involves the following steps:

1. Access to National Prescription Delivery Service (NPDS) and the Active Script List (ASL): A signed contract with Medication Knowledge, who operates the connection between Mobile Intermediaries and the NPDS/ASL. This contract allows you access to our integration environments.

2. Agreement with Oexa: This agreement outlines project specifics and monthly subscription fees with our Managed Intermediary service.

3. Development and Conformance: You’ll need to develop your product to meet conformance requirements and undergo the necessary conformance process. We offer consulting services to guide you through the conformance process.

Yes, connecting to the MI enables eScript token lookup functionality. This allows customers to validate their eScript tokens, saving time for pharmacies by instantly confirming whether a script is valid for dispensing without back-and-forth communication.

Connecting to the MI can help with repeat token management in the following ways:

• Connection to Active Script List/MySL: customers who link to MySL in your product via the MI will automatically have access to repeat tokens

• Script chain matching: solutions using token lookup can use payload information from repeat tokens to help link script chains for customers. However, the repeat token will need to be sourced from external means such as the customers SMS, or dispense system integration

eScripts include essential details such as:

• Script/Medication identifiers (e.g., AMT codes, PBS codes)

• Script details such as medication name, dosage, and quantity

• Prescriber information

• Previous dispense data

This information is also useful for helping manage repeat tokens for your patients / customers.

With this payload, vendors can perform product matching, provide pricing or brand options for patients to order medications online, and facilitate a seamless experience for patients receiving their scripts.

While we have the expertise to assist with development, we do not build Mobile Apps or Websites for this product. This is because we act as assessors for your app's conformance process, and offering development services would create a conflict of interest.

Instead, we provide you with access to our API and ongoing support for your development team to help them integrate and meet conformance requirements. If you don’t have a development team, we recommend working with an external developer or agency familiar with such technical processes.

Yes. Even if your only goal is to validate eScript tokens, your product still needs to go through the conformance process. This ensures your app meets security, privacy, and functionality standards required for integration with the ePrescribing system. To connect to ‘eRX’ which is the provider for the National Prescription Delivery Service (NPDS), you need to connect to it via a Mobile Intermediary. You can build your own or connect to Oexa’s Managed Intermediary. See the ePrescribing eco-system.

Meeting conformance involves the following steps:

• Ensuring your app meets strict functional and non-functional requirements set by the ADHA and the Department of Health and Aged Care.

• Submitting documented evidence that your product complies with these standards.

• Completing observed conformance, where your company representative demonstrates the product functionality live to confirm it meets the requirements.
  

For more detailed information, visit our conformance process page or ADHA developer portal at ADHA ePrescribing Conformance.

Yes. To connect to our conformant mobile intermediary, your platform(s) also need to go through the conformance process. But don't worry, we'll guide you!

To adhere to conformance requirements outlined by the Australian Digital Health Agency (ADHA), your product must follow specific guidelines for handling eScript data, account security, and functionality. Examples include:

• "The system SHALL permit the user to select and view prescription information and tokens for every token stored by the system. The tokens SHALL be rendered as QR codes."

• "The system SHALL provide a means for the user to hide and unhide prescription items that are in the ASL and active."

For more detailed information, visit the ADHA developer portal at ADHA ePrescribing Conformance.

The timeline varies depending your product's readiness and on your team’s capability to develop, test, and prepare your app or website. For example, are you building a solution from scratch, or are you adding in additional eScript functionality to your app or website?

Most vendors allow 2–3 months to complete the process, while some may take up to 6 months. Again this will depend on your scope, development capability and other priorities.

Product Readiness

• Assess how close your product is to meeting conformance requirements.

• Updates to your product and functionality may be necessary, along with time to gather and submit evidence of compliance.

Conformance Process

• Once your product is ready, the conformance process typically takes 3–4 weeks.*

• Observed testing is conducted with the Oexa team.

Processing by the Australian Digital Health Agency (ADHA) is required afterward. This step is outside of Oexa's control and may influence the overall timeline.

What's great with Oexa's MI: Connecting to our API is a straightforward and quick process, helping you streamline the integration phase and focus on other readiness activities.

*Once you’ve submitted your evidence to Oexa, we will review it to identify any remediation work required. If the evidence is satisfactory, the submission is sent to the ADHA for their approval, which typically takes 3–4 weeks. This timing depends on the ADHA’s schedule and processing queues

Updates to conformance profiles are determined by the ADHA. We actively participate in ePrescribing working groups and will keep you informed whenever profile updates are announced, ensuring that your product remains compliant and up to date.

The current conformance profile for ePrescribing mobile intermediary and mobile app is CP3.0.1. No sunset date has been set for CP3.0.1. The previous conformance profile CP2.3 is due to sunset in September 2026. For updates on profiles and their sunset dates, refer to ADHA ePrescribing Conformance.

Yes, we can support your connection to the ASL through an assisted registration process. A pharmacy using supported dispensing software must generate an ASL/MySL activation code to complete this process successfully.

Not yet. Self-registration requires regulatory amendments, an approved digital identity solution, and collaboration between the Australian Digital Health Agency (ADHA) and the Department of Health and Aged Care. We will closely monitor developments and provide updates as self-registration becomes available.

Costs can vary depending on your situation but generally fall into internal and external categories:

• Internal Efforts: These involve your team understanding the conformance requirements, updating or developing your product, and preparing evidence to meet the standards.

• External Costs:

  • Oexa Monthly Subscription Fees: Cover integration with and ongoing use of our Managed Intermediary.

  • Optional Consulting Services: For additional guidance or support during the conformance process, which may incur additional charges.

  • Medication Knowledge Fees: Separate from Oexa and include setup and maintenance costs for connecting to NPDS and ASL.

While the integration process involves effort, we aim to simplify it for you. We provide the API for integration, but understanding the requirements and updating your product to meet conformance standards will require time and resources from your team.

No, we only offer conformance guidance to vendors who intend to connect to Oexa’s Managed Intermediary.

Unfortunately, no. Developing Mobile Intermediaries competes with our core product offering, and we are unable to assist in this area.

You’ll need to undertake the conformance process again as your declaration is tied to your current mobile intermediary. However, much of your previously submitted evidence will be a great reference for you, making the process smoother.

We work with a wide range of clients, including telehealth providers, pharmacies, medicinal cannabis companies, and health software vendors.

If you’d like to better understand the requirements for conformance, we recommend downloading Scripty, a conformant mobile app owned and operated by Oexa. Scripty demonstrates how to look up eScripts and connect to the ASL (Active Script List). It successfully passed the same conformance process that your app or website will need to complete.

Please note, to explore such functionality, you will need real tokens and an ASL code. Scripty is a great starting point for visualising how your product can operate in a conformant environment.