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 US hospitals. Each heading gives the short answer. Open it for the detail, tagged Tech, Legal or Security.

UNITED STATES · OR CAMERA · DATA SECURITY & HIPAA · v1.1 · Effective November 4, 2026

Deeper detail is tagged TECH LEGAL SECURITY.

RAW VIDEO
Never leaves the device

Deleted on the device right after de-identification

VIDEO STORAGE
AWS US-East-1

Reviewed by DEO.care engineers in the US and Europe

VIDEO RETENTION
3 months

After the report is delivered

PROCESS DATA
Up to 10 years

Period set by the hospital; hosted in the EU

Informational overview, not legal advice. It does not account for state-specific recording, consent, or privacy law, which varies by state and changes over time. Verify the requirements for your jurisdiction before deployment.

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 de-identified recording before it is uploaded. The raw recording never leaves the phone.

The five steps, start to finish Capture, de-identify, 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.

2. De-identify. 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 de-identified version is produced.

3. Approve. A hospital user reviews the de-identified recording on the device and either approves it for upload or deletes it.

4. Encrypted upload. Only approved, de-identified video is uploaded over an encrypted connection to AWS US-East-1. It is then deleted from the phone.

5. Analysis. The video is analyzed into 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 cellular 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 cellular 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 de-identified 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 de-identification 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 and creates no biometric data. 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 de-identification fails?

If de-identification 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. The surgeon is identified by name or by pseudonym, as the hospital chooses. Other staff are analyzed by role.

