Geye / Industry playbookReception flow
Overlapping appointments put pressure on a shared waiting area.
Geye / Industry playbook
Hospital
Review movement through waiting areas, entrances, and restricted zones with privacy-aware event design.
Planning guidance, not a claim of installed capabilities or customer results. Validate scope and feasibility before deployment.
Industry overview
Hospital facilities teams coordinate reception, public corridors, and controlled entrances across changing shifts. Visual operations signals are separate from clinical assessment and must not expose patient care.
Clear corridors
A parked trolley and a moving stretcher require different responses.
Entrance review
Shift handovers can explain activity outside normal visiting hours.
Use cases
01
Reception flow
- Context
- Overlapping appointments put pressure on a shared waiting area.
- Human action
- Review reception congestion for service coordination.
- Intended outcome
- A reception coordination note, separate from clinical triage.
02
Clear corridors
- Context
- A parked trolley and a moving stretcher require different responses.
- Human action
- Flag obstruction candidates in agreed public corridors.
- Intended outcome
- An obstruction checked by facilities before escalation.
03
Entrance review
- Context
- Shift handovers can explain activity outside normal visiting hours.
- Human action
- Review after-hours activity at staff-only entrances.
- Intended outcome
- An access observation reconciled with the duty schedule.
AI vision capabilities
Read the scene, retain the context
Assess occupancy bands, corridor obstruction duration, and entry-zone events. Wheelchairs, stretchers, and accompanying families require representative validation; no symptom or diagnosis inference is proposed.
Evidence contract
Keep zone, source timestamp, and view availability together. A stale frame must not become a current event.
A person owns the decision
A reception coordination note, separate from clinical triage.
Define acceptanceProposed capabilities must be tested against representative inputs. Unsupported or low-confidence results belong in a review queue, not an automatic decision.
Real-world scenario
Hypothetical, not a client story
Hypothetical: reception congestion rises after several appointments overlap. A facilities coordinator validates the queue and asks reception to adjust guidance, without ranking patients or changing triage.
- 01
Context
Overlapping appointments put pressure on a shared waiting area.
- 02
Review trigger
A candidate observation in the selected zone requires confirmation against current conditions.
- 03
Human response
Review reception congestion for service coordination.
- 04
Intended result
A reception coordination note, separate from clinical triage.
How it works
CCTV
Read an authorized stream from the selected zone. Track source health and timestamps; a missing view is not an empty scene.
AI analysis
Apply validated models and zone rules on assessed compute. Group candidate events and expose uncertainty instead of implying certainty.
Reviewed insight
An assigned person checks evidence, records the outcome, and follows the existing operational procedure. Rejected signals feed back into evaluation.
Business and operational value
Measure event review time, false alerts, and coverage across shifts.
Evidence quality
Accepted observations / reviewed observations. Count missed cases separately against the manual reference.
Target: agree before pilotReview effort
Record minutes per reviewed item, including rework and escalations. Compare the same task with the manual baseline.
Target: agree before pilotSafe failure
Record whether stale inputs, denied access, and unavailable sources stop or visibly degrade the workflow.
Target: agree before pilotEstablish a manual baseline, agree acceptance thresholds with the operational owner, and compare review effort as well as accuracy. Any benefit must be measured in the pilot; no savings or ROI are promised here.
Deployment plan
Start in a non-clinical public waiting area with clinical governance and facilities approval. Test visiting hours and shift changes, assign a reception reviewer, and document manual operation during outages.
- Scope: name the owner, permitted inputs, reviewers, and acceptance criteria.
- Prepare: assess edge, on-premises, or approved hybrid compute, storage, power, and network capacity with representative streams.
- Validate: compare with human-labelled samples, exercise denied access and outages, and document rejected results.
- Decide: approve a limited rollout only after review; keep a rollback owner and re-evaluate when inputs change.
Existing CCTV and infrastructure
Review camera framing for accidental views of consultations, readable records, and patient beds. Validate network separation from clinical systems and confirm recorder access with hospital IT.
| Check | Required evidence |
|---|---|
| Source access | Authorized stream, codec, resolution, frame rate, recorder connection limit. |
| Scene quality | Day, night, occlusion, and missing-frame samples from the selected zone. |
| Compute & recovery | Concurrent decoding benchmark, storage budget, clock sync, outage fallback. |
Existing CCTV may be reusable after compatibility assessment, not by default. Inventory codecs, resolution, frame rate, authorized stream protocols, recorder limits, time synchronization, and sample quality. Benchmark concurrent decoding and models before sizing hardware.
Integration planning
01
Approved source
02
Scoped processing
03
Human approval
04
Controlled export
Example: route reviewed facilities events to an approved service desk. Keep patient identifiers and medical records out of the payload; clinical-system integration is not assumed.
These are example integration plans, not live connectors. Confirm schemas, least-privilege credentials, delivery acknowledgements, retry limits, and duplicate handling in a sandbox before enabling data exchange.
Security and privacy
Exclude treatment rooms and intimate care areas. Limit retention and reviewer roles around patient dignity; alerts must never diagnose, prioritize treatment, or replace clinical judgement.
Least privilege
Approve reviewer roles and test a denied-access case before launch.
Data lifecycle
Set retention, deletion ownership, and encryption for stored and transmitted evidence.
Accountable operations
Log access and decisions; rehearse incident escalation and rollback.
Before launch, approve purpose and lawful access, role-based permissions, encryption configuration, retention and deletion rules, audit logging, and incident ownership. Verify these controls in the chosen environment; this page does not claim compliance certification.
Hypothetical pilot example
HYPOTHETICAL PILOT
One bounded question. Evidence before expansion.
Hypothetical pilot: reception staff annotate congestion windows across two different shifts. Compare missed congestion and nuisance alerts, then have facilities and privacy reviewers decide whether the view is acceptable.
A proposed evaluation exercise, not a deployed case study. There are no named clients, claimed results, or implied endorsements.
Frequently asked questions
Can it diagnose patient distress?
No. This scope supports facilities review, not diagnosis, triage, or clinical monitoring.
Are treatment rooms required?
No. Exclude clinical and intimate spaces from this operational pilot.
Who receives congestion alerts?
An assigned reception or facilities reviewer, with an agreed escalation path and no patient details.
Plan your next step
Bring an authorized camera inventory, representative scenes, and one operational question. Prepare a planning brief, then validate sizing assumptions with a scoped pilot.