Skip to main content

Table 9 Summary of responses to perceptions of mHealth and patient-gathered data being integrated into healthcare providers’ electronic health record (EHR) systems

From: How mHealth can facilitate collaboration in diabetes care: qualitative analysis of co-design workshops

Groups

Codes

Summary

Example quotations

Specialists

Preferences

• Automatic data transfer

• Visual summary of specific data types within patient-gathered data

“Automatically getting the continuous glucose values for the last week, into my electronic diabetes journal system... and the use of insulin or automated data easily, visually presented” (Specialist1)

Risks

• Data-overload

• Capacity of personnel and resources

• Personal liability of not identifying indicators of dangerous habits and symptoms

“The other thing that comes to my mind when you say [integrating technology] is “Please stop it!” because I if you are the patient and I get your data continuously for your whole life on my screen, then I am responsible because if something happens to you, if you go into your car and have a traffic accident with hypoglycaemia it’s my responsibility because I should have seen that last week you had several hypoglycaemias … but we do not have the resources for this” (Specialist1).

GPs

Preferences

• While prefer no integration, alternatives could include automatic and simple data-transfer that do not require the provider to perform additional tasks

• Rely on entering own notes into EHRs about a patient’s status

“We don’t need to load [PGD] into the EHRs, because there are many problems and overload of information. And, why should we keep it?” (GP3).

“If we would to have it on our computers, partly via a journal. Not extra software! Then [the patient] can have [their] phone, plug in USB, and I have it, okay, we could do that … a compromise - But not one manually!” (GP3).

“Instead, I prefer] to type [notes about PGD] myself … write it short. Reminder [to focus on this] for next time” (GP3).

Risks

• Data-overload

• Overloading the provider with additional tasks

It’s always a chance of overload … a whole lot of data. We can’t relate to it” (GP1)