Clinical Document Architecture with Australian Schema - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Home

Official URL: http://ns.electronichealth.net.au/cda/ImplementationGuide/au.digitalhealth.cda.schema				Version: 1.0.0
Draft as of 2024-08-29				Computable Name: ClinicalDocumentArchitectureAuSchema
Copyright/Legal: Copyright © 2024 Australian Digital Health Agency - All rights reserved. This content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/.

Introduction

This Australian Digital Health Agency FHIR Implementation Guide is a representation of the Clinical Document Architecture (CDA) R2.0 specification using HL7^® FHIR^®© Logical Models expressed as HL7^® FHIR^®© StructureDefinition instances.

It is an adaptation of the HL7 International CDA Logical Model Specification with specific modifications and inclusions to represent the CDA schema including Australian CDA extensions using the FHIR StructureDefinition framework.

Document purpose and scope

The primary aim of this implementation guide is to support implementers who are contemplating a transition from CDA to FHIR. It contains CDA extensions in Australian context and the HL7 CDA classes using the Australian extensions.

This implementation guide does not describe presentation of the information, user experience, or expected behaviour of producing and receiving systems.

Wherever possible, material in this specification is based on existing standards. All efforts have been made to minimise divergence from the HL7 international CDA classes to provide for system interoperability and compatibility with other classes. Issues of an editorial nature in the source material (such as spelling or punctuation errors) are intentionally reproduced.

Context and use

This CDA extensions logical model FHIR implementation guide should be read in conjunction with the remaining documentation available from HL7 International CDA Logical Model Specification.

The guide includes:

• CDA extensions used in Australian context
• CDA classes in the form of structure definitions
• Vocabularies for the content exchange

Intended audience

This implementation guide is aimed at software development teams, architects, and designers of CDA implementation in Australia.

This implementation guide and related artefacts are technical in nature and the audience is expected to be familiar with the language of health data specifications and to have some familiarity with health information standards and specifications, such as CDA.

Document information

Intellectual property considerations

This implementation guide and the underlying FHIR specification are licensed as public domain under the FHIR license.

This publication includes IP covered under the following statements.

• ISO Maintains the copyright on the country codes, and controls it's use carefully. For futher details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
  Show Usage
  • ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code: AD, CD... Show 101 more, CE, CV, ClinicalDocumentArchitectureAuSchema, Container, EntryRelationship, Specimen, SpecimenRole, TEL, administrativeGenderCode, admissionReferralSourceCode, asEmployment, asEntityIdentifier, asIngredient, asPersonalRelationship, asQualifications, asQualifiedEntity, asSpecimenInContainer, assigningGeographicArea, au-Act, au-AssignedAuthor, au-AssignedCustodian, au-AssignedEntity, au-AssociatedEntity, au-Author, au-AuthoringDevice, au-ClinicalDocument, au-Component, au-ComponentOf, au-Custodian, au-CustodianOrganization, au-Device, au-EncompassingEncounter, au-Encounter, au-EncounterParticipant, au-Entity, au-EntityName, au-Entry, au-ExternalAct, au-ExternalDocument, au-HealthCareFacility, au-InFulfillmentOf, au-Informant, au-InformationRecipient, au-IntendedRecipient, au-LegalAuthenticator, au-ManufacturedProduct, au-Material, au-Observation, au-ObservationMedia, au-ObservationRange, au-Order, au-Organization, au-OrganizationName, au-OrganizationPartOf, au-Organizer, au-ParentDocument, au-Participant1, au-Participant2, au-ParticipantRole, au-Patient, au-PatientRole, au-Performer2, au-Person, au-PersonName, au-Place, au-PlayingEntity, au-Precondition, au-Procedure, au-RecordTarget, au-Reference, au-RegionOfInterest, au-RelatedDocument, au-Section, au-StructuredBody, au-SubstanceAdministration, au-Supply, au-languageCommunication, code, completionCode, controlAct, coverage, coverage2, deceasedInd, deceasedTime, desc, employerOrganization, entitlement, expirationTime, formCode, id, ingredientManufacturedMaterial, methodCode, multipleBirthInd, multipleBirthOrderNumber, name, participant, personalRelationship, subjectOf1, subjectOf2, substitutionPermission and telecom
• This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
  Show Usage
  • LOINC: ExternalDocument, ParentDocument... Show 4 more, Section, au-ExternalDocument, au-ParentDocument and au-Section

Relationships with other work

This implementation guide builds on other specifications, helping ensure a consistent approach to data sharing that should ease adoption. The specific guides used, and the portions relevant from each of them are as follows:

Package hl7.fhir.uv.extensions.r5#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Global profiles

There are no Global profiles defined

Known issues

This table lists known issues with this specification at the time of publishing. We are working on solutions to these issues and encourage comments to help us develop these solutions.

Reference	Description
https://github.com/HL7/CDA-core-sd/issues/19	The terminology binding on the au-Participant1 `@typeCode` attribute has been changed to use the v3-ParticipationType valueSet rather than the valueSet as used in HL7 International CDA Participant1 class. This is due to the attribute value of `PART`, which is mandated in many of the My Health Record CDA implementations.