This is a search for Pages, Articles, and Resources. Switch to a scoped search for Resources to find Products, Components, and Guides.
My Health Record B2B Gateway - Upload document
This guide will walk through the steps to create and upload clinical documents
… which would likely be entered by the healthcare provider which your system … 5 above. 1. Create a new class called EventSummarySample in our existing …
Healthcare Identifier Service - Individual Healthcare Identifiers Business Requirements v1.0
Component
NEHTA-1162:2009
Status
Active
Version
1.0
The purpose of this document is to define the high-level business requirements for Individual Healthcare Identifiers (IHIs) as part of the Healthcare Identifiers (HI) Service. The intention is to explain, at a high level: why IHIs are required; and the requirements that need to be included in the technical design and build of…
… business requirements for Individual Healthcare Identifiers (IHIs) as part of the Healthcare Identifiers (HI) Service. The …
Healthcare Identifier Service - Q&A for Healthcare Identifiers v1.0
Component
NEHTA-1190:2009
Status
Active
Version
1.0
Frequently Asked Questions regarding Healthcare Identifiers.
… Frequently Asked Questions regarding Healthcare Identifiers. … Frequently Asked Questions regarding Healthcare Identifiers. … …
Event Summary v1.5
Event Summary documents are used to capture key health information about significant healthcare events that are relevant to the ongoing care of an individual. Event Summary documents can be submitted to an individual’s digital health record by any participating organisation. For example, an Event Summary document could be submitted by an after-hours…
… key health information about significant healthcare events that are relevant to the ongoing …
PCA™ - Count and paging
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.
Healthcare Identifiers Integration Toolkit v1.2
The Healthcare Identifiers Integration Toolkit contains libraries for B2B connectivity to the Healthcare Identifiers service, used to search for IHI, HPI-Is and HPI-Os. The sample code and integration tools provided here should only be used in conjunction with the Agency's detailed specifications for the Healthcare Identifiers Service and, where appropriate…
… The Healthcare Identifiers Integration … libraries for B2B connectivity to the Healthcare Identifiers service, used to …
PCA™ - Create healthcare service
Now that we have created a Location we want to add one or more Healthcare services that are delivered at that Location.
… a Location we want to add one or more Healthcare services that are delivered at … "valueString": "Australia/Brisbane" } ] }, "availableEndTime": …
HI Service - Test and Go Live
All products developed, or updated, to connect with the HI Service are required to undergo testing before production access is granted.
… that you will need to complete: 1. Healthcare Identifiers Notice of … [email protected] 2. Healthcare Identifiers Conformance …
Healthcare Identifiers Service - Support Documents v1.4
This release of the end product contains a reorganisation of worksheets to provide for requirement #22000 and Electronic Prescribing has been introduced. The supporting documents on this page provide background and guidance for healthcare provider organisations, and conformance, compliance and accreditation requirements for vendors. For more…
Event Summary - My Health Record Conformance Profile v1.5
Component
DH-3418:2022
Status
Active
Version
1.5
This document provides the requirements for producers and consumers of Event Summary documents that connect to the My Health Record system. It lists the specific conformance requirements for Event Summary documents in the context of the My Health Record system and provides references to all other documents that specify requirements applicable to event…
My Health Record Software Vendor Welcome Pack - Vendor Product Details Form v20190903
Component
DH-2941:2019
Status
Active
Version
20190903
A form to be completed by new software vendors intending to connect their software to the My Health Record system. It captures information about the software vendor organisation and their software product.
… ndorWelcomePack_VendorProductDetailsForm_v20190903.docx …
Event Summary - Release Note v1.5
Component
DH-3416:2022
Status
Active
Version
1.5
This minor release of the Event Summary specification bundle includes the following change to the Event Summary – My Health Record Conformance Profile: Document subtyping introduced to improve clinical document discoverability. The following change was also made to the Event Summary – Template Package Library: List of non-critical and non…
… of non-critical and non… … DH_3416_2022_EventSummary_ReleaseNote_v1.5.pdf …
My Health Record Software Vendor Welcome Pack - Software Vendor Support Contacts v20190903
Component
DH-2942:2019
Status
Active
Version
20190903
A list of support contacts, listing the appropriate support channel by scenario.
Healthcare Identifier Service - Concept of Operations v2.0
Component
NEHTA-1163:2010
Status
Active
Version
2.0
This Concept of Operations provides an overview of the Healthcare Identifiers Service by: describing the current state of healthcare identification; describing the Healthcare Identifiers (HI) Service in such a way that key stakeholders can visualise how the HI Service will be used and how it will work; documenting key concepts…
… Operations provides an overview of the Healthcare Identifiers Service by: describing the current state of healthcare identification; describing the …
Electronic Prescribing - Notification of Intent v20191031
Component
DH-2994:2019
Status
Active
Version
20191031
This form is to be completed by Open Prescription Delivery or Active Script List Registry Service software vendors. By submitting this form, you are consenting for the Australian Digital Health Agency (the Agency) to disclose the information in this form about you, your organisation and your product to the Department of Human Services (DHS) and contractors…
… ectronicPrescribing_NotificationofIntent_v20191031.pdf …
Event Summary - CDA Implementation Guide v1.3
Component
NEHTA-1846:2015
Status
Active
Version
1.3
This document provides a guide to implementing the 'logical' model detailed in the Agency's Event Summary Structured Content Specification (SCS) as an HL7 Clinical Document Architecture Release 2 (CDA) XML document. The guide takes implementers step by step through mapping each data component of the Event Summary SCS to a corresponding CDA attribute or…
… submission of event summaries from healthcare providers to shared health …
Requesting IHIs for Newborns - A Guide for Healthcare Provider Organisations v1.0
Component
NEHTA-1819:2014
Status
Active
Version
1.0
This document provides guidance for a healthcare provider organisation implementing the Create Verified IHI for Newborns web service to request a verified IHI from the HI Service for newborns. It does not provide advice about technical implementation of the web service within the HI Service.
… This document provides guidance for a healthcare provider organisation … … This document provides guidance for a healthcare provider organisation …
HI Service - Search for HPI-I
Guide
DG-3092
Status
Active
Version
1.0
It is highly recommended that your software conduct HPI-I searches for users of your system.
… The primary reason for this is that most healthcare provider individuals do not … Case Name UC.131 Outline To retrieve a Healthcare Provider Identifier Individual …
Healthcare Identifiers Integration Toolkit - Release Note v1.2
Component
DH-2611:2018
Status
Active
Version
1.2
Version 1.2 of the Healthcare Identifiers Integration Toolkit provides defect fixes and performance improvements for the Healthcare Identifiers B2B Client Library.
… Version 1.2 of the Healthcare Identifiers Integration … and performance improvements for the Healthcare Identifiers B2B Client …
Healthcare Identifiers Service - Support Documents - Conformance Profile v4.0
Component
DH-3360:2020
Status
Active
Version
4.0
This software conformance requirements specification supports the safe use of healthcare identifiers in health software systems. The conformance requirements listed apply to one or more business use cases, where each business use case describes a scenario in which healthcare identifiers are used.
… specification supports the safe use of healthcare identifiers in health software … use case describes a scenario in which healthcare identifiers are used. … This …
Event Summary - Structured Content Specification v1.2
Component
NEHTA-1847:2015
Status
Active
Version
1.2
This document describes the structured component specifications and guidelines to be adopted when producing electronic Event Summary documents for sharing within the Australian healthcare community. This specification references or contains excerpts of intellectual property (IP) owned by the Regenstrief Institute, IHTSDO, or HL7 International…
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…
… for health software that uses Healthcare Identifiers. A developer who … conforms to the requirements for using healthcare identifiers must complete this …
Clinical Terminology - Guidance for Use in Healthcare Software v1.0
Component
NEHTA-1786: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…
… – Australian Release (SNOMED CT AU) in healthcare software. This guidance … _2014_ClinicalTerminology_GuidanceforUseinHealthcareSoftware_v1.0.pdf …
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…
… This document provides guidance to aid healthcare organisations provide high … 3Model_ImplementationProcessandGuidanceforHealthcareOrganisations_v1.0.pdf …