please edit the following draft protocol for infant security system. kindly make sure that only formal english is used. Thank you.

2. PROCESS/PATIENT FLOW – CURRENT PROCEDURE/PROCESS

The units are locked to the general public and main doors need to be unlocked for visitors to be allowed in. There is a strong security presence throughout the facility, and staff can call them if there is an issue with a breach.

The units have quiet hours in the afternoon so moms can rest. Units also have visiting hours

Babies are brought to the nursery by staff when moms request them (so moms don’t ever move the babies back and forth)

Babies are sent to the nursery during visiting hours, so decreased chance of visitors interacting with and possibly absconding with patients.

TBD items:

-do they want cut band lockdown?

-Keypad to allow egress in a cut band lockdown? (we highly recommend this as an option if possible)

-will they do transfers or give patients new tags when they get to their new unit?

-can they do AD?

Also: client added this to the alarm option sheet they returned to me and I don’t know what it means

Special note:

To incorporate these adjustments of downtime to IP-CODE-106 CODE BROWN.

5. ACCESS SETTINGS

The purpose of Access Settings is to set unique configurations for each type of Security Controller. Our goal is to create a customized environment for your campus while maintaining an operation that is predictable enough to ensure clinicians and other staff members become comfortable with their expected results.

1. Key Terms in this Section

Security Solutions offers two general alarm codes: Regular and Latching.

• Regular describes when an event naturally completes without a user interaction. An example event is when a Tag/Patient leaves the field at a protected exit and the exit where the event occurred returns to its normal state.
• Latching describes when an event requires physical intervention to close the event. Popup Notifications on a workstation require a user with the appropriate authorization to log in with a User Name and Password to clear the event. In Latching mode, the Security Controller requires some type of intervention to clear the local alarm and reset the door or elevator. An example of an intervention is entering a PIN code into a bypass keypad.
• Admitted Patient Tag Use Case on TIF

We want controllers to react this way when an admitted tag enters the protected field.

Patient Risk Level	Should Doors/Elevators Lock?	Should Doors/Elevators Buzz?
1	YES (if in scope)	YES at the keypad or door controller if doing badge integration
2
Additional Notes Need door to make noise, but can’t be too loud

3. Undefined Patient Tag Use Case on TIF

We want controllers to react this way when a non-admitted tag (undefined) enters a protected field.

Tag Type	Should Doors/Elevators Lock?	Should Doors/Elevators Buzz?
Patient	YES	Yes
Additional Notes Reviewed SecureTag operation, and tag still in “Discharging” status or any part of the band still in place to get alarming and locking with undefined TIF. Remove bands and discard immediately after cutting band and removing pieces from SecureTag.

Additional Notes

Keypads to reset door controller. Security to use keypad to reset controller to badge onto a locked unit. Clinical staff to use code to reset controller as needed.

1. Workstations –

MUST BE DEDICATED COMPUTERS – NO OTHER APPLICATIONS OR SCREENSAVERS

Controller Offline	Enable (15 min. default timer)	Latching With a message appearing “please call security at 9999 AND notify your director and call IT to report”
Server Offline	Enable	Latching With a message appearing “please call security at 9999 AND notify your director and call IT to report”
Workstation Offline	Enable	Latching With a message appearing “please call security at 9999 AND notify your director and call IT to report”

8. TRANSPORT/TRANSFER PATHS

At our hospital, we take a patient out of a protected unit for a procedure (in an unprotected area) and then return them back to the same protected unit when completed.

1. Transport Paths

We DO transport patients for a round trip from the units below and back to sending unit.

9. ADMIN

Admins generally include IT and Security personnel. They are responsible for overseeing and reporting hardware alerts. Admins should have their own Security Solutions workstation application. Must attend Admin training.