NUR 307 Module 2 Short Paper Example

When the Watch Calls the Clinic: Smartwatch Rhythm Alerts, the Patient Portal and a Nurse's Responsibility

[Student Name]

Southern New Hampshire University

NUR 307: Exploring Information Technology for Professional Practice

Module Two Short Paper

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

When the Watch Calls the Clinic: Smartwatch Rhythm Alerts, the Patient Portal and a Nurse's Responsibility

Patients now bring data to their care teams that no clinician ordered. Blood pressure cuffs, glucose monitors, sleep trackers and smartwatches send readings to phones, and patient portals make it easy to forward them. This paper examines one such case in a composite primary care practice: a patient who sends smartwatch irregular rhythm notifications through the portal on a Friday evening. It argues that the data are useful but uncertain, that the practice rather than the individual nurse is responsible for deciding how such data are received and reviewed, and that without a policy the burden falls on whichever nurse opens the message.

The Message

Mr. R., a composite 71-year-old patient with hypertension and no known heart rhythm disorder, sends a portal message at 7:15 p.m. on a Friday with six screenshots. Each shows a notification from his smartwatch reporting an irregular rhythm suggestive of atrial fibrillation over the past two weeks. He writes that he feels fine but has read that atrial fibrillation can cause strokes, and asks whether he should go to the emergency department. The portal's automatic reply says that messages are reviewed during business hours and that urgent concerns should go to 911 or the after-hours line. The practice's nurse opens the message on Monday at 8:05 a.m.

What the Data Can and Cannot Show

The best-known evaluation of smartwatch rhythm notifications is the Apple Heart Study, which enrolled 419,297 participants without self-reported atrial fibrillation (Perez et al., 2019). Over a median of 117 days, 0.52% received an irregular pulse notification. Among notified participants who returned a usable electrocardiogram patch, worn on average 13 days after the notification, atrial fibrillation was found in 34%, and 35% of those aged 65 or older. When a later notification occurred while the patch was being worn, the positive predictive value for atrial fibrillation on the simultaneous recording was 0.84.

Those numbers cut both ways for Mr. R. A notification is uncommon and often reflects a real rhythm problem when it recurs, so six notifications deserve attention. But a notification is not a diagnosis, the study population differed from a single primary care patient, and atrial fibrillation may not be present when an electrocardiogram is finally done. The data justify prompt evaluation; they do not justify either reassurance or an emergency visit in a patient without symptoms.

What Clinicians and Patients Report

Lavallee et al. (2020) interviewed patients, care partners, clinicians and administrators about patient-generated health data. Participants valued such data for supporting care decisions and improving communication and engagement. They also named significant barriers: doubts about data validity and whether the data could be acted on, and the burden of fitting the data into existing care processes. Mr. R.'s message illustrates all three. The screenshots are valid enough to prompt action but not to diagnose, the right action is not obvious to a patient reading about strokes online, and nothing in the practice's workflow says who should read a smartwatch screenshot or how quickly.

Who Is Responsible

Once Mr. R. sent the message, the practice had received information about a possible health problem, whether or not anyone had asked for it. Under the profession's code, each nurse answers for the quality of their own practice and for responding to information that affects a patient's safety (American Nurses Association, 2025). But the nurse who opens the portal on Monday did not design the portal, set its hours or decide that patients could upload device data. Responsibility for those choices belongs to the practice. The nurse is responsible for triaging the message promptly and appropriately once it is seen; the practice is responsible for making sure it is seen within a safe timeframe and that staff know what to do with it.

The Nursing Decision

On Monday morning, the nurse calls Mr. R. rather than replying in the portal, because the triage questions need answers: palpitations, shortness of breath, chest pain, dizziness or fainting, and any sudden weakness, numbness, facial droop or trouble speaking. Mr. R. reports none. His blood pressure log from home is at his usual level. The nurse explains that the watch may be detecting a rhythm called atrial fibrillation, that it needs to be confirmed with a medical test and that, if confirmed, his clinician will discuss stroke prevention with him. Following the practice's triage protocol, the nurse schedules a visit with an in-office electrocardiogram within two days, flags the message for his clinician, documents the screenshots and the call in the chart, and reviews stroke warning signs and when to call 911. Mr. R. is asked to bring his watch to the visit. Before ending the call, the nurse asks him to repeat back the warning signs and what he would do if one appeared, and he names three of them correctly, which is recorded in the note. The call takes eleven minutes, time the practice's current schedule does not budget for anywhere.

A Governance Policy for the Practice

The case points to a simple policy the practice should adopt. First, define which kinds of patient device data the practice will accept through the portal and in what form. Second, assign review to a named role, such as the triage nurse, with a timeframe during business hours and clear escalation criteria. Third, tell patients in the portal, before they send data, what will happen to it and how long review may take, and repeat the symptoms that require 911 regardless of the portal. Fourth, document device data in a consistent place in the chart so the next clinician sees it. Such a policy protects patients and also protects nurses from being the only safeguard in a system no one designed.

Conclusion

Smartwatch rhythm notifications are neither noise nor diagnoses. The evidence shows they often point to a real problem when they recur, and stakeholders value them, but their usefulness depends on a care team that knows who reads them and what to do. Mr. R.'s six screenshots were handled well because a nurse called him and followed a protocol; a practice policy would make that response reliable rather than lucky.

References

American Nurses Association. (2025). Code of ethics for nurses. https://codeofethics.ana.org/

Lavallee, D. C., Lee, J. R., Austin, E., Bloch, R., Lawrence, S. O., McCall, D., Munson, S. A., Nery-Hurwit, M. B., & Amtmann, D. (2020). mHealth and patient generated health data: Stakeholder perspectives on opportunities and barriers for transforming healthcare. mHealth, 6, Article 8. https://doi.org/10.21037/mhealth.2019.09.17

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. The New England Journal of Medicine, 381(20), 1909-1917. https://doi.org/10.1056/NEJMoa1901183