eReferrals v1.3

eReferrals facilitate the seamless exchange of significant patient information from one treating healthcare provider to another. The eHealth record system supports the collection of Referrals. When a healthcare provider creates a Referral, it will be sent directly to the intended recipient, as per current practices. A copy may also be sent to the eHealth record system.

End products superseded by

A new version has been released for this end product

Please refer to eReferral v1.4 or refer to the Release History for all releases of this End Product.

Identifier: 
EP-0936:2012
Date: 
13-03-2012
Type: 
application/zip
SHA256 Checksum: 
d1d95a55e6e31ade321848abd8e0d4b56567ead2912c4178a43ed76a241c3173
Size: 
13.86 MB

Product Components

Product component
Identifier: 
NEHTA-0970:2012

This document summarises the requirements for producers and consumers of the Electronic Referral Clinical Document that connect to the national My Health Recrod system.

Product component
Identifier: 
NEHTA-0969:2012

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

Product component
Identifier: 
NEHTA-0972:2012

The role of this release is to define the goal-state solution for the content of an eReferral communicated between general practitioners and specialists. That is, the creation, delivery, receipt, assimilation, and confirmation of patient referral documents in electronic form.

Product component
Identifier: 
NEHTA-0968:2011

This document presents the core information components of the e-Referrals Release 1.3 package, which are recommended for use in populating a referral.

Product component
Identifier: 
NEHTA-0971:2011

This document is a structured content specification (previously called a structured document template) for an e-Referral.

Product component
Identifier: 
NEHTA-0967:2012

This document provides a guide to implementing the 'logical' model detailed by the Agency's eReferrals Structured Content Specification as an HL7 Clinical Document Architecture Release 2 (CDA) XML document.

Product component
Identifier: 
NEHTA-1067:2011

The FAQs are guidance material for implementation. They are to be used for clarification purposes and to support existing documentation.

Product component
Identifier: 
NEHTA-0571:2009

The primary purpose of this report is to inform the Agency of the environment in Australia’s health care system related to referrals. This knowledge will support the further development of its e-referrals program.

Product component
Identifier: 
NEHTA-1155:2011

This Business Requirements Specification document provides the high-level requirements, business models and use case descriptions of the e-Referrals Release 1.1 package, relevant to the exchange of referral documents within Australia.

Product component
Identifier: 
NEHTA-1272:2013

This FAQ answers the question: How do you indicate in a CDA document that a problem/diagnosis has been resolved when the date of resolution is unknown?

Release history

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