Security Requirements for My Health Record Connecting Systems Conformance Profile - FAQs
The Security Requirements for My Health Record Connecting Systems Conformance Profile contains software requirements that harden clinical information systems from cyber security attacks, uplift information security and protect patient information and your software product.
Data Types in NEHTA Specifications - A Profile of the ISO 21090 Specification v1.0
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.
Electronic Prescribing – Frequently Asked Questions
Electronic Prescribing Frequently Asked Questions covering topics such as Prescribing Systems, Dispensing Systems, Mobile Applications, Mobile Intermediaries, Transitional eNRMC and Conformance Profile and more.
eDischarge Summary - Business Requirements Specification v1.1
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.
Participant Model Specification - Participant Model Specification v1.0
My Health Record FHIR Mobile Gateway - Registration and Overview
In this tutorial, you will; register as a developer for the Gateway, understand your testing obligations and more
Data Types in NEHTA Specifications v1.0
eReferrals - Business Requirements Specification v1.1
Victoria IHI Pre-Implementation Project - Business Requirements Specification v1.1
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.
Participation Data Specification - Participation Data Specification v3.3
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.
My Health Record FHIR Gateway - Presentation Requirements and Guidelines v1.2
About digital health standards
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.
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
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.
National Secure Messaging Network - Interoperability Specification v1.0
Participant Model Specification v1.0
Clinical Documents - CDA Rendering Specification v1.0
Australian Digital Health Agency (ADHA) OID Repository
OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.