MR Protocols Module (Numaris XA20) - USA

Welcome to the MR Protocols Module Online Training. In this online training you will learn more about the MR protocols module (based on the software version Numaris XA20). The MR protocols module (MRPM) is new software which enables easy configuration and management of protocols for several scanners.  On the following pages, you will learn more about the concept behind and the main features of this product. In addition, interactive simulations will guide you through the typical workflow to manage your protocols across your fleet. Congratulations. You have completed the MR Protocols Module online training. Listed below are the key points that have been presented. Take time to review the material before you proceed to the final quiz. Concept and Benefits The MR protocols module is a standalone Dot Cockpit which can be connected to one or more systems in your fleet. You can install the software on a standalone workstation or virtual PC. It enables you to manage your protocol trees efficiently, independently and without blocking the system. Installation and Configuration For installation, a computer with appropriate prerequisites must be available. As well as installing the software, it is important that a shared network location is set up. In the next step, configuration of the connected systems and the MR protocols module is required to set up the connection between the fleet and the MRPM. Please note: you need to be logged in as medadmin.  Fleet Configuration can be performed from the MRPM using the Dot Cockpit settings and on the Configuration Panel on the system. Opening the MR protocols module You can open the MRPM in two different ways (depending on your product): from the computer on which the software is installed simply by clicking on the application icon, or from Teamplay protocols if the product has been purchased with the Teamplay option. In the Dot Cockpit of the MRPM and in the connected scanners, you can find different protocol trees: Default, Siemens, User and Fleet. The fleet tree is stored in the fleet database. A central master version of the fleet database resides on a network share. Every Dot Cockpit in your fleet has a local copy of the fleet database. To ensure that only staff with adequate expertise have access to the fleet tree and work on the protocols, you can protect fleet trees using a password.   Groups The term group defines a group of scanners of equivalent system type and hardware configuration. This definition is really important to define which systems can share the same protocol tree and use the same optimized version of the protocols. In the MRPM, every group of systems will have a fleet tree in the fleet database.   Manage your fleet The MRPM provides the basic functionality of the Dot Cockpit. In addition, you can manage and organize the protocols of all systems connected to your fleet based on your needs and requirements. When you add the first scanner to your fleet, you can fill your fleet tree with the protocols of, for example, your user tree or Siemens tree by using the Copy and Paste functionality in the Dot Cockpit. For protocol management of additional scanners, using the Import and Export functionality is recommended in order to keep the same tree structure. Systems connected to your fleet normally have different licenses. Protocols may therefore be empty or greyed out on some systems.   Update and Publish When you manage your protocols within your fleet, changes need to be distributed across your connected systems and the MRPM. You must keep your fleet database updated in order to avoid conflicts within your fleet. We differentiate between pending local changes (publish) and pending remote changes (update).   Resolving conflicts Conflicts may occur when you edit a region, examination, measurement program or program step in the fleet tree from a scanner and another user publishes the same changes from another system or the MRPM at the same time. We differentiate between three types of conflicts: structure conflicts, program conflicts and directory conflicts. Conflicts can be resolved manually or automatically.   General recommendations When you use the software for the central measurement program and protocol configuration, we recommend that you adopt a very structured and well-documented mode of working.   Upon successful completion of this course, you will be able to describe the concept of the MR Protocols Module​ and its benefits ​describe the basic steps of installation and configuration ​identify trees and scanner groups​ perform basic steps such as organizing and editing trees, regions and programs in the fleet  ​resolve conflicts Please note that the learning material is for training purposes only! For the proper use of the software or hardware, please always use the Operator Manual or Instructions for Use (hereinafter collectively “Operator Manual”) issued by Siemens Healthineers. This material is to be used as training material only and shall by no means substitute the Operator Manual. Any material used in this training will not be updated on a regular basis and does not necessarily reflect the latest version of the software and hardware available at the time of the training. The Operator Manual shall be used as your main reference, in particular for relevant safety information like warnings and cautions. Note: Some functions shown in this material are optional and might not be part of your system. The information in this material contains general technical descriptions of specifications and options as well as standard and optional features that do not always have to be present in individual cases. Certain products, product related claims or functionalities described in the material (hereinafter collectively “Functionality”) may not (yet) be commercially available in your country. Due to regulatory requirements, the future availability of said Functionalities in any specific country is not guaranteed. Please contact your local Siemens Healthineers sales representative for the most current information. The reproduction, transmission or distribution of this training or its contents is not permitted without express written authority. Offenders will be liable for damages. All names and data of patients, parameters and configuration dependent designations are fictional and examples only. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Copyright © Siemens Healthcare GmbH, 2019 The MR Protocols Module is a central workplace which can be connected to one or more scanners in your fleet. You can install the software on a standalone workstation or virtual PC.  It enables you to manage your protocol trees efficiently without blocking the system. By maintaining your fleet from a centralized location you can minimize protocol inconsistencies and enhance productivity and reproducibility across all your systems. In this way you can manage and distribute your protocols across your fleet efficiently.  Before you start working with the software, it is important to know some key terms. These terms will be explained on the following pages. In the Dot Cockpit of the MRPM and in the connected systems, you can find different protocol trees: Default: contains all default sequences and is read-only Siemens: available by default, it includes all Siemens released sequences, Dot Engines, clinical programs and libraries specific to your system. Protected from modifications by read-only access ​User: automatically created on the single scanners and empty. You can fill it with acquisition protocols optimized on the basis of your clinical and acquisition needs ​Fleet tree: automatically created after installation of the MR Protocols Module on both standalone workstation and connected scanners. This tree, initially empty, will be populated manually with the common tree to be shared across the fleet. Please note: This tree is available on all systems which form a group (see Group page for more details) The fleet tree is stored in the fleet database. A central master version of the fleet database resides on a network share. The fleet tree is visible in the Dot Cockpits (both MRPM and scanners) and as a local copy. When you create or edit measurement programs or protocols on the MR Protocols Module, you can work on the MRPM or just on a local copy of the fleet database. When the modifications are completed and published for distribution, the master version will be updated. From there, your modifications will be distributed to connected scanners in your fleet automatically and immediately. This will be explained in the section Working with the MR Protocols Module. Remember: you can protect the fleet tree by using a password to ensure that changes are published only by expert staff.  When to use which tree? Click here for some tips on when to use which tree Tab TitleTextUser treeThe user tree contains system-specific protocols.  Use for cases such as  dedicated protocols that will not be shared with the whole fleet (e.g. research protocols, disease examined only on one selected scanner) sequence testing Fleet treeThe fleet tree harmonizes protocols across the fleet. Use for  reproducible results and easier management of examinations across the fleet The term group defines a group of scanners that can share the exact same sequence parameters for type and configuration. This is automatically defined from the software and cannot be changed. In the MRPM, every group of systems will have a fleet tree in the fleet database. Protocol and sequence adaptions performed on a single scanner belonging to the group are automatically applied to the other scanners in the scanner group only. Changes across different groups have to be propagated manually. Please note: The visualization of the other scanners and groups is available only on the Dot Cockpit of the MRPM for fleet management. The view of the single scanner Dot Cockpit remains unchanged except that the fleet tree has been added. The scanner Dot Cockpit is still used to operate the single scanner.  The software enables you to manage your protocols for different scanners in an efficient way without interrupting your examination workflows. On the following pages, you can learn more about the different steps and simulate some typical working scenarios.  As the MRPM is applying changes to all the scanners automatically, it is really important that you adopt working rules based on guidelines that will enable you and your colleagues to use the product efficiently in your daily working routine. Some recommendations are: define naming conventions for fleet trees. make use of both the local and fleet database for program maintenance in the MRPM. password protection for fleet trees. define a schedule. click Publish only when you have completed the task. When you manage your protocols within your fleet, changes need to be distributed across your connected systems and the MRPM. It is essential to keep your fleet database in a shared location updated in order to avoid conflicts within your fleet.  We differentiate between pending local changes (publish) and pending remote changes (update). If you create a new region in your fleet tree in the MRPM, this action results in a new pending local change appearing in the upper right corner of your screen as an arrow pointing up. Pending local changes need to be published manually. After publishing from MRPM, the scanners in your fleet have new pending remote changes and need to be updated. Updates are performed automatically as soon as possible. You can manage both actions in the upper right corner of the Dot Cockpit screen. The same applies vice versa from scanners to MRPM. Please note: Publish new measurement programs or program modifications only when you are certain that you have completed the task. Never publish intermediate versions of new or modified measurement programs or program steps. Before you publish, always update first to avoid conflicts. Publish changes Click here to see a practical example Checklist TitleChecklist TypeChecklist ContentNo remote or local changesHTMLOne local change (e.g. create new region)HTMLPublish local change manuallyHTMLSynchronization Progress is executedHTMLNo pending local or remote changesHTML Conflicts may occur when you edit a region, examination, measurement program or program step in the fleet tree from a scanner and another user publishes the changes to the same item from another system or the MRPM at the same time.  If this is the case, updates will not be done automatically and the software will inform you about conflicts in the upper right corner of the Dot Cockpit screen (next to pending local or remote changes) or on the scanners. Conflicts can also be recognized on the home screen where the Dot Cockpit icon will display a warning icon. We differentiate between three types of conflicts: structure conflicts, program conflicts and directory conflicts. The structure conflict is resolved by the system automatically. In such cases, updates are distributed automatically across the fleet and in the background. User action is required only when the system cannot resolve conflicts autonomously. Types of conflicts Learn more about the different types of conflicts Type of conflict Examples How to resolve Resolve options Structure Conflict    Moving/adding/deleting programs or directories Automatically - Program Conflict  Moving steps, renaming program Manually Take Server Version  Keep Local Version  Both  Directory Conflict  Renaming directories, changing directory properties e.g. in the protocols module and on the system Manually Take Server Version  Keep Local Version   Example for Merge Conflict Resolution Learn more about Merge Conflict Resolution Tab TitleTextWhat happened Region has been renamed on scanner and in MRPM in the fleet tree and causes a Directory Conflict. ​Merge Conflict Resolution information appears at Dot Cockpit screen. How to proceed Click on Merge Conflict Resolution to get more information and to resolve the conflict. Select your preferred option to solve the conflict from the dialog. Don't forget to distribute changes Finally, distribute the changes to the fleet by clicking Publish. If you work with the MRPM software, you have the basic functionalities of the Dot Cockpit. For example, you can:  create new programs or regions in your trees, or copy new programs or regions and rename them, and so on  With the extended functionalities, you can manage and organize the protocols for all systems connected to your fleet based on your needs and requirements.   Simulate how to manage your fleet using two typical examples in the interactive simulations in the pop up below. In addition, learn more about license inconsistencies between systems connected to your fleet and possible consequences.  Fill the fleet tree for the first time Click to simulate how to fill the fleet tree for the first time Instructions:Flash File:HTML5 File:/content/generator/Course_90023141/MRPMSim1_20200130/index.htmlPDF File: Manage the fleet tree for more than one scanner Click to simulate how to manage the fleet tree for more than one scanner Instructions:Flash File:HTML5 File:/content/generator/Course_90023141/MRPMSim2_20200123/index.htmlPDF File: Management of license inconsistencies Learn more about the management of license inconsistencies between scanners within one group Normally,  the scanners belonging to the same fleet can have different licenses and hardware configurations. Therefore, protocols in one of your systems may be empty or greyed out.  Hint: Always handle protocols carefully and do not delete any of them in the fleet until you are really sure that they can be deleted. When you delete an empty program because of missing license, this program will be deleted from all the scanners in the same group. This will cause additional efforts for setting up the protocols again. Have a look at the video below to see an example:   After installation and configuration, you can start working on your fleet management. Depending on your product, you can open the MR protocols module in two different ways: from the computer on which the software is installed, simply by clicking on the application icon from Teamplay protocols, if the product has been purchased with the Teamplay option Please note: the Teamplay license needs to be installed and depends on country availability. ​Hint: If you open the Dot Cockpit from the single scanner, the functionality will remain the same as always. Nevertheless, when a scanner is connected to MRPM, the fleet tree can be automatically updated with the latest changes and immediately used. In addition, local changes performed on the single scanner can be published in MRPM and suggested for fleet updates. Overview of User Interface MRPM Click here to get an overview of the User Interface of the MRPM Tab TitleTextSelected scanner Licenses and hardware configuration for the scanner are automatically used. Tree structure (regions and exams) The tree structure is shared across the full fleet.  Programs and sequences Programs and sequences are defined specifically for scanner types and shared only inside the single scanner group.  Update information Update information regarding:  pending local changes (called publish) pending remote changes (called update) merge conflicts between publish and update The software will be installed and configured by the Customer Service Engineer.  For installation, a computer with appropriate prerequisites must be available. During installation, a shared network location needs to be set up. This shared location provides a main exchange folder for the data from scanners and vice versa.   A connection needs to be enabled between the scanners and the MRPM for the MRPM to work correctly. This will be done in the Fleet Configuration of the MRPM and the fleet’s scanners. Please note: you need to be logged in as medadmin. In the MRPM, you can access the Fleet Configuration by clicking on the Settings icon – on the individual scanners, you have access from the scanner’s Configuration Panel. If further configuration is necessary, please contact your local helpdesk hotline.  How to recognize connected systems Click here to learn more about how to recognize connected systems Tab TitleTextat your scanner1) On the Home-Screen of the scanners, the Dot Cockpit icon includes now a cloud which shows that the scanner is connected. 2) In the Dot Cockpit, an additional user tree FLEET appears in the tree overview. You can recognize the fleet tree by the cloud icon next to the name. It is shared with the MRPM and synchronized from the MRPM across the whole fleet. at the MRPMYou can see a list of all connected systems in the two menus group and systems below the toolbar. The configured network share contains important data about the scanners connected and the fleet database. Please do not manually manipulate the content of the share because it may break the fleet functionality. These files are there for troubleshooting.