ASL connection troubleshoot

Medisecure Adaptor Version

Go to Options and check which machine is set as Medisecure machine. Log into that machine.

Open

1. Open the Medisecure adaptor and check the version number. In order for ASL to work the version number needs to be 2.5.19 or above. If you have an older version, then:

   • Call Mediscure invite them to TeamViewer and ask them to upgrade

   • Upgrade it yourself by running the installer \Phcypro\MediscureAdaptorSetup.mi

   • Download the latest installer from the medisecure website http://www.medisecure.com.au/downloads/MediSecureAdapterInstaller.zip

Open

Best to note down the site number in case you lose it.

Now bring up a patient on the Medisecure machine and see if the ASL is working, if you can see ‘Sign Up ASL’ instead of ‘ASL Connection Error’ then you know it’s working.

Master ASL is working but client machines are not

Exit out of RxOne and reopen. Make sure there are not two copies of RxOne in task manager and try again

If the client is still not able to connect to ASL then it could be the firewall blocking from the master. Turn off the firewall temporarily and restart RxOne on client machine, if ASL is working on client machine then you know it’s something to do with firewall. Turn the firewall back on the master and follow #3 to see which part of the firewall is blocking.

Go to the Windows Defender Firewall > Advanced Setting > Inbound Rules on RxOne master and make sure there is no block on RxOne, if there is a block on RxOne (a circle with a slash), delete it. Do the same as for client machine. Often the block happens when you open RxOne as administrator and RxOne ask if you want to allow something some people say No that’s how the block got added.

After you clear the block, start the RxOne as administrator on client machine and if you get question asking if you want to allow RxOne make sure you say yes, ASL should be working.

ASL sometimes connects but sometimes showing ASL Connection error

Possible Cause: Socket not always firing - under investigation

This could be a socket issue, which is currently being investigated, often fixed by closing RxOne home screen, and reopening, but only last a while before seeing connection error again. This is on the programmers list to investigate.