IMPAX 6.5.1 Client Knowledge Base: Extended > Troubleshooting IMPAX Client > Logging system activity > Creating summary files of the client_performance log file

ianalyze report fields


Some reports contain different metric calculations and the information in the fields change depending on the calculation. The description columns lists the different options if more than one calculation is possible.

ReportField titleDescription
AppStart.txtTUIDThe Transaction Unique Identifier
EventTypeCopied from Transaction column in client_performance.log
StartTime
  • How long it took to show the login screen—The date and time when the user double-clicks the IMPAX Client executable to start the application (AppStart->Begin)

  • How long it took to authenticate the user—The date and time when the user clicks the OK button on the Login window (->Step->LoginUsingCredentials)

  • How long it took to present the main Client GUI—The date and time when initialization of the IMPAX Client begins (Initialize->Begin)

EndTime
  • How long it took to show the login screen—The date and time when the Login window is shown and active after a user logs out of the IMPAX Client (AppStart->End)

  • How long it took to authenticate the user—The date and time when user-entered credentials have been authenticated and are correct (Login->End)

  • How long it took to present the main Client GUI—The date and time when initialization of the IMPAX Client ends and the GUI is presented (Initialize->End)

ElapsedTime
  • How long it took to show the login screen—The time it took to show the Login window in milliseconds (the time difference between AppStart->Begin and AppStart->End)

  • How long it took to authenticate the user—The time it took to authenticate the user in milliseconds (the time difference between Login->Step->LoginUsingCredentials and Login->End)

  • How long it took to present the main Client GUI—The time it took to show the Client GUI after initialization in milliseconds (the time difference between Initialize->Begin and Initialize->End)

NumberOfWorklists

-1 indicates that no worklist calculation has taken place as no worklists are loaded during the application start activity or the loading of user credentials

A positive integer indicates the number of worklists available in the List area, including any minimized worklists

ianalyze-worklistDateTimeStartThe time the worklist query started (Worklist->Begin)
DateTimeEndThe time the worklist query ended (Worklist->End)
TUIDThe Transaction Unique Identifier
CountThe number of studies returned. This value is extracted, by ianalyze, from “the Info Fields.
TimeDiffThe time it took for a worklist query to return results in milliseconds (time difference between Worklist->Begin and Worklist->End)
AeTitleThe location where studies are being searched for. This value is extracted, by ianalyze, from “the Info Fields.
QueryIDThe unique TUID of the query transaction that the worklist transaction belongs to. This value is extracted, by ianalyze, from “the Info Fields.
Grid ItemsThe number of grid lines filled in either the Simple or the Advanced Search grid in List area
ianalyze-CycleDateTimeStartThe date and time when the user has selected Cycle and is sending one or more studies to the Image area or Text area(Cycle->Begin)
DateTimeEndThe date and time when the cycle process has finished and all images have been sent to the Image area or Text area for display (Cycle->End)
CycleType
  • Studies—Indicates that this metric is calculated for the cycling of studies

  • Teaching Files—Indicates that this metric is calculate for the cycling of teaching files

  • Reports—Indicates that this metric is calculated for the cycling of reports

TUIDThe Transaction Unique Identifier
TimeElapsedThe time difference (in milliseconds) when the user selects a study to cycle and the study and all images have been sent to the Image area or Text area for display (time difference Cycle->Begin and Cycle->End)
ianalyze-TextAreaStartTimeThe date and time when the user double-clicks the study in the List area (TEXT_AREA_INIT action)
TotalEndTimeThe date and time when the Text area has completed all tasks and displays all required information (TEXT_AREA_END action)
TUIDThe Transaction Unique Identifier
TextAreaDisplayElapsedTimeThe time the user double-clicks the study in the List area to the time the Text area completes all task and displays all needed information (time difference between the TEXT_AREA_INIT and TEXT_AREA_END actions)
OrderInfoDisplayElapsedTimeThe time the process of obtaining the order information for the Text area begins to the time the order information is retrieved and displayed (time difference between the ORDER_INFO_BEGIN and ORDER_INFO_END actions)
ReportInfoDisplayElapsedTimeThe time the process of obtaining the report information for the Text area begins to the time the report information is retrieved and displayed (time difference between the REPORT_INFO_BEGIN and REPORT_INFO_END actions)
PriorsInfoDisplayElapsedTimeThe time the process of obtaining the list of priors for the Text area begins to the time the list of priors is obtained and displayed (time difference between the PRIORS_DISPLAY_BEGIN and PRIORS_DISPLAY_END actions)
StudyInfoDisplayElapsedTimeThe time the process of obtaining the study information for the Text area begins to the time the study information is retrieved and displayed (time difference between the STUDY_INFO_BEGIN and STUDY_INFO_END actions)
PatientInfoDisplayElapsedTimeThe time the process of obtaining patient information for the Text area begins to the time the patient information is retrieved and displayed (time difference between the PATIENT_INFO_BEGIN and PATIENT_INFO_END actions)
ModalityThe modality used to acquire the study
StudyUIDThe study UID of the study being opened
NumberOfImagesInStudyThe number of images in the study
PatientIDThe patient ID
OrderInfoDisplayStartTimeThe date and time when obtaining the order information for the List area begins (ORDER_INFO_BEGIN action)
OrderInfoDisplayEndTimeThe date and time when retrieved order information is displayed (ORDER_INFO_END action)
ReportInfoDisplayStartTimeThe date and time when obtaining the report information for the List area begins (REPORT_INFO_BEGIN action)
ReportInfoDisplayEndTimeThe date and time when the retrieved report information is displayed (REPORT_INFO_END action)
PriorsInfoDisplayStartTimeThe date and time when obtaining the list of priors for the List area begins (PRIORS_DISPLAY_BEGIN action)
PriorsInfoDisplayEndTimeThe date and time when the retrieved the list of priors is displayed (PRIORS_DISPLAY_END action)
StudyInfoDisplayStartTimeThe date and time when obtaining study information for the List area begins (STUDY_INFO_BEGIN action)
StudyInfoDisplayEndTimeThe date and time when the retrieved study information is displayed (STUDY_INFO_END action)
PatientInfoDisplayStartTimeThe date and time when obtaining the patient information for the List area begins (PATIENT_INFO_BEGIN action)
PatientInfoDisplayEndTimeThe date and time when the retrieved patient information is displayed (PATIENT_INFO_END action)
ianalyze-OpenStudyDateTimeStartThe date and time of “OpenStudy->Begin” (when user double-clicks the study in the List Area)
DateTimeFirstImage The date and time when the first image was loaded
Modality The modality used to acquire the study
TimeFirstImageThe elapsed time to display the first image in milliseconds
StudySize The size of the study
FirstImageSize The size of the first image
TUIDThe Transaction UID for open study action
TimeFirstImageCoarseThe time to display the first third of the image. This value (9 ms) is different from TimeFirstImage value only if a web image is being displayed.
TimeFirstImageSharpThe time to display the first two thirds of the image. This value (9 ms) is different from TimeFirstImage/TimeFirstImageCoarse value only if a web image is being displayed.
TimeDisplayStart The time difference between when a study open is requested and the study is displayed in the Image area (time difference between OpenStudy->Begin and “Step->ImageDisplayed->event=Display_Study). During this time interval:
  • Studies are retrieved to cache (if not in cache already)

  • The Image area adds studies to its internal worklist

  • The Image area obtains any snapshot information, if applicable

