Common - Clinical Document v1.1

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

End products superseded by

A new version has been released for this end product

Please refer to Common - Clinical Document v1.1.1 or refer to the Release History for all releases of this End Product.

Identifier: 
EP-1457:2013
Date: 
09-10-2013
Type: 
application/zip
SHA256 Checksum: 
dce690ece5be307e31711f392a2ffd90a90875101124dff3748cea6a634814a1
Size: 
24.77 MB

Product Components

Product component
Identifier: 
NEHTA-1096:2011

The FAQs are guidance material for implementation. They are to be used for clarification purposes and to support existing documentation.

Product component
Identifier: 
NEHTA-1097:2011

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.

Product component
Identifier: 
NEHTA-1165:2012

The guidance contained in this document has been superseded and should no longer be used for implementations of clinical documents specifications.

Product component
Identifier: 
NEHTA-1191:2012

Australian CDA Schemas for Discharge Summary, eReferral, Event Summary, Shared Health Summary, Specialist Letter, Electronic Transfer of Prescription and National Prescription and Dispense Repository and My Health Record documents. 

Product component
Identifier: 
NEHTA-1192:2012

Australian CDA Compilable Schema (Extension 3.0) used to generate classes for Discharge Summary, eReferral, Event Summary, Shared Health Summary, Specialist Letter and My Health Recor documents. 

Product component
Identifier: 
NEHTA-1199:2012

This document:

Product component
Identifier: 
NEHTA-1200:2012

Generic Style sheet - Sample Stylesheet 1. This Style sheet is still valid but will NOT be further developed. Only major defects will be addressed. Revision.txt included in zip.

Product component
Identifier: 
NEHTA-1217:2012

This document describes the design for a Vendor End 2 End Portal on the External Reference Platform (XRP). The purpose of the portal is to enable collaboration and end to end testing between parties implementing the Agency specifications stack.

Product component
Identifier: 
NEHTA-1226:2011

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.

Product component
Identifier: 
NEHTA-1229:2011

This specification defines three logical models for clinical data that consists of a single CDA XML document and related byte streams. This specification also defines a possible serialised representation for those logical models.

Product component
Identifier: 
NEHTA-1255:2012

This FAQ answers the question: What is the appropriate use of date and date-time values in clinical documents?

Product component
Identifier: 
NEHTA-1256:2012

Question: When receiving a CDA® package, how can we ensure that the content is from a trusted source?

Product component
Identifier: 
NEHTA-1270:2013

This FAQ describes an extension to these eDischarge Summary, eReferral and Specialist Letter that involves encapsulating the CDA package within an HL7 v2 MDM^T02 message (which covers the delivery of a document).

Product component
Identifier: 
NEHTA-1271:2013

A list of attachment document types specified in the CDA Rendering Specification v1.0 and those supported by the My Health Record system.

Product component
Identifier: 
NEHTA-1276:2013

The FAQs are guidance material for implementation. They should be used for clarification purposes and to support existing documentation.

Product component
Identifier: 
NEHTA-1275:2013

The FAQs are guidance material for implementation. They should be used for clarification purposes and to support existing documentation.

This FAQ answers the question: What is the proper representation of pathology test result date/time?

Product component
Identifier: 
NEHTA-1277:2013

The FAQ Patient Medications has been archived and is no longer included in this end product release. Its contents have been superseded by updates to the latest versions of the CDA Implementation Guides for Event Summary and Specialist Letter document types.

Product component
Identifier: 
NEHTA-1278:2013

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?

Product component
Identifier: 
NEHTA-1283:2013

Generic Style sheet - Sample Stylesheet 2. This new Style sheet has been aligned more closely to the My Health Record system and has a better look and feel and layout compared with the 1.1.x version.

Product component
Identifier: 
NEHTA-1282:2013

Generic Style sheet - Sample Stylesheet 2. This New Style sheet has been aligned more closely to the My Health Record system and has a better look and feel and layout compared with the 1.1.x version. Revision.txt included in zip.

Product component
Identifier: 
NEHTA-1285:2013

CDA Packaging Library for wrapping up CDA documents and attachments - using latest CDA Packaging v1.0 specification (no metadata.xml) to support My Health Record and P2P messaging - Fixed ZipEntry for directories.

Product component
Identifier: 
NEHTA-1287:2013

HL7 MDM Library for wrapping up CDA Package for .net clients.

Product component
Identifier: 
NEHTA-1286:2013

HL7 MDM Library for wrapping up CDA package for java clients.

Product component
Identifier: 
NEHTA-1288:2013

Java eSignature Library

Product component
Identifier: 
NEHTA-1328:2013

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:

Product component
Identifier: 
NEHTA-1329:2012

Conformance test specification for clinical documents

Product component
Identifier: 
NEHTA-1330:2012

Conformance test specification for CDA rendering.

Product component
Identifier: 
NEHTA-1332:2013

CDA Document Library for Shared Health Summary, eReferral, Specialist Letter, Event Summary and Discharge Summary using CDA compilable schemas.

Product component
Identifier: 
NEHTA-1331:2012

Conformance Test Specification for CDA Packaging

Product component
Identifier: 
NEHTA-1378:2013

CDA Packaging Library for wrapping up CDA documents and attachments - using latest CDA Packaging v1.0 specification (no metadata.xml) to support My Health Record and P2P messaging - Fixed ZipEntry for directories.

Product component
Identifier: 
NEHTA-1473:2013

This release of the Common Clinical Document end product introduces updates to the conformance profile for clinical documents.

Product component
Identifier: 
NEHTA-1446:2013

This document provides conformance requirements applicable to all types of clinical documents.

Release history

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).

Back to Top