Standards search

This document describes Early Years (EY) Assessment Form and User's Manual: For Use with Community-Based Assessments (Standard English Edition), 10.0 and supports consistent use in digital health settings.

This document describes Early Years (EY) Assessment Form, 10.0 - License to Print and supports consistent use in digital health settings.

This document describes Emergency Department (ED) Assessment System Manual: For use with the interRAI ED Screener (EDS) and ED Contact Assessment (ED-CA), (Standard English Edition), 9.3.0 and supports consistent use in digital health settings.

This document describes Emergency Department Contact Assessment (ED-CA) Assessment Form, (Standard English Edition), 9.3.0 - License to Print and supports consistent use in digital health settings.

This document describes Emergency Screener for Psychiatry (ESP) Assessment Form and User's Manual, (Standard English Edition), 9.1.1 and supports consistent use in digital health settings.

This document describes Emergency Screener for Psychiatry (ESP) Assessment Form, (Standard English Edition), 9.1.1 - License to Print and supports consistent use in digital health settings.

This document describes Family Survey on Long-Term Care Facility Quality of Life (FamQOL) (Standard English Edition), 10.0.0 and supports consistent use in digital health settings.

This document describes FamQOL Self-Reported Surveys and Scoring Templates, (Standard English Edition), 10.0.0 and supports consistent use in digital health settings.

This document describes FamQOL Self-Reported Surveys and Scoring Templates, (Standard English Edition), 10.0.0 and supports consistent use in digital health settings.

This document describes Functional Supplement to CHA (CHA-FS) Assessment Form, (Standard English Edition), 9.1.1 - License to Print and supports consistent use in digital health settings.

This document describes Home Care (HC) Assessment Form (Standard English Edition), 10.0 - License to Print and supports consistent use in digital health settings.

This document describes Home Care (HC) Assessment Form (Standard English Edition), 9.1.2 - License to Print and supports consistent use in digital health settings.

This document describes Home Care (HC) Assessment Form and User's Manual (Standard English Edition), 10.0 and supports consistent use in digital health settings.

This document describes Home Care (HC) Assessment Form and User's Manual, (Standard English Edition), 9.1.2 and supports consistent use in digital health settings.

This document describes Intellectual Disability (ID) Assessment Form and User's Manual, (Standard English Edition), 9.2.1 and supports consistent use in digital health settings.

This document describes Intellectual Disability (ID) Assessment Form, (Standard English Edition), 9.2.1 - License to Print and supports consistent use in digital health settings.

The My Health Record SVT environment allows software vendors to build and test the B2B Gateway web services for interactions with the My Health Record system. To express your interest in connecting to the My Health Record SVT environment or if you require further information about software vendor testing, please contact Customer Support at help…

From 25 May 2022, any application using interaction model 4 and provider apps to connect to the SVT environment must trust the new My Health Record public SSL certificate in the app’s intermediary server trust store. My Health Record - FHIR Mobility Certificate V1.1 removes the Apache Server instructions and text files related to language…

This version is an update to address a defect with the generation of XDS metadata for Pathology Report and Diagnostic Imaging Report documents. "My Health Record" is the new name of the system previously known as "PCEHR". This is reflected in the name of this updated product component.

This document seeks to assist software vendors with implementing the Clinical Information System to National Provider Portal (CIS to NPP) interface implementation.

These test cases have been written against the specified requirements in the Electronic Prescribing - Software Conformance Profile v3.0.1 document.

The Electronic Prescribing - Declaration of Conformance v2.0 has been developed in consultation with key participants in the Electronic Prescribing community to better address the requirements of the contemporary Conformance Assessment Scheme (CAS), and to clearly articulate vendor roles and responsibilities. It was redesigned as a form that can be filled,…

In this guide, we will be accessing Prescription and Dispense List and Allergies List contained in a patient’s clinical document service

Within these guides we will demonstrate the functionality of the FHIR® Gateway using Xamarin.Forms in Visual Studio and the Android Emulator

This guide will look at retrieving all clinical document data (including these 2, but excluding MBS documents)

In this tutorial, you will; register as a developer for the Gateway, understand your testing obligations and more

When a patient has an appointment with a healthcare provider, and that healthcare provider is eligible for a Medicare rebate, a Medicare Benefits Schedule (MBS) clinical document is sent to Medicare

We will use the token received from MyGov to access the patient’s My Health Record

In this guide, we will be accessing a patient’s medications and allergies contained in a Personal Health Summary

