Security and IG summary
How a 60-day ORbserve pilot handles data, on one page.
| Area | What we do | Status |
|---|---|---|
| Hardware | One camera above the operating table, one small computer in the theatre, and a small mobile-data box for the team's phone alerts. All supplied by ORbserve. | Pilot design |
| Hospital network | Not connected to the hospital network or patient record system during a pilot. No inbound connections. | Pilot design |
| Video | Frames are analysed in memory on the theatre computer and discarded. Nothing is recorded or streamed. | Built in |
| Data kept | Event times, changeover durations, observation-mode alert logs, pauses and corrections. No names, NHS numbers, images or audio. | Built in |
| Encryption | Encrypted disk on the theatre computer; reports exported only to a location the hospital approves. | For the pilot |
| Access and audit | Device password; ORbserve access only with the hospital's agreement; every correction and pause logged. | For the pilot |
| Retention | Kept on the device for the pilot, then copied to the hospital and wiped unless the pilot continues. | Agreed in DPIA |
| Data protection | DPIA written with the hospital's IG lead before installation. ORbserve expected to act as data processor. ICO registration. | Before pilot |
| Clinical safety | Clinical safety case (DCB0129) with a Clinical Safety Officer; the hospital completes DCB0160. | In preparation |
| Medical device | Changeover features are operational software. Sterile-field alerts run in observation mode only until an MHRA route is agreed with a clinical partner. | Observation mode |
| NHS DTAC | Digital Technology Assessment Criteria. | Before wider rollout |
| Cyber Essentials / DSPT | Cyber Essentials certification and the Data Security and Protection Toolkit. | Before wider rollout |
Contact: Alannam Akabusi, founder · alannam@orbserve.co.uk · More detail: How the camera protects privacy