eLABS Zambia

Whats New?

Please read through the documents listed below with all the changes (explained in the documents) on the eLabs Mobile Application and Web Portal.

Technical Information

General	Detail
Helium/Journey	Journey Application
APN/ Zero rated	Zero-rated
SSO APK Link	https://appinstall.xyz/elabs/android/production/armv7/4.37.3.apk
Barcode APK Link	https://za-zerorated-journey.mezzanineware.com/static/zam/eLABS-4.34.0.apk
Device	Android

Product Information

Item	Description
Web URL	https://elabsonline.com/
Handover Notes	https://docs.google.com/document/d/1GyAaP82JYyGYB-jV1MkUtUPUtAa9WUccTT4m2GulwG4/edit
WIP eLABS Zambia Training Manual	WIP eLABS Zambia Training Manual.pdf
eLabs Zambia Driver SOP	eLABS Zam - Driver SOP (4).pdf

Support Contact Details:

First Line Support	Details
Lead Contact Equip	Kumbirai Chigudu IT Technical Specialist kumbirai.chigudu@equiphealth.org
Lead Contact Sead	Njongo Ntlangeni Njongo.Ntlangeni@sead.co.za nomaphelo.sofute@sead.co.za
Other First Line Support Contacts	List of Champions are found on the document below: Training Register_eLabs Champions.xlsx Below find the update information for the lead contacts for first line support. It is documented on the SOP's for communication purposes. Normal communication will proceed on eLabs support, with the additional province added to the equation. eLABS Zam - Driver SOP.pdf eLABS Zam - HCP SOP.pdf
Western Province	Western Province First line Champion Details
When do I contact My First Line Support	Follow this link for details on your support lines Support Procedures and Levels

Channel Partner: Second Line Support Contact Details : AfriConnect (Device and Sim related Issues)

3rd Line Support Contact Details: Mezzanineware

Disa Lab Support

Below is a list of FAQ's specific for eLabs Zambia.

Questions	Answers
Is there a Workaround for Disa Lab when the Integration is down?	Please follow the steps as explained in the document below to serve as Work Around when the Integration is down. Disa Workaround for Laboratories if Integration is down.docx
2. I have problems with the requisitions. When receiving them in the laboratory it give me the code below(screenshot). The've been created at the facility but for some reason in the line of Attributes: Form Type: HIVVL, it shows attributes: gender: Unknown and therefore the DISA number is not assigned due to not identifying the test code. They are from different facilities: AAAD1303P AAAD1308P AAAA1259P AAAD1260P AAAD0376P AAAA6710P AAAC0011P – 00116P and AAAC0018P	The HCP's must make sure that they synchronise their phones. The information missing on those barcodes should come from the HCP's.
2 . We have five eLab samples that have failed to be registered on DISA. The error message is as follow: Lab number not assigned: Test code not recognised (See screenshot below).	The following steps and tests needs to be done by the support agent before logging it with the developers. Troubleshooting steps for client: The HCP's must make sure that they synchronise the phones. Make sure that you have captured the correct barcode Did any of the barcodes that has been captured gone through or is it only one that is not going through? Support agent troubleshooting steps: To see if integration is on or off go to: More Third party dashboard On the requisition integration screen search the barcode number, if the barcode picks up then the HCP have synchronise the device. To see who the HCP was who synchronise the device go to: Dashboard Samples Recorded On the hierarchies table select the province Search the barcode that has been scanned Should the barcode exist on the system, log a ticket with the developers for investigation. (needs to be escalated to DISA)
3. How do I check if the Integration is off	The following steps below will assist you on how to check if the Integration is off: Login with your administrator role. Go to More on the side bar. Click on Third Party Dashboard. Scroll down to Results Integration log. In the search label type in the barcode number Should you find the barcode and see their latest result, it means the integration is on. If the barcode is not found, search the date and time the result was sent. If other records were received on or after this date and time, then the integration is not off. If no records were received on or after this date and time, support will log a ticket with the developing team.