Industry Playbooks
Healthcare Video Enhancement Playbook
Healthcare video — telehealth recordings, surgical documentation, patient monitoring — contains PHI and requires HIPAA compliance. This playbook covers how to enhance healthcare video while maintaining compliance.
Healthcare Video Types
| Type | PHI Risk | Common Issues |
|---|---|---|
| Telehealth recordings | High | Low bandwidth, compression, poor lighting |
| Surgical documentation | High | Lighting variation, blood, quick movements |
| Patient monitoring | High | Low resolution, continuous recording |
| Wound documentation | High | Color accuracy critical, detail needed |
| Medical education | Varies | Depends on de-identification |
HIPAA Compliance Requirements
Technical Safeguards (§164.312)
- ☐ Encryption in transit (TLS 1.2+)
- ☐ Encryption at rest (AES-256)
- ☐ Access controls and audit logs
- ☐ Automatic logoff
Administrative Safeguards
- ☐ Business Associate Agreement (BAA) signed
- ☐ Workforce training
- ☐ Incident response plan
BetterVideo HIPAA Support
- BAA: Available on all paid tiers
- Encryption: TLS 1.3 transit, AES-256 rest
- Access: Per-customer isolation, audit logs
- Retention: Zero-retention architecture
Enhancement Workflow for Healthcare
1. VERIFY BAA
# Ensure BAA is signed before processing PHI
if not baa_signed:
raise ComplianceError("BAA required")
2. PREPARE VIDEO
- Remove unnecessary PHI if possible
- Minimize data sent for processing
3. ENHANCE WITH PHI CONTROLS
response = bettervideo.enhance(
video_url=secure_presigned_url,
resolution="1080p",
# Regional processing if required
region="us"
)
4. AUDIT LOGGING
log_phi_access(
video_id=video_id,
patient_id=patient_id,
action="enhancement",
job_id=response.job_id,
timestamp=now()
)
5. RETRIEVE AND STORE
- Download to HIPAA-compliant storage
- Update EHR/clinical system
- Log access
EHR Integration
Epic Integration
Integrate via MyChart or Haiku:
- Trigger enhancement on video upload
- Store enhanced video in Media Manager
- Link to patient encounter
Cerner Integration
Use CareAware iBus:
- Event trigger on new video
- Enhancement workflow
- Update Millennium record
HL7/FHIR
// FHIR Media resource update
PUT /Media/{id}
{
"content": {
"url": "enhanced_video_url",
"title": "Enhanced procedure video"
}
}
Use Case: Telehealth Quality
The Problem
Telehealth video quality is often poor:
- Patient bandwidth limitations
- Provider reviews recorded calls
- Detail needed for clinical decisions
The Solution
# After telehealth call ends
if call.recording_enabled:
enhanced = bettervideo.enhance(
video_url=call.recording_url,
resolution="1080p"
)
attach_to_encounter(call.encounter_id, enhanced)
Clinical Impact
- Better skin tone visibility for dermatology
- Clearer wound assessment
- Improved documentation for follow-up
- Better training material
Frequently Asked Questions
BetterVideo provides BAA on all paid tiers, uses encryption (TLS 1.3, AES-256), zero-retention architecture, and maintains audit logs.
Yes, if you're sending PHI (video with identifiable patients). Contact us to execute BAA before processing.
Yes — enhance recordings after calls for better documentation and clinical review.
Ready to get started?
Try BetterVideo's privacy-first video enhancement API — free sandbox, no credit card required.