Skip to main content

Table 4 Coding overview for Hospital interviews

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

  Hospital interviews codes Sample comments
Acquisition history Financial Accountability: mention of financial accountability as reason to implement system H13: Ok currently we depend on the user fee, because we collect the user fee from the patients, we also have the County government supporting us, and again we have partners who also contribute all this money is put in admnH4: Transactions done via the system aren’t reversible except by specific persons with such system privileges.
Manage processes
Reason for acquisition:
To manage clinical data
Previous experience from others
Previous system challenges
Improved information (mentioned as a reason for system acquisition)
System selection and development process
Funding: initial funding and running costs, county funds, hospital funds
System initiator: Any person mentioned to have initiated system implementation
Usability Speed  
Integration with other systems H6: The system doesn’t allow changing of a radiology request during certain instances when it may be necessary. E.g. a clinician sends a patient for an x-ray for the left leg, when it really is the right leg that is injured and needs the x-ray done.
H4: During power interruptions, any receipts that are printing or sent to print cannot be re-created
User friendly: relating to the user interface and whether the users find it difficult to navigate
hanging/crashing
Work made easier
Decision support
Workflow/business logic
Govt requirements: Does the system meet government requirements? /Are any requirements from the Government that enable/hinder system use?
Computer literacy: relates to ability of users to use computers and software
Workarounds: Users using shortcuts to get system working
Time and Workload / reduce paperwork
Report generation and data issues Poor documentation H13: For our consumption yes, like the financial report, commodity use reports we are able to know which drugs I need to stock, so we use a lot of the reports that we get from the program to make decisions
Clinical data entry
Unavailable reports
Error reduction/improved accuracy
Report generation and access to reports: MOH reports, Local facility reports
Data confidentiality
Data quality: comments regarding ensuring data quality
missed data
Data extraction at facility
Data audits: mentions of ability to go back to data to counter-check issues
Data lookup and tracking
Inpatient data
Diagnosis and test availability
Infrastructure issues Hardware issues H4: Power interruptions and fluctuations that slow down work. Power interruptions also cause problems with interchange of information with [system X] in the lab.
Network issues
Electrical power interruptions
Theft/Equipment safety
Power fluctuations
System support, acceptance and user training Support by local staff: System user support provided by staff available at the hospital H13: Most of the training is actually done by the IT team, but one of the guys you saw, a records officer is able to handle most of the clinical challenges and not just the IT personnel.
Support by vendor, remote support
Response speed: relate to how fast or slow support is provided
Training: initial system training and ongoing training
Backup procedures: procedures in place in case system is not functioning
Procedure documentation
County IT support
Support prioritisation
System acceptance: persisting resistance, initial system resistance
Departmental communication and system interoperability System interoperability H4: Connected to the CellTac FHG/CBC machine, allowing printing of reports and posting of results directly to the system.
interdepartmental communication