• Discovery MR750w and SIGNA™ Architect T 3.0T System Service Methods
  • 5690002-2EN Revision 4
  • Object ID: 00000018WIA309AE030GYZ
  • Topic ID: id_12374202 Version: 1.7
  • Date: Oct 11, 2021 3:47:41 PM

Imaging Protocol Manager

Prerequisites

Table 1. Personnel requirements
Required personsPreliminary requirementsProcedureFinalization
- - -

About this task

Overview

Imaging Protocol Manager (IPM) is a cloud-based protocol management software solution that helps to maintain and standardize CT, MR and X-Ray protocols at a centralized location by creating protocol libraries, standardizing imaging workflow, identifying protocol variation, improving adherence to protocol compliance set up by the clinical practice to meet regulatory requirement, and achieving improved quality of care, operational efficiency and optimized patient experience.

There are 2 parts to the service documentation for this feature. One deals with the Imaging Protocol Manager application which resides on the cloud and the other part which deals with configuring the MR System to connect to this application. This manual covers the procedures needed to connect the MR System to the IPM application on the cloud. For any details regarding the IPM application on the cloud, look for Imaging Protocol Manager Service documentation on the SIMS Content Viewer.

Only DV26.0_R02 software supports IPM Application on MR. Support on other software revisions is being worked on and will be communicated once released.

Figure 1. Connectivity Architecture Scanner to Cloud – Typical Hospital Network
Topic ID: id_SL16395746-1365752

Protocol Import/Export Criteria:

Procedure

  1. Only Site Protocols are available to be exported or imported via the IPM Application.
  2. The whole protocol (directory) is considered as a unit and is transferred during the PULL/PUSH operation. Embedded images in protocol notes are also transferred during the PULL/PUSH operation.
  3. There will be a compatibility checker both on the cloud and the device side which will check equality for fields like grad coil, field strength etc. before pushing and committing the protocol.
  4. A unique identifier is created using the timestamp and MAC of the device for each new protocol on the device being pulled to the cloud. Each protocol coming from the cloud will have also have a unique identifier.
  5. The scanner must be InSite checked out to enable registering with the cloud.
Topic ID: id_SL15474962-1365752

General IPM Workflow

Procedure

  1. Register: Registers scanners into the organization registry.
  2. PULL: Imports protocols to the cloud library from multi-modality scanners (CT, MR, Xray) and allow basic editing.
  3. PUBLISH: Views protocol(s) and publishes them as Published Protocol for the fleet of same scanners.
  4. DISTRIBUTE: Distributes protocols to scanners throughout the hospitals within the organization.
Topic ID: id_SL12228886-1365752

Pre-Requisites

Procedure

  1. MR System InSite checked out with correct model type – FE & OLC
  2. MR System should have been registered in IPM Cloud – Healthcare Cloud Admin
  3. Customer should have the IPM Credentials : User ID, Password and IPM Configuration URL
  4. Proxy IP address/port# to connect to internet - customer IT support
  5. Domain Name Service (DNS) Server IP addresses if applicable – customer IT support
Topic ID: id_SL15255769-1365752

Device Registration Process

Procedure

  1. 1. Healthcare Cloud Admin registers the device in GE HealthCloud by providing SystemID.
  2. The device gets added to HCM and generates a globally unique IPM DeviceID for the system. Device Status is READY (Device gets added to the device pool of the registering cloud admin).
  3. If the site is using DNS, then enable Use DNS and key in the DNS information into the Network Info tab of the Guided Install screen on the MR System.
    Figure 2. Guided Install Screen
  4. Launch CSD.
    1. Click on the Configuration tab.
    2. Click Configure Cloud Connectivity on the left side menu.
      Figure 3. Configuration Tab
  5. The IPM Registration Page is displayed.
  6. Enter the following details (Have the customer key in these details on the system).
    1. User name.
    2. Password.
    3. Static URL.
    4. Click on Proxy Settings and update as needed for the site.
  7. Click Connect. The Device Authorization process begins.
    Figure 4. Device Authorization
  8. If all of the credentials are correct, the device is authorized and enrolled.
  9. Device credentials/security keys are generated and stored on the system.
  10. MR system configuration data is then uploaded to the Cloud.
  11. Device Status is activated when the following screen appears.
    Figure 5. Device Activated
  12. Perform a Save Info to retain connectivity information.
  13. The Protocol Manger can now start Import/Exporting protocols to and from this system.
Topic ID: id_SL16396469-1365752

Protocol Import/Export status

About this task

The status of the Protocol Import/Export actions are seen on the bottom right corner of the screen as one of 3 icons (All icons display for 5min). A reboot is needed for the protocols to get updated.
Figure 6. Download Complete
Figure 7. Protocol Update Success
Figure 8. Protocol Update Failure
Topic ID: id_SL16396610-1365752

Restore Protocols from the Device (MR System)

Procedure

  1. The IPM application in the scanner takes a backup of protocols before committing the new protocols to the site library. Restore is a scanner based action to restore the backed-up protocols to the site folder. The scanner initiates restoring the system’s site protocol to the selected state on receiving the User command.

    • Launch CSD.

    • Click on the Configuration tab.

    • Click Configure Cloud Connectivity on the left side menu.

    • Click Restore Protocols tab.

  2. Choose the protocol set to restore. There will be at maximum 3 protocol sets backed up for each system. Any protocol content issue should be handled by the Protocol Admin. The Admin can always restore an older revision.
    Figure 9. Restore Protocols Screen
Topic ID: id_SL16400742-1365752

Diagnostics

About this task

The Diagnostics tab allows you to check the status of the Imaging Protocol Manager application.

  • It shows the application connectivity status and the status of protocols sent, received, and committed along with its last updated time.

  • It also provides an option to run Diagnostics which performs pre-defined diagnostic tests including the proxy connection test, the internet connection test, the polling test, and heartbeat tests and others.

Procedure

  1. To perform diagnostics, launch CSD
  2. Click the Configuration tab.
  3. Click Configure Cloud Connectivity.
  4. Click Diagnostics tab.
    Figure 10. Diagnostics Screen
  5. Click on Run Diagnostics to run the predefined tests. The screen showing the in-progress tests will be shown.
    Figure 11. Run Diagnostics
  6. Once the diagnostics run is completed, it updates the status with either green (done) or red (not done) icons against each test.
    Figure 12. Diagnostic Test Status
Topic ID: id_SL16400772-1365752

Logs

About this task

The user has an option to check the operations that have occurred in IPM along with its statuses from the Logs tab.

Procedure

  1. To view logs, Launch CSD
  2. Click the Configuration tab.
  3. Click Configure Cloud Connectivity.
  4. Click Logs tab. The screen will be displayed showing the status of the transactions and the corresponding log details
    Figure 13. Logs Tab