The Agency released the Security Requirements for My Health Record Connecting Systems Conformance Profile (Security Profile) draft v1.1 in September 2023 and invited stakeholder feedback during a review period that extended into early November. This document summarises the key themes from stakeholder feedback provided to the Agency. The Agency anticipates…

The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth Reference Platform, forming part of the code library for tools and simulators.

This standard identically adopts ISO 81001 1:2021, which provides the principles, concepts, terms and definitions for health software and health IT systems, key properties of safety, effectiveness and security, across the full life cycle, from concept to decommissioning.

This standard identically adopts IEC 82304 1:2016, which provides requirements for the safety and security of health software products designed to operate on general computing platforms and intended to be placed on the market without dedicated hardware, with a primary focus on the requirements for manufacturers.

Demonstrates the relationship between the codes in the World Health Organization's ICD-10 and the Australian Modification of ICD-10 (ICD-10-AM). The maps describe a directional relationship between a classification where the data is recorded in (the source classification) to the classification the data needs to be reported in (the target classification). The relationship between two classification systems is described using one of two possible types of maps: � One-to-one. This type of map is used where a code from the source classification is only linked with one code from the target classification. � One-to-many. This type of map is used where a code from the source classification is linked with more than one code from the target classification, which may be of different types. Where a code has a one-to-many relationship, a new row is used to demonstrate this relationship. The source classification code is repeated against different target classification codes.

This document establishes requirements and gives guidance on assurance case framework for healthcare delivery organisations (HDOs) and for health software and medical device manufacturers (MDMs) and can be used to support the communication and information transfer between all parties.

This document provides quality requirements for health apps and defines a health app quality label in order to visualise the quality and reliability of health apps.

This standard provides a framework of life cycle processes with activities and tasks necessary for the safe design and maintenance of medical device software. This standard provides requirements for each life cycle process. Each life cycle process is further divided into a set of activities, with most activities further divided into a set of tasks.

A map between the supplementary codes for chronic conditions (Chapter 21 Codes for special purposes, U78-U88 Supplementary codes for chronic conditions) to the equivalent codes in the disease chapters of ICD-10-AM.

Provides the link between two editions of the classification. Backward maps - provides equivalent code for new codes in the newer edition Forward maps - provides equivalent codes for deleted codes in the newer edition The maps provide an equivalent code that best matches the concept from a clinical perspective (called historical maps) as well as an AR-DRG perspective (called DRG maps - previously logical maps). Sometimes the historical map and the DRG map are the same code. Multiple historical maps are provided where there are multiple codes that can be mapped from one edition to the next. The first historical map provided in the mapping table is the closest match to code descriptor, alphabetic index entries or relevant coding conventions. To map between multiple editions, users need to use all the mapping tables between these editions. For example, to map between Tenth Edition and Twelfth Edition, users need to use the mapping tables for both Eleventh Edition and Twelfth Edition. Codes need to be mapped from Tenth Edition to Eleventh Edition, then from Eleventh Edition to Twelfth Edition.

Provides the map between MBS item numbers to the equivalent stem code in ACHI Twelfth Edition. ACHI is based on the MBS and further expanded to cover interventions not part of the MBS such as dental, allied health interventions, cosmetic surgery. It uses a numeric coding scheme structured by body system, site and intervention type. ACHI codes have seven numeric digits. For most codes the first five digits are the MBS item number, followed by a two-digit extension.

The map connects PBS data, which lists medications subsidised by the Australian government, with the Australian Medicines Terminology (AMT), a SNOMED CT-based terminology. This integration helps ensure that both pharmaceutical and clinical systems use consistent terminology

The Australian Register of Therapeutic Goods Identification (ARTG ID) reference set, is a component of the AMT (and SNOMED CT-AU). Its purpose is to link medicines and other therapeutic goods to their corresponding entries in the ARTG.

The document provides a framework of environmental sustainability and climate resilience actions that use a health service organisation's existing governance, safety and quality systems.

This document provides readers with an understanding of what artificial intelligence (AI) is and how it may impact the digital systems and services they use.

Smart places are places that use smart technology (IT)-enabled systems to provide enhanced services to citizens. This document explores the key security risks of smart places and ways to mitigate risk.

This document provides organisations with guidance on how to use artificial intelligence (AI) systems securely.

Provides the link between two editions of the classification.
Backward maps provides equivalent code for new codes in the newer edition.
Forward maps provides equivalent codes for deleted codes in the newer edition.
The maps provide an equivalent code that best matches the concept from a clinical perspective (called historical maps) as well as an AR-DRG perspective (called DRG maps previously logical maps). Sometimes the historical map and the DRG map are the same code.