Clinical Workflows for Camera-Based Vitals in Televisits

Deploying camera-based vital sign technology in a health system is a technical integration project. Designing the clinical workflows around that technology is where the real work happens. The difference between a vital signs module that providers actively use and one that gets ignored comes down to workflow design -- when vitals are captured, how they are presented, what actions they trigger, and how they fit into the clinical rhythms that providers and nursing staff already follow.

This guide is written for clinical informatics teams, nurse informaticists, and clinical workflow designers who are responsible for operationalizing camera-based vitals within existing televisit programs. It covers the full visit lifecycle from pre-visit preparation through post-visit documentation, with attention to the specialty-specific variations that matter in practice.

Pre-Visit Workflows

Successful vital sign capture during a televisit starts before the visit begins. Pre-visit workflows set the stage for reliable measurement and smooth patient experience.

Patient Notification and Instructions. Patients should receive information about camera-based vitals as part of their standard pre-visit communication. This does not need to be elaborate. A brief addition to the appointment reminder is sufficient: "During your video visit, your vital signs will be measured through your device camera. Please ensure you are in a well-lit area and your face is clearly visible on camera."

Key environmental factors that affect rPPG measurement quality include lighting (adequate, even illumination on the face -- avoid strong backlighting or very dim rooms), camera positioning (face centered in frame, camera at roughly eye level), stability (patient seated with minimal head movement during measurement), and background (a non-moving background reduces signal noise). Pre-visit instructions should address these factors in plain language without being technically overwhelming.

Device Compatibility Check. Not every patient device will support camera-based vital sign capture. The clinical workflow should include a pre-visit device check, ideally automated, that confirms the patient's camera meets minimum resolution and frame rate requirements. Patients whose devices do not meet requirements should be flagged so that the clinical team does not expect vitals data for that encounter.

Scheduling System Flags. For health systems that use visit-type-specific scheduling, consider adding a flag or attribute to virtual visit appointments indicating whether camera-based vitals are expected. This helps nursing staff and providers set appropriate expectations. Not every virtual visit warrants vital sign capture -- a brief medication refill check or a results review may not need vitals, while a chronic disease follow-up or new symptom evaluation absolutely does.

During-Visit Workflows: Timing and Capture

The most important workflow design decision is when during the visit to capture vital signs. There are three primary patterns, each with distinct advantages.

Pattern 1: Intake Capture (Recommended Default). In this pattern, vital signs are captured during the intake phase of the visit, before the provider joins. This mirrors the in-person workflow where a medical assistant takes vitals before the provider enters the room.

The workflow proceeds as follows. The patient joins the video visit and connects with a medical assistant or registered nurse for intake. During the intake conversation (medication reconciliation, chief complaint documentation, review of systems), the rPPG measurement runs in the background, requiring 30-60 seconds of adequate facial video. By the time the provider joins the encounter, vital signs are documented in the chart and available for review. The provider sees vitals in their workflow exactly as they would for an in-person visit.

This pattern is preferred because it does not consume provider time, the data is available before the clinical encounter begins, and it maps directly to existing intake workflows that clinical staff already understand.

Pattern 2: Provider-Initiated On-Demand Capture. In this pattern, the provider triggers vital sign capture at a specific point during the encounter. This is useful when the provider wants vitals in response to something the patient reports ("I have been feeling short of breath" prompts the provider to capture SpO2) or when vitals were not captured during intake.

The workflow requires a provider-facing control -- a button or command within the telehealth interface -- that initiates the rPPG measurement. Results are returned within 30-60 seconds and displayed in the provider's view. This pattern is valuable as a complement to intake capture but should not be the sole capture mechanism, as it depends on provider behavior and adds time to the encounter.

Pattern 3: Continuous Background Monitoring. In this pattern, rPPG analysis runs continuously throughout the video visit, with vital sign values updated periodically (every 30-60 seconds). This provides the most complete physiological picture and can capture changes during the visit -- for example, a stress response when the provider delivers difficult news, or heart rate changes when the patient describes anxiety-provoking situations.

