Security Requirements for My Health Record Connecting Systems Conformance Profile - FAQs
The Security Requirements for My Health Record Connecting Systems Conformance Profile contains software requirements that harden clinical information systems from cyber security attacks, uplift information security and protect patient information and your software product.
My Health Record Notice of Connection (NoC) and Conformance Compliance and Declaration (CCD) testing
Software products must pass testing requirements before gaining access to the My Health Record production system.
Electronic Prescribing - Mobile Intermediary System - Conformance Process
A mobile intermediary system is a software product that a mobile application uses to connect to, and interact with, the National Prescription Delivery Service (NPDS) and/or Active Script List Registry (ASLR).
Australian Digital Health Agency (ADHA) OID Repository
OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.
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.
PCEHR Connecting Systems - Conformance Test Specification Assisted Registration Amendment v1.1
Electronic Prescribing - Mobile Applications - Conformance Process
A mobile application or web-based application is used by a subject of care or carer to manage prescriptions and to present an electronic prescription token to a pharmacy.
Electronic Prescribing - CIS to NPDS or ASLR
The following steps will assist prescribing and dispensing Clinical Information System (CIS) software developers connect to the National Prescription Delivery Service (NPDS) and declare software conformance with the Agency’s Electronic Prescribing technical framework.
Security Requirements for My Health Record Connecting Systems - Conformance Profile - Draft v1.1
National Secure Messaging Network - FAQs
Information about NSMN solution design, Provider Directories, message formats, message content, reference data, testing, technical support, standards, terminology and more.
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.
My Health Record - Mobile integration
The Australian Digital Health Agency aims to increase the adoption of the My Health Record by connecting the My Health Record platform to mobile applications through industry-standard APIs.
PCEHR Connecting Systems - Conformance Test Specification v1.6
Participant Model Specification - Participant Model Specification v1.0
Participation Data Specification - Participation Data Specification v3.3
Clinical Information System (CIS) vs Contracted Service Provider (CSP) Software
A contracted service provider (CSP) in the My Health Record system is an organisation that provides technology services or health information management services relating to the My Health Record system to a healthcare provider organisation
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.
Electronic Prescribing - Connecting Systems - Conformance Profile v3.0.1
Electronic Prescribing - CIS with a Direct PDS
The following steps will assist Clinical Information System (CIS) software developers with a direct Prescription Delivery Service (PDS), declare software conformance with the Agency’s Electronic Prescribing technical framework.
NASH SHA-2 Certificates - Developer Guide
This Developer Guide is for the use of developers whose products connect to the Healthcare Identifiers (HI) Service, My Health Record, Electronic Prescribing and Secure Messaging with a National Authentication Service for Health (NASH) PKI Certificate.
HI Service - Search for HPI-I
It is highly recommended that your software conduct HPI-I searches for users of your system.