Site search

OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.

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…

The NESAF v4 Standards Mapping describes a suite of standards that have been referenced or mapped in the development of the NESAF, which may provide useful references for readers seeking a deeper understanding of this domain. It is intended primarily for business executives and ICT professionals.

The NASH Organisation Certificate Tracker is a simple tool for listing the expiration dates of NASH PKI certificates for healthcare provider organisations. The product data sheet provides essential information about the capabilities, limitations and prerequisites of the tool.

RCPA  - APUTS Chemical Pathology Terminology Reference Set provides a set of terms for reporting chemical pathology in Australia and their associated codes and preferred units. Specifically, it provides preferred terms and units for reporting chemical pathology test results, which can be used in the electronic communication of a pathology report…

This release includes updates to the eHealth Pathology Report View Presentation Guide based on feedback from early implementers. The updates give software developers greater flexibility in designing software and meeting conformance requirements. The changes are largely related to column headings, displaying text blocks where space is limited, as well as…

The CDA Validator has been superseded by the Clinical Package Validator.

  Clinical Document Library (Java) to support the PCEHR R5 documents Pathology Report and Diagnostic Imaging Report. This product component was previously called CDA Document Library - Java Sample Code. The name has changed but the content has not changed.   This document mentions the NPDR. Please note: the National Prescription…

This is the introduction to the functional design, and the document includes all business processes developed during the project. Of the detailed design documents, this one should be read first. Previous file name: Vic IHI Integration IHI functional design (Summary & Business Processes) v2.1.pdf

This document presents the information requirements for Consumer Entered Notes. These are a logical set of data items for use in the My Health Record system and are therefore independent of any particular platform, technology, exchange format or presentation format. Clarification: PCEHR means the My Health Record, formerly the "Personally Controlled…

This document summarises the requirements for producers and consumers of the Australian Organ Donor Register clinical document that connect to the My Health Record system. This document lists the specific conformance requirements for the Australian Organ Donor Register clinical document that are in addition to the Clinical Documents - Common Conformance…

This document provides an overview of the changes for each HIPS Mobile release and can be used to identify the defect fixes and functional enhancements that have been incorporated.

The content covered in this FAQ has been clarified in the Document Exchange Technical Services Specification, section 4.1 as well as through the introduction of Conformance Point DEXS-T 124.

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

This Business Requirements Specification document provides the high-level requirements, business models and use case descriptions of the e-Referrals Release 1.1 package, relevant to the exchange of referral documents within Australia. The package describes the specifications and guidelines to be adopted by implementers when developing…

This document lists the specific conformance requirements for the PCEHR Prescription Record v1.0 and PCEHR Dispense Record v1.0 clinical documents that are in addition to the Common Conformance Profile for Clinical Documents. Please note that this document has been superseded by two separate conformance profiles: NEHTA-1455:2013 PCEHR Prescription Record …

Before you can create a PractitionerRole, you must first find an existing Practitioner using their AHPRA Registration Number.

Once a business partner has attempted to match the service offerings that a publisher has authorised, it may provide the status of those matches back to the PCA for the publisher to download. This provides confirmation back to the publisher of the status of matched records.

In cases when a publisher submits a business partner identifier and the business partner identifies that an incorrect identifier has been provided the business partner can patch the identifier provided in PCA.

After creating a healthcare service(s) at a location, you can search for available partner services.

When you have found a partner service (HealthcareService), you can download the information use statement to inform the publication authorise operation.

The _count search parameter returns the number of requested resources per page (excluding the resources returned with _include search parameter) as requested by the client.

Now that you have created an Organization and HealthcareService at a Location, and have found a Practitioner, you can create a PractitionerRole.

Now that we have created a Location we want to add one or more Healthcare services that are delivered at that Location.