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.
HI Service - Additional requirements for Electronic Prescribing
Guide
DG-3041
Status
Active
Version
1.0
This guide will discuss potential changes which are required in your software.
… Cases UC.010 Register patient HI_010_005812, HI_010_005813, HI_010_005814, … Update patient health record HI_015_005812, HI_015_005813, HI_015_005814, …
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 …
Security Requirements for My Health Record Connecting Systems - Conformance Profile - Responsibility Assignment Matrix v1.1
Component
DH-3881:2023
Status
Active
Version
1.1
The Agency recognises that certain conformance requirements outlined in the Security Requirements for My Health Record Connecting Systems Conformance Profile draft v1.1 (Security Profile) establish shared responsibility for implementation between software developers and healthcare provider organisations (HPO). In most cases, software developers are expected…
NASH - Obtaining Identity From a Production or Test NASH Certificate v1.0
Component
NEHTA-1281:2013
Status
Active
Version
1.0
This FAQ answers: What identity information contained in a production or test NASH certificate should I use when validating a signature And What will be the impact on the CCA status of any SMD product that was tested with code that used the URI in the test NASH certificates issued before June 2012
My Health Record FHIR Gateway - Release Note v2.4
Component
DH-3812:2023
Status
Active
Version
2.4
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.
Australian Medicines Terminology v3 Model - Common - Release Note v1.7
Component
NEHTA-2381:2016
Status
Withdrawn
Version
1.7
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…
Electronic Prescribing - State and Territory Legislative Readiness and Technical Requirements v2.3
Component
DH-3281:2020
Status
Archived
Version
2.3
Each software developer needs to consider the jurisdictions they think their software will operate in and consider the legal obligations for those jurisdictions. Software developers are responsible for contacting their relevant state and territory regulation authorities to attain this information. This document has been developed and is maintained by the…
Clinical Documents - Common Conformance Profile v1.7
Component
DH-2481:2017
Status
Active
Version
1.7
This document provides conformance requirements applicable to all types of clinical documents. This includes references to other documents containing additional normative content. Conformance requirements listed in this document are supplemented with and superseded by conformance requirements for specific types of clinical documents or for particular usage…
HIPS - Documentation Package v7.3
Component
DH-2981:2020
Status
Active
Version
7.3
HIPS Documentation Packages contains a comprehensive set of product documentation, including license terms for incorporated third-party products.
Detailed Clinical Model Library - Problem Diagnosis Detailed Clinical Model Specification - Release Note v3.0
Component
NEHTA-1181:2011
Status
Active
Version
3.0
Release Note
Electronic Transfer of Prescription - Release Note Status Update v1.3
Component
NEHTA-1381:2013
Status
Active
Version
1.3
The Agency’s ETP 1.1 technical specification documents are replaced by Australian Technical Specification 4888.x for Electronic Transfer of Prescription as described in this release note. ETP 1.1 conceptual and business documents, which are no longer completely aligned with the Australian Technical Specifications, will be updated as part of a future…
Electronic Transfer of Prescription - ePrescription CDA Implementation Guide v2.1
Component
NEHTA-0981:2010
Status
Archived
Version
2.1
This document describes the structured document template for a prescription request, from a clinical communication perspective. This specification references or contains excerpts of intellectual property (IP) owned by the Regenstrief Institute, IHTSDO, or HL7 International. Applicable IP constraints apply: This material contains content from…
How do I populate MSH-3, MSH-4, MSH-5 and MSH-6 segments of the outgoing REF-I12 and MDM-T02 messages to support successful message exchanges?
Successful message exchange is dependent upon the correct population of segments MSH-3, MSH-4, MSH-5 and MSH-6 of outgoing messages.