Philips MX400 - Triggering Events Manually; Running a Car Seat Assessment Record; The Events Database

26 Event Surveillance
339
4
Set the trigger for each measurement. Select each trigger name and select either an alarm trigger or
a user-defined trigger from the pop-up trigger list. If you select a user-defined trigger, set the
required threshold level and delay time. If a deviation trigger is configured, set the deviation and
duration.
5 Select Confirm to confirm your changes.
Triggering Events Manually
To manually trigger an event, select the SmartKey Manual Event and (for Advanced Event
Surveillance) select the group in which the event will be triggered.
For manually-triggered events, patient information for the time leading up to the trigger moment is
stored using the settings of the assigned event group.
Running a Car Seat Assessment Record
In the NER group you can run a Car Seat Assessment Record (CAR). This is a special period of event
surveillance using the current setup of the NER group.
To start a CAR period:
1 Select the Start CAR pop-up key or SmartKey.
2 Select the required time period for the assessment.
3 Select Confirm to start the CAR.
If the NER group was not active it will be activated automatically.
During the CAR period an SpO
2
histogram is also generated with 1 second samples. For general
information about the presentation of data in a histogram, see “Viewing Histogram Trends” on
page 314. The CAR SpO
2
histogram is unique: it can only be accessed from the events function. It is
generated from the beginning of the CAR period (contrary to the non-SpO
2
histograms which are
generated from trended data retrospectively at the end of a time period). Settings are fixed for this
histogram and cannot be changed when viewing it.
The Events Database
The maximum number of events that can be stored in the event database depends on the database
configuration and the level of event surveillance used. The event database is set up in the monitor's
Configuration Mode. Events are stored in the monitor's event database for the configured lifetime,
either 8 hours or 24 hours. Deleted events cannot be retrieved. Events are automatically deleted when:
• their configured lifetime is over
• the storage capacity of the database is exceeded (storing a further event deletes the oldest event in
the memory)
• a patient is discharged.
As the event database is cleared when you discharge a patient, you should ensure that you have
documented any events you require for the patient records before you confirm the discharge.