Detail The full measured and not-measured list
MEASURED (PROCESS DATA) NEVER COLLECTED
  • Timing of workflow steps
  • Task sequences and overlap
  • Role participation patterns (staff other than the surgeon by role, not name)
  • Resource presence and utilization
  • Procedure context
  • Surgeon, by name or pseudonym (hospital's choice)
  • Patient identifiers
  • Medical records, diagnoses or outcomes
  • Clinical quality metrics
  • Behavioral scoring or profiling of staff
  • Speech content
Tech Does DEO.care see our EHR 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, de-identified video.

Why patient privacy is protected

Faces and exposed skin are blurred on the device. Audio is off unless the hospital selects it, and then speech is removed on the device. DEO.care cannot link a recording to a patient without the hospital's own OR schedule, which DEO.care does not have.

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 How identifiers are handled

This table shows how each type of identifier listed in the HIPAA de-identification standard (45 CFR §164.514(b)(2)) is handled. How the data is classified under HIPAA is for the hospital to determine. DEO.care can support that assessment.

IDENTIFIER HOW IT IS HANDLED
Names Patient names are not recorded. Faces and exposed skin are blurred on the device. Recording is at low resolution with an ultra-wide view, so text on screens or whiteboards is not legible.
Geographic subdivisions smaller than a state Not recorded for patients. DEO.care's separate database records which hospital a recording came from.
Dates (except year) directly related to a patient Not stored with the video. The recording date and time are held only in DEO.care's separate database, linked to the hospital and never to a patient. Process data is kept per case, with its date.
Telephone and fax numbers, email addresses, Social Security numbers, medical record numbers, health plan beneficiary numbers, account numbers, certificate and license numbers, vehicle identifiers and license plates, web addresses (URLs) Not recorded.
Device identifiers and serial numbers Not stored with the video. The device used for each recording is recorded only in DEO.care's separate database.
IP addresses The upload IP address is logged for security auditing only. It is not stored with the video.
Biometric identifiers, including finger and voice prints Audio is off by default. Where the hospital selects it, speech is removed on the device, so no voice is transmitted. Faces and hands are located only to blur them. They are never recognized, and no biometric template is created, stored or transmitted.
Full-face photographs and comparable images Faces and exposed skin are blurred on the device, at low resolution. Recording is limited to high-volume procedures, so distinctive features do not narrow down the patient population.
Any other unique identifying number, characteristic or code Files and folders are named by randomly generated codes that contain no hospital, case or patient information.

Where data is stored and who can access it

Video is stored in the US and reviewed by DEO.care engineers in the US and Europe. Process data, and the database that records which hospital and date each recording came from, are hosted in the EU.

Security Who can access the video
  • Storage: AWS S3, region US-East-1.
  • Review: DEO.care engineers in the US and Europe, 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 de-identified recording during approval.
Legal We're a European company. Does GDPR apply, and does our data go to the EU?

Raw video never leaves the device in the OR. De-identified video is stored in the US and reviewed by DEO.care engineers in the US and Europe. Process data and the record of which hospital and date each recording came from are hosted in the EU. None of this contains patient names or other direct patient identifiers, and DEO.care cannot link it to a patient without the hospital's OR schedule.

GDPR applies to DEO.care's own processing as a company established in the EU. It does not make the US hospital subject to GDPR, and it does not change the hospital's obligations under HIPAA.

HIPAA roles and who decides on patient notice

The hospital is the Covered Entity and decides how patients are informed. For camera projects, DEO.care acts as a Business Associate under a signed Business Associate Agreement (BAA) and processes data only on the hospital's instructions.

Legal Who plays which role
  • Hospital (Covered Entity): decides purpose, scope, case selection and retention, and documents how patients are informed.
  • DEO.care (Business Associate): processes only on the hospital's documented instructions and defines no purpose of its own.
  • AWS (subcontractor, US-East-1): stores the de-identified video. DEO.care holds a Business Associate Addendum with AWS.
  • Other subcontractors: a current list is available on request.
Legal How are patients informed? Is authorization required?

The hospital decides. DEO.care does not make this call.

  • Health care operations (45 CFR 164.506(a); definition at 164.501): OR workflow analysis supports quality assessment and improvement, covered in the Notice of Privacy Practices. The Privacy Officer documents the determination under 164.530(j).
  • HIPAA authorization (164.508): collected in the pre-operative process where the hospital or state law requires it.
Legal State law may add requirements
STATE WHAT IT ADDS
California (Penal Code §632) All-party consent for recording confidential communications. Audio is off by default. Where the hospital selects it, speech is removed on the device before anything leaves the OR.
Illinois (BIPA) Biometric privacy. The pipeline only detects faces and hands to blur them and never creates a biometric template. A written notice and a retention and destruction policy are provided as additional safeguards.
Texas (SB 1188) Since January 1, 2026, electronic health records containing patient information must be physically maintained in the US. Video is stored in the US. Process data is hosted in the EU, and engineers in Europe review video. Texas hospitals should assess whether SB 1188 applies; contact DEO.care to discuss.
New York (SHIELD Act) and Massachusetts (201 CMR 17.00) Information security program requirements, addressed by DEO.care's ISO/IEC 27001-certified information security management system.
Other all-party consent states Audio is off by default. Where selected, speech is removed on the device before anything leaves the OR, and staff receive advance notice.
Legal Breach notification

DEO.care notifies the hospital of any breach of unsecured PHI without unreasonable delay, and no later than 60 calendar days after discovery, as set out in the BAA (45 CFR 164.410). The BAA carries the full contents required by 45 CFR 164.504(e), including subcontractor flow-down and return-or-destroy obligations.

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 the surgeon's identity is removed, dates are reduced to the year and the hospital is reduced to its country. Recordings and project 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. The hospital chooses whether the surgeon is identified by name or by pseudonym.

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 BAA and the workforce notice.
  • Advance written notice: given before any recording window, covering purpose, dates, ORs in scope and how to object. Consent is not relied on in the employment relationship; notice is the mechanism.
  • Objection: raised with a supervisor or the Privacy Officer. Exclusion is accommodated where operationally feasible.
Legal Biometrics (BIPA) and the NLRA
  • BIPA (Illinois) and similar laws: the pipeline only detects faces and hands, never recognizes them, and computes, stores or transmits no biometric template. A written notice and a retention and destruction policy are provided as additional safeguards.
  • NLRA: advance written notice and the purpose limitation above address the risk of a chilling effect on staff.
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

Video is deleted 3 months after the report is delivered. Process data is kept for the period the hospital sets, up to 10 years. The camera is deliberately visible, and the whole process runs inside an ISO/IEC 27001-certified security program with no access to hospital networks or clinical systems.

Detail Retention and litigation hold
  • Video: deleted 3 months after the report is delivered.
  • Process data: kept for the period the hospital sets, up to 10 years, recorded in the engagement schedule.
  • Recordings never approved for upload: deleted on the device when it is returned, and no later than 3 months after recording.
  • Litigation hold: a preservation notice suspends deletion.
  • Peer-review privilege: where state law and hospital governance permit, the engagement can be scoped under the hospital's quality improvement committee.
Detail Transparency: why it isn't covert
  • The camera is placed where staff and patients can see it.
  • Staff receive a written briefing in advance, with an in-person session offered. Patients receive an information sheet, and a poster is displayed in the OR during any recording window.
  • All engagement materials state that recording is not covert.
Security Security controls in detail
  • Encryption: in transit TLS 1.2 or higher (1.3 preferred); at rest AWS SSE-KMS; 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.
  • 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 and improves OR workflow from video that is de-identified on the device. 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 analyze OR workflow: timing and structure, role interactions, friction and delay, resource utilization
  • De-identify every recording on the device before anything is transmitted
  • Let the hospital approve every recording before upload
  • Deliver reports based on workflow, with the surgeon identified by name or pseudonym as the hospital chooses
  • Provide model patient and OR staff privacy notices for the hospital to adapt
  • Evaluate individual staff, or support HR or disciplinary decisions
  • Assess clinical quality or analyze patient outcomes
  • Access EHR or EMR systems, clinical databases or the OR schedule
  • Integrate with hospital IT systems
  • Transmit or keep speech

Privacy notices: DEO.care supplies model patient and OR staff privacy notices. The hospital determines the notice and authorization requirements that apply under HIPAA and state law.