Video production for medical devices

What this is about

What a device film may claim is bounded by the device's intended purpose and its instructions for use — marketing cannot promise what the documentation does not state, and frameworks like the MDR make that a compliance matter, not a style question. Showing the device in use raises the second wall: filming in an operating room needs hospital approval, patient consent, sterile-field discipline and a crew that knows where it must never stand. Many productions sidestep this with simulation labs, phantoms or staged procedures — which must then be recognizable as such. Every scene needs an answer to two questions before the shoot: real or simulated, and cleared to claim what.

Sector routine beats general experience: knowing the field's approval paths and constraints produces more realistic plans than more shoot days without that context.

What runs differently here

In planning terms, that means:

• Claims must stay inside the device's intended purpose — a benefit the instructions for use do not support cannot appear in the film
• OR shoots require hospital sign-off, written patient consent and sterile-zone briefing; one wrong step voids the procedure's sterility
• Simulation labs and phantoms replace real procedures for most shots, but the film must not pass them off as clinical reality
• Demo units and cleared production units differ — the serial number in frame can matter in regulatory review
• Clinician appearances often involve disclosure of the collaboration; their statements are reviewed like any claim

What the plan has to deliver

A production plan is useful to this role when it provides the following:

• A scene list that declares real vs. simulated per shot, with the consent and approval chain attached
• Claim wording locked with regulatory affairs before scripting the voiceover
• An OR logistics plan — positions, sterile boundaries, minimal crew — agreed with the hospital
• Backup scenes in the simulation lab for every shot that depends on a live procedure

Common pitfalls

What most often goes wrong in practice:

• Scripting patient-benefit language the device documentation cannot back
• Planning an OR day without a fallback when the procedure is cancelled
• Framing monitors that show real patient data

With TillyGen

TillyGen carries the real-or-simulated flag and the claim status on every scene from briefing to schedule, so an OR cancellation reroutes the day to the simulation lab instead of ending it.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.