Sysmex XQ320

1. Clone/Copy the xq320 driver from: https://github.com/HISMalawi/mlab_drivers  onto the server 2. Navigate to xq320 directory and do: npm install .Since servers do not have internet,  you can do this on your local machine, make sure node version is the same as that  on the server via node –version then copy node_modules to this directory on the  server. 3. Navigate to config/settings.json file of xq320 and change serverIp to your server ip  address and localhost on lispath to actual server IP. LisUser and lisPassword to  credentials used to log into iBLIS and serverPort to 5555 4. Open the file xq320.js via vim xq320.js and the last line as follows: where there is  settings.serverPort, it should be 5555 and where there is settings.serverIP should be  server ip address just the same as those you have set in config/settings.json 5. Do run this command to allow firewall on the server: sudo ufw allow 5555/tcp 6. In the xq320 folder, run this to start the driver: node xq320.js This should start the  service and a successful start will show a log that it has started on this ip address and  port which are set in the config/settings.json. 7. Go to the machine and give the machine network by connecting to it at the back via  ethernet cable. Make sure the network is capable of DHCP as the machine  automatically picks the IP address, there is no manual setting of network. 8. On the machine software interface, go to settings then TCP/IP connection and set  the Host IP as the Server Ip which is the same as that in config/settings.json and the  port to the port same as serverPort in config/settings.json 9. Save the TCP/IP connections. Upon saving and going back to main screen and clicking  browser, bottom left of the screen has to show a green bar as shown in the picture  below. This indicates that there is connection between the service that was run in  step 4 and the machine. Without this not communication can happen. This also  shows that network between machine and LAN is Ok via the ethernet. 10. Once this is ok, Register one FBC test in IBLIS, take the accession number without the  facility code i.e starting from the number, go to the machine, let the lab tech do one  dummy test but the test should have the sample id as the accession number of the  just registered test( achieved by entered the accession number on the sample ID  input field when recording the detail of the sample in the machine before testing it). 11. Once it has finished testing, click on explore on the top navigation on the machine,  you will be presented with a list as below image. Select the test with the accession  number you registered(should be highlighted blue), then click browserr.    12. Browser will have the details of the test(results and the sample id i.e accession  number ) as shown in the picture in step 7. Click validate and once its validated, click  on Output the HC Outpus. This should send results to the service and you can  observe the log of the service running that was done in step 4. 13. If all is good, fetch the result in IBLIS for the test you registered and compare the  results if the machine what is in the browser of step 9. 14. Should some results be missing, check the mapping in config/xnseries.json. 15. If every this is OK, make the service to auto start by doing: pm2 start xq320.js then  pm2 save. 16. To make the machine automatically sent the results once the machine finishes  testing, do step 15 and 16. 17. Making sure the test is auto validated once testing finishes by going to the machine  interface Menu, then settings and choose the settings for auto validation (can be  found in operational) as below image. Then click modify settings and set auto  validation to be for all samples and save. 18. Making sure the test results are automatically sent to iblis once testing finishes by  going to the machine interface Menu, then settings and choose the settings for auto  output (can be found in operational) as below image. Then click modify settings and  make sure HC is select to as well to be an auto output destination as well and save. That’s it. You can try testing an actual sample and verify if its sent to iblis automatically  without you clicking on output as was done in step 10.