Using Guardian's Administration Tool (pre 2020)
The administration tool can be used by system administrators to manage system users and annotations. Administrators can also change timed parameters for the Guardian system.
Users
By clicking on the [Users] button and authenticating, the user list tree window is displayed. Guardian organises user access into groups and users shown in a tree layout. The groups created are at the hospitals discretion, but common groups can include ‘Student Midwife’, ‘Midwife’, ‘VMO’, ‘Consultant’, ‘ICT’, etc. By clicking on the ‘+’ symbol to the left of a group, that group is expanded to show the users it contains. Users created in Guardian will be indicated by a user symbol. Users brought across from AD will be indicated by a windows symbol (as shown below). To alter an existing user’s details (non AD only), simply click once on the user’s name in the list and then click on the [Details] button to the right hand side of the window.
If Active Directory (AD) is being utilised to pull the user list across, the groups will have been configured prior to the system going live. Also, an additional [Sync AD Users] button will be present on the user list window that can be clicked on at any time to synchronise the user list in Guardian with that of the hospital AD. This includes pulling new users across as well as activating and de-activating existing users. The Guardian system will automatically synchronise users every six hours regardless of whether the synchronisation button is used or not.
Note: Users created directly in Guardian cannot be merged with users pulled across from AD and vice versa. If AD is being utilised, it is important to avoid creating users directly in Guardian. If this is not possible, it is important to maintain users created directly in Guardian manually.
Add Group
To add a new group, click on the [Add Group] button to the right of the window. Enter the name of the group in the ‘Name’ field and ensure the ‘Active’ box is ticked for that list to appear in the Guardian system. If the ‘Active’ box is not ticked, the group will not appear in Guardian and will be shown greyed out with a small red cross in the corner in the user list. Under ‘Group Visibility’, if Guardian covers multiple hospital sites, select the option that is most appropriate for that group.
Search/ Add User
To search for a user, click on the [Search/Add User] button to the right of the user administration window to bring up the search window, type either: Surname; First Name; or ID into the appropriate text fields and then click on the [Search] button to the right of the window. Any users that match the search criteria will be listed. Double click on a user in the list to bring up their details.
To add a new user directly in Guardian, click on the [Add New User] button from the search window. A blank user details window is displayed allowing the users details to be filled out. The users initials are displayed where space is limited (e.g. the chalkboard view on Central Station).
A password provides a backup to the finger print in case this cannot be used (data entered into Guardian by a user is logged as to whether it was authenticated by finger print or password). The user identification type and number allows the user to be uniquely identified where names alone may be duplicated.
Please Note: The user identification number can also be an alphabetical string and will be the login name for any user that has remote surveillance web access.
Staff group is selected from the list created by the hospital and which is most appropriate for the user. Security Access Levels can be either clinical; applicable to clinical staff and allowing data to be entered at the bedside and viewed at the Central Station or from an office, or administrator; allowing access to the administration tool as well as patient merging or session viewing from Archive Review.
Fingerprint enrolment
Guardian employs finger print authentication. This is considered to be more medico legally robust and is also much quicker to use than entering a password. To register a user’s finger print, click on the [Enrol] button to display the fingerprint reader display window. If an existing user requires a different finger print to be enrolled, clicking on the remove button will remove the currently stored finger print data and permit the user to re-enrol using a different finger.
The user should place their finger firmly but gently onto the finger print reader. Once the software has registered the print, the number will count from 4 to 3. The user should remove and then replace their finger. This process continues until the finger has been placed four times onto the reader, at which point a message will be displayed to say the finger print has been registered successfully.
The system records features of a user’s fingerprint that makes it unique from other peoples and does not store an image of the fingerprint itself. It is therefore not possible to recreate a user’s fingerprint from the system. User's passwords are also encrypted within the database.
Please Note: If AD is being utilised, the fingerprint will be the only item that can be set or updated under the user’s details. All other information will be displayed as read only.
Once all the user’s details and finger print have been entered, click on the [Save] button and authenticate to commit the details to the database.
CTG Annotations
Annotations are added to Guardian using the Annotation option in the admin tool. Annotations are a way of recording information in Guardian other than CTG trace data and labour events. Annotations are divided into groups to make selection easier for the user. Annotations are populated across multiple sites if they share the same database.
The annotation screen shows groups and annotations in a tree with groups at the top level and annotations grouped underneath. To add a group, click on the [Add Group] button to the right of the window. A window is display allowing a name for the group to be entered and also if the group is to be active. Un-ticking the ‘Active’ option means that the user will not see that group on the Bedside Monitor.
Once a group has been created, it can be selected and then the [Add Annotation] button clicked to add an annotation to that group. A window is shown allowing a name to be given to the annotation (maximum of 10 characters). This name will be displayed in the black label on the CTG trace if this option is selected. A description can be given to the annotation to provide more information. The description is displayed on touching the label on the CTG trace or by viewing the annotation in the notes. Options allow the annotation to be active and visible to the user in the annotation list on the bedside monitor and also to allow the annotation to be shown on CTG trace.
The order that groups and annotations appear in to the user in the annotations list on the bedside monitor can be set by selecting the required group or annotation in the tree view and clicking on the up or down arrow under the ‘Ordering’ controls to the right of the tree view.
System Parameters
The system parameters option allows certain time out aspects of Guardian to be configured.
WARNING: Do not alter System Parameters without first consulting K2 Medical Systems. Default timeouts are suitable for most clinical scenarios and altering the timeouts may have unintended consequences for system operation.
Automatic monitoring episode timeout
The length of time before a break is recorded in the trace indicated by a vertical red bar displaying the time and date the CTG trace was stopped. Prior to this timeout, a gap is left in the trace.
Automatic discharge timeout
The length of time before a patient is automatically discharged from the bedside monitor if no activity is detected. Activity would be any interaction with the Portal.
Anonymous session alert timeout
If CTG trace is being recorded but no patient has been admitted to the bedside monitor, a blue alert box is displayed requesting a patient is admitted. By clicking ‘Admit Now’ and then clicking ‘Cancel’, this box can be dismissed for a length of time the timeout after which, the alert box will re-appear.
Permit discharge after
If transferring a patient from one Portal to another, CTG trace must have stopped being recorded for the length of the timeout before the transfer is allowed.
Permit event entry up to
The length of time labour events and annotations can be entered into Guardian retrospectively after the actual event occurred.
Alarm mute timeout
If the Infant alarm system is being used, an alarm can be muted for the length of this timeout.
Clear disconnected rooms after
If a Portal becomes disconnected from the network or is turned off, the room will be cleared from the Central Station after this timeout.
Related Articles
Guardian Administration Guide
Guardian's Administration tools can be accessed via the Admin button located at the top right of the Guardian Athena desktop application. Access to each of these options is restricted to users with Administration rights to the system. Clicking on ...Using the Archive
Opening the archive door allows you to search for and review previous cases. It is important to note that this view only shows recorded data and is not a live representation of incoming data. A list of all previous patient records in patient ID order ...Guardian Online
uardian Online is a web based service that provide consultants with view only access to currently monitored patients from their smartphone/ tablet or laptop. Important Patient Safety Notes ALWAYS check with the onsite caregiver that the patient ...Guardian Release Notes
Version 2.050.129.001 (ECO 135-18) New Features / Changes Telstra Interface - A new interface has been developed for Healthscope in Australia. The interface provides access to the Telstra 'Emerging' system at the bedside ER24349 Fingerprint Enrolment ...Guardian Desktop Installation Guide (Central Station and Admin Tool)
Prerequisites A desktop PC running MS Windows 7 or higher Approximately 20 MB of free disk space .NET Framework 4.6.1 pre-installed TCP / IP connectivity to the Guardian Database Server Administrator rights are required as the application writes to ...