This is a search for Pages, Articles, and Resources. Switch to a scoped search for Resources to find Products, Components, and Guides.
My Health Record B2B Gateway - Upload document
This guide will walk through the steps to create and upload clinical documents
… HealthcareFacilityTypeCodes.GeneralPractice, // Update to relevant … 5 above. 1. Create a new class called EventSummarySample in our existing …
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…
… information about significant healthcare events that are relevant to the ongoing … information about significant healthcare events that are relevant to the ongoing …
Event Summary - My Health Record Conformance Profile v1.5
Component
DH-3418:2022
Status
Active
Version
1.5
This document provides the requirements for producers and consumers of Event Summary documents that connect to the My Health Record system. It lists the specific conformance requirements for Event Summary documents in the context of the My Health Record system and provides references to all other documents that specify requirements applicable to event…
Event Summary - Release Note v1.5
Component
DH-3416:2022
Status
Active
Version
1.5
This minor release of the Event Summary specification bundle includes the following change to the Event Summary – My Health Record Conformance Profile: Document subtyping introduced to improve clinical document discoverability. The following change was also made to the Event Summary – Template Package Library: List of non-critical and non…
… of non-critical and non… … DH_3416_2022_EventSummary_ReleaseNote_v1.5.pdf …
Event Summary - CDA Implementation Guide v1.3
Component
NEHTA-1846:2015
Status
Active
Version
1.3
This document provides a guide to implementing the 'logical' model detailed in the Agency's Event Summary Structured Content Specification (SCS) as an HL7 Clinical Document Architecture Release 2 (CDA) XML document. The guide takes implementers step by step through mapping each data component of the Event Summary SCS to a corresponding CDA attribute or…
Event Summary - PCEHR Usability Recommendations v1.1
Component
NEHTA-1921:2014
Status
Active
Version
1.1
This document provides usability recommendations for clinical information systems and contracted service provider systems authoring or rendering information contained in Event Summary documents exchanged with the My Health Record system. The usability recommendations are provided to all software developers interested in improving the usability of…
Event Summary - Information Requirements v1.2
Component
NEHTA-1845:2015
Status
Active
Version
1.2
This document defines the minimum set of data groups and data elements that are recommended for inclusion in electronic event summary documents.
Event Summary - Structured Content Specification v1.2
Component
NEHTA-1847:2015
Status
Active
Version
1.2
This document describes the structured component specifications and guidelines to be adopted when producing electronic Event Summary documents for sharing within the Australian healthcare community. This specification references or contains excerpts of intellectual property (IP) owned by the Regenstrief Institute, IHTSDO, or HL7 International…
Event Summary - Template Package Library v1.5
Component
DH-3417:2022
Status
Active
Version
1.5
This template package library provides validation rules for Event Summary documents to identify points of non-conformance to the relevant specifications. The template packages contained in this library can be used by the My Health Record system and the Agency's Clinical Package Validator.
Electronic Prescribing – Frequently Asked Questions
Electronic Prescribing Frequently Asked Questions covering topics such as Prescribing Systems, Dispensing Systems, Mobile Applications, Mobile Intermediaries, Transitional eNRMC and Conformance Profile and more.
… (Updated 15 March 2024) General Questions Who is eligible for … in Electronic Prescribing to view, and general enquiries are welcome at any …
Security Requirements for My Health Record Connecting Systems Conformance Profile - FAQs
The Security Requirements for My Health Record Connecting Systems Conformance Profile contains software requirements that harden clinical information systems from cyber security attacks, uplift information security and protect patient information and your software product.
… General Questions What is the intent of … Policy Framework was introduced in 2018 and is therefore not a new …
Referral v2.0
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. The Service Referral v1.1 specifications expand this scope of use to include any referrals for healthcare…
… to supporting referrals from a General Practitioner to a private … any referrals for healthcare… … EP_2718_2018_Referral_v2.0.zip …
Service Referral - Template Package Library v1.1
Component
DH-2703:2018
Status
Active
Version
1.1
The template package library provides validation rules for Service Referral documents to identify points of non-conformance to the relevant specifications. The template packages contained in this library will be used by the clinical information systems and the Agency's Clinical Package Validator. Template packages in general are restricted to assessing…
… Package Validator. Template packages in general are restricted to assessing … Package Validator. Template packages in general are restricted to assessing… … …
Advance Care Document Custodian - Template Package Library v1.1.1
Component
DH-2663:2018
Status
Active
Version
1.1.1
The template package library has been updated to correct a defect in the MANIFEST file that prevented the MHR system from correctly retrieving the CDA schema files.
Advance Care Document Custodian v1.1.1
Advance care documents let individuals make choices about their future medical treatment in the event that they are cognitively impaired or otherwise unable to make their preferences known. Currently, a completed directive is kept in a safe place, with a designated custodian controlling access to it. Advance care document custodian documents can be used to…
Core Level One - CDA Implementation Guide v1.1
Component
DH-2580:2018
Status
Active
Version
1.1
This document provides a guide to implementing the logical model detailed by the Australian Digital Health Agency's Core Level One Clinical Document (CLOCD) Structured Content Specification (SCS) as an HL7 Clinical Document Architecture (CDA) Release 2 XML document. This implementation guide is based on Version 1.1 of the CLOCD SCS [DH2018e]. The primary…
… based on Version 1.1 of the CLOCD SCS [DH2018e]. The primary aim of the … based on Version 1.1 of the CLOCD SCS [DH2018e]. The primary… … …
Advance Care Document Custodian - Release Note v1.1.1
Component
DH-2664:2018
Status
Active
Version
1.1.1
This incremental release of the Advance Care Document Custodian end product provides an update to the Template Package Library.
Pharmacist Shared Medicines List - Implementation Guidance for Download and View PSML (Mobile) v1.0
Component
DH-2762:2018
Status
Active
Version
1.0
Guidance for mobile applications which provide My Health Record viewing functionality using the mobile gateway. Configuration changes to such mobile apps might be required to download and display PSML documents from the My Health Record system.
Service Referral - Information Requirements v1.1
Component
DH-2675:2018
Status
Active
Version
1.1
This document presents the information requirements for the content of a Service referral, as recommended for use in Australian eHealth systems. It is therefore recommended to be implemented in any system that creates or transfers referrals. Note that it does not cover the content of communication exchanges between organisations related to workflow.
Secure Messaging Integration Toolkit - Release Note v1.2.5
Component
DH-2728:2018
Status
Active
Version
1.2.5
Version 1.2.5 of the Secure Messaging Integration Toolkit provides an update of the Secure Messaging Conformance Test Tools – Software Package to include updated National Authentication Service for Health (NASH) Public Key Infrastructure (PKI) test certificates. The test certificates are required by the following tools included in the software package…
Secure Message Delivery B2B Client Library - .NET Sample Code v1.1.1
Component
DH-2615:2018
Status
Active
Version
1.1.1
This version of the Secure Message Delivery B2B Client Library provides internal optimisations and performance improvements. These changes do not affect the functionality or interfaces of the Client Library. GitHub This resource is also available here: https://github.com/AuDigitalHealth/smd-b2b-client-dotnet
Digital Health Icon Library v1.0
The Icon Library is available as a resource for developers and implementers of digital health solutions and other interested parties. The digital health icons are user-friendly designs that represent the human nature of the healthcare sector. The icon library outlines the standard look and presentation of each icon to maintain brand integrity.
… to maintain brand integrity. … EP_2704_2018_DigitalHealthIconLibrary_v1.0.zip …
Healthcare Identifiers Integration Toolkit - Release Note v1.2
Component
DH-2611:2018
Status
Active
Version
1.2
Version 1.2 of the Healthcare Identifiers Integration Toolkit provides defect fixes and performance improvements for the Healthcare Identifiers B2B Client Library.
Service Referral - P2P Delivery Technical Service Specification v1.4
Component
DH-2725:2018
Status
Active
Version
1.4
This document defines the service interfaces and associated conformance points for the provider-to-provider (P2P) delivery of Referral CDA document packages.