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 Views
This guide will use the My Health Record getView web service to download collated information from a My Health Record in a ‘View’
… package (zip file) that contains two XML files. In the next steps we will call the … // This value overrides anything defaulted in the xslt …
Victoria IHI Pre-Implementation Project - Detailed IHI Functional Design for IHI Processing v2.1
Component
NEHTA-1353:2011
Status
Active
Version
2.1
These use cases effectively form the intermediary layer between business processes and user initiated functions, and the HI Service. This includes the functions to search for an IHI, to check the IHI, and to perform batch processing of the IHI. This document contains the bulk of the complex processing in the IHI integration design. The Validate IHI is…
… the intermediary layer between business processes and user initiated functions, … to check the IHI, and to perform batch processing of the IHI. This document …
Australian Digital Health Agency (ADHA) OID Repository
Guide
DG-3127
OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.
… government. 1.2.36.1.2001.1005.15 State Authority Number State Authority … Note that this OID is provided as a default option; if the organisation has …
Electronic Prescribing – Frequently Asked Questions
Electronic Prescribing Frequently Asked Questions covering topics such as Prescribing Systems, Dispensing Systems, Mobile Applications, Mobile Intermediaries, Transitional eNRMC and Conformance Profile and more.
… in accordance with their relevant state and territory drugs and poisons (or … can be used for PBS, RPBS and private medicines, and they can be …
PCA™ - Subscriber capability statement
The capability statement of the Publisher Agent is specific to the organisation and can be accessed using:
… Quick intro The capability statement of the Publisher Agent is … the command: FHIR server - Capability Statement FHIR server Capability …
Victoria IHI Pre-Implementation Project - Detailed IHI Functional Design Summary and Business Processes v2.1
Component
NEHTA-1355:2011
Status
Active
Version
2.1
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
… and the document includes all business processes developed during the project. … functional design (Summary & Business Processes) v2.1.pdf … This is the …
Common - Continuity of Care - FAQ Global Statements None Known v1.1
Component
NEHTA-1274:2013
Status
Active
Version
1.1
A global exclusion statement is common in CDA clinical documents and has three possible values: None known Not asked None supplied This FAQ answers the question: What is the proper use of none known in global exclusion statements
… A global exclusion statement is common in CDA clinical … use of none known in global exclusion statements? … A global exclusion …
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
… PatientDocument class in step 4 below. private void GetDocumentList(string … with a CDA package that contains two XML files. We will call this web service, …
National Product Catalogue - Procurement Process Paths v1.0
Component
NEHTA-0308:2008
Status
Archived
Version
1.0
When a process is highly automated as it is in e-Procurement, it loses the capacity for easy human intervention when exceptional situations occur. This is because the goal of automation is to eliminate the need for human intervention. In order to minimise the impact of exceptional situations on automated systems, it is wise to fully review the existing…
… When a process is highly automated as it is in … it is wise to fully review the existing processes through the entire process path …
SNOMED CT-AU - Combined Release File v20161130
Component
DH-2477:2016
Status
Active
Version
20161130
This is the data file for the SNOMED CT-AU and AMT combined release for November 2016. It contains all of the relevant data, including the SNOMED CT core terminology files, the Australian Dialect Reference Set, and other reference sets for use in Australian healthcare.
Electronic Prescribing - State and Territory Legislative Readiness and Technical Requirements v2.3
Component
DH-3281:2020
Status
Archived
Version
2.3
Each software developer needs to consider the jurisdictions they think their software will operate in and consider the legal obligations for those jurisdictions. Software developers are responsible for contacting their relevant state and territory regulation authorities to attain this information. This document has been developed and is maintained by the…
… for contacting their relevant state and territory regulation … for contacting their relevant state and territory regulation …
Healthcare Identifiers Service - Support Documents - Implementation Conformance Statement Proforma and Instructions v4.1
Component
DH-3501:2021
Status
Active
Version
4.1
The Agency, in conjunction with industry (including Services Australia, Medicare Australia, the Department of Health, MSIA, AIIA and ACIVA, and state and territory health jurisdictions), has specified a set of conformance requirements for health software that uses Healthcare Identifiers. A developer who wishes to claim that their software conforms to…
… of Health, MSIA, AIIA and ACIVA, and state and territory health … of Health, MSIA, AIIA and ACIVA, and state and territory health …
My Health Record - App Vendor Guide to the Connection Process v1.2
Component
DH-3710:2023
Status
Active
Version
1.2
This document describes the process involved in developing an application (app) that connects with the My Health Record system.
… This document describes the process involved in developing an … system. … This document describes the process involved in developing an …
Electronic Prescribing - State and Territory Legislative Readiness and Technical Requirements v2.3
Each software developer needs to consider the jurisdictions they think their software will operate in and consider the legal obligations for those jurisdictions. Software developers are responsible for contacting their relevant state and territory regulation authorities to attain this information. This document has been developed and is maintained by the…
… for contacting their relevant state and territory regulation … for contacting their relevant state and territory regulation …
Provider Connect Australia - Implementation Conformance Statement v2.0
Component
DH-3824:2023
Status
Active
Version
2.0
This document specifies software Implementation Conformance Statement (ICS) for Integrated Systems connecting to the Provider Connect Australia (PCA) solution. A developer who wishes to claim that their software conforms to the requirements for connecting to PCA must complete this ICS to indicate which requirements are satisfied by their implementation…
… software Implementation Conformance Statement (ICS) for Integrated Systems … software Implementation Conformance Statement (ICS) for Integrated Systems …
SNOMED CT-AU - Release File Bundle v20150531
Component
NEHTA-2068:2015
Status
Withdrawn
Version
20150531
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…
… of the release file in preparation for future integration work. Earlier versions …
Provider Connect Australia™ - Information Use Statements - Guide for Business Partners v1.1
Component
DH-3761:2023
Status
Active
Version
1.1
This document is a guide for Business Partners to use when developing their Information Use Statements for each partner service they have registered in Provider Connect Australia™ (PCA™).
… when developing their Information Use Statements for each partner service they … when developing their Information Use Statements for each partner service they …
Information Quality Rules - Configuration File v1.6
Component
DH-2900:2019
Status
Active
Version
1.6
The Information Quality Rules Configuration File supports the Information Quality Rules (IQ Rules). The Information Quality Rules (IQ Rules) is a tool that helps developers, testers and analysts determine the quality of clinical documents including the conformance of clinical documents to the My Health Record system conformance requirements.
SNOMED CT-AU - Reference Set Implementation Process and Guidance for Vendors v1.0
Component
NEHTA-1956:2015
Status
Withdrawn
Version
1.0
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…
… 015_SNOMEDCT-AU_ReferenceSetImplementationProcessandGuidanceforVendors_v1.0.pdf …
Secure Message Delivery - Implementation Conformance Statement Proforma v1.0.1
Component
NEHTA-1896:2014
Status
Active
Version
1.0.1
Proforma for providing detailed information about conformance to the Australian Technical Specifications.
… eMessageDelivery_ImplementationConformanceStatementProforma_v1.0.1.doc …
Australian Medicines Terminology v3 Model - Implementation Process and Guidance for Healthcare Organisations v1.0
Component
NEHTA-1952:2014
Status
Withdrawn
Version
1.0
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…
Clinical Terminology - Guidance for People and Processes v1.0
Component
NEHTA-1785:2014
Status
Withdrawn
Version
1.0
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…
… 4_ClinicalTerminology_GuidanceforPeopleandProcesses_v1.0.pdf …
SNOMED CT-AU - Reference Set Implementation Process and Guidance for Healthcare Organisations v1.0
Component
NEHTA-1955:2015
Status
Withdrawn
Version
1.0
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…
My Health Record Software Vendor Welcome Pack - Software Vendor Guide to the Connection Process v1.9
Component
DH-3874:2023
Status
Active
Version
1.9
This document describes the steps required in preparing a Clinical Information System (CIS) or software used by a Contracted Service Provider (CSP) for connection to the My Health Record system (previously known as PCEHR or Personally Controlled Electronic Health Record).
… Vendor Guide to the Connection Process v1.9.pdf …