This is a search for Resources (Products, Components, and Guides). Switch to search for all content to find Pages and Articles as well as Resources.
Event Summary v1.5
Event Summary documents are used to capture key health information about significant healthcare events that are relevant to the ongoing care of an individual. Event Summary documents can be submitted to an individual’s digital health record by any participating organisation. For example, an Event Summary document could be submitted by an after-hours…
… health record by any participating organisation. For example, an Event … health record by any participating organisation. For example, an Event …
PCEHR - Participation Guide v1.3
Component
NEHTA-1105:2012
Version
1.3
Status
Active
This document provides sufficient information to allow software developers, such as third party software vendors or software development teams engaged within healthcare provider organisations, to consider options and plan for implementation of the required functionality and integration components to interact with the My Health Record system.
Secure Message Delivery - Overview v1.0
Component
NEHTA-0999:2009
Version
1.0
Status
Active
The purpose of this document is to introduce and contextualise the body of work facing software vendors and organisations who choose to implement the Agency Secure Message Delivery (SMD). It is a supporting document for the endpoint specification [SMD-ES], which defines detailed requirements and behaviour for implementations of SMD.
… body of work facing software vendors and organisations who choose to implement the … body of work facing software vendors and organisations who choose to implement the …
RCPA - Pathology Terminology and Information Models - Release Note v1.0
Component
DH-2354:2016
Version
1.0
Status
Withdrawn
This release note identifies new or changed pathology terminology and information model resources developed by the Royal College of Pathologists Australasia (RCPA). The resources are published by the Australian Digital Health Agency.
… The resources are published by the Australian Digital Health Agency. … This … The resources are published by the Australian Digital Health Agency. … …
My Health Record B2B Webinar Recording v1.0
The Australian Digital Health Agency has developed the following webinar recording for My Health Record B2B Software Developers. This webinar recording provides an introduction to integrating B2B software with the My Health Record system. Topics covered include: Foundational information about The Healthcare Identifier (HI) Service including HI Service…
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…
Provider Connect Australia™ - Information Use Statements - Guide for Business Partners v1.1
Component
DH-3761:2023
Version
1.1
Status
Active
This document is a guide for Business Partners to use when developing their Information Use Statements for each partner service they have registered in Provider Connect Australia™ (PCA™).
… for each partner service they have registered in Provider Connect Australia™ … for each partner service they have registered in Provider Connect Australia™ …
My Health Record FHIR Gateway - Release Note v2.4
Component
DH-3812:2023
Version
2.4
Status
Active
Version 2.4 of the My Health Record FHIR® Gateway introduces reference to the Agency My Health Record Document Register GitHub page which has the full list of My Health Record supported document types including the new Aged Care Transfer Summary documents.
… to the Agency My Health Record Document Register GitHub page which has the full … to the Agency My Health Record Document Register GitHub page which has the full …
PCA™ - Get access token
Once you have a signed authentication JWT, the client can request an access token.
… client_id Mandatory As obtained from register client operation. … as described in roles section of the Register client . The response is a …
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
… completed the previous 2 guides, have registered as a developer, and … InitializeComponent(); DependencyService.Register<MockDataStore>(); …
Clinical Terminology - Guidance for Use in Healthcare Software v1.0
Component
NEHTA-1786:2014
Version
1.0
Status
Withdrawn
All SNOMED CT-AU and AMT resources, including implementation collateral, are now available to download from the document library on the National Clinical Terminology Service website. This toolkit provides a short introduction or ‘quick start’ reference for developers wishing to work with SNOMED CT-AU Reference Sets (Refsets). It includes…
… for managing risks when implementing Australian Medicines Terminology (AMT) or … of Medicine, Clinical Terms® – Australian Release (SNOMED CT AU) in …
PCA™ - Publisher operations
This section explains how to configure Provider Connect Australia™ (PCA™) for publisher operations.
… API only Low 2 Create a location for an organisation Required Portal & API Low 3 … Publisher Agent will be specific to the organisation and can be accessed using …
My Health Record Mobile Developer Welcome Pack v1.7
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. This version includes updated versions of each document to note the inclusion of share functionality and the Get XML View functionality. A preview copy of the Portal Operator…
NESAF v4 - Release Note v4.0
Component
NEHTA-1553:2014
Version
4.0
Status
Active
NESAF v4.0 is derived directly from the previous releases and includes refinements and minor inclusions to improve the value of the current product set. This release consolidates stakeholder feedback from independent reviews by reputable security firms as well as updates based on lessons learned during the application of the framework from the March 2012…
… • The use of NASH certificates; and • Australian privacy legislation. …
Secure Message Delivery - Conformance Test Specification v1.13
Component
NEHTA-1894:2011
Version
1.13
Status
Active
The Agency has a Compliance, Conformance and Accreditation (CCA) program that supports clinical safety and quality in health software. CCA provides leadership, guidance and materials for assessing the conformance of software that implements e-health specifications and standards. These conformance test specifications should be used by implementers and third…
… for the E-Health Secure Message Delivery Australian Technical Specification. Test … only be used to test for conformance to Australian Technical Specification 5822 …
Security Requirements for My Health Record Connecting Systems - Conformance Profile - Draft v1.1
Component
DH-3802:2023
Version
1.1
Status
Active
The Agency is cognisant of the inherent cyber security risks posed by systems connected to and accessing the My Health Record system, as well as potentially vulnerable aspects of the national infrastructure and all services under its care. To address this risk, a set of security requirements for systems connecting to the My Health Record system have been…
… development of software for healthcare organisations, have been selected from the Australian Cyber Security Centre’s …
SNOMED CT-AU - Release File Bundle v20150531
Component
NEHTA-2068:2015
Version
20150531
Status
Withdrawn
All SNOMED CT-AU and AMT resources, including implementation collateral, are now available to download from the document library on the National Clinical Terminology Service website. This toolkit provides a short introduction or ‘quick start’ reference for developers wishing to work with SNOMED CT-AU Reference Sets (Refsets). It includes…
… Health Terminology Standards Development Organisation (IHTSDO). All rights … "SNOMED" and "SNOMED CT" are registered trademarks of the IHTSDO. … …
Secure Messaging v2.0
This release of the Secure Messaging end product reflects the introduction of the: National Secure Messaging Network Blueprint; and National Secure Messaging Network Interoperability Specification The Blueprint describes the key roles within the secure messaging national network and the capabilities required of each role, as well as providing examples of…
… of Secure Message Delivery (SMD) and the Australian Provider Directory FHIR … industry, Standards Australia published Australian Technical Specification (ATS) …
Clinical Documents - Template Package Directory v1.14
Component
DH-3375:2022
Version
1.14
Status
Active
The template package directory provides a comprehensive overview of available template packages and their current status. It contains hyperlinks to the download locations of all template packages. Template package libraries are published for each clinical document type and are contained in the end product for the document type. This version of the template…
… for the following end products: Australian Immunisation Register v1.2 Discharge Summary v1.6 …
Clinical Terminology - Guidance for People and Processes v1.0
Component
NEHTA-1785:2014
Version
1.0
Status
Withdrawn
All SNOMED CT-AU and AMT resources, including implementation collateral, are now available to download from the document library on the National Clinical Terminology Service website. This toolkit provides a short introduction or ‘quick start’ reference for developers wishing to work with SNOMED CT-AU Reference Sets (Refsets). It includes…
… guidance for those involved in adopting Australian Medicines Terminology (AMT) v2 … of Medicine, Clinical Terms® – Australian Release (SNOMED CT AU). This …
Participation Data Specification - Release Note v3.3
Component
DH-2498:2017
Version
3.3
Status
Active
The purpose of this release note is to provide a brief description of the Participation Data Specification v3.3. This release note details the location of the specification, highlights resolved and outstanding issues, and also provides links to supporting documentation. Changes to the Participation Data Specification include: statements implying that…
… removed to avoid potential conflict with Australian Privacy Principle 9; and rebranding to the Australian Digital Health Agency and …
Security Requirements Conformance Profile
Services
Guide
DG-3094
Version
1.0
Status
Active
The Agency is cognisant of the inherent cyber security risks posed by systems connected to and accessing the My Health Record system, as well as potentially vulnerable aspects of the national infrastructure and all services under its care.
… development of software for healthcare organisations, have been selected from the Australian Cyber Security Centre’s …
Healthcare Identifiers Integration Toolkit v1.2
The Healthcare Identifiers Integration Toolkit contains libraries for B2B connectivity to the Healthcare Identifiers service, used to search for IHI, HPI-Is and HPI-Os. The sample code and integration tools provided here should only be used in conjunction with the Agency's detailed specifications for the Healthcare Identifiers Service and, where appropriate…
… Identifiers Service. GitHub The Australian Digital Health Agency has … libraries and selected resources. The Australian Digital Health Agency code …
Clinical Documents Integration Toolkit v1.9
The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth Reference Platform, forming part of the code library for tools and simulators. Access to sample code and the eHealth Reference Platform’s online simulator…
… GitHub The Australian Digital Health Agency has … libraries and selected resources. The Australian Digital Health Agency code …