Differences

This shows you the differences between two versions of the page.

--- support:user_logging [2022/05/11 15:45] – dpatenaude
+++ support:user_logging [2022/05/24 19:20] (current) – [p.d] dpatenaude
@@ Line 1: / Line 1: @@
 ====== User Logging ======
-This page serves as a high level reference guide to what .decimal logs for user interactions with our software. There are 3 difference sections detailed here:
+This page serves as a high level reference guide to what .decimal logs for user interactions with our software. There are 3 different sections detailed here for the use cases of user logging:
-  - **[[support:user_logging#user_authentication_auth0|User Authentication for Auth0]]:** .decimal uses [[https://auth0.com/|Auth0]] as it's user authentication service. As such Auht0 maintains the user login logs for every user.
+  - **[[support:user_logging#user_authentication_auth0|User Authentication for Auth0]]:** .decimal uses [[https://auth0.com/|Auth0]] as its user authentication service. As such Auht0 maintains the user login logs for every user.
   - **[[support:user_logging#customer_applications|Customer Applications]]:** Customer Applications include .decimal developed applications used by end clinical users that are downloaded and installed on the customer's local computers.
   - **[[support:user_logging#decimal_direct|decimal Direct]]:** Users will interact with the decimal Direct website to perform certain tasks. These interactions are logged for each user. In addition, Customer Applications connect to decimal Direct and some actions of the application may be logged.
@@ Line 15: / Line 15: @@
-.decimal uses [[https://auth0.com/|Auth0]] as it's user authentication service. Auth0 provides users logs including:
+.decimal uses [[https://auth0.com/|Auth0]] as its user authentication service. Auth0 logs user actions including:
   * Successful & Failed Logins
   * Successful Logouts
   * Blocked Account (after too many login attempts)
+Note: These logs are not directly accessible by end users, but may be provided by .decimal staff upon request.
 See below for example logs for common Auth0 events:
@@ Line 81: / Line 83: @@
 ==== p.d ====
-p.d logs the local user activity and records the following information to it's local patient database:
+p.d logs the local user activity and records the following information to its local application database:
 ^ Log Item ^ Description ^
 | username | The username/email of the user performing the action |
 | patientName | An encrypted string  for the patient the log entry applies to |
-| medicalRecordNumber | An encrypted string for the patient the log entry applies to |
+| medicalRecordNumber | An encrypted string for the patient's MRN the log entry applies to |
 | uniquePlanName | An encrypted string for the plan the log entry applies to |
 | planName | An encrypted string for the plan the log entry applies to |
 | logDate | The local date time of the log entry |
-| logEvent | The event that the log entry is for. logEvents include, but are not limited to: \\ -User log in \\ -User log out \\ -Plan Opens \\ -Plan Saves \\ -Plan Closes \\ -Orders placed to decimal Direct \\ -Local and DICOM AE file exports (e.g.: DICOM) \\ -Patient deletion |
+| logEvent | The event that the log entry is for. logEvents include, but are not limited to: \\ -User log in \\ -User log out \\ -Plan Open \\ -Plan Save \\ -Plan Close \\ -Order placed to decimal Direct \\ -Local and DICOM AE file export (e.g.: DICOM) \\ -Patient deletion |
+  * If on p.d 5.4.5 or later these logs may be exported from the About menu within p.d to the designated Data folder in the p.d settings. A new Logs folder will be created that contain the unencrypted user logs.
+  * Otherwise these logs may be exported to a local text file only by a .decimal administrator. For assistance exporting the logs please contact .decimal support.
 ==== decimal3D ====
-[[decimal3d:decimal3d|decimal3D]] logs the local user activity and records the following information to it's local patient database. This information is exportable from the Advanced menu option within the application.
+[[decimal3d:decimal3d|decimal3D]] logs the local user activity and records the following information to its local application database. This information is exportable from the Advanced menu option within the application.
 ^ Log Item ^ Description ^
@@ Line 103: / Line 108: @@
 ==== decimal eRT ====
-[[electronrt:electronrt|decimal eRT]] logs the local user activity and records the following information to it's local patient database. This information is exportable from the Organization Configuration -> Export Logs block within the application.
+[[electronrt:electronrt|decimal eRT]] logs the local user activity and records the following information to its local patient database. This information is exportable from the Organization Configuration -> Export Logs block within the application.
 ^ Log Item ^ Description ^
@@ Line 109: / Line 114: @@
 | ID | The ID of the corresponding Data Type of the log entry |
 | Date | The date time of the log entry |
-| Log Event | The even that was logged. Log Event's include, but are not limited to: \\ -Import Patients\\ -View Patients\\ -Open Patients\\ -Import Courses\\ -Update Course\\ -Create Plans\\ -Update Plans\\ -Clone Plans\\ -Open Plans\\ -Update Organization\\ -Export DICOM files locally\\ -Export DICOM files to AE service\\ -Approve Plans\\ -Order files to decimal Direct\\ -Export Reports|
+| Log Event | The event that was logged. Log Event's include, but are not limited to: \\ -Import Patients\\ -View Patients\\ -Open Patients\\ -Import Courses\\ -Update Course\\ -Create Plans\\ -Update Plans\\ -Clone Plans\\ -Open Plans\\ -Update Organization\\ -Export DICOM files locally\\ -Export DICOM files to AE service\\ -Approve Plans\\ -Order files to decimal Direct\\ -Export Reports|
 | Data Type | What data caused to the log entry. Data Type's include, but are not limited to: \\ -Application (root level interactions without a specific data to link to)\\ -Organization\\ -Patient\\ -Course\\ -Plan\\ -Export\\ -Order |
 | Username | The users first and last name that caused the log entry |