Continuous monitoring generates more data and requires more thoughtful display design to avoid overwhelming the provider with constantly updating numbers. It is most relevant for behavioral health encounters (where stress index trends during the visit are clinically meaningful) and for longer encounters where physiological changes over time may be significant.

Nursing Triage Integration

For health systems with nurse triage lines or nurse-first virtual care models, camera-based vitals add a powerful dimension to remote triage.

Triage Nurse Workflow. When a patient calls or connects via video for triage, the triage nurse can capture vital signs during the assessment. This adds objective data to the triage decision, potentially changing the disposition. A patient reporting "chest tightness" with a normal heart rate, normal HRV, and adequate SpO2 may be triaged differently than one with elevated heart rate and reduced HRV.

Triage Protocol Integration. Vital sign values should feed into existing triage protocols and algorithms. If your health system uses Schmitt-Thompson triage protocols or similar decision support tools, camera-based vitals can provide the physiological inputs that these protocols reference. Clinical informatics teams should map rPPG-derived vital signs to the specific data points in triage protocols and update protocols to include instructions for when camera-based vitals are available versus unavailable.

Escalation from Triage. When triage vital signs indicate potential clinical concern (e.g., heart rate above 110, SpO2 below 93, significantly depressed HRV), the workflow should include defined escalation paths. These may include immediate warm transfer to a provider, direction to the emergency department, or scheduled urgent follow-up with repeat vitals.

Provider Review Workflows

How vital sign data is presented to providers determines whether it gets used. Clinical informatics teams should design the provider experience with the same attention given to any clinical data display.

Display Location. Vital signs should appear in the same location within the provider's EHR workflow where in-person vitals appear. For Epic users, this means the Vital Signs section of the Storyboard, the Vital Signs flowsheet, and the visit navigator. For Oracle Health users, the vital signs band and results review. Providers should not need to open a separate application, navigate to a different screen, or perform additional clicks to find televisit vital signs.

Data Presentation. Display rPPG-derived vitals with clear labeling that distinguishes the measurement method. A common convention is to include the source in the vital sign documentation: "HR 78 bpm (camera-based)" or to use a specific vital sign row that indicates the measurement modality. This transparency helps providers calibrate their interpretation appropriately.

Trending and Context. Individual vital sign readings are more useful in context. Where possible, display current televisit vitals alongside the patient's historical vital sign trend. A heart rate of 92 bpm is interpreted differently for a patient whose resting heart rate is typically 70 versus one whose baseline is 88. EHR vital sign trend views provide this context automatically if the data is stored in standard vital sign flowsheet rows.

Abnormal Value Alerting. Configure clinical decision support to flag vital sign values outside normal ranges or outside the patient's historical baseline. These alerts should follow existing CDS conventions in your EHR -- BPA (Best Practice Alert) in Epic, discern alerts in Oracle Health -- to maintain consistency with provider expectations. Be judicious with alerting thresholds to avoid alert fatigue. Consider implementing alerts only for clearly actionable abnormalities (e.g., SpO2 below 92, heart rate above 120 or below 50) rather than for minor deviations.

Post-Visit Documentation

Vital signs captured during a televisit should be documented with the same rigor as in-person vitals.

Structured Data Entry. Vital sign values must flow into structured EHR fields, not free-text notes. This ensures they appear in vital sign trends, are available for clinical decision support, can be included in quality reporting, and are discoverable for population health analytics. The clinical informatics team should validate that rPPG-derived vitals populate the correct flowsheet rows with appropriate LOINC codes.

Clinical Note Integration. For providers who use note templates or smart phrases for virtual visits, update templates to include a vitals section that auto-populates from the captured data. This reduces documentation burden and ensures vitals are consistently included in the clinical note. Example template language: "Vital signs obtained via camera-based measurement during video visit: HR [value], SpO2 [value], HRV [value], Stress Index [value]."

Attestation and Context. Some health systems may require provider attestation that vital signs were reviewed during the encounter. This can be implemented as a checkbox or attestation statement within the visit documentation workflow. Additionally, providers should have the ability to add clinical context to vital sign readings -- for example, noting that the patient appeared anxious (which contextualizes elevated heart rate and stress index).

Alert and Escalation Rules

Abnormal vital signs detected during a televisit require defined response pathways. Clinical informatics teams should design escalation rules that are clinically appropriate without being overly sensitive.

Tier 1: Informational Display. Vital signs outside normal range but within clinically manageable parameters are displayed with visual highlighting (color coding, icons) but do not trigger interruptive alerts. Example: heart rate 102 bpm in a patient with known anxiety disorder.

Tier 2: Provider Alert. Vital signs significantly outside normal range trigger a non-interruptive alert to the provider. Example: SpO2 reading of 91%, heart rate above 110 without known cause. The provider acknowledges the alert and determines clinical response.

Tier 3: Clinical Escalation. Vital signs indicating potential acute concern trigger an interruptive alert with defined escalation steps. Example: SpO2 below 88%, heart rate above 140. Escalation steps may include immediate verbal assessment of the patient, direction to call 911 if warranted, urgent in-person evaluation scheduling, and documentation of escalation actions taken.

The specific thresholds for each tier should be established by clinical leadership with input from the specialties using the technology. Thresholds may vary by specialty and patient population.

Specialty-Specific Workflow Variations

Different clinical specialties will use camera-based vitals in distinct ways. Clinical informatics teams should design specialty-specific workflow configurations rather than forcing a one-size-fits-all approach.

Primary Care. Vital signs during primary care virtual visits serve the same foundational role as in-person vitals -- establishing a physiological baseline for the encounter. Intake capture (Pattern 1) is the standard workflow. All four vital sign parameters (HR, HRV, SpO2, stress index) are relevant. Documentation follows standard vital sign conventions.

Cardiology. Heart rate and HRV are the primary parameters of interest. Cardiologists may want trending data across multiple virtual visits to assess rate control, medication response, or arrhythmia screening. Consider configuring multi-visit HRV trend displays for cardiology encounters. On-demand repeat capture (Pattern 2) is useful when cardiologists want to assess heart rate response to positional changes or other maneuvers during the visit.

Pulmonology. SpO2 is the critical parameter for pulmonology virtual visits, particularly for COPD management, post-COVID follow-up, and interstitial lung disease monitoring. Configure pulmonology workflows to prominently display SpO2 with the patient's historical SpO2 trend. Alert thresholds for SpO2 may be adjusted for pulmonology patients with known baseline desaturation.

Behavioral Health. Stress index and HRV are the most clinically relevant parameters for behavioral health encounters. Continuous background monitoring (Pattern 3) is valuable in behavioral health, as physiological stress responses during the encounter can provide clinical insight that complements patient self-report. Behavioral health providers may benefit from a longitudinal stress index trend across visits to assess treatment response.

Chronic Disease Management. For virtual visits focused on chronic disease management (diabetes, heart failure, hypertension), camera-based vitals supplement but do not replace disease-specific monitoring (glucose levels, daily weights, blood pressure). The workflow should present camera-based vitals alongside disease-specific data from RPM devices when available, giving the provider a comprehensive physiological picture.

Workflow Governance and Iteration

Clinical workflows are never final. Establish a feedback loop that captures provider and staff experience with vital sign workflows and drives continuous improvement. Quarterly workflow review sessions with clinical informatics, nursing leadership, and physician champions keep workflows aligned with evolving clinical practice and technology capabilities. Monitor utilization data at the provider and department level to identify workflow barriers that need attention.

The goal is not perfection at launch but a well-designed initial workflow with the governance structure to improve it continuously based on real clinical experience.