Logserver

Overview –  Installation –  Configuration –  Administration –  Data Visualization –  Example Queries

 Overview

Yarra LogServer is a central monitoring hub for enterprise Yarra installations. It is typically installed on a separate intranet server (usually on a small VM server) and allows monitoring all activities of YarraServers as well as of the RDS and ORT clients running on the different MR scanners. This enables timely detection of problems (e.g., network connectivity problems) and generation of statistics on the processing performance (e.g., it allows measuring the total wait time from task submission to PACS transfer).

Moreover, RDS clients can be configured to continuously send clinical workflow information from the scanners to Yarra LogServer, where the workflow information is concatenated into examinations and stored in an SQL database. The collected workflow data can be analyzed retrospectively to generate various statistics on the examination efficiency, to detect acquisition problems, or to answer specific research questions regarding the examination procedure. It also makes it very easy to monitor progress in research studies and allows identifying patient exams during which specific research sequences have been acquired.

Collected data can be analyzed either using the provided Yarra LogViewer web application, using the Redash web application for rapid dashboard generation, or using other business-intelligence (BI) software tools.

 

Capabilities

  • Monitor Yarra clients and other Yarra components
  • Catalogue scanners and monitor scanner health
  • Log every sequence and adjustment scan acquired on RDS-enabled scanners
  • Concatenate sequences into discrete exams (by patient name)
  • Parse “Epic-formatted” patient names
  • Tag exams with procedure information (e.g., body region or exam protocol)
  • Combine collected data with additional data sources
 

Limitations

  • Workflow information includes patient name, sequence name, begin / end time of sequences, and scan size
  • Additional sequence parameters (e.g., TE, TR, BW, etc.) are currently not captured
  • Procedure information captured by “tagging” exam with a dummy sequence (typically performed after scout)
  • Only provides basic data analysis out-of-the-box (comprehensive analyses require Redash or other BI software)
  • LogServer works only for MR scanners with software VB17A or newer
Open Chat