Home
Common - Clinical Documents

Common - Clinical Documents

Product

Context

The Common - Clinical Document end product provides developers of systems generating CDA documents with important updates of:

Clinical Documents - Common Conformance Profile;
Conformance Test Specification for Authoring Systems.

It also introduces a new FAQ document providing important guidance for the usage of qualifiers in structured parts of CDA documents.

Common - Clinical Documents Diagram

Specifications

Current Specifications:

Common - Clinical Document v1.5.2

Identifier:

EP-2807:2019

Specifications, guidance and associated collateral applicable to all types of clinical documents.

External Specifications:

Clinical document library java

The Clinical Document Packaging Library provides a sample implementation of how to package CDA documents (and any attachments) following the Agency specifications.

https://github.com/AuDigitalHealth/clinical-document-library-java

Roadmap

This product is in maintenance mode and no further releases are planned at this stage. The Agency may publish maintenance releases to address any defects. When new releases become available the Agency will send out email notifications to anyone who has previously downloaded the product.

Roadmap:

June, 2017

Completed

This incremental release of the Common - Clinical Document end product provides a new Conformance Test Specification for Authoring Systems and updates to the My Health Record Usability Recommendations.

May, 2016

Completed

This incremental release of the Common - Clinical Document provides updates to the Clinical Documents - Template Package Directory v1.7, the FAQ OIDs for HL7 has been revised and three FAQs from Common - Continuity of Care have been moved under this end product.

March, 2016

Completed

This incremental release of the Common - Clinical Document provides updates to the Clinical Documents – Template Package Directory v1.6.

January, 2016

Completed

This incremental release of the Common - Clinical Document provides updates for Clinical Documents – Conformance Test Specification for CDA Rendering and Clinical Documents – My Health Record Usability Recommendations.

December, 2015

Completed

This release provides a new product component, Conformance Test Specification for PCEHR Views v1.0, which provides a targeted set of test cases, managed using a Microsoft Excel workbook. This conformance test specification supports the currently published My Health Record views specifications and their conformance requirements.

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 Personally Controlled Electronic Health Records Act 2012 (Cth).

July, 2015

Completed

This incremental release of the Common - Clinical Document end product provides updates to the Conformance Test Specification for CDA Packaging and Template Package Directory.

April, 2015

Completed

This release introduces the conformance test specification for My Health Record usability and provides updates to the common conformance profile and the template package directory.

February, 2015

Completed

This release introduces an updated version of the Template Package Directory including references to updated template packages for eHealth Prescription Record v1.2 and eHealth Dispense Record v1.2. These updated template packages now support the inclusion of codes from the Australian Medicines Terminology (AMT) v3.

December, 2014

Completed

Includes an updated version of the Common – Clinical Documents - PCEHR Usability Recommendations and provides an update of the template package directory.

September, 2014

Completed

Includes maintenance updates for Clinical Documents – Common Conformance Profile and template package directory.

August, 2014

Completed

This incremental release of the Common – Clinical Documents end product introduces a template package directory to provide implementers of clinical document specifications and other stakeholders with a comprehensive overview of available template packages and their current status.

Foundational elements for digital health

By operation of the Public Governance, Performance and Accountability (Establishing the Australian Digital Health Agency) Rule 2016, on 1 July 2016, all the assets and liabilities of NEHTA will vest in the Australian Digital Health Agency. In this website, on and from 1 July 2016, all references to "National E-Health Transition Authority" or "NEHTA" will be deemed to be references to the Australian Digital Health Agency. 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 Personally Controlled Electronic Health Records Act 2012 (Cth).