Nursing Informatics Systems, Data, AI, and Digital Practice · 2026 Edition

Chapter 15 Part IV — Clinical and Consumer Technology

Patient-Generated Data, Portals, Telehealth, Remote Monitoring, and Population Health

How digital health extends beyond institutional walls and changes the relationship among patients, clinicians, data, and care delivery.

Chapter Orientation

Healthcare information no longer originates primarily inside hospitals and clinics. Patients schedule visits, read notes, message clinicians, measure physiologic data at home, use wearables, participate in telehealth, and generate information continuously. These capabilities can increase access and agency, but they can also shift work to patients and caregivers, widen digital inequities, and create data volumes that clinical teams cannot meaningfully review.

Nursing informatics must therefore design not merely for access to technology, but for a sustainable care model: who generates data, who receives it, what thresholds matter, who responds, and what happens when technology fails outside a controlled clinical environment.

Learning Objectives

By the end of this chapter, you should be able to:

  1. Evaluate patient portals and consumer access as components of care workflow.
  2. Distinguish patient-generated health data from clinician-generated clinical data.
  3. Design remote monitoring around actionable thresholds and response capacity.
  4. Explain major telehealth workflow and equity considerations.
  5. Describe registries, population health, and public-health information flows.
  6. Evaluate digital inclusion, proxy access, and patient agency in digital systems.

Lesson 15.1 — Patient Portals Move the Record Into the Relationship

  • Portals expose information that was once primarily clinician-facing. Patients can view results, medications, notes, appointments, bills, and care plans. This can improve transparency while requiring organizations to write and release information with patient comprehension in mind.

  • Messaging creates a new care channel. Secure messages can prevent visits and answer questions efficiently, but volume, routing, response-time expectations, and compensation/workload must be governed. An inbox is a clinical queue, not merely an email feature.

  • Proxy access requires identity and relationship governance. Parents, caregivers, guardians, and family members may need access, but the appropriate scope can change with age, capacity, legal authority, and sensitive information.

  • Immediate access changes result communication. Patients may see abnormal results before a clinician discusses them. Informatics design should support understandable context and reliable follow-up rather than assuming delayed release is the default solution.

  • Portal adoption should not become a condition for receiving competent care. Patients who cannot or choose not to use digital tools still require equitable access to information and services.

EClinical Example

Clinical Example — The Message Queue

A clinic celebrates a 60% increase in portal messaging. Nurses report that messages now contain medication questions, symptom triage, refill requests, forms, scheduling issues, and urgent concerns in one undifferentiated queue. The access metric improved while workflow design lagged behind.

NI-BC Connection: Data Management and Healthcare Technology — patient-facing systems, communication technologies, portals.

?Retrieval Checkpoint

Retrieval Checkpoint

  1. How does a portal change the clinical record’s audience?
  2. Why should portal messaging be designed as a care queue?
  3. What makes proxy access complex?
  4. Why can high portal adoption still coexist with inequity?

Lesson 15.2 — Patient-Generated Health Data Expand the Observation Window

  • Patient-generated health data are created outside traditional clinical encounters. Examples include home blood pressure, glucose readings, symptom diaries, activity, sleep, weight, and device-generated physiologic data.

  • More frequent measurement can reveal patterns hidden by episodic visits. Home blood pressure may better represent daily life than one clinic measurement, but only if the device and measurement technique are sufficiently reliable.

  • Consumer devices vary in intended use and validation. A wellness wearable and a regulated medical device may produce similar-looking numbers with very different evidence, accuracy expectations, and clinical claims.

  • Context remains essential. A high heart rate during exercise differs from the same value at rest. Algorithms that ingest patient-generated data need activity, timing, device, adherence, and symptom context where relevant.

  • Data volume must be matched to review capacity. Collecting thousands of readings without a triage strategy can create liability and burden without improving care.

AIAI in Practice

AI in Practice — Summarize Trends, Preserve the Raw Evidence

AI can help summarize large streams of patient-generated data into patterns and exceptions. The summary should link back to underlying measurements, preserve uncertainty, and never imply that unreviewed consumer data have the same status as validated clinical measurements.

NI-BC Connection: Data Management and Healthcare Technology — patient-generated data, devices, analytics.

?Retrieval Checkpoint

