Hospital ELV coordination: the cause-and-effect matrix is the contract, not the BOQ

Hospital ELV is the most misunderstood category of engineering deliverable in the Indian building stock. Tendered as a parts list, executed as independent trades, audited as a coordinated system — the gap between procurement and operation is where the failures live. A coordinated hospital ELV stack is not the sum of fire-alarm, nurse-call, CCTV, access-control, BMS and medical-gas-alarm; it is the cause-and-effect lattice that ties them into a single supervisory response, with explicit acknowledgement-delay rules that preserve surgical-anaesthesia workflow and a per-zone audit trail the NABH inspection cycle reads against.

## The matrix is the deliverable, not the panel

The leading silent failure mode in hospital ELV is the absence of a written cause-and-effect matrix. The fire-alarm panel is programmed; the lift-homing relay is wired; the nurse-call PA suppression is configured; the access-control evacuation mode is set. None of it is in a single document that ties the inputs to the outputs with explicit per-zone rules. When we audit inherited hospital deployments, we extract the as-is matrix from the panel programming, walk it through with the operations team, and produce a written register that becomes the spec for any subsequent change. Without that register, the operational response lives in someone's head and disappears the day they leave.

## Acknowledgement-delay tiers preserve surgical-anaesthesia workflow

A naïve fire-alarm matrix closes every AHU damper immediately on a fire trigger. In a hospital, that includes the OT-zone dampers — which compromises anaesthesia delivery for any surgery in progress. The correct architecture tiers the cause-and-effect by acknowledgement-delay. Tier-1 (no delay): sounders, strobes, PA voice-evac, lift homing for non-occupied lifts. Tier-2 (5 s ack-delay): magnetic door-holder release on egress paths, lift homing for occupied lifts. Tier-3 (operator-acknowledgement): OT-zone AHU damper response, with clinical-engineering acknowledgement window before damper closure. The tiering is written into the matrix, witnessed at commissioning, and signed by both the fire-safety officer and the clinical-engineering lead.

## Nurse-call escalation is an IP-PBX hunt-group problem, not a panel problem

Code-blue escalation from a bedside pull, a bath-pull or a button press has to reach the local nurse station, the resident on-call mobile and the MICU-board simultaneously, without false-alarm storms during routine bathroom-pull testing. The escalation pattern is implemented on the IP-PBX hunt-group — code-blue events trigger a multi-leg call into the on-call rotation, with caller-ID identifying the bedside source and the IP-CCTV bookmark surfacing the pre-event clip. The matrix gates the escalation; the hunt-group executes it.

## Medical-gas alarm integration is a separate cause class with a separate priority

Oxygen, nitrous oxide, vacuum and medical-air alarms are their own cause class with their own escalation pattern — the matrix routes the alarm to the local nurse station and to the medical-engineering on-call mobile, separately from fire-alarm and code-blue. Cross-routing a medical-gas alarm into the fire-alarm escalation generates false-positive evacuations; cross-routing a fire-alarm into the medical-gas channel delays the clinical response. Each alarm class has its own annunciator, its own escalation hunt-group and its own audit-log entry.

## CCTV bookmark on every cause is the audit trail

Every cause in the matrix triggers a 30-second pre-event CCTV bookmark on the nearest ONVIF cameras — fire-alarm trigger, nurse-call code-blue, medical-gas alarm, access-control evacuation, BMS critical alarm. The bookmark is the incident review's primary evidence; without it, the post-event audit relies on operator memory and timestamp correlation. The bookmark integration sits on the VMS, not on the cameras — every camera class with ONVIF metadata can participate.

## Phase-2 access-control evacuation mode is the egress-path discipline

A fire trigger from any addressable zone releases magnetic door-holders on egress paths and switches the access-control system into evacuation mode (every door overrides to free egress, audit log preserved). The matrix is written so the evacuation mode is gated by the fire-alarm panel's loop event, not by an operator gesture — the operator cannot fail to trigger evacuation, but the door-holders cannot release on a software-only event. The egress-path schedule is witnessed by the AHJ at commissioning, signed off per door class, and re-tested at every quarterly AMC visit.

## BMS event log is the audit-ready timestamp register

Every cause in the matrix writes an entry to the BMS event log — timestamped, audit-ready, indexed by zone. The log is the document the NABH inspection cycle reads against; the matrix-and-log discipline is what separates a hospital that can answer the inspection from one that cannot. Configuration baselines for the BMS log filter and the matrix are exported offline after every firmware refresh, with the recovery procedure rehearsed at each AMC visit.

## Coordination challenges that survive into commissioning

Even with a written matrix, the seam-level coordination is where the deployment fails. The fire-alarm panel programmes one cause-effect; the BMS programmes another; the access-control programmes a third. The matrix is the single source of truth — every panel's programming is verified against the matrix at commissioning, witnessed by the integrator and the operations team. We hold the matrix as the contract document; the panel programming is supporting evidence. Any panel-programming mismatch is treated as a discrepancy from the matrix, not a clarification of intent.

## Callout — what hospital procurement most miss

**The matrix, not the BOQ, is the operational contract.** Hospital ELV tendered as a parts list produces a parts list; hospital ELV tendered with the matrix as a deliverable produces an operational system. The matrix is the document the clinical-engineering lead is held to during an event, not the BOQ.

## Reference deployment context

Tinsukia Medical College & Hospital runs a 320 input × 184 output cause-and-effect matrix across academic, clinical and admin blocks, with the surgical-anaesthesia override on AHU-1, AHU-2 and AHU-7 captured explicitly. The matrix is signed by the hospital's clinical-engineering lead, the fire-safety officer and the AHJ; re-tested per zone at every quarterly AMC visit; the test record is in the AMC log.

## References

1. NBC 2016, Volume 2 — fire and life-safety provisions for hospital occupancy.

2. IS 2189 — code of practice for installation of automatic fire-detection and alarm systems.

3. NABH 5th edition — hospital accreditation standards on environmental safety and infection control.

4. NFPA 99 — health care facilities code (international cross-reference).