Identifier: 
EP-3115:2020

The My Health Record Mobile Developer Welcome Pack is a collection of forms and guides to help new app developers connect to the My Health Record system for the first time.

Product component
Identifier: 
DH-3092:2020

The purpose of this form is for mobile app developers to request access to the My Health Record Production Environment by providing information about the developer’s organisation, details of their application (app), declaring that the app conforms to the mandatory My Health Record requirements an

Identifier: 
EP-3132:2020

The My Health Record Software Vendor Welcome Pack is a collection of forms and guides to help new software vendors connect to the My Health Record system for the first time.

Identifier: 
EP-3131:2020

Click on the link below to download the latest version of Managing Your B2B Software in Production.

Product component
Identifier: 
DH-3121:2020

A form to be completed by new software vendors intending to connect their software to the My Health Record system. It captures information about the software vendor organisation and their software product.

Product component
Identifier: 
DH-3118:2020

This document describes the steps required in preparing a Clinical Information System (CIS) or software used by a Contracted Service Provider (CSP) for connection to the My Health Record system.

Product component
Identifier: 
DH-3119:2020

A declaration that states software products comply with all applicable My Health Record technical specifications and conformance points and have undergone the necessary internal testing. This form is required to connect new or updated software to the My Health Record system. 

Product component
Identifier: 
DH-3129:2020

This document outlines the process for liaising with the My Health Record System Operator (SO) about production incidents and events requiring notification to the SO, such as changes and upgrades to software that connects to the My Health Record system.

Product component
Identifier: 
DH-3120:2020

A list of support contacts, listing the appropriate support channel by scenario.

Identifier: 
EP-3041:2020

Electronic Prescribing - Technical Framework documents
These technical framework documents are provided to software vendors and demonstrate what will be required to enable electronic prescribing. These technical documents are:

Pages

By operation of the Public Governance, Performance and Accountability (Establishing the Australian Digital Health Agency) Rule 2016, on 1 July 2016, all the assets and liabilities of NEHTA will vest in the Australian Digital Health Agency. In this website, on and from 1 July 2016, all references to "National E-Health Transition Authority" or "NEHTA" will be deemed to be references to the Australian Digital Health Agency. PCEHR means the My Health Record, formerly the "Personally Controlled Electronic Health Record", within the meaning of the My Health Records Act 2012 (Cth), formerly called the Personally Controlled Electronic Health Records Act 2012 (Cth).

Back to Top