Smart Locks for Hospitals and Ward Blocks: Credential Model that Survives 24/7 Uptime Expectations
Hospitals credential model is what this piece covers for this kind of building. A hospital never closes. The same ward entrance is used at three in the morning by a porter, a night-shift nurse, a relative carrying a pass, and an engineer sent to a plant room. That single operating fact changes what a credential has to be, because a credential that only works when a server answers is not a credential at night — it is a queue at the door.
Direct answer. The one-line answer — hospitals credential model is the working record for hospitals credential model. hospitals credential model is worthless until the decision record is attached to it as evidence. A hospitals credential model is a building-level specification record. Door classes come in order. hospitals credential model is the first one closed for hospitals credential model.
This handbook sets out the hospitals credential model as clauses. A clause here is a decision that has already been taken, written so the estates team, the security office and a clinical lead can each check their part of it without asking a supplier to interpret the requirement. The model fixes which credentials exist, who may issue them, how long they stay valid, what a door does when the network is down, and what happens when a person leaves the organisation.
The order of work is deliberate. The credential model is written before doors are counted, because it decides how many readers must be networked and which doors can run alone, and the door survey then confirms that the leaf, the frame and the lock body will carry the reader where the model assumes. That survey work is set out in Smart Locks for Hospitals and Ward Blocks: Door Survey and Fit Reality.
Clause 1 — Settle the credential model before the door schedule
The credential model is a decision document that precedes hardware. It fixes the credential classes, the issuing authority for each class, the validity window applied to each, the behaviour of a reader that cannot reach the server, and the route by which a credential is withdrawn. Once those answers exist, the rest of the programme becomes arithmetic: reader count, network topology, the number of doors that can operate standalone, and the manual fallback plan for every door class.
Hospitals are the hardest place to write such a model for, because the building is occupied continuously while the right to be inside changes every few hours. Patients, relatives, agency staff, porters, cleaners, phlebotomists, engineers and a ward clerk may present credentials at one door on the same night. A model written as a list of job titles will be wrong within a shift. A model written as a list of places, with people attached to those places, can be checked by anyone who works there. The buyer-side checklist sits in Fingerprint Smart Locks for Commercial Property Owners. The range this procurement eventually buys from is the smart door locks.
The model also has to be written by the hospital and not by the supplier, because only the hospital knows which doors it would rather leave open during a fault and which it would rather hold closed. That decision is a risk decision, and it belongs with the estates lead, the security manager and the authority that owns life safety on the site.
Clause 2 — The terms the schedule has to define
Six words do most of the work in a credential schedule. If one word is used for two ideas, the supplier will adopt the more convenient meaning and the estates team will discover the difference at handover rather than at design.
- Credential class — the purpose a credential serves, independent of the person carrying it.
- Zone — a named set of doors that share an access rule.
- Credential validity window — the longest period a reader may accept a cached credential it has not re-checked against the server.
- Cached right — what the reader currently believes about a credential while it is offline.
- Master credential — the credential held under custody for privileged and emergency entry.
- Degraded state — the defined behaviour of a door when validation, power or the credential database is unavailable.
Write these into the schedule as definitions, not as headings in a supplier brochure. The difference sounds academic until a night-shift porter asks whether the badge in their hand opens the ward corridor or the plant room, and nobody in the building can answer.
Clause 3 — Credential classes and the custody chain
The model begins with classes rather than doors, because doors change and classes describe intent. Each class has exactly one issuing authority and one removal trigger. Where a class has two of each, the model has two owners and it will drift.
| Credential class | Who holds it | Doors it opens | Issuing authority | Removed when |
|---|---|---|---|---|
| Staff zone badge | Clinical, administrative and estates staff | The zones listed on the badge | Workforce credentialing office | Role change, rotation or leaving |
| Ward entry visitor pass | Relatives, companions and visitors | Ward entrance and any agreed day-room door | Security desk | End of visit, or the set time window |
| Escorted service credential | Contractors and engineers | The named service door and the corridors needed to reach it | Estates, with the sponsor's approval | Task order or permit closes |
| Restricted clinical credential | Pharmacy, controlled store and records staff | Named restricted doors | Two named authorisers | Assignment or registration changes |
| Engineering credential | Plant, laundry and estates technicians | Engineering, plant and laundry doors | Estates engineering manager | Leaves the trade team |
| Master credential | Security office | A defined set of doors under custody | Security manager | Loss, transfer or scheduled review |
| Records credential | Records and audit staff | Records room and reading room | Records manager | Transfers or leaves |
Classes are not ranks. A contractor carrying a service credential is not a lesser member of staff; that credential simply opens a smaller number of doors and for a bounded period. The important discipline is that no class exists without a named holder, a stated validity window and a removal trigger, because an unowned class is the one that will still be working in a ward after the person who authorised it has left.
Clause 4 — Zones attach rights to places, not to job titles
A zone is a named set of doors. Hospital badge zone access works when the badge carries a zone list rather than a department name, because departments reorganise and buildings do not. The six zones below cover most hospital estates, and each one can be granted, withheld or withdrawn without reprinting a single card.
| Zone | Doors in the zone | Who may be granted | Record behaviour |
|---|---|---|---|
| Public concourse and main entrance | Main doors and reception | Anyone entering the building | Counted by class |
| Ward circulation | Ward entrance, day room, ward corridor | Staff on duty in that ward, plus escorts | Recorded by class |
| Restricted clinical | Pharmacy, controlled store, treatment rooms | Named clinical roles with two approvals | Recorded by class and reviewed |
| Staff-only corridor | Back-of-house corridors and staff stairs | Staff with a duty in that wing | Recorded by class |
| Engineering and plant | Plant rooms, laundry and medical gas spaces | Estates technicians and permitted contractors | Recorded by class |
| Service and delivery entrance | Goods door and delivery bay | Suppliers with a booked slot | Recorded by class |
Under this rule a porter who transfers from a ward to the laundry gains a zone in the new area and loses the ward zone in the same action, because the grant follows the task rather than the card. That single decision removes most of the paperwork that otherwise makes a transfer slow, and it makes the revocation step in Clause 7 an ordinary routine instead of an exception discovered during an audit.
Clause 5 — Issuing authority and the record that follows
Every class names one issuing authority, and that authority leaves a record when it issues. For restricted clinical classes the authority is two named people acting together, so that a single person cannot grant access to a pharmacy or a controlled store and act as the only witness to it. For visitor passes the authority is the security desk, which already holds the identity check function. For agency and temporary staff, the sponsoring ward or department confirms the start and end dates, and the credential is issued from the office rather than at the door.
Nothing is issued without a named holder, an expiry, and a record of who issued it. Those three fields are what make the later clauses possible: without an expiry there is no validity window, and without a holder there is nothing to revoke.
The request path should be the path the hospital already runs for identity, payroll and mandatory training onboarding. A parallel access-request form creates two versions of the truth about who is on site tonight, and the version that matters at three in the morning is rarely the one the estates team holds. The wider contractor population, including suppliers who never set foot in a ward, is handled in Contractor and Third-Party Access for Hospitals and Ward Blocks.
Clause 6 — Validity windows and offline door validation
This is the clause that decides whether the model survives a night shift. Every networked reader keeps a cached copy of the credential record and the zone map. The credential validity window is the longest period during which a reader may accept a cached credential it has not been able to re-check against the server. Set the window per class, write it into the schedule as a number of hours, and set the same number in the reader configuration.
The window is what makes offline door validation defensible, because it converts an open-ended outage into a bounded and observable one. Inside the window the reader acts on the cached right and writes an event. Outside the window the reader refuses, unless an authorised person has placed that door in an approved degraded state. The clock inside each reader is the reference for the window, so clock state is monitored and reported like any other fault; a reader that cannot trust its own clock cannot be trusted with a window.
stateDiagram-v2
[*] --> Issued
Issued --> Active
Active --> Suspended
Suspended --> Active
Active --> Revoked
Suspended --> Revoked
Active --> Expired
Expired --> [*]
Revoked --> [*]
Suspension and cancellation are different states and the distinction matters on a night shift. A badge handed in by mistake and returned the same shift can be suspended and reinstated without being reissued. A credential that has expired, or that has been revoked, does not come back by reinstatement — it is destroyed or returned to the holder.
Four rules keep the window honest in practice: one window per class, shared with the reader configuration; a shorter window for the classes that open restricted doors; no lengthening without a documented, versioned change; and a reader that has not refreshed inside its window reports a fault to the network team rather than to the ward. Denial is an event as well. A credential presented at a door it has no right to open produces a denial record, and denial records are how an over-privileged badge is found before it becomes an incident.
Clause 7 — Revocation at role change
Revocation is the clause estates teams test first in their own heads, because they have all seen a badge keep working after the person has gone. The triggers are ordinary and should be listed in full: leaving the organisation, moving ward or department, an agency assignment ending, a reported lost badge, a disciplinary suspension, a badge found in a lost property tray, and a visitor or escort pass that was never returned.
Define revocation in three steps. The credential is withdrawn at the issuing record. It is removed from the cached set held by the readers. It is then refused at the door and recorded as a denial event. The interval between the first step and the third is the revocation latency, and it should appear in the schedule as a stated figure that the operator has chosen and tested, because a latency nobody has written down is a latency nobody has agreed to. The mechanics of clearing a credential set at the end of a service life are covered separately in End-of-life and Re-Keying Planning for Hospitals and Ward Blocks.
Run the withdrawal job against shift patterns rather than against midnight. A single nightly job is comfortable on paper and wrong in practice, because the badge of someone who finished a shift in the morning still opens a ward corridor that evening. Schedule the job so that the gap between the last shift a person works and the moment their rights disappear is as short as the operation allows.
Clause 8 — Master credential custody
The hospital holds a master credential, and the credential model treats it as a controlled object rather than as a convenient feature. One named holder at a time, stored in a cabinet in the security office, issued against a signed log that records the person, the door and the reason, and returned at the end of the shift or when the holder leaves the site. Two people are present when it is used at a restricted clinical door. There are no copies on a keyring, in a drawer, or in the pocket of a coat left in a ward office.
The master credential is an operational tool, not a system of record and not a substitute for the manual route. Every use generates an event that the security manager reviews, and a pattern of use at unusual hours is either a training problem or an incident depending on what the log says about it. The parallel decision about mechanical cylinders, override keys and how many of them exist is a different exercise, and it is set out in Smart Lock Key Control and Master Key Decisions for Hospitals and Ward Blocks. Out-of-hours entry, including the arrangements that apply after hours when the master credential is not the route used, is handled in Emergency and Out-of-Hours Access for Hospitals and Ward Blocks.
Clause 9 — The life-safety boundary the credential model
For every door in the schedule, record two things: whether the door sits on an escape route as drawn in the operator's own fire risk assessment, and what locking arrangement has been agreed for it. A credential right to open a door never overrides the release behaviour of a door on an escape route, and no credential model may be used to justify holding a door locked against escape. Where a ward entrance releases on alarm or on loss of power, the credential's role is to grant entry from the corridor side; the release is handled by the door's own arrangement and is not something a handset can switch off.
Where a building has ward accommodation above or beside the clinical floors, the two parts of the site are assessed separately. The hospital model applies to the clinical doors, and the residential doors follow their own rules, even when a single corridor joins them and a badge carried by a member of staff opens both.
CONFIRM-WITH-LOCAL-FIRE-AUTHORITY: confirm which escape doors may be held locked, the locking arrangement accepted for each, and who signs that arrangement off before any door is scheduled.
CONFIRM-WITH-LOCAL-BUILDING-AUTHORITY: confirm the door-by-door access-control and locking requirements the local building authority applies to hospital and ward-block doors.
CONFIRM-WITH-LOCAL-HEALTH-AND-SAFETY-ADVISER: confirm the ward-level expectations the health-and-safety adviser places on escape routes, night working and lone working in clinical areas.
Clause 10 — Visitors, escorts and the contractor population
The ward entrance is the most heavily used door in the building and the one most likely to be given away. A ward entry visitor pass is issued at the security desk after an identity check, carries the name of the visitor and the host, is time-boxed, and is limited to the ward entrance and any agreed day room. It is voided or returned at departure, and it is not passed on. A shared ward code handed to relatives solves the reception desk problem by creating a revocation problem instead, because a shared code cannot be attributed to anyone and cannot be withdrawn from one visitor without withdrawing it from all of them.
Contractors are usually the largest uncontrolled population in the building. A contractor credential is tied to a task order or a permit, carries rights for the service door and the corridors needed to reach it, and names an escort where the task requires one. Engineering and plant access is granted by the estates team, which already knows which work is booked and for how long. If the task order closes, the credential closes with it, and nothing about that depends on a supplier remembering.
Clause 11 — What the credential model records
And what it.
| Event | What the record holds | Why it matters operationally |
|---|---|---|
| Access granted | Door, credential class, holder reference, time | Shows who was given access to which zone |
| Access denied | Door, class, holder reference, time, reason code | Finds over-privileged and stale credentials |
| Master credential use | Door, holder, reason, staff present | Keeps the privileged route accountable |
| Manual or forced opening | Door, person, reason | Separates a planned override from a fault |
| Door held open | Door, start, duration | Finds propped doors on ward routes |
| Reader offline | Door, start and end | Bounds the period of degraded validation |
| Controller change | What changed, who authorised it | Keeps local behaviour changes traceable |
Keep the record at the level of the door and the credential rather than the person and their purpose. Record retention periods and the lawful basis for holding entry records are not access-control decisions and are handled in Audit Trail Requirements for Hospitals and Ward Blocks: What Records Matter and Data Retention and Privacy for Smart Locks in Hospitals and Ward Blocks.
CONFIRM-WITH-LOCAL-DATA-PROTECTION-REVIEWER: confirm the lawful basis, retention period and access controls for entry records that identify staff and visitors before the record set is written into the schedule.
CONFIRM-WITH-LOCAL-LICENSING-AUTHORITY: confirm the access-control expectations the local licensing authority applies to the pharmacy, controlled stores and medicine records areas.
Clause 12 — Degraded states and the fault that arrives
Every hospital door eventually meets one of four conditions: the network is down, the credential database is unreachable, the reader has lost power, or the lock on the leaf has lost power. The credential model states the behaviour for each condition, for each door class, before the fault arrives rather than during it.
| Condition | Door behaviour | Operator action | Return to normal |
|---|---|---|---|
| Network unreachable, cached right inside the window | Opens on the cached right | Network team investigates; no ward action | Automatic once the network returns |
| Network unreachable, window expired | Refuses, or releases if the door is set to release on fault | Ward uses the manual route named in the schedule | Local authorised override, logged |
| Reader without power | Door behaves as its own arrangement states | Facilities replace the reader or use the manual route | Reader replaced and re-registered |
| Lock battery depleted | Door behaves as the stated fail arrangement | Estates changes the cells and logs the event | Re-tested and recorded |
| Controller restart | Door holds its last known state until rights reload | Security checks the door list against the schedule | Zone map and class list re-pushed |
| Escape-route door during any fault | Release behaviour is unchanged by the credential system | Ward follows the fire procedure | Authority-approved behaviour restored |
Two philosophies exist — release on fault, and hold closed on fault — and the choice belongs to each door, with the authority that owns the risk, rather than to the site as a whole. Where a pharmacy holds closed during a fault, the manual route and the custody described in Clause 8 become the primary path for the duration, and the schedule has to say so plainly.
flowchart TD
A[Credential presented at the reader] --> B{Reader holds a cached right for it}
B -->|yes| C[Apply the cached zone rule]
C --> D[Grant and write an access event]
B -->|no| E[Send an online check]
E --> F{Server answers within the door timeout}
F -->|yes| G[Apply the zone rule from the server]
G --> D
F -->|no| H[Deny and write a fault event]
The choice between standalone and networked doors at each entrance is set out in Choosing Between Standalone and Networked Smart Locks for Hospitals and Ward Blocks, and the diagnosis of a specific door that has stopped behaving is covered in Smart Lock Failure Triage for Hospitals and Ward Blocks.
Clause 13 — Change control when a ward opens, moves or closes
A hospital's door map is never finished. A ward opens, a department relocates to the other side of the site, a wing closes for refurbishment, a door is temporarily removed to move equipment. The credential model is therefore versioned, and the version number is quoted in every instruction given to a supplier: the zone map version, the credential class list version, the validity windows, and the list of readers that have taken each version. A reader still running an older map is a known state that the network team can see, rather than a surprise that a ward discovers at a door.
The closure path deserves as much attention as the opening path. When a ward closes, its zone rights are withdrawn as one action rather than badge by badge, the shared credentials that served it are physically checked, and the returned badges are reconciled against the class list. Leaving a single staff badge live on a closed wing is the kind of loose end that surfaces months later in an audit. The sequencing of these changes across a portfolio is treated in Rollout Sequencing for a Hospitals and Ward Blocks Smart Lock Programme.
Clause 14 — The evidence to demand from a supplier
Ask for evidence in the same shape as the clauses, so that answers can be checked against the schedule rather than admired. The questions worth putting in writing are these: which credential classes the reader holds and which are held elsewhere; how the validity window is configured and who may change it; what the door does when the server is unreachable and the cached copy is stale; how quickly a revocation reaches the door and how that interval is measured; what event data is stored on the reader, on the controller and off site; whether an authorised operator can change a door's behaviour locally and whether that change is logged; what the manual route is for each door class; and what happens to the credential set and the records if a supplier's platform is withdrawn.
Every answer should carry a page reference in the supplier's own documentation, and every specification in it should be checked against the dated product page for the specific SKU rather than against a family brochure. Add one question that catches most estates teams out: how does the system behave in a ward that has been isolated from the rest of the site during a network cut, and what does a reader do for the length of that isolation. The fuller question set sits in Questions to Ask a Supplier Before Choosing Locks for Hospitals and Ward Blocks, the written form belongs in the RFQ Template for Smart Locks for Hospitals and Ward Blocks, and the scoring of the answers in Smart Lock Vendor Selection Criteria for Hospitals and Ward Blocks.
It is worth pairing this with smart lock commissioning project planning. That is the same question hospitals credential model has to answer here.
Clause 15 — Acceptance tests a live ward can run
Before handover, test the model in an occupied ward, with staff present, and at a time that includes a shift change. Pull the network from one ward for a defined period and observe the doors. Present a badge that carries rights to another zone and confirm that the denial is refused and recorded. Revoke a leaver's badge during a shift and confirm it no longer opens the door. Remove a reader's power and confirm the agreed behaviour. Use the master credential and confirm the issue log and the event record match. Compare the clock on a sample of readers against a reference. Hand over a ward running a new zone map and confirm the readers take it.
The same question is worked through in more detail in the smart lock motor selection. That is the same question hospitals credential model has to answer here.Record each result, who ran the test and what was observed. A signed test sheet is what stops the model from quietly drifting back into a badge list that nobody has read since installation day, and it is the artefact a later audit will ask for.
Closing — put the schedule in front of the people who work it
A hospitals credential model earns its keep on the night it is tested rather than the morning it is signed. Send the door schedule, the zone map, the class table and the window figures with your request for a quote, and they will be mapped to reader and lock options for the door types you actually have, with each specification confirmed on the dated product page for the specific SKU and the egress, licensing and privacy questions carried to the authorities that decide them. Start with a request for a quote.

