Product component
Identifier: 
DH-2749:2018

This document defines the error scenarios and the associated error codes for all APIs except the Medicines View API.

Identifier: 
EP-2748:2018

Technical specifications to enable developers to connect applications to the My Health Record system via the FHIR® Gateway.

Product component
Identifier: 
DH-2751:2018

This document provides an overview of the API specifications required by developers to connect applications (apps) to the My Health Record system. This document describes API requests, API responses, OperationOutcome details, and error conditions that apply to application transactions.

Product component
Identifier: 
DH-2750:2018

This document contains the mapping between CDA Implementation Guide fields and Fast Healthcare Interoperability Resources (FHIR®) (Version 1.4.0 of standard).

Identifier: 
EP-2656:2018

Discharge Summary documents support the transfer of a patient from a hospital back to the care of their nominated primary healthcare provider.

Identifier: 
EP-2718:2018

The previous eReferral clinical document specifications were constrained to supporting referrals from a General Practitioner to a private specialist. Referrals to public hospitals, allied health providers or human services providers were not supported.

Product component
Identifier: 
DH-2725:2018

This document defines the service interfaces and associated conformance points for the provider-to-provider (P2P) delivery of Referral CDA document packages.

Product component
Identifier: 
DH-2724:2018

This document defines the error scenarios and the associated error codes for all APIs except the Medicines View API.

Product component
Identifier: 
DH-2722:2018

This document contains the mapping between CDA Implementation Guide fields and Fast Healthcare Interoperability Resources (FHIR®) (Version 1.4.0 of standard).

Product component
Identifier: 
DH-2721:2018

This document provides an overview of the API specifications required by developers to connect applications (apps) to the My Health Record system. This document describes API requests, API responses, OperationOutcome details, and error conditions that apply to application transactions.

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