Assisted living video tours that clear HIPAA
A resident's face in a tour video can disclose protected health information. Build a two-track library so a revoked authorization is a re-render, not a reshoot.
The marketing instinct for a senior living community is obvious and mostly correct: show the residents. Empty buildings sell nothing. Families are not choosing a floor plan, they are choosing who their mother will eat dinner with, and a tour video with nobody in it reads as a listing rather than a home.
The complication is that on a campus which provides care, the fact that a particular person lives there is health information. Put an identifiable resident in a video and label it as your assisted living community, and you have disclosed that this person receives assisted living services. That is a disclosure, and a standard photo release is not the document that authorises it.
Who is actually covered, and why marketing can't answer that alone
HIPAA applies to covered entities — health plans, clearinghouses, and health care providers who transmit health information electronically in connection with covered transactions. A skilled nursing facility that bills electronically is squarely inside that. Assisted living communities that provide and bill for health care services generally are too. A purely residential independent living campus that provides no care and bills no insurer may not be.
Most operators run more than one of these under a single brand, on a single site, with a single marketing team. That is exactly why the question "are we a covered entity?" cannot be answered by the person editing the video. Get it answered in writing by whoever owns compliance, per building, before you plan the shoot. The answer changes what you are allowed to point a camera at in each wing.
The safe operating assumption in the meantime: treat every resident on a care campus as if their residency is protected information, and build the library so that assumption costs you nothing.
A HIPAA authorization is not a model release
This is the mistake that shows up most often. A production company brings a standard talent release, everyone signs it, and the footage ships. A model release covers likeness and publicity rights. It does not cover the use or disclosure of protected health information for marketing, which requires its own authorization with its own required contents — what information is being used, who may use it, who may receive it, the purpose, an expiration date or event, and a statement of the individual's right to revoke it, signed and dated.
Three practical consequences fall out of that:
- You need both documents, not one. The likeness release and the HIPAA authorization do different jobs and one does not absorb the other.
- Capacity matters. A resident with cognitive impairment may not be able to give a valid authorization, in which case it must come from a personal representative with actual legal authority, not simply the adult child who visits most. In memory care, the practical answer is usually that you do not film residents at all.
- Authorization is revocable. Someone can withdraw it, in writing, after your video has been live for eight months and is embedded on every page of the site. If your hero asset is built around that person, you now have a reshoot and a full re-edit on a deadline you did not choose.
Point three is the one that should shape how you produce, not just how you paper it.
Build the library in two tracks
Stop producing single monolithic tour videos. Produce two separate libraries and assemble from them.
Track A — generated and filmed-empty ambience. No residents, no staff, no PHI. Exteriors through the seasons, the courtyard at golden hour, the dining room laid before service, a corridor with the afternoon light coming through, the activity room, the therapy gym, parking and step-free entrances. Some of this you film on a quiet morning. The rest — the seasons you don't have footage of, the weather you never get, the aerial you can't afford — you generate. This track never expires, never gets revoked, and never needs a signature.
Track B — authorized resident and family stories. Real people, filmed with a valid authorization plus a likeness release on file, each one cut as a self-contained module of fifteen to forty seconds with its own top and tail. Never intercut a Track B subject through the whole video. Keep them modular.
Then assemble: Track A carries the spine and the voiceover, and Track B slots in as removable modules. When an authorization is revoked, you pull one module, drop in another, and re-render. Because the Versely editor is EDL-based — one timeline you can re-render rather than a baked file — that swap is an edit, not a production. Run the recut through the free 480p preview pass first, which carries a short per-user cooldown, then export once; a single charge applies to the final export regardless of how many clips are on the timeline. Saving the assembly as a reusable draft is what makes this a five-minute job the second time.
What to generate for Track A
Generated footage is doing a specific job here: covering the shots that are either impossible to film without capturing residents incidentally, or impossible to film at all this quarter.
| Shot | Why it's generated |
|---|---|
| Exterior in four seasons | You have one season of footage and a launch date |
| Courtyard and gardens in bloom | Same problem, weather-dependent |
| Dining room set before service | Filmable, but only in a narrow window |
| Aerial or elevated establishing | Cost and airspace |
| Corridors and common areas with warm light | Filmable empty, but light is hard to control |
| Generic activity ambience with no faces | Avoids incidental capture entirely |
Two hard limits on generated material. Do not generate a photorealistic version of your own building that has amenities the building does not have — that is a misrepresentation with a very short fuse when the family arrives for a visit. And do not generate people who read as residents and put words in their mouths. A synthetic older adult saying they love it here is a fabricated testimonial and is treated as one no matter how it was made; the fake review rule and AI testimonials covers where that line sits. Generated humans are ambience — a figure at distance, hands on a garden fork, a silhouette in a doorway — and never testimony. Label them under normal synthetic media disclosure practice.
The AI B-Roll Generator is the surface for most of Track A. The general structure of a walkthrough, meaning order of rooms, pacing, and what to show when, carries over from how to make a real estate walkthrough with the resident-privacy layer added on top.
Incidental capture is the other half of the problem
Authorization protects you for the people you meant to film. It does nothing about the resident who walks through the back of frame while you are shooting the lobby, and a recognisable face in the background of a marketing video is the same disclosure as a recognisable face in the foreground.
Three controls, in order of reliability:
- Film common areas empty. Early morning, posted notice, a staff member at each end of the corridor. This solves it completely and costs an hour.
- Post notice in advance through the usual resident communication channels, so nobody is surprised and anyone who objects can stay clear.
- Review every frame before export, not just the ones you were watching during the shoot. Backgrounds, reflections in glass, name plates beside doors, whiteboards with room numbers and initials. The pre-publish check step exists for exactly this class of miss.
Blur is a last resort, not a plan. It looks like what it is, and it draws attention to the person you were trying to protect.
FAQ
Can we film residents if we only use the footage on our own website?
The channel is not what determines whether a use is permitted — the authorization is. An authorization that names social media and paid advertising covers those; one that says nothing about them does not, and "we only put it on our site" is not a defence if the site feeds a retargeting pixel and the clip ends up in an ad. Write the authorization to name every destination you actually intend, including the ones you might add later, and re-paper it if the plan changes.
What about staff on camera?
Staff are an employment and likeness matter rather than a HIPAA one, so a normal release covers them. Get it in writing, and make it survive their departure. A beloved activities director who leaves for a competitor is a common reason a tour video has to come down. The same modular approach applies: keep staff-led segments as swappable blocks rather than threading one person through the whole piece.
Is a signed release from years ago still good?
Check the expiration term. A HIPAA authorization is supposed to state an expiration date or an expiration event, and one that has passed is no longer operative regardless of how good the footage is. Keep a simple register — subject, date signed, expiry, destinations named, revocation status — and audit it before any campaign refresh rather than after a complaint.
Can we use a generated voice over real resident footage?
Yes for narration, no for the resident. A synthesised narrator reading your script over Track A footage is ordinary production. Putting a generated voice in the mouth of a real, identifiable resident — or re-voicing what they actually said into something cleaner — turns their appearance into something they did not say and did not authorise. That is a different thing entirely, and no authorization you have on file covers it.