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.
My Health Record B2B Gateway - Get Patient Document List and View Document
This guide will walk through the process to get patient clinical documents from the My Health Record system and display them to your users using a generic style sheet
… walk through the process to get patient clinical documents from the My Health Record …
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…
… the eHealth Reference Platform. The Clinical Documents Integration Toolkit contains …
My Health Record FHIR Mobile Gateway - Clinical Document Service
Guide
DG-3048
Status
Active
Version
1.0
Services
Topics
In this guide, we will be accessing Prescription and Dispense List and Allergies List contained in a patient’s clinical document service
… Clinical Document Services - FHIR Gateway … Date is a search criteria to select the documents whose start date is after the …
Clinical Documents - Implementation Guidance - Masking of Address and Communication Details in Clinical Documents v1.1
Component
DH-2788:2019
Status
Active
Version
1.1
This document provides advice for developers on the masking of consumers’ address and communication details in clinical documents. It includes specific recommendations for implementers using HIPS for the generation of clinical documents. Safety risks can result for consumers from the inclusion of their address or communication details in clinical…
Clinical Documents - Supplementary Notes for Implementers Relating to Clinical Document Presentation v1.0
Component
NEHTA-1328:2013
Status
Active
Version
1.0
This document recommends a set of presentation guidelines for CDA® document authors. It complements the CDA® Rendering Specification and the CDA® implementation guides by describing: how to ensure that the data is properly, consistently and safely represented in the presentation; and the recommended order of the sections in a document…
… upplementaryNotesforImplementersRelatingtoClinicalDocumentPresentation_v1.0.pdf …
Clinical Documents Integration Toolkit - Release Note v1.9
Component
DH-3544:2021
Status
Active
Version
1.9
Version 1.9 of the Clinical Documents Integration Toolkit provides improvements to following products: Australian Digital Health Agency CDA Schema Extension 3.0 - CDA Schema Australian Digital Health Agency CDA Schema Extension 3.0 - Compliable CDA Schema
My Health Record FHIR Mobile Gateway - Generic Document Services
This guide will look at retrieving all clinical document data (including these 2, but excluding MBS documents)
Clinical Documents - Conformance Test Specification for Clinical Documents v1.2
Component
NEHTA-1329:2012
Status
Archived
Version
1.2
Conformance test specification for clinical documents
… Conformance test specification for clinical documents … Conformance test …
Clinical Documents - FAQ Appropriate use of date and date-time values in Clinical Documents v1.0
Component
NEHTA-1255:2012
Status
Active
Version
1.0
This FAQ answers the question: What is the appropriate use of date and date-time values in clinical documents
… use of date and date-time values in clinical documents? … This FAQ answers the …
Clinical Document Library - Product Data Sheet v1.6
Component
DH-2914:2020
Status
Active
Version
1.6
The Clinical Document Library provides .NET and Java sample implementations of how to create a range of CDA documents. The .NET variant of the library supports all Agency-specified document types. The Java variant of the library focusses on document types for use in a hospital context. This document describes the features and capabilities of the Clinical…
… The Clinical Document Library provides .NET … of how to create a range of CDA documents. The .NET variant of the …
Generic Clinical Document Style Sheet - Product Data Sheet v1.3
Component
DH-2466:2017
Status
Active
Version
1.3
The Generic Clinical Document Style Sheet provides a sample implementation of a style sheet which will render clinical documents of all CDA document types published by the Agency. This product component was previously called Generic CDA Style Sheet.
… The Generic Clinical Document Style Sheet provides a … a style sheet which will render clinical documents of all CDA document types …
Clinical Document Packaging Library - Product Data Sheet v1.2
Component
NEHTA-2131:2015
Status
Active
Version
1.2
The Clinical Document Packaging Library provides a sample implementation of how to package CDA documents (and any attachments) following the Agency specifications. This product component was previously called CDA Packaging Library - Product Data Sheet.
Clinical Document Data Extractor Library - Product Data Sheet v1.1
Component
NEHTA-2130:2015
Status
Active
Version
1.1
The Clinical Document Data Extractor Library simplifies the development process by providing vendors with a simple interface for extracting data from a range of CDA documents. The library uses the information from Agency-developed CDA implementation guides. This product component was previously called CDA Data Extractor Library - Product Data…
Clinical Documents - Implementation Guidance - Representing Coding in CDA Documents v1.0
Component
NEHTA-1097:2011
Status
Active
Version
1.0
This document provides advice for implementers with respect to coding common clinical concepts in Agency CDA documents, including e-Referral, Discharge Summary, Event Summary, Shared Health Summary, and Specialist Letter. This document describes how to correctly encode a concept for maximum utility in the future.
Clinical Documents - FAQ Qualifiers for Clinical Information v1.0
Component
DH-2594:2017
Status
Active
Version
1.0
This document provides guidance for the correct inclusion of qualifiers for structured clinical information contained in CDA documents.
… inclusion of qualifiers for structured clinical information contained in CDA documents. … This document provides …
Clinical Documents - Clinical Package v1.0
Component
NEHTA-1226:2011
Status
Active
Version
1.0
This specification defines a clinical package as a logical model of the data it contains. This model can be profiled to create data models for specific clinical data. This specification also defines the "CP-ZIP" representation: a serialised syntax for representing instances of the clinical package logical model. This representation can be used…
… This specification defines a clinical package as a logical model of … can be used… … NEHTA_1226_2011_ClinicalDocuments_ClinicalPackage_v1.0.pdf …
Core Level One Clinical Document v1.0
The Core Level One Clinical Document is a CDA container for the electronic representation of clinical information provided by source systems. For example, documents in PDF format could be included in the CDA container so it can be accepted by the My Health Record. Although this Core Level One Clinical Document could ostensibly be used for any clinical…
… The Core Level One Clinical Document is a CDA container for … provided by source systems. For example, documents in PDF format could be included …
Clinical Documents - FAQ Representing patient IDs in CDA documents v1.1
Component
NEHTA-1278:2013
Status
Archived
Version
1.1
The FAQs are guidance material for implementation. They are to be used for clarification purposes and to support existing documentation. This FAQ answers the question: How to represent patient identifiers (other than IHIs) in CDA documents
… identifiers (other than IHIs) in CDA documents? … The FAQs are guidance … identifiers (other than IHIs) in CDA documents … …
My Health Record B2B Gateway - Remove document
This guide will describe the steps to remove a Clinical Document
… will describe the steps to remove a Clinical Document. If your software product uploads Clinical Documents then you must have the option …
My Health Record Integration Toolkit v1.2.2
The My Health Record Integration Toolkit contains libraries for B2B connectivity to the My Health Record system, providing sample code for all operations, as well as the schemas used and sample SOAP request and response messages. The sample code and integration tools provided here should only be used in conjunction with the Agency’s detailed…
… the Agency’s detailed specifications for clinical documents and national infrastructure …
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…
… requirements applicable to all types of clinical documents. This includes references to …
My Health Record B2B Gateway - Upload document
This guide will walk through the steps to create and upload clinical documents
… through the steps to create and upload clinical documents. The following steps are …
Secure Messaging Integration Toolkit v1.2.5
The Secure Messaging Integration Toolkit contains libraries for B2B connectivity to Secure Message Delivery (SMD) and Endpoint Location Services (ELS), providing sample code for all operations, as well as a Medical Document Management (MDM) library to create the payload for SMD. It also includes secure messaging conformance test tools, which support the…
… the Agency’s detailed specifications for clinical documents and messaging infrastructure. …
My Health Record - Mobile integration
The Australian Digital Health Agency aims to increase the adoption of the My Health Record by connecting the My Health Record platform to mobile applications through industry-standard APIs.
… which is extracted for B2B. Access and Integration The integration approach … here Developer Guides - My Health Record Clinical Software The following Developer …