This is a search for Resources (Products, Components, and Guides). You can switch to search for all content to find Pages and Articles (as well as Resources).
My Health Record FHIR Gateway - Operations Requirements and Guidelines v1.2
Component
DH-3704:2023
Status
Active
Version
1.2
The purpose of this document is to define the operations requirements and guidelines for applications (apps) connecting with the My Health Record system APIs via the My Health Record FHIR® Gateway, using interaction models #1 or #4 (refer to Appendix A for details).
… define the operations requirements and guidelines for applications (apps) … define the operations requirements and guidelines for applications (apps) …
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).
… to define the consent requirements and guidelines for applications (apps) … to define the consent requirements and guidelines for applications (apps) …
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…
… intact by the intended recipient. This guideline describes processes and … intact by the intended recipient. This guideline describes processes and …
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).
… requirements and recommended security guidelines for applications (apps) … requirements and recommended security guidelines for applications (apps) …
Clinical Package Validator - User and Configuration Guide v3.2
Component
DH-3350:2020
Status
Active
Version
3.2
Guide for users of the Clinical Package Validator, including information about its configuration options.
… Guide for users of the Clinical Package … about its configuration options. … Guide for users of the Clinical Package …
Clinical Documents - Conformance Test Specification for CDA Rendering v1.4
Component
NEHTA-2064:2016
Status
Active
Version
1.4
This version of Conformance Test Specification provides clarifications for many of the test cases, improves the readability of the document, and adds a number of test cases to support recently published Pathology Report and Diagnostic Imaging Report conformance profiles. It supports the currently published Clinical Documents - CDA Rendering Specification,…
… currently published Clinical Documents - CDA Rendering Specification , the My … currently published Clinical Documents - CDA Rendering Specification,… … …
HIPS - Module Guide (UI) v7.2.1
Component
DH-2970:2019
Status
Withdrawn
Version
7.2.1
The purpose of this document is to provide a detailed view of the design of the HIPS-UI Web module that supports participating organisations integrating with the My Health Record system. The intended use of this document is to help implementers understand the modules of the HIPS-UI Web product, and the user-oriented functions they provide. This document…
… This document… … DH_2970_2019_HIPS_ModuleGuideUI_v7.2.1.pdf …
Information Quality Rules - User Guide v1.6
Component
DH-2895:2019
Status
Active
Version
1.6
This document is a guide for developers, testers and analysts who use version 1.6 of the Information Quality Rules (‘the IQ Rules’). The IQ Rules are a set of machine readable instructions and not software. The IQ Rules are intended to be used in a testing, non-clinical environment only. The IQ Rules are licensed for use by the Agency in…
… This document is a guide for developers, testers and … with the IQ Rules. … This document is a guide for developers, testers and …
SNOMED CT-AU - Mapping Guidelines v2.0
Component
NEHTA-1790:2014
Status
Withdrawn
Version
2.0
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…
… CT-AU and AMT resources, including implementation collateral, are now … … NEHTA_1790_2014_SNOMEDCT-AU_MappingGuidelines_v2.0.pdf …
Clinical Documents - Conformance Test Specification for CDA Packaging v1.5
Component
NEHTA-2065:2015
Status
Active
Version
1.5
Specifies test cases for the assessment of conformance of clinical information systems with requirements related to CDA packaging.
… systems with requirements related to CDA packaging. … Specifies test cases for … systems with requirements related to CDA packaging. … …
NASH Organisation Certificate Tracker - Installation and User Guide v1.0.1
Component
NEHTA-2295:2016
Status
Active
Version
1.0.1
The NASH Organisation Certificate Tracker is an simple tool for listing the expiration dates of NASH PKI Certificates for Healthcare Provider Organisations. The Installation and User Guide provides instructions and explanation for the installation and usage of the tool.
… Organisations. The Installation and User Guide provides instructions and … Organisations. The Installation and User Guide provides instructions and …
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…
… and it describes the operational guidelines for E-Procurement … and it describes the operational guidelines for E-Procurement …
My Health Record Overviews, Guides and Conformance Material v1.7
Product
EP-3804:2023
Status
Active
Version
1.7
Services
This release of the My Health Record Overviews, Guides and Conformance Material have been updated to include the newly released Security Requirements for My Health Record Connecting Systems Conformance Profile - Final Draft v1.1. The security profile boosts cyber-security defences for clinical information systems connected to the My Health Record system. DH…
… of the My Health Record Overviews, Guides and Conformance Material have been … of the My Health Record Overviews, Guides and Conformance Material have been …
Common - CDA - FAQ MIMS Coding Requirements v1.0
Component
NEHTA-1165:2012
Status
Archived
Version
1.0
The guidance contained in this document has been superseded and should no longer be used for implementations of clinical documents specifications.
… and should no longer be used for implementations of clinical documents … specifications. … NEHTA_1165_2012_Common-CDA_FAQMIMSCodingRequirements_v1.0.pdf …
Victoria IHI Pre-Implementation Project - Detailed Functional Design for IHI Exceptions v2.1
Component
NEHTA-1349:2011
Status
Active
Version
2.1
This document list the exceptions raised within the Victorian IHI integration design, and the available resolutions. The exception handling is a major part of the design, with some IHI related functions only available through the IHI exception resolution process. The Best Practice Guide should be referenced for more information. Note that the Best Practice…
… resolution process. The Best Practice Guide should be referenced for more … information. Note that the Best Practice Guide has undergone more recent revision …
Healthcare Identifiers Service - Support Documents - Implementation Conformance Statement Proforma and Instructions v4.1
Component
DH-3501:2021
Status
Active
Version
4.1
The Agency, in conjunction with industry (including Services Australia, Medicare Australia, the Department of Health, MSIA, AIIA and ACIVA, and state and territory health jurisdictions), has specified a set of conformance requirements for health software that uses Healthcare Identifiers. A developer who wishes to claim that their software conforms to…
… by their Healthcare Identifiers implementation. … The Agency, in …
NASH SHA-2 Certificates - Developer Guide
Guide
DG-3080
Status
Active
Version
1.0
Services
Topics
This Developer Guide is for the use of developers whose products connect to the Healthcare Identifiers (HI) Service, My Health Record, Electronic Prescribing and Secure Messaging with a National Authentication Service for Health (NASH) PKI Certificate.
… Introduction This Developer Guide is for the use of developers whose … Purpose and functionality changes This guide is intended to assist developers to …
PCEHR Prescription and Dispense View - Structured Content Specification v1.0
Component
NEHTA-1126:2013
Status
Active
Version
1.0
This document provides a guide to implementing the 'logical' model detailed by the eHealth 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 purposes…
… Document Architecture Release 2 (CDA) XML document. The guide contains … of fulfilling the requirements for implementations of an eHealth …
My Health Record B2B Gateway - Find whether a My Health Record exists
This developer guide helps you to verify whether a My Health Record exists for a patient using their Individual Healthcare Identifier (IHI)
… hours Quick Intro This developer guide helps you to verify whether a My … should follow our HI Service Developer Guides . In this example, you'll learn …
My Health Record B2B Gateway - Supersede document
This guide describes the steps to supersede a Clinical Document in the My Health Record system
… Development: 1-2 hours Quick Intro This guide describes the steps to supersede a … = File.ReadAllBytes(@"C:\adha\cda\upload\CdaPackageOutputFilePath.zip"); // Create …
Secure Messaging - HL7 v2 MDM message for CDA package v2.5
Component
DH-3798:2023
Status
Active
Version
2.5
Secure Message Delivery - Implementation Conformance Statement Proforma v1.0.1
Component
NEHTA-1896:2014
Status
Active
Version
1.0.1
Proforma for providing detailed information about conformance to the Australian Technical Specifications.
My Health Record - App Vendor Guide to the Connection Process v1.2
Component
DH-3710:2023
Status
Active
Version
1.2
This document describes the process involved in developing an application (app) that connects with the My Health Record system.
… - My Health Record - App Vendor Guide to the Connection Process v1.2.pdf …
My Health Record Software Vendor Welcome Pack - Software Vendor Guide to the Connection Process v1.9
Component
DH-3874:2023
Status
Active
Version
1.9
This document describes the steps required in preparing a Clinical Information System (CIS) or software used by a Contracted Service Provider (CSP) for connection to the My Health Record system (previously known as PCEHR or Personally Controlled Electronic Health Record).
… Record). … DH-38742023_Software Vendor Guide to the Connection Process v1.9.pdf …