How to Catch PHI in a Telehealth Training Video's Screen Recording Before It Goes Out for Review

Somewhere in your telehealth training library right now, there's probably a screen recording of someone's real EHR session sitting in a review folder, and there's a decent chance nobody's looked closely enough to notice that the patient name in the top left corner, the date of birth in the intake field, and the insurance ID halfway down the chart all belong to an actual person who never consented to being part of a training video. We see this constantly with telehealth and health system clients building out their onboarding and scheduling-software training content, someone on the training team screen-records a real walkthrough because it's faster than building a sanitized demo environment, and that recording gets treated like any other piece of raw footage headed into review. It isn't. A screen recording of a live EHR session is protected health information the moment a real patient's data appears on screen, and once that file is sitting in a shared drive or an email thread waiting for feedback, the exposure has already started, whether the video ever makes it to a public audience or not.

That's the specific problem this post is about, not general video security, but the exact moment in a review workflow where someone needs to be looking at every frame of a screen recording asking one question, is there a real patient's information visible right now, before that file goes anywhere else, even to a colleague two desks away. Sound familiar? If you've ever sat in a training review meeting and watched a scheduling walkthrough scroll past a real patient's chart without anyone in the room reacting, you already know exactly how invisible this problem is once you're used to seeing that interface every day.

The reason this keeps happening isn't carelessness, it's that screen recordings occupy an odd middle ground in most production workflows. They don't feel like "real" video the way a filmed interview or a produced explainer does, so they don't get routed through the same scrutiny, they feel more like documentation, something closer to a screenshot than a video asset, and that perception is exactly what lets protected health information ride along undetected into a review folder, a shared drive, or an inbox.

Why "It's Just Internal" Is the Riskiest Assumption in This Workflow

The instinct on most training teams is that a review draft shared internally doesn't carry the same risk as a public-facing video, and that assumption is exactly backwards when PHI is involved. HIPAA doesn't distinguish between a file sent to one internal reviewer and a file posted publicly, exposure is exposure the moment protected data leaves a controlled, access-limited environment, and a raw screen recording forwarded over email or dropped into a general Slack channel has already left that environment even if only three people ever open it. The catch here is that internal sharing actually tends to be less careful than external sharing, because nobody applies the same scrutiny to a quick "hey can you check this real quick" message that they'd apply to something going out the door, which means the file with the least oversight is often the one carrying the most exposure.

Where PHI Actually Hides in a Screen Recording Nobody Meant to Capture

The tricky part of this problem is that the PHI is rarely the thing the recording is about. Someone is capturing a five-minute walkthrough of how to reschedule an appointment in the scheduling module, and the actual patient name sitting in the header bar the entire time is incidental, background information nobody was thinking about when they hit record. That's exactly why it slips through. The trainer is focused on demonstrating the workflow, the editor cutting the video is focused on pacing and clarity, and the reviewer watching the draft is focused on whether the instructions make sense, so the patient name sitting quietly in the corner for the full four minutes and thirty seconds doesn't register as the thing anyone's supposed to be checking.

The usual suspects

A single training recording can carry PHI in more places than people expect once you actually go looking frame by frame. The patient banner or header bar that most EHR platforms pin to the top of every screen is the most common offender, since it typically shows full name, date of birth, and a medical record number all at once and stays visible through the entire recording. Search results and patient lists are another, because a scheduler demonstrating how to look someone up will often pull a real name from a live queue rather than typing in a fake one. Chart notes, lab results, and insurance fields that get scrolled past quickly are easy to miss because they're only on screen for a second or two, but a second or two is still enough for a reviewer pausing the video, or anyone downloading the raw file later, to read a name clearly. And notification pop-ups, the little toast alerts that say "new message from patient," tend to slip through because they appear and disappear on their own timeline, completely outside whatever the trainer was narrating at that moment.

Building a PHI Checkpoint Into the Review Chain, Before the First Share

The fix here isn't asking editors or trainers to be more careful, because they're already focused on a different job, the workflow itself needs a dedicated checkpoint that exists specifically to catch this, sitting before the file is shared with anyone beyond the person who recorded it.

This is the part where the tool you're reviewing in actually matters, because a PHI check only works if the reviewer can pin a note to an exact frame and have that note travel with the file, rather than writing "there's a name visible somewhere around the three-minute mark" in a Slack message that the editor then has to go hunting for. PlayPause was built around exactly this kind of frame-accurate, timecoded commenting on a video review, so a reviewer scrubbing through a training recording can drop a note directly on frame 4,212 and say "patient name visible top left, blur or trim before this goes any further," and that note stays attached to that exact moment through every version of the file that follows, so nobody downstream has to go hunting for the frame the note was actually about.

That matters more than it might sound like on paper, because the alternative, a written note in a separate document describing roughly where the problem is, is exactly the kind of gap that lets a flagged issue slip through a second time. We've had training teams tell us that before they moved their PHI review into a proper review tool, the same exposed patient banner made it into two separate versions of a video because the note describing it the first time was vague enough that the editor fixed a different frame entirely and thought the job was done.

