My Health Record Notice of Connection (NoC) and Conformance Compliance and Declaration (CCD) testing
Software products must pass testing requirements before gaining access to the My Health Record production system.
HI Service - Additional requirements for Electronic Prescribing
This guide will discuss potential changes which are required in your software.
HI Service - Test and Go Live
All products developed, or updated, to connect with the HI Service are required to undergo testing before production access is granted.
HI Service - FAQs
The following frequently asked questions relate to the use of Healthcare Identifiers in Health Software Systems.
My Health Record CIS to NPP - Registration, Testing Requirements
Before you can begin development, you are required to register for access to the My Health Record system
HI Service - IHI Lookup - Test Cases
After successfully executing the IHI Lookup, it is important to modify your implementation to meet the Test Cases for the Use Cases we have built to UC.010 and UC.015.
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.
My Health Record - Mobile integration
The Australian Digital Health Agency aims to increase the adoption of the My Health Record by connecting the My Health Record platform to mobile applications through industry-standard APIs.
Secure Message Delivery - Conformance Test Specification v1.13
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.
Electronic Prescribing - Mobile Intermediary System - Conformance Process
A mobile intermediary system is a software product that a mobile application uses to connect to, and interact with, the National Prescription Delivery Service (NPDS) and/or Active Script List Registry (ASLR).
Electronic Prescribing - Mobile Applications - Conformance Process
A mobile application or web-based application is used by a subject of care or carer to manage prescriptions and to present an electronic prescription token to a pharmacy.
Secure Messaging Conformance Test Tools - Software Package v1.0.3
Clinical Documents - Conformance Test Specification for CDA Rendering v1.4
Electronic Prescribing - Test Data - HPI-O v2.0
Pharmacist Shared Medicines List - Conformance Test Specification v1.1.1
Electronic Prescribing - Test Data - Subjects of Care v2.0
Electronic Prescribing - Test Data - IHI v1.0
eHealth Diagnostic Imaging Report - Conformance Test Specification v1.0
NASH SHA-2 - Readiness Test Specification v1.3
eHealth Pathology Report - Conformance Test Specification v2.0
Electronic Prescribing - Conformance Test Specifications v3.0.3
Resources
The Australian Digital Health Agency provides resources, tools, code, guides, information and contacts to assist software developers connecting digital health solutions to each other and to the national infrastructure