This is a search for all content including Pages, Articles, and Resources. You can switch to a scoped search for Resources to find Products, Components, and Guides.
Interoperability and digital health standards
Interoperability is a strategic priority of Australia’s National Digital Health Strategy, and relies on consistently implemented standards
About digital health standards
… profiles . Types of standards Interoperability standards can be … challenges in identifying appropriate resources for Australian use. Collective …National Product Catalogue - E-Procurement Operational Guidelines v1.0
Component
NEHTA-1185:2007
Status
Archived
Version
1.0
This document is part of the technical perspective of the E-Procurement Architecture and it describes the operational guidelines for E-Procurement Hub Services. This document is intended to form a checklist of capabilities that Hub Services should provide, and may be used as a foundation for the terms and conditions presented in Service…
My Health Record FHIR Mobile Gateway - Clinical Document Service
Guide
DG-3048
Status
Active
Version
1.0
Services
Topics
In this guide, we will be accessing Prescription and Dispense List and Allergies List contained in a patient’s clinical document service
My Health Record FHIR Mobile Gateway - Patient Details and Record List
We will use the token received from MyGov to access the patient’s My Health Record
Interoperability Framework - Interoperability Framework v2.0
Component
NEHTA-1146:2007
Status
Active
Version
2.0
The Agency Interoperability Framework (IF) is a common reference point that provides guidance to business and IT experts in delivering interoperable eHealth systems in Australia. This document presents the Agency Interoperability Framework (IF), version 2.0.
Interoperability Framework - Interoperability Maturity Model v1.0
Component
NEHTA-0062:2007
Status
Active
Version
1.0
This document defines a maturity model for interoperability aspects of ehealth systems and organisational practices from a national perspective. Although much will also be applicable within an enterprise context, the Agency has specifically identified issues that will foster interoperability within the national e-health context.
My Health Record FHIR Mobile Gateway - Generic Document Services
This guide will look at retrieving all clinical document data (including these 2, but excluding MBS documents)
RCPA - APUTS Requesting Pathology Terminology Reference Set v2.2
Component
DH-2361:2016
Status
Withdrawn
Version
2.2
RCPA - APUTS Requesting Pathology Terminology Reference Set v2.2, which provides a set of terms for requesting pathology in Australia and their associated SNOMED CT codes. It is intended to provide request terminology reference set for the most commonly requested terms used in both public and private practice.
National Product Catalogue - E-Procurement Business Architecture v1.1
Component
NEHTA-1188:2011
Status
Archived
Version
1.1
This business architecture provides the high level solution for the implementation of e-procurement in the Health supply chain. It explains the roles in the e-procurement community, and the shared processes that they use to achieve procurement using electronic document exchange. The purpose of the architecture is to define an Agency…
Resources
The Australian Digital Health Agency provides resources, tools, code, guides, information and contacts to assist software developers connecting digital health solutions to each other and to the national infrastructure
My Health Record FHIR Mobile Gateway - Personal Health Summary
In this guide, we will be accessing a patient’s medications and allergies contained in a Personal Health Summary
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
eHealth Interoperability Framework v1.1
This document describes a standards-based set of concepts, structuring rules and approaches for use in specifying and building interoperable eHealth systems. It includes guidelines for: structuring specifications; recommending document components for an eHealth specification; and defining the capability of healthcare organisations to…
eProcurement v1.6.1
eProcurement provides a standardised messaging format to electronically communicate standardised and accurate product and price data between Australian health departments and private hospital providers. The messages contain technical and business requirements for common procurement messages including purchase order, purchase order response, advanced…
Interoperability Framework v2.0
The Agency Interoperability Framework (IF) is a common reference point that provides guidance to business and IT experts in delivering interoperable eHealth systems in Australia.
National Secure Messaging Network - Interoperability Specification v1.0
Component
DH-3569:2023
Status
Active
Version
1.0
The NSMN Interoperability Specification (IS) details the technical requirements that underpin the NSMN. The Interoperability Specification Requirements are structured around the Blueprint solution roles. The NSMN Solution Requirements define the requirements that each solution role must meet, and any solution constraints that must be adhered to when meeting…
National Product Catalogue - Message Integrity Guidelines v1.0
Component
NEHTA-0307:2008
Status
Archived
Version
1.0
Retaining the integrity of the message is critical to e-Procurement as any compromise in integrity leads to the whole process being brought into question. Similarly, it is important that the message is received intact by the intended recipient. This guideline describes processes and activities that will assist in ensuring the integrity of the message, and…
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.
eHealth Interoperability Framework - Framework v1.1
Component
NEHTA-1024:2012
Status
Active
Version
1.1
This document describes a standards-based set of concepts, structuring rules and approaches for use in specifying and building interoperable eHealth systems. It includes guidelines for: structuring specifications; recommending document components for an eHealth specification; and defining the capability of healthcare organisations to…
Supporting Document Library - Communicating a Request Not to Upload a Pathology or Diagnostic Imaging Report to the My Health Record System Implementation Guide v1.0
Component
DH-2951:2019
Status
Active
Version
1.0
This guide explains how a requesting clinician can communicate to a pathology or diagnostic imaging provider that they should not upload a report to the patient’s My Health Record. The intended audience includes developers and vendors of digital health systems that generate pathology and/or diagnostic imaging requests. Background Pathology and…
eProcurement - Release Note v1.6.1
Component
NEHTA-1728:2014
Status
Active
Version
1.6.1
This incremental release updates the Description/Comments row in GS1 XML Purchase Order Response – Message Implementation Guidelines Section 4.18 Substitute Product Identifier. This change clarifies trade item identification and substitution variances between the GS1 Business Message Standards and the Agency message implementation guidelines. The…
My Health Record FHIR Gateway - Consent Requirements and Guidelines v1.2
Component
DH-3705:2023
Status
Active
Version
1.2
The purpose of this document is to define the consent requirements and guidelines for applications (apps) connecting with the My Health Record system APIs via the FHIR® standard gateway, using interaction models #1 or #4 (refer to Appendix A for details).
My Health Record FHIR Gateway - Security Requirements and Guidelines v1.2
Component
DH-3706:2023
Status
Active
Version
1.2
This document specifies the mandatory security requirements and recommended security guidelines for applications (apps) connecting with the My Health Record system APIs via the FHIR® standard gateway, using interaction models #1 or #4 (refer to Appendix A for details).