Collection of personal information
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.
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.
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.
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.
National Authentication Service for Health v1.0
My Health Record B2B Gateway Services - View Service - Logical Service Specification v1.5
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.
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.
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.
HI Service - Search for HPI-I
It is highly recommended that your software conduct HPI-I searches for users of your system.
My Health Record B2B Gateway - Find whether a My Health Record exists
This developer guide helps you to verify whether a My Health Record exists for a patient using their Individual Healthcare Identifier (IHI)
My Health Record B2B Gateway - Upload document
This guide will walk through the steps to create and upload clinical documents
My Health Record B2B Gateway Services - Document Exchange Service - Technical Service Specification v1.8
My Health Record B2B Gateway Services - Document Exchange Service Logical Service Specification v1.5
My Health Record B2B Gateway Services - View Service - Technical Service Specification v2.0
Healthcare Identifiers Service - Support Documents - Implementation Conformance Statement Proforma and Instructions v4.1
HI Service - Additional requirements for Electronic Prescribing
This guide will discuss potential changes which are required in your software.
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.
My Health Record B2B Gateway - Registration
My Health Record integration is typically done in two steps. Connecting to the HI Service and the My Health Record system.
National Secure Messaging Network - FAQs
Information about NSMN solution design, Provider Directories, message formats, message content, reference data, testing, technical support, standards, terminology and more.
My Health Record B2B Gateway - Gain access to a My Health Record
This guide walks through the steps to access a patient’s My Health Record using the GainPCEHRAccess web service
My Health Record FHIR® Mobile Gateway - Clinical Document Service
In this guide, we will be accessing Prescription and Dispense List and Allergies List contained in a patient’s clinical document service