What the PHI Reviewer Is Actually Scanning For, Frame by Frame

This checkpoint works best as a slow, deliberate watch-through rather than a normal review pass, because the whole point is catching things that were never meant to be the focus of the shot.

• Patient banner or header bar visible anywhere in the frame
• Full name, DOB, MRN, or insurance ID in any field, even scrolled past quickly
• Chart notes, diagnoses, or lab values readable on screen
• Notification pop-ups or toast alerts referencing a real patient
• Provider notes or next-of-kin contact information in sidebar panels

We tell teams to treat this the same way you'd treat a legal or compliance review, which is to say slower than feels natural, because a normal review pass moves at the speed of the narration and this one needs to move at the speed of the slowest-changing element on screen. A trainer talking for ten seconds about how to click through a menu might have a patient's insurance ID sitting untouched in a side panel that whole time, and the only way to catch it is watching with the sound off at least once, purely scanning the frame for text that shouldn't be there.

Who Should Own This Checkpoint

On most teams we work with, this ends up split between two roles depending on organization size. Smaller training teams usually designate one person, often whoever owns HIPAA compliance training internally, as the standing PHI reviewer for every screen recording before it moves past the first round, and that person's sign-off becomes a hard gate the same way legal sign-off is a hard gate on a public-facing video. Larger health systems with a dedicated compliance or privacy office tend to route screen recordings through that office as a first-stage checkpoint before the video even reaches the instructional design or training team for content review, which flips the usual order, security first, content quality second, precisely because a PHI leak is a much bigger problem than an awkward cut.

Whoever holds the seat, the role only works if it's named and staffed consistently rather than assigned informally whenever someone happens to remember. General production workflow guidance from sources like StudioBinder's blog tends to emphasize the same principle for any specialized review step on a project, a checkpoint without a clearly assigned owner and a hard deadline quietly becomes optional the first time a schedule gets tight, and PHI review is exactly the kind of step that cannot afford to become optional even once.

What Happens After a Flag: Redact, Trim, or Re-Record

Once a reviewer flags a frame, the fix usually falls into one of three buckets, and picking the right one matters because they're not interchangeable. A quick blur or box-out over a name or ID field works fine when the data is incidental and only visible for a moment, and it's the fastest fix when the rest of the shot is otherwise usable. Trimming or cutting the clip entirely makes more sense when PHI is on screen for an extended stretch, since blurring a patient banner for forty straight seconds is both harder to do cleanly and more likely to distract from the training content itself. And a full re-record, going back into a sandbox or test environment with dummy patient data, is the right call whenever the same PHI exposure would recur across multiple takes of similar content, which is common with scheduling and intake walkthroughs where the same screens get demonstrated repeatedly across a training series.

Locking Down Who Can Even Open the File While It's Under Review

Catching PHI on screen is only half the job, the other half is making sure the file itself isn't sitting somewhere that anyone with the link can open it while it's still in this vulnerable, unredacted state. This is where a lot of teams unintentionally undercut their own checkpoint, they build a careful PHI review step but then still share the raw draft through a general file-sharing link that never expires and that anyone in the org could stumble onto. Using expiring share links and role-restricted access for anything still in the PHI review stage means the file simply isn't reachable by anyone outside the two or three people who are supposed to be looking at it, and that access automatically closes once the review window is over rather than depending on someone remembering to revoke it later. It's the same logic behind sharing security on any sensitive project, the fewer people who can technically open a file, the fewer chances there are for a mistake, and pairing that access control with a formal approval workflow means the video literally cannot move to the next stage until the PHI flag shows resolved in the record.

Making This a Habit Instead of a One-Time Audit

The teams that keep this discipline going long term treat the PHI checkpoint as a permanent, named stage in their video review process for any training content touching real systems, not a special step someone remembers to add after a scare. That means every new hire on the training team learns the checkpoint exists before they ever hit record, it means the checkpoint applies to every screen recording without exception, not just the ones that "probably" have PHI in them, and it means the sign-off lives in the same review trail as every other note on the file so there's a clear record of who checked it and when if that question ever comes up later. This pairs naturally with the kind of structured, dedicated-round thinking we've written about for other high-stakes healthcare content too, including our companion piece on running a health literacy pass on patient education videos, since both problems share the same root cause, a real risk that's invisible to whoever's job is to review something else entirely, and both get fixed the same way, by giving the risk its own named seat in the workflow instead of hoping someone catches it in passing.

Set Up This Checkpoint Before Your Next Training Video Ships

If your telehealth training content includes screen recordings of real systems, the question isn't whether PHI has ever slipped through unnoticed, it's how many times, and a dedicated, timecoded review checkpoint is the fix that doesn't require rebuilding your whole production process. PlayPause gives training and compliance teams frame-accurate commenting, expiring access links, and a full audit trail on every review round, all under one flat workspace price rather than a per-seat cost that discourages adding another reviewer to the chain, and you can see how the plans break down on our PlayPause pricing page. Contact PlayPause to walk through setting up a PHI checkpoint in your existing review workflow before your next training video goes out for its first round.