Information about NSMN solution design, Provider Directories, message formats, message content, reference data, testing, technical support, standards, terminology and more.
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.
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.
After successfully executing the IHI Lookup, it is important to modify your implementation to meet the Test Cases for the Use Cases we have built to UC.010 and UC.015.
The Agency is cognisant of the inherent cyber security risks posed by systems connected to and accessing the My Health Record system, as well as potentially vulnerable aspects of the national infrastructure and all services under its care.
How do I populate MSH-3, MSH-4, MSH-5 and MSH-6 segments of the outgoing REF-I12 and MDM-T02 messages to support successful message exchanges?
Successful message exchange is dependent upon the correct population of segments MSH-3, MSH-4, MSH-5 and MSH-6 of outgoing messages.
It is highly recommended that your software conduct HPI-I searches for users of your system.