SMD eReferral Topic Sheet V1.1 (Profile 7.8.1)

terms terms definitions nehta national e health transition authority hpi i healthcare provider identifier – individual hpi o healthcare provider identifier – organisation ihi individual healthcare identifier csp contracted service provider pcehr personally controlled electronic health record purpose this document describes the setup and use of the secure message delivery service of nehta this service isintegrated into profile through the use of the healthlink messaging system client application, healthlink six(hmsv6 6 3 3102) which must be configured as a separate activity at the present time, only ereferrals can be sent using this delivery service note that the existing rsd delivery service is still available and has not changed in functionality intended audience practice managers or systems administrators intending on setting up the smd service in profile providers intending on exchanging ereferrals using smd the practice should consider the smd implementation a very similar but more secure – version of the rsddelivery of ereferrals both delivery systems use healthlink’s system of incoming and outgoing folders deliver hl7 messagesif a practice is not using smd – they can still use the rsd system background profile has been changed to bring it into conformance with the australian secure messaging delivery standard this standard is met by the messaging provider system – healthlink this enables profile to exchange ereferrals with other smd compliant healthcare providers as depicted in the diagram below this is one component of the nehta requirement for the completion of a nationwide personally controlled electronic health record (pcehr) system a personally controlled electronic health record (pcehr) is a secure, electronic record of a patient’s medical history, stored and shared in a network of connected systems the pcehr will bring key health information from a number of different systems together and present it in a single view assumptions the health identifiers service has been set up the exchange of messages using healthlink’s smdrequires that both parties have hi service identifiers the practice has received its nash certificate the practice has installed the healthlink messaging system client application, healthlink six (hmsv6 6 3 3102) the practice has created the incoming and outgoing directories for the healthlink application to exchange messages note smd (like rsd) will only be successful if both parties are participating – i e they have set up the appropriate certificates, healthlink software, hi service and so on just because an external provider has a hpi o and hpi i number does not automatically imply that they are using smd for exchange of their ereferrals it may be necessary to confirm this with the external provider smd changes set up installing emessage service for smd the practice must have installed the nash certificate for its hpi o the same certificate is used for secure message delivery pcehr access the setup process has been streamlined into one emessage with 2 tabs either pcehr or ereferral can be set up separately or both can be set up (the certificate will have a subject name similar to general 8003623233351435 id electronichealth net au) if the practice has set up an ereferral or a pcehr emessage service, these should be deleted and replaced with the single ehealth access service go to organisation\preferences\emessages drag ehealth access service from available services to installed services once the new ehealth access service window opens update the name to “ehealth access service” leave pos blank enter your organisation’s certificate passphrase into the box then click import, profile will prompt you to browse to and select your nash hpi o certificate (fac sign p12), once selected click ok this will import the certificate click test, this should pop up stating that the certificate is valid enter the hpi o for the organization and the organization name name must match that on the certificate the number and name will be verified with the hi service click on the ereferral tab and enter the appropriate folder locations these will be used sending / receiving ereferrals using smd click ok preparing an ereferral for smd delivery the following steps are used to prepare an ereferral to be delivered using smd ensure the external provider (receiver) of the emessage has an hpi i and hpi o numbers these are required for the message create a new outbound referral – make sure the following data is present click on the reason letter tab to add a letter and the attachments tab to add any existing document to the ereferral when ready to send the ereferral, click on emessage, the following dialog will appear preview ereferral will check the referral error messages may appear that data is missing or the emessage is incorrectly set up if there are no errors, the message will be previewed and then can be sent once sent, the document is then frozen and the letter status is set to fina attachments