Setting Up Logging Configurations

You can control application logging in i.s.h.med by creating and activating a Logging Profile.

Logging profiles control the attributes of the logs which are created from the messages about activities of a user or the system, relating to an object (e.g. create clinical order).

If you have defined and activate several Logging Configurations, you can comprise these configurations to form a logging profile.

Note Note

You can define cross-institutional logs. To do this you must group logging configurations of various institutions to make one logging profile.

The logging configuration controls the attributes of the messages, the logging profile controls the attributes of the log.

End of the note.

Each logging profiles results in logs which you can view using special evaluation functions. The system creates the logs depending on the log type, either per user or per patient.

See Evaluate Logged Messages

Patient-Related Log Type

The system creates a log for each patient. If a user executes an activity, e.g. on a clinical order or a document, the system checks whether there is already an active and valid log for this patient and proceeds as follows:

If an active valid log already exists, the system writes the message in this log.
If no active valid log exists, the system creates a new log for this patient, with the properties defined in the logging profile. The system writes the message in this newly created log.

You use the patient-related log type particularly if you wish to receive an evaluation, from the patient's point of view, to see, which users have accessed the documents, clinical orders, etc. of this patient. This setting is particularly suitable for converting a log for the Display function.

User-Related Log Type

The system creates a log for each user. If a user executes an activity, e.g. on a clinical order or a document, the system checks whether there is already a log for this user which is active and valid.

If an active valid log already exists, the system writes the new message in this log.
If no active valid log exists, the system creates a new log for this user, with the properties defined in the logging profile. The system writes the message in this newly created log.

Use the user-related log particularly if you wish to receive an evaluation from the user's point of view, concerning which documents, clinical orders, etc. a specific user has viewed, modified, etc. This setting is particularly suitable if a specific user or a group of users is to be monitored (for example following the allocation of a temporary treatment contract).

Caution Caution

You must assign a log type to each logging profile. You cannot subsequently change this data.

End of the caution.

Prerequisites

You have executed the basic settings for application logging and created logging configurations.

Procedure

In the implementation guide select Industry-Specific Component Clinical System Cross-Application Settings Event Management Application Logging Configure Application Logging .
You access the Change Logging Definitions screen (transaction N1ALDEF) while editing the logging profiles.

If you have already previously edited logging configurations in the Change Logging Definitions screen, select the Logging Profiles pushbutton at the upper end of the navigation area, to access the function for editing profiles.
In the navigation area, select a log type (e.g. patient-related log) or one of the profile groups created below.

Note
Profile groups are used to clearly structure the profiles of a log type in the navigational area in the setup function for application logging (Change Logging Definition screen).

End of the note.

You can also create a new profile group for a log type by selecting the log type and, in the selection list for Profile (Create Profile), selecting the Create Group function. You access the Create Profile Group dialog box. Enter the name of the new profile group.
Choose Profile (Create Profile).
You access the Create Profile dialog box.

The system presets the log type using the selection made in the navigation area.
Enter the necessary data, e.g. profile ID and choose (Continue).
You must provide logging profiles with a profile ID in order to be able to differentiate between them. The profile name further specifies the logging profile.
On the General tab page in the work area, enter the necessary data for the new logging profile, for example, the validity of the profile.
On this tab page you can also determine when created logs expire. To do this you enter an expiry date when creating a log. You can therefore automatically complete and periodically archive or delete logs once this time period has expired. Enter a relative time interval in days, weeks, months, or years after creating a log.

You can also activate a logging profile, restricted to specific users/roles or a specific group of users/roles.

Note
Note that events which are triggered by system actions (in the background) are also logged. If you do not wish to log these events, you must exclude the users with which the background process is started, from the logging profile.

End of the note.
On the Logging Configurations tab page in the work area, assign the previously defined logging configurations to the logging profile.
Choose (Add Configurations), to assign configurations to the profile. You access the Add Configurations dialog box. Select the configuration, and then choose (Continue).

If you wish to remove an assigned configuration from the profile, choose (Remove Configurations).
Choose (Check) or save the profile.
Select (Activate Profile), to activate the profile and to use it for application logging.

Example

For a display logging you create a logging configuration, in which the display events are activated, for each logging application. You collate these different configurations in a logging profile, which you name, for example, “Display Log”.