Skip to main content

Table 5 Coding overview for Hospital interviews

From: Digital health Systems in Kenyan Public Hospitals: a mixed-methods survey

 

Vendor interviews codes

Sample comments

Data and reporting

Coded data

Vendor 5: the doctor can do the coding, and in most cases that is what happens, but in case where the module has not been bought, you know we sell it in models sometimes depending on resources availability and all that and I mean other things, so the health information people can still do it. We have a form as they collect the files the work has been done the people can still do the coding manually, but in our case, we prefer when the doctors are doing the coding themselves.

Report generation

Unique identifiers

POC data entry

Retrospective data entry

Data transmission to DHIS2

Data export

Access to data or reports

Data quality

Support to facilities

Remote support

Vendor 8: Ok it’s a bit unique, ok there are things which you can call over the phone and sort them outside and there is an issue of password, someone has forgotten a password you just direct them to a senior person who will go and rectify the password. Like if now it’s an issue about a report like now what I was talking about DHIS. Now that one has to be written formally, there is an email, it’s a kind of a letter that we respond to it we seek the way forward that why I am saying if something requires a meeting now we go and have a meeting with them

In person support

Outsourced support

Documentation

Training

Support: simple/first level or advanced support

Maintenance contract

Hardware support

Local IT support

Issue tracking

Support prioritisation

Facility installations

User Related

Positive attitude

Vendor 2: Maybe when they are not ready for training, you know sometimes you can go to a place where they have not dealt with computers and sometimes people find it very frightening to start using these things and all that, some of it can also be due to human factors, resistance to change, that inertia, so just the normal, normal things, when you are introducing a new thing,

Negative attitude

Workload and time

Motivation to use system

User readiness

System

Interoperability

Vendor 8: Those who are not very/ you know, those don’t have IT guys, they do external ones once in a week. Those who have IT guys, there is a day, there are some whom because of the sensitivity of the of the data and they sometimes collect a lot, they do backup straight, during the day they can do manual and wait for the one at night to be done automatically its only that they are limited in terms of the internet they have. If they had internet they wanted to be backing up back up outright in a cloud server somewhere. But you know when thy do the costing and all that sometimes they say that is a lot. So there are some facilities who have big data bases, they go around 500mb when it is zipped, and when it’s not zipped its around 3GB.

Effect of system change

Setup process customisation and challenges

Architecture

Role based access

Backup - data dumps, location, redundancy, large files, costs, challenges, timing/frequency

Data protection - encryption

Backup - challenges

Modules: inpatient, important modules, new modules

Internet connectivity

Legislation, Governance and National Programmes

MOH issues

Vendor 8: We can in fact the good thing about DHIS tool, we are using the same data base, we are using Postgres, they are Postgres we are Postgres, the only thing is that there has not been any agreement or the go ahead from the DHIS site for us to integrate

Permission to access DHIS2

Integration with MOH requirements

Reduce resource wastage

County influence