NURS 521 Week 6 Discussion Board 2 on Patient-Generated Data From Wearables Example

Discussion Board 2: Consumer Wearables, Patient-Generated Data and Nursing Practice

NURS 521 Nursing Issues, Informatics and Technology, Discussion Board 2

Thread by [Student Name]

The patient example and the classmates replied to are composites written for a model discussion.

A 67-year-old retired bus driver at a primary care visit holds out a phone to the nurse. The patient's watch has sent three notifications in two weeks saying it detected an irregular rhythm suggestive of atrial fibrillation, and the patient wants to know whether a stroke is coming. Scenes like this are now common, and they raise a question for nursing practice: what should a clinician do with data the patient generated at home? My position is that these data are valuable but incomplete, and that nurses should help their practices build a defined pathway for them rather than either dismissing them or treating every alert as an emergency.

The evidence on detection is encouraging. In the Apple Heart Study, 419,297 people without known atrial fibrillation were monitored for a median of 117 days, and just over one in two hundred, 0.52%, were alerted to an irregular pulse (Perez et al., 2019). Of the alerted people whose mailed ECG patches returned usable data, 34% turned out to have atrial fibrillation, and when a new notification occurred during patch monitoring, atrial fibrillation was confirmed 84% of the time. In plain terms, when the watch speaks up, it is usually right, but its silence does not mean the heart is normal, because the study was not designed to measure how many cases the watch misses.

The evidence on outcomes is less settled. Davies et al. (2026) followed wearable research along the chain from detection to treatment and found that the strength of the evidence weakens at every step. Randomized trials show that wearable pathways speed up diagnosis, but none has shown that screening with consumer devices reduces stroke, embolism or death. The evidence for treating device-detected atrial fibrillation comes from implanted devices and shows that anticoagulation trades fewer strokes for more major bleeding. The authors also point to unresolved problems with confirmation pathways, workflow burden, equity and overdiagnosis.

A nurse-led pathway can respect both sides of that evidence. The nurse records the notification history as patient-generated data in the chart, obtains a 12-lead ECG at the visit, and, if it is normal, arranges confirmation with a short-term patch monitor ordered by the provider. Meanwhile, the nurse calculates a stroke risk score for the provider, reviews bleeding risk factors and teaches the patient which symptoms require emergency care. For this patient, that means explaining that sudden weakness on one side, facial droop, trouble speaking, chest pain or fainting call for 911, while another watch notification alone calls for a message to the clinic. The nurse also shows the patient how to record a 30-second ECG on the watch when symptoms occur, since a tracing captured during palpitations can be printed or sent through the portal for the provider to review. Finally, the nurse documents the device model and the dates of each notification in a structured field rather than a free-text note, so that the next clinician can see the history at a glance and the practice can later count how many patients arrive with these alerts and what the confirmation testing showed. Nelson and Staggers (2018) describe consumer health informatics as a partnership in which patients bring their own data into care, and a pathway makes that partnership routine rather than improvised.

Scripture calls us to be "good stewards of God's varied grace" (English Standard Version Bible, 2001/2016, 1 Peter 4:10). Patients who monitor their own health are exercising a kind of stewardship, and nurses honor it by taking their data seriously while interpreting it honestly.

Reply to Hannah

Hannah, your argument that telehealth closed the distance between your rural patients and the nearest psychiatric provider is persuasive, and I agree it has been one of the most important changes of the past few years. I would add the same equity caution that applies to wearables. Davies et al. (2026) list equity among the unresolved problems in wearable-based care, since the people who own smartwatches are often younger and wealthier than the people at highest risk of atrial fibrillation. Telehealth has a similar gap: a video visit helps the patient with broadband and a private room, but not the farmworker sharing a phone with three family members or the older patient who has never used a camera. Nelson and Staggers (2018) note that consumer technologies depend on the user's access and skills as much as on the technology itself. One response is to keep audio-only visits as a recognized option and to offer patients a private room at the clinic or library for video sessions. Does your practice track which patients decline telehealth or fail to connect? Knowing who drops off might reveal whether the gap is about connectivity, comfort with the technology, or privacy at home, and each of those calls for a different fix.

Reply to James

James, I share your concern that consumer health apps collect sensitive data with far fewer protections than the hospital record. You are right that many apps are not covered by HIPAA because they are not offered by a covered entity, so a patient's heart rhythm or menstrual cycle data may be shared with third parties under a privacy policy few people read. I would push your point one step further into nursing practice. When a patient brings app data into the visit, as in the smartwatch example in my thread, the data become part of the protected record once we enter them, but the original copy remains on the app's servers under the app's rules. Nelson and Staggers (2018) describe teaching patients about privacy as part of consumer health informatics. Nurses could add one or two questions to the visit, such as whether the patient knows who can see the app's data and whether they would like help changing its sharing settings. The Apple Heart Study required participants to give consent through the app before monitoring began (Perez et al., 2019), which shows that consent can be built into a device workflow when designers choose to. Do you think health systems should recommend specific apps to patients after reviewing their privacy practices, or would that create a liability the systems would rather avoid?

References

Davies, M., Bulluck, H., & Tayebjee, M. H. (2026). Smartwatch and wearable detection of atrial fibrillation: Current evidence and clinical implications. Trends in Cardiovascular Medicine. Advance online publication. https://doi.org/10.1016/j.tcm.2026.08.003

English Standard Version Bible. (2016). Crossway. (Original work published 2001)

Nelson, R., & Staggers, N. (2018). Health informatics: An interprofessional approach (2nd ed.). Elsevier.

Perez, M. V., Mahaffey, K. W., Hedlin, H., Rumsfeld, J. S., Garcia, A., Ferris, T., Balasubramanian, V., Russo, A. M., Rajmane, A., Cheung, L., Hung, G., Lee, J., Kowey, P., Talati, N., Nag, D., Gummidipundi, S. E., Beatty, A., Hills, M. T., Desai, S., ... Turakhia, M. P. (2019). Large-scale assessment of a smartwatch to identify atrial fibrillation. New England Journal of Medicine, 381(20), 1909-1917. https://doi.org/10.1056/NEJMoa1901183