MétaCan
Menu
← Back to cohort
Record W2800464538 · doi:10.2196/mhealth.9726

“The Doctor Needs to Know”: Acceptability of Smartphone Location Tracking for Care Coordination

2018· article· en· W2800464538 on OpenAlexvenueno aff
David T. Liss, Eloisa Serrano, Julie Wakeman, Christine Nowicki, David Buchanan, Ana Cesan, Tiffany Brown

Bibliographic record

VenueJMIR mhealth and uhealth · 2018
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
FundersAgency for Healthcare Research and Quality
KeywordsmHealthTracking (education)Smartphone applicationInternet privacyComputer scienceMedicinePsychologyMultimediaNursingPsychological intervention

Abstract

fetched live from OpenAlex

BACKGROUND: Care coordination can be highly challenging to carry out. When care is fragmented across health systems and providers, there is an increased likelihood of hospital readmissions and wasteful health care spending. During and after care transitions, smartphones have the potential to bolster information transfer and care coordination. However, little research has examined patients' perceptions of using smartphones to coordinate care. OBJECTIVE: This study's primary objective was to explore patient acceptability of a smartphone app that could facilitate care coordination in a safety net setting. Our secondary objective was to identify how clinicians and other members of primary care teams could use this app to coordinate care. METHODS: This qualitative study was conducted at a federally qualified health center in metropolitan Chicago, IL. We conducted four focus groups (two in English, two in Spanish) with high-risk adults who owned a smartphone and received services from an organizational care management program. We also conducted structured interviews with clinicians and a group interview with care managers. Focus groups elicited patients' perceptions of a smartphone app designed to: (1) identify emergency department (ED) visits and inpatient stays using real-time location data; (2) send automated notifications (ie, alerts) to users' phones, asking whether they were a patient in the hospital; and (3) send automated messages to primary care teams to notify them about patients' confirmed ED visits and inpatient stays. Focus group transcripts were coded based on emergent themes. Clinicians and care managers were asked about messages they would like to receive from the app. RESULTS: Five main themes emerged in patient focus group discussions. First, participants expressed a high degree of willingness to use the proposed app during inpatient stays. Second, participants expressed varying degrees of willingness to use the app during ED visits, particularly for low acuity ED visits. Third, participants stated their willingness to have their location tracked by the proposed app due to its perceived benefits. Fourth, the most frequently mentioned barriers to acceptability were inconveniences such as "false alarm" notifications and smartphone battery drainage. Finally, there was some tension between how to maximize usability without unnecessarily increasing user burden. Both clinicians and care managers expressed interest in receiving messages from the app at the time of hospital arrival and at discharge. Clinicians were particularly interested in conducting outreach during ED visits and inpatient stays, while care managers expressed more interest in coordinating postdischarge care. CONCLUSIONS: High-risk primary care patients in a safety net setting reported a willingness to utilize smartphone location tracking technology to facilitate care coordination. Further research is needed on the development and implementation of new smartphone-based approaches to care coordination.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.017
metaresearch head score (Gemma)0.065
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.017
Threshold uncertainty score0.087

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0170.065
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0000.000
Science and technology studies0.0020.002
Scholarly communication0.0030.002
Open science0.0010.004
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0030.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.070
GPT teacher head0.478
Teacher spread0.408 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designQualitative
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations8
Published2018
Admission routes1
Has abstractyes

Explore more

Same venueJMIR mhealth and uhealth→Same topicMobile Health and mHealth Applications→French-language works237,207→