This is a search for Pages, Articles, and Resources. Switch to a scoped search for Resources to find Products, Components, and Guides.
Pharmacist Shared Medicines List - Release Note v1.1.1
Component
DH-2927:2020
Status
Active
Version
1.1.1
PSML documents allow pharmacists in both hospital and community pharmacy settings to document the outcome of consumer consultations regarding their current medications and upload it to the My Health Record system. This is the first public release of this end product. It contains the conformance profile, validation rules and implementation guides for the…
Personal Health Summary v1.1
Personal health summary documents allow individuals to store information as part of their digital health record. This may include their contact details, information about allergies and adverse reactions, and any medications they may be taking. Such documents can be used in consultation with the individual’s healthcare provider to help gather…
… provider to help gather… … EP_2272_2016_PersonalHealthSummary_v1.1.zip …
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.
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…
Service Referral - FAQ Referral Resolution Flag v2.0
Component
DH-2726:2018
Status
Active
Version
2.0
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
Service Referral - Release Note v2.0
Component
DH-2727:2018
Status
Active
Version
2.0
This release note introduces a new clinical document specification, Service Referral v1.1 - which replaces the previous eReferral clinical document specifications. NOTE: There are no current plans for the My Health Record to accept Service Referral v1.1 documents. Service Referral v1.1 is primarily for point-to-point use. The My Health Record continues to…
HIPS Mobile - Release Note v3.1
Component
DH-3827:2023
Status
Active
Version
3.1
HIPS Mobile allows clinicians in the hospital setting to have mobile device access to patient My Health Record information while engaging with patients in ward and bed-side settings or remotely off-site. Clinicians in public and private hospitals already widely rely on mobile devices (smart phones and tablets) for accessing their patients’ clinical…
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…
PCEHR Prescription Record and PCEHR Dispense Record - Conformance Profile v1.1
Component
NEHTA-1327:2013
Status
Active
Version
1.1
This document lists the specific conformance requirements for the PCEHR Prescription Record v1.0 and PCEHR Dispense Record v1.0 clinical documents that are in addition to the Common Conformance Profile for Clinical Documents. Please note that this document has been superseded by two separate conformance profiles: NEHTA-1455:2013 PCEHR Prescription Record …
Electronic Prescribing - Conformance Test Specifications - Release Note v3.0.3
Component
DH-3727:2022
Status
Active
Version
3.0.3
This release of the end product EP-3726:2022 updates Conformance Test Specifications and test data for electronic prescribing software vendors. It also includes instructions for Transitional eNRMC software vendors.
HL7 MDM Library - Product Data Sheet v1.1
Component
NEHTA-1627:2014
Status
Active
Version
1.1
The HL7 MDM Client Library provides vendors with a sample implementation of how to create and populate an HL7 v2 MDM message using the information within a CDA package as the input. The library also works in reverse, allowing the CDA package to be extracted out of the message.
My Health Record - Implementation Guide v1.4
Component
DH-3427:2021
Status
Active
Version
1.4
This document provide guidance to software developers on how to use the My Health Record system B2B interface, produce well-formed B2B request messages and receive and use responses from the system.
Diagnostic Imaging Report - Structured Content Specification v1.0
Component
NEHTA-1527:2014
Status
Active
Version
1.0
This specification describes a logical data model for eHealth Diagnostic Imaging Report clinical documents that are uploaded to the individual's My Health Record. Clarification: 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…
Goals of Care - Template Package Library v1.0
Component
DH-3027:2020
Status
Active
Version
1.0
The Template Package Library provides validation rules for Goals of Care documents to help identify points of non-conformance to the relevant specifications. The template packages contained in this library will be used by the My Health Record system, other clinical information systems and the Agency's Clinical Package Validator. Template packages in general…
PCEHR Prescription and Dispense View - CDA Implementation Guide v1.0
Component
NEHTA-1127:2013
Status
Active
Version
1.0
This document provides a guide to implementing the 'logical' model detailed by the Agency's PCEHR Prescription and Dispense View Structured Content Specification as an HL7 Clinical Document Architecture Release 2 (CDA) XML document. The guide contains descriptions of both constraints on the CDA and, where necessary, custom extensions to the CDA, for the…
Clinical Document Packaging Library - .NET Sample Code v1.5.4
Component
DH-2627:2018
Status
Active
Version
1.5.4
The Clinical Document Packaging Library provides sample code for the wrapping and unwrapping of clinical documents, their digital signature and associated attachments. The functionality is based on the CDA Packaging v1.0 specification (no metadata.xml) and is particularly aimed at supporting document uploads to and downloads from the My Health Record system…
P2P Document Delivery - Technical Service Specification v1.1
Component
NEHTA-1227:2012
Status
Active
Version
1.1
This document is a Technical Service Specification (TSS) for the secure point-to-point delivery of clinical documents. It provides coverage of the Implementable Specification layer as defined in the National eHealth Framework (NeHF).
Secure Messaging Conformance Test Tools - Software Package v1.0.3
Component
DH-2729:2018
Status
Active
Version
1.0.3
Version 1.0.3 of the Secure Messaging Conformance Test Tools provides 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 Messaging Test Harness; Secure Messaging Delivery Agent. The test certificates…
SNOMED CT-AU - Reference Set Implementation Toolkit v1.0
Component
NEHTA-1427:2013
Status
Withdrawn
Version
20131130
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…
Australian Digital Health Agency (ADHA) OID Repository
Guide
DG-3127
OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.
… is taken fromNote: The OID is a leaf node - it is used in a coded data element … length. Note: The OID is a leaf node - it is used in a coded data element …