Versions Compared

Version Old Version 30 New Version Current
Changes made by

Lucinda Basjan

Tanswill Achilles

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

children

Table of Contents


Child pages (Children Display)


Click on the “Submit a request” button below if you require assistance with any queries:

Submit a Request


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


Barcode APK Link
 General
Detail 
Helium/JourneyJourney Application
APN/ Zero rated

Zero-rated

SSO APK Link

SSO APK Link 

Short-link

https://appinstall

.xyz/elabs/android

-xyz.s3-accelerate.amazonaws.com/builds/production/

armv7/4.37.3.apk

615dde583c02c40006ded563-31975/eLABS-21.9.2.apk

https://appinstall.xyz/elabs/list  

Older APK Linkshttps://za-zerorated-journey.mezzanineware.com/static/zam/eLABS-4.34.0.apk
https://appinstall.xyz/elabs/android/production/armv7/4.60.2.apk

Device Android


Product Information

Item
Description
Web URLhttps://elabsonline.com/
Handover Noteshttps://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 SupportDetails

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

/wiki/spaces/SUP/pages/6653729
WHC First Line Support Team

/wiki/spaces/SUP/pages/6653729

 1st Line Support

Sead

/wiki/spaces/SUP/pages/6653729

Other First Line Support Contacts
 List of Champions are found on the document below:

Training Register_eLabs Champions.xlsx

/wiki/spaces/SUP/pages/6653729


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.

Contact InstanceContact Details
Driver SOPeLABS - Driver SOP.pdf
HCP SOPeLABS - Driver SOP.pdf
Lab SOPeLABS - LAB SOP .pdf

eLABS Zam - Driver SOP.pdf
eLABS Zam - HCP SOP.pdf

Western ProvinceWestern Province First line Champion Details/wiki/spaces/SUP/pages/6653729
Copperbelt Province

/wiki/spaces/SUP/pages/6653729

When do I contact My First Line Support

Follow this link for details on your support lines Support Procedures and Levels or contact one of the WHC Support team members above to guide you in the right direction

Configuration 


eLabs Zambia Configuration process


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.

QuestionsAnswers
  1. 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
      Image Removed

 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).

Image Removed

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.