A hospital is open to the public by design, which makes blanket monitoring both impractical and wrong. The security problem is concentrated in specific rooms — pharmacy, records, plant, stores — and in the hours when corridors are empty.
Entrances and corridors are open to anyone. The controlled space is a small subset, and that is where configuration should go.
Service corridors, plant rooms and stores are often worked single-handed outside core hours.
Patient areas carry obligations that make a general-purpose analytics rollout inappropriate.
Which of these apply to you, and which cameras can carry them, is what the site survey establishes before anything is proposed.
A badge opens pharmacy, records or a store outside the agreed window.
The camera at that door captures the frame at the read.
Whether the person matches the credential on record.
Acknowledged, or escalated with the clip retained for the audit.
A person detected inside a marked area during hours it should be empty.
The detection frame with the area drawn on it.
Engineer on a call-out, or unexplained.
Alert to the duty security lead with the frame.
A person detected on the floor where nobody may pass for some time.
The frame and the clip around it, with the location.
Raised immediately rather than found on the next round.
Alert to the nominated responders. Supplementary to your clinical and emergency procedures, never a replacement for them.
A controlled door stays open past its timer.
The doorway view for the open period.
A delivery, or a door defeated.
Logged with footage for the controlled-drugs or stock audit.
Areas are drawn deliberately narrowly. Patient-facing space is left out of configuration unless you have a specific, lawful reason and have approved it.
The appliance runs on your own network; continuous video does not leave the building.
Door events read from your existing system during onboarding, with no control over the doors themselves.
How long evidence is kept, and who can see it, follows your own information-governance policy.
Video analytics here supplement clinical, emergency and certified life-safety systems. They do not replace them, and nothing on this page should be read as a clinical or emergency-response capability.
Capabilities are selected per site during the survey. Nothing is on by default, and several depend on camera placement and lighting — which is what the survey establishes.
Identify people, vehicles, objects and security events as they happen.
Add identity, context, movement and event intelligence to live video.
Trigger alerts, sirens, speakers, lights, guard workflows and evidence when action matters.
Camera streams, recording, playback, AI events, evidence clips, alerts, reports, users and roles and camera health — centralised in one appliance inside your premises. Faces, clips and reports stay on site.
Camera count, retention and storage are specified per appliance configuration and confirmed during the assessment.
We do not publish improvement percentages, because none have been measured across a fleet and yours would not match them anyway. What a bounded proof of concept gives you is your own numbers, on your own footage:
Not in any configuration we would recommend or build. The useful scope is controlled rooms and service areas. Patient-facing space stays out of it unless you have a specific lawful basis, documented and approved on your side first.
On an appliance on your own network, with retention you set. The data flow is written down during the assessment so your information-governance review has something concrete to approve.
No. It is a security event that tells a responder someone appears to be on the floor in a particular place. It supplements your clinical and emergency procedures and is not a medical device.
Yes, and that is usually the right start. A small number of controlled doors, proven on your own footage, tells you more than a site-wide rollout.
See how PARVEK supports this workflow.
See how PARVEK supports this workflow.
See how PARVEK supports this workflow.
Access and perimeter events across halls, cages and the site boundary, each with the footage that explains it.
Perimeter, restricted zones, yard movement and shift-change activity on a working plant.
Unmanned compounds and remote sites, analysed at the edge where the link is thin or intermittent.
AI surveillance and analytics are technology-assisted and do not guarantee prevention or detection of every security incident or 100% accuracy.