StudyRef The IMPAX study reference
StudyDate The DICOM study date and time
StudyUid The DICOM study instance UID
Compression The compression type: lossy or lossless
ImageType The image type: original or wavelet
Protocol The protocol: HTTP, HTTPS, ASPFTP, or SPFTP
LocationStatus The status of the study can be one of the following: UnknownBestLocation, PartiallyLocal, FullyLocal, PartiallyCached, FullyCached, PartiallyMod, FullyMod, PartiallyTape, FullyTape, PartiallyHsm, FullyHsm, PartiallyPacs, FullyPacs, PartiallyOffline, FullyOffline, PartiallyCd, FullyCd, PartiallyWeb, FullyWeb, PartiallyExternal, FullyExternal, PartiallyCdr, FullyCdr, PartiallyDvd, FullyDvd, PartiallyRis, FullyRis, FullyCachedFullyWeb, PartiallyCachedFullyWeb
AvailabilityThe availability of the study can be one of the following:
  • Available—Can load the study in the Image area

  • AvailableNeedsRetrieve—Can load the study in the Image area but needs a retrieve job

  • RemoteNeedsRetrieve—The study is remote

  • NeedsRetrieve—The study cannot be added to the Image area; it must be retrieved

  • NeedsPrepare—The study cannot be added to the Image area; it must be prepared

  • Unavailable—The study cannot be added to the Image area; it cannot be retrieved

RemoteAeRefThe Remote AeRef was retrieved from, if available
TimeDisplayEnd When the last image is visible in the current screen layout (the time difference between OpenStudy->Begin” and the last Step->ImageDisplayed->event=ICON_DOWNLOAD_COMPLETE… entry)
ianalyze-GenericDateTimeStart
  • Time to build the patient tree—The date and time of the Begin->check_patient_for_completeness() action

  • Time to execute the setup_and_display_patient() method call—The date and time of the Begin->setup_and_display_patient() action

  • Time to populate all Image area wizards—The date and time of the Begin->user_action_DisplayPatient action

  • Time to navigate to the next study—The date and time of the Begin->user_action_NavStudy action

  • Time to navigate to the next CRM—The date and time of the Begin->user_action_NavCRM action

TUIDThe Transaction Unique Identifier
DateTimeLastStep
  • Time to build the patient tree—The time (in milliseconds) it took to check the patient for completeness

  • Time to execute the setup_and_display_patient() method call—The date and time of the End->setup_and_display_patient() action

  • Time to populate all Image area wizards—The date and time of the End->user_action_DisplayPatient action

  • Time to navigate to the next study—The date and time of the End->user_action_NavStudy action

  • Time to navigate to the next CRM—The date and time of the End->user_action_NavCRM action

TimeElapsedThe time (in milliseconds) it took to check the patient for completeness (time difference between Being and End in the log entries)
InfoFieldsianalyze copies the Info Fields value only from the Step event type. As the check_patient_for_completeness() event has no Step event type log entry, this value is blank
TypeExact name (or action) of the generic metric calculation
: ianalyze-statsTransactionDescThe metric type used for the sample set of the statistics calculation
startThe time of the first transaction in the sample set
endThe time of the last transaction used in the sample set
Mean (average)The mean time (in milliseconds) of all the sample set values
medianThe median time (in milliseconds) of all the sample set values
minFor all the metrics in the sample set, this value is the quickest one
maxFor all the metrics in the sample set, this value is the slowest one
Perc95The value representing the 95 percentile of the sample set
countThe number of values in the sample set

Topic number: 131032

Applies to: IMPAX 6.5.1 Client Knowledge Base