A supervised camera that measures OR workflow. Raw video never leaves the device.
This page explains how DEO.care’s OR camera handles data for hospitals in Europe and in other countries whose data protection laws follow the same principles, such as the EU GDPR, the UK GDPR and the Swiss data protection act. Each heading gives the short answer. Open it for the detail, tagged Tech, Legal or Security.
EUROPE AND INTERNATIONAL · OR CAMERA · DATA PROTECTION · v1.0 · Effective [date]
Deleted on the device right after depersonalisation
Stored with AWS in Frankfurt; processed from the EEA
After the report; never later than 6 months after upload
Unless the hospital chooses longer retention, up to 10 years
Informational overview, not legal advice. The data processing agreement is the binding document. National requirements vary; verify those that apply to your hospital.
How the camera works
A dedicated iPhone, centrally managed by DEO.care through mobile device management (MDM), records the OR during the measurement days. Faces and exposed skin are blurred on the device. Audio is off unless the hospital selects it for a project, and then speech is removed on the device. A hospital user approves each depersonalised recording before it is uploaded. The raw recording never leaves the phone.
The five steps, start to finish Capture, depersonalise, approve, encrypted upload, analysis
1. Capture. The device records the OR at low resolution with an ultra-wide view. Video is written only to the app's encrypted, private storage on the device, which no other app can reach. Audio is recorded only where the hospital has selected it. A recording carries only its date, time and the device used. The OR room is not recorded.
2. Depersonalise. Faces and exposed skin are blurred and, where audio is recorded, speech is removed. This happens entirely on the device. The raw recording is deleted as soon as the depersonalised version is produced.
3. Approve. A hospital user reviews the depersonalised recording on the device and either approves it for upload or deletes it. A recording whose depersonalisation failed cannot be uploaded. Approval does not move responsibility for depersonalisation from DEO.care to the hospital.
4. Encrypted upload. Only approved, depersonalised video is uploaded over an encrypted connection to Amazon Web Services (AWS) in the EU (Frankfurt region). It is then deleted from the phone.
5. Analysis. DEO.care reviews the video to extract process data: step timings, task sequences and role activity. The process data is stored in DEO.care's database and used to produce the hospital's report.
Tech Does it connect to the hospital IT network?
No. The device uploads over hospital guest Wi-Fi or its own mobile connection. It never touches clinical systems or the hospital network.
Tech Network and transport: encrypted, outbound-only, upload-only
- Uploads are encrypted in transit (TLS 1.2 minimum, TLS 1.3 preferred).
- The device can only upload. It cannot list, read or delete anything in storage, and its access credentials expire after a short time.
- Nothing can connect into the device. It only makes outbound connections.
- It uses hospital guest Wi-Fi, with a DEO.care-provided mobile eSIM as backup.
Security What DEO.care can do with the device remotely
The iPhones are registered in Apple Business Manager and managed through MDM. MDM is used to configure, restrict, lock and remotely wipe the device, for example after loss or theft. It gives no access to recordings or app data. Devices are returned to DEO.care after the measurement days and wiped on return.
Tech What happens to the raw recording?
Raw video is written only to the app's private, encrypted storage. It is never written to the camera roll, Files, iCloud or any shared location, so the person using the device cannot access it. The raw recording is deleted as soon as the depersonalised version is produced. An approved recording is deleted from the phone once its upload completes. A recording that is not approved can be deleted by the hospital user at any time. Otherwise it is deleted when the device is returned, and in any case no later than 3 months after recording.
Tech Why deletion is irreversible
Each file has its own encryption key. Deleting the file destroys that key, so the remaining data cannot be recovered (cryptographic erase, NIST SP 800-88). iCloud Photos and iCloud backup are disabled on the devices.
Tech The depersonalisation engine: detection only, never recognition
DEO.care's engine uses an established, commercially licensed image-detection model to find faces and exposed skin in each frame and blur them. It only locates where these are in the image. It never identifies who a person is. The engine has been tested on difficult OR conditions such as masks and gowns, surgical drapes and unusual camera angles. Model and validation details are available on request.
Tech What if depersonalisation fails?
If depersonalisation on the device does not meet its quality threshold, the recording cannot be uploaded and the raw footage is deleted. Raw footage never reaches the cloud.
What is and is not measured
The output is process data: how the OR day flows, case by case. No patient identifiers and no clinical records are collected. Staff are analysed by role. The hospital decides whether a surgeon identifier is recorded.
Detail The full measured and not-measured list
| MEASURED (PROCESS DATA) | NEVER COLLECTED |
|---|---|
| Timing of workflow steps | Patient identifiers |
| Task sequences and overlap | Medical records, diagnoses or outcomes |
| Role participation patterns (staff by role, not name) | Clinical quality metrics |
| Resource presence and utilisation | Behavioural scoring or profiling of staff |
| Procedure context | Speech content |
| Surgeon identifier, where the hospital selects it |
Detail What a recording contains
- Video at low resolution with an ultra-wide view, in which faces and exposed skin are blurred. Text on screens or whiteboards is not legible in practice.
- No audio, unless the hospital selects it for a project. Even then, speech is removed on the device.
- As recording information, only the date, time and device. No OR room, case number or patient details.
- A file name and folder name made of randomly generated codes.
Tech Does DEO.care see our patient records or clinical systems?
No. DEO.care never accesses electronic health records, medical records or clinical databases, and does not integrate with hospital IT systems. The only data leaving the OR is the approved, depersonalised video.
How the recordings are protected
Depersonalisation removes faces, exposed skin and speech, but the recordings are not anonymous: the hospital can still link a recording to a procedure through its own OR schedule. DEO.care therefore treats the recordings as personal data and protects them at the level required for health data.
Legal How the link to a patient is split between two parties
Video files are stored under randomly generated codes, in folders that are also named by random codes. The storage holds no information about the files beyond what the storage service records automatically, such as the upload date. Someone with access to the storage alone would see only video files, with no indication of where or when they were recorded other than that upload date.
- DEO.care keeps a separate database recording which hospital each file came from and when it was recorded.
- The hospital keeps its own OR schedule showing which patients were treated at that time.
- Linking a recording to a patient requires both. DEO.care has no access to the hospital's schedule.
Legal Are the recordings health data?
In the hands of the hospital, the recordings may constitute data concerning health, because the hospital can link them to a patient's procedure. Whether they do is for the hospital to assess as controller. DEO.care protects them at the level required for health data in either case.
Where data is stored and who can access it
Recordings and process data are stored in the EU and processed by DEO.care from the European Economic Area (EEA). Personal data is disclosed to public authorities only where EU or EU Member State law requires it.
Security Who can access the recordings
- Storage: AWS, EU (Frankfurt region).
- Review: DEO.care engineers working from the EEA, on DEO.care-managed laptops under MDM with remote wipe. Video is downloaded only inside a DEO.care review application with private, controlled storage.
- Device user: cannot access the raw recording, and sees only the depersonalised recording during approval.
Legal Sub-processors
DEO.care uses two sub-processors for the recordings: Amazon Web Services (hosting, EU region) and ITLicious (software development and infrastructure maintenance), which can access the systems that hold the recordings when it maintains them. Both are bound by written terms equivalent to DEO.care's own obligations. The hospital is informed in advance of any change and can object.
Legal Hospitals outside the EU and EEA
For hospitals outside the EU and EEA, the recordings are transferred to the EU for processing. Many national data protection laws, including those of the United Kingdom and Switzerland, recognise the EU as providing an adequate level of protection. The agreement includes the transfer terms the hospital's national law requires. DEO.care has standard addenda for the United Kingdom and Switzerland.
Legal Requests from authorities
DEO.care discloses personal data to public authorities only where EU or EU Member State law requires it. A court order or request from an authority outside the EU is not on its own a basis for disclosure.
Roles and who decides
The hospital is the controller and decides how patients and staff are informed. DEO.care is the processor and processes the data only on the hospital's documented instructions, under a data processing agreement.
Legal Who plays which role
- Hospital (controller): decides purpose, scope, case selection and retention options; determines the lawful basis; informs patients and staff; carries out a DPIA where required.
- DEO.care (processor): processes only on the hospital's documented instructions and defines no purpose of its own. It tells the hospital if an instruction appears to break data protection law, and assists with security, DPIAs and requests from individuals.
- Sub-processors: AWS and ITLicious, under written terms equivalent to DEO.care's own.
Legal Lawful basis and health data
The hospital determines the lawful basis for the recordings. Data protection laws generally allow health-related processing that is needed to manage and improve health care services, under the conditions national law sets. Some countries add specific rules for health data or for video in the workplace. DEO.care supplies the information the hospital needs to assess this.
Legal Supporting your DPIA
Video recording in the OR may require a data protection impact assessment (DPIA), depending on the hospital's own assessment. DEO.care provides its DPIA and data protection documentation to support it.
Legal Breach notification
DEO.care notifies the hospital without undue delay, and within 48 hours of becoming aware of a personal data breach, with the information the hospital needs for its own notifications.
Legal Audits and evidence
The hospital can verify that DEO.care meets its obligations. DEO.care's ISO/IEC 27001 certificate and security evidence pack are available on request, and audits are possible under the conditions in the agreement.
Legal Requests from patients or staff
Requests to exercise data protection rights go to the hospital. If DEO.care receives one, it forwards it to the hospital and helps the hospital respond.
Benchmarking and report sharing
Benchmark use is a condition of every engagement. The channel partner receives the project report without surgeon names or video.
Detail How benchmark data is prepared
Process data enters the benchmark only after it is anonymised: the surgeon identifier is removed, dates are reduced to the year and the hospital is reduced to its country. Recordings and personal data are not used to train models or develop products.
Detail What the channel partner receives
Engagements run through a channel partner. The partner receives the project report without surgeon names or video. Any other data reaches the partner only in aggregated form.
What this means for OR staff
Recording is open, not covert, and is never used to evaluate, discipline or credential individuals. Staff are told in advance and can object.
Detail Purpose limitation and how notice works
- Purpose limitation: recordings and results are not used for individual performance management, discipline, credentialing, clinical outcome attribution, patient monitoring or marketing. This is written into the agreement.
- Advance notice: the hospital informs staff before any recording window, covering purpose, dates, ORs in scope and how to object. DEO.care provides information material the hospital can adapt.
- Staff representatives: where national law requires works councils or staff representatives to be consulted, the hospital arranges this.
- Objection: raised with a supervisor or the hospital's data protection contact. Exclusion is accommodated where operationally feasible.
Legal No biometric processing
Faces and exposed skin are located only to blur them. They are never recognised, and no data is created that could identify a person. DEO.care does not process biometric data.
Tech How audio is handled
- Audio is off by default. It is recorded only where the hospital selects it for a specific project.
- Where audio is recorded, an on-device speech-detection model finds speech and removes it before anything leaves the OR. This is not speech recognition, speaker identification or emotion detection.
- The remaining non-speech audio is used only to mark workflow events, such as the sound of a surgical saw.
Retention, transparency and security
Recordings are deleted 3 months after the report, and never later than 6 months after upload. Process data is anonymised after the project unless the hospital chooses longer retention. The camera is deliberately visible, and the work runs inside an ISO/IEC 27001-certified security programme.
Detail Retention
- Recordings: deleted 3 months after the report is delivered, and never later than 6 months after upload.
- Backup copies: erased no later than 9 months after upload.
- Recordings never approved for upload: deleted on the device when it is returned, and no later than 3 months after recording.
- Process data: anonymised within 3 months after the project, unless the hospital selects longer retention for follow-up projects, up to 10 years. Anonymisation removes the surgeon identifier, the day and month, and the hospital name.
Detail Transparency: why it isn't covert
- The camera is placed where staff and patients can see it.
- Staff are informed in advance by the hospital, and a briefing can be arranged.
- The hospital informs patients, for example with an information sheet or a notice in the OR, using material DEO.care can provide.
Security Security controls in detail
- Encryption: in transit TLS 1.2 or higher (1.3 preferred); at rest with AWS-managed encryption; on the device AES-256, with raw recordings cryptographically erased after processing.
- Least-privilege upload: the device has upload-only access (no list, read or delete), with short-lived credentials.
- Processing environment: multi-factor authentication for administrative access, role-based access, and access logging and monitoring.
- Review laptops: DEO.care-managed, under MDM with remote wipe; video only inside a DEO.care application with private, controlled storage.
- Confidentiality: everyone at DEO.care and its sub-processors who can access the recordings is bound by confidentiality. Evidence is available on request.
- Governance: operated within DEO.care's ISO/IEC 27001-certified information security management system, with a formal incident management and breach notification process.
Security Device management and lost devices
The iPhones are used only for the DEO.care recording app and managed through MDM, which can configure, restrict, lock and wipe them but cannot read recordings or app data. A lost or stolen device is protected by full-disk encryption (AES-256), cryptographic erase on deletion, remote wipe, and Activation Lock: a wiped device cannot be used without DEO.care's account.
What DEO.care does and does not do
DEO.care measures OR workflow from video that is depersonalised on the device, and processes it only on the hospital's instructions. It does not evaluate individuals, access clinical systems or see the hospital's patient schedule.
Detail The full does and does-not list
| DEO.CARE DOES | DEO.CARE DOES NOT |
|---|---|
| Measure and analyse OR workflow: timing and structure, role interactions, friction and delay, resource utilisation | Evaluate individual staff, or support HR or disciplinary decisions |
| Depersonalise every recording on the device before anything is transmitted | Assess clinical quality or analyse patient outcomes |
| Let the hospital approve every recording before upload | Access patient records, clinical databases or the OR schedule |
| Process personal data only on the hospital's documented instructions | Integrate with hospital IT systems |
| Provide documentation to support the hospital's DPIA and staff and patient information | Use recordings or personal data to train models or develop products |
The data processing agreement is the binding document. This page summarises how DEO.care works and does not replace it.