Retrieval Checkpoint

  1. What advantage can patient-generated data provide over episodic visits?
  2. Why does device intended use matter?
  3. What contextual information can change interpretation of a sensor value?
  4. Why can data collection itself create risk?

Lesson 15.3 — Remote Monitoring Is a Service Model, Not a Device Program

  • Remote patient monitoring combines technology with an operational response. Devices may transmit weight, blood pressure, glucose, oxygen saturation, or other measures, but the care model must specify who reviews data and what happens next.

  • Thresholds should be clinically and operationally designed. A sensitive threshold may detect more deterioration while producing excessive alerts. Personalized baselines may improve relevance but increase complexity.

  • Escalation pathways must match urgency. Some findings can wait for the next business day; others require same-day contact or emergency guidance. The system should communicate what monitoring does and does not guarantee.

  • Adherence is partly a usability problem. Failure to transmit may reflect illness, battery problems, connectivity, dexterity, cognition, language, caregiver availability, or unclear instructions rather than “noncompliance.”

  • Program evaluation should include workload and equity. A reduction in hospital use may be offset by substantial nursing monitoring burden or by excluding patients without broadband, smartphones, or stable housing.

FFigure

Figure 15.1 — Remote Monitoring as a Closed Service Loop

Production brief: Patient/device → transmission → data validation → threshold/analysis → clinical queue → assessment → intervention → documentation → feedback to patient. Mark failure points.
Alt text: Remote-monitoring service loop showing data generation, validation, review, escalation, intervention, documentation, and patient feedback.

NI-BC Connection: Data Management and Healthcare Technology — telehealth, remote monitoring, patient-generated data.

?Retrieval Checkpoint

Retrieval Checkpoint

  1. Why is remote monitoring more than deploying a device?
  2. What tradeoff occurs when thresholds become more sensitive?
  3. Why should transmission failure not automatically be labeled noncompliance?
  4. Which workload measure belongs in program evaluation?

Lesson 15.4 — Telehealth Changes Access, Assessment, and Workflow

  • Telehealth changes what can be observed directly. Video can provide visual and conversational information but may limit physical examination, environmental context, or measurement reliability. Workflow should define when virtual care is appropriate and when escalation to in-person care is needed.

  • Technology readiness belongs in pre-visit workflow. Device compatibility, browser permissions, audio, camera, connection quality, language services, and patient identity verification can determine whether clinical time is spent on care or troubleshooting.

  • Licensure, consent, reimbursement, and prescribing rules can depend on jurisdiction and program. Informatics teams should avoid hard-coding assumptions based on temporary policies or one state.

  • Privacy is environmental as well as technical. A secure platform cannot ensure privacy if the patient is in a crowded home, workplace, shelter, or shared room. Clinicians should establish whether the patient can speak safely.

  • Hybrid care is often more realistic than virtual-versus-in-person thinking. Digital tools can support follow-up, monitoring, education, and triage while physical care handles procedures and assessments that require direct presence.

EClinical Example

Clinical Example — The "No-Show" Telehealth Visit

A patient repeatedly misses video visits. Review reveals that the link works only through a portal account the patient cannot recover, and cellular data become unreliable near the end of each month. Labeling the pattern nonadherence hides a digital-access problem.

NI-BC Connection: Data Management and Healthcare Technology — telehealth, communication technology, workflow.

?Retrieval Checkpoint

Retrieval Checkpoint

  1. What clinical information may be reduced in a virtual encounter?
  2. Why should technology readiness occur before clinical time begins?
  3. How can privacy fail despite a secure telehealth platform?
  4. Why is hybrid care a useful design model?

Lesson 15.5 — Population Health Uses Data to Manage Groups, Not Just Encounters

  • Population health organizes care around defined groups and outcomes. A population may be defined by disease, geography, payer, risk, age, or another characteristic. The definition determines who appears in a registry and who can be missed.

  • Registries create longitudinal lists for action. A diabetes registry may identify patients overdue for testing, poorly controlled, or missing follow-up. A registry becomes valuable when it connects to outreach and care-management workflows.

  • Public-health exchange operates across organizational boundaries. Immunization reporting, syndromic surveillance, laboratory reporting, and case reporting depend on standardized data and reliable interfaces.

  • Risk stratification can direct scarce resources but can reproduce inequity. Historical utilization and cost may reflect access barriers rather than underlying need. Models should be examined for who is underrepresented or systematically scored lower.

  • Social determinants data need purpose and governance. Asking about housing, food insecurity, transportation, or safety creates an expectation of appropriate use. Collecting sensitive information without a response pathway can erode trust.

AIAI in Practice

AI in Practice — Population Outreach Drafting

AI can generate culturally and reading-level appropriate outreach variants from approved content, but translation and health-literacy output should be reviewed by qualified humans and tested with intended populations. Personalization should not become ungoverned profiling.

NI-BC Connection: Foundations and Data/Technology — population health, equity, analytics, public-health information exchange.

?Retrieval Checkpoint

Retrieval Checkpoint

  1. What determines who appears in a population registry?
  2. Why is a registry useful only when connected to action?
  3. How can utilization-based risk models reproduce access inequities?
  4. What obligation arises when organizations collect social-risk information?

Lesson 15.6 — Digital Inclusion Is an Informatics Design Requirement

  • Access includes more than device ownership. Connectivity, affordability, digital literacy, disability access, language, trust, identity verification, technical support, and caregiver context all shape effective use.

  • Accessibility should be designed from the beginning. Keyboard navigation, screen-reader compatibility, captions, sufficient contrast, understandable language, and alternatives to visual-only cues are fundamental system requirements.

  • Digital identity can become a barrier. Complex passwords, multi-factor authentication, identity proofing, and account recovery improve security but can lock out patients who change phones, lack stable addresses, or rely on caregivers.

  • Patient agency includes the ability to understand and contest data. Portals and exchange systems should support correction processes, questions, and visibility into information rather than treating the patient as a passive data source.

  • Equity analysis belongs in implementation monitoring. Overall adoption can rise while gaps widen. Stratifying access, completion, abandonment, response time, and outcomes can show who is benefiting and who is not.

PInformatics in Practice

Informatics in Practice — Measure the Drop-Off

Do not measure only who successfully completed a digital workflow. Measure where people stop: invitation, account creation, identity proofing, device setup, first use, sustained use, and escalation. The failure point tells you what to redesign.

NI-BC Connection: Foundations — health equity, SDOH, patient engagement, communication.

?Retrieval Checkpoint

Retrieval Checkpoint

  1. Why is device ownership an incomplete measure of digital access?
  2. How can security controls create access barriers?
  3. What does patient agency add to portal design?
  4. Why should equity measures be stratified across workflow stages?

Chapter Case Study — Remote Heart-Failure Monitoring

A health system gives connected scales and blood-pressure cuffs to patients after heart-failure hospitalization. The platform sends an alert after a 3-pound weight increase in 24 hours. Nurses receive 70–100 alerts daily, many caused by missed measurements, device resynchronization, or patients weighing at inconsistent times. One-third of eligible patients decline enrollment; refusal is highest among patients who prefer languages other than English and those living in rural areas.

Leadership wants to add an AI model that predicts decompensation from the incoming data.

Analyze the case

  1. What must be fixed before adding predictive AI?
  2. Which alert-threshold and data-quality issues are visible?
  3. How should the program measure nursing workload?
  4. What equity questions should be investigated?
  5. Which failure states should patients understand?
  6. How would you redesign the service loop before evaluating outcomes?

Chapter Synthesis

  • Patient-facing digital health changes both information access and care workload.
  • Patient-generated data increase observation but vary in quality and context.
  • Remote monitoring requires a complete response service, not merely devices.
  • Telehealth should be designed for clinical appropriateness, technical readiness, privacy, and escalation.
  • Population analytics and digital health can improve reach while reproducing inequity if access and data biases are ignored.

Key Terminology

Patient-generated health data (PGHD)
Health-related data created or recorded by patients or caregivers outside traditional clinical documentation workflows.
Patient portal
Digital interface through which patients access records, services, communication, and other health functions.
Proxy access
Authorized access to another person’s patient-facing health account or information.
Remote patient monitoring
Care model using remotely collected patient data with defined review and response workflows.
Telehealth
Delivery or support of health services through telecommunications and digital technologies.
Registry
Structured longitudinal list of patients/populations defined for monitoring and action.
Digital divide
Differences in meaningful access to and ability to use digital technologies.
Digital inclusion
Design and support practices intended to enable equitable effective participation in digital services.

NI-BC Chapter Mapping

Domain Blueprint area Lessons Depth
III. Data/Technology Patient-generated data/telehealth 15.2–15.4 Applied
I. Foundations Equity/SDOH/patient engagement 15.5–15.6 Applied
III. Data/Technology Portals/communication technologies 15.1 Applied
III. Data/Technology Population/public-health information 15.5 Applied

Chapter Quiz

Answer each question, then select “Check answer” to reveal feedback. For Select All That Apply items, choose every correct option before checking. Expand “Why?” after checking to read the rationale.

1

Portal message volume doubles after a new release, but messages enter one undifferentiated queue. What is the primary informatics concern?

Why?

Expanding access without redesigning triage and routing can simply move burden into a single queue. Informatics must align access with accountable response workflows.

2

Which statement best describes patient-generated health data?

Why?

Patient-generated data can extend observation beyond encounters, but device characteristics, collection conditions, adherence, and context affect interpretation.

3

A remote-monitoring program should define:Select all that apply

Why?

Remote monitoring requires ownership, prioritization, escalation, expected response, and contingency processes so incoming data lead to safe action rather than passive accumulation.

4

Which factor most directly distinguishes remote monitoring from simple data collection?

Why?

Monitoring becomes clinically meaningful when there is an explicit response pathway for interpreting and acting on incoming data.

5

A patient cannot complete telehealth because account recovery requires a phone number that no longer exists. This is primarily an example of:

Why?

The clinical encounter is blocked by the design of identity recovery, illustrating how authentication and account-management workflows can become digital-access barriers.

6

Why can utilization-based risk stratification disadvantage some patients?

Why?

Utilization reflects both need and access. People with high unmet need but poor access may appear deceptively low risk in utilization-based models.

7

Meaningful digital access can depend on:Select all that apply

Why?

Connectivity, affordability, literacy, accessibility, language, and trust all influence whether digital services are genuinely reachable and usable.

8

What is a major concern when collecting social-risk information?

Why?

Collecting social-risk information creates duties around protection, appropriate use, follow-up, and avoidance of harmful or stigmatizing secondary uses.

9

A virtual visit cannot provide the physical examination needed to evaluate a new focal neurologic deficit. What should the workflow support?

Why?

Telehealth workflows need defined escalation when remote assessment cannot safely answer the clinical question or a symptom requires urgent in-person examination.

10

Which measure best helps identify where digital inequity occurs?

Why?

Overall registration can hide where inequity occurs. Stratifying drop-off at each step reveals whether barriers arise at enrollment, verification, device setup, visit completion, or follow-up. —

Progress: 0 of 10 checked.

References and Further Reading

  • U.S. Department of Health and Human Services. Telehealth and Remote Patient Monitoring. https://telehealth.hhs.gov/providers/best-practice-guides/telehealth-and-remote-patient-monitoring
  • U.S. Department of Health and Human Services. Developing a Remote Patient Monitoring Strategy. https://telehealth.hhs.gov/providers/best-practice-guides/telehealth-and-remote-patient-monitoring/developing-remote-patient
  • Assistant Secretary for Technology Policy / Office of the National Coordinator for Health Information Technology. (2026). Patient Access to Health Records. https://healthit.gov/patient-access-to-health-records/
  • Office of the National Coordinator for Health Information Technology. (2024). Advancing Health Equity by Design. https://www.healthit.gov/sites/default/files/2024-04/ONC-HEBD-Concept-Paper_508.pdf
  • Federal Communications Commission. Mapping Broadband Health in America. https://c2h.fcc.gov/broadband-health-map.html
  • Ahmed, N., Sanghavi, K., Mathur, S., & McCullers, A. (2023). Patient portal use: Persistent disparities from pre- to post-onset of the COVID-19 pandemic. International Journal of Medical Informatics, 178, 105204. https://doi.org/10.1016/j.ijmedinf.2023.105204
  • World Health Organization. (2025). Global strategy on digital health 2020–2027. https://www.who.int/publications/i/item/9789240116870
  • American Nurses Credentialing Center. (2025). Informatics Nursing Board Certification Examination: Test Content Outline. https://www.nursingworld.org/globalassets/informatics-tco_08292025-for-webposting.pdf