• SIGNA™ Hero 3.0T Service Methods
  • 5852800-8EN Revision 1.0
  • Object ID: 00000018WIA30E6C030GYZ
  • Topic ID: id_12374103 Version: 1.14
  • Date: Oct 11, 2021 3:47:41 PM

Arterys PHI Service Installation

Prerequisites

Table 1. Personnel requirements
Required personsPreliminary requirementsProcedureFinalization
1 -120 minutes -

About this task

Overview

ViosWorks is powered by the Arterys cloud platform, which is FDA cleared and CE marked. Arterys is a web-accessible, image analysis software intended to automate and simplify the visualization and quantification of cardiovascular images. Cine3d and flow4d are the options on MR console that enable ViosWorks.

ViosWorks Workflow:

  • MR technician sends exams/series to Arterys from the MR host.

  • PHI Server used enroute to abstract patient and hospital sensitive information from the images.

  • Images are then sent over to Arterys cloud.

  • Processed images from Arterys are returned to DICOM end points.

  • Information from PHI Server is re-integrated and displayed

Figure 1. Secure Hospital Network (only allows outgoing https requests through port 443)
ITEM DESCRIPTION
A Hospital network
B Arterys network
C MR scanner
D PHI server
1Scanner
2Host
3Tarball of DICOM files containing PHI
4Data storage
5PHI service
6PACS
7Firewall
8Tarball of DICOM files with PHI metadata removed
9Request to retrieve: DICOM secondary capture encapsulated PDF reports
10Private cloud

This feature is available only on MR systems running software versions DV26 and later.

Documentation is available on the Arterys website (https://support.arterys.com) and requires a login. Contact Arterys (support@arterys.com) with questions and to create a login for their website. You must provide your GE credentials.

Note:

Customers must create their own Arterys login to complete the installation process. This is separate from the login that the GE FE creates.

Topic ID: id_SL15474962-1330299

Infrastructure

Procedure

  1. Customer supplied computer/VM with minimum hardware specifications as available in the PHI service operator manual at https://arterys.com/docs/phi-service-manual OR GE-supplied Dell T5810 computer.
  2. Internet connectivity via hospital network to the computer.
  3. Network configured to enable external connectivity (the PHI server requires a dedicated static IP address).
  4. Arterys login created by FE. Send out mail to support@arterys.com and obtain access.
  5. Arterys account created and registered by customer or customer’s IT personnel. Ask the customer to contact Arterys (support@arterys.com) to create an account before you begin installation. The customer must provide his or her name, the hospital name, and contact information.
  6. Scientific Linux operating system DVD (As indicated in the PHI service operator manual).
  7. eLicense options (flow4d and/or cine3d) (generated for the customer site).
Topic ID: id_SL12228886-1330299

Scientific Linux OS Software Load

Procedure

  1. (For GE supplied PHI server) Install the operating system and complete the PHI software load using the procedure located in the PHI service operator manual (https://arterys.com/docs/phi-service-manual).

    (For customer supplied PHI server) Follow up with the customer or customer’s IT personnel to get the PHI server loaded with the correct OS along with the PHI software using the procedure located in the PHI service operator manual (https://arterys.com/docs/phi-service-manual).

  2. PHI Local Hostname is provided by Arterys as part of the customer account creation and registration process. PHI Port Number is 443 by default unless otherwise modified on the PHI server by the customer’s IT personnel. PHI IP Address is the IP address of the PHI server configured during the PHI software load procedure.
Topic ID: id_SL15255769-1330299

Host PC and PHI Server Connectivity Configuration

Procedure

  1. Launch Guided Install from the Service Desktop Manager.
  2. Click on the HIS/RIS tab.
  3. Click on the PHI Client tab.
  4. Enter the required parameters and click Verify.
    1. If the connection succeeds, a pop-up displays that confirms the PHI server responded.
    2. If the connection fails, check the parameters and retry.
    Figure 2. Guided Install PHI Client Configuration
  5. Click Configure and reboot the system.
Topic ID: id_SL15475011-1330299

Sending Images and Monitoring Status

Procedure

  1. Select the Exam/Series scanned from Image Browser and click on ViosWorks Transfer (1), then in the pop up click on send (2).
  2. Images will get pushed over to PHI Server and then only pixel data will transfer over to Arterys cloud.
  3. Status of transfer can be monitored by clicking the refresh button (3).
    Figure 3. Sending Images
  4. Table below shows various status codes for the transfer. Error statuses are marked in red.

    • Column on the right is what is seen on the UI by the customer

    • Column on the left shows status as in log file

    • Log file path: /usr/g/service/log/ViosDataTransferService.log*

    Figure 4. Monitoring Status
Topic ID: id_SL15236389-1330299

Troubleshooting

About this task

Log File:

  • Location of Log File: /usr/g/service/log/

  • File name(s): ViosDataTransferService.log*

Procedure

  1. Check the log files ViosDataTransferService.log* for a log record pertaining to the exam in question, looking for the appropriate exam number and approximate time that the transfer was initiated. This could be accomplished manually or using the egrep command below:

    Egrep command: egrep -i "statuspollingthread.*exam.*enter exam# here" ViosDataTransferService.log*

  2. View output.
    Note:

    Example Service Log output for exam#: 646 is shown below. Observe the Arterys Return Codes (highlighted).

    Figure 5. Service Log
    Note:

    In case the MR console was shut down before the entire workflow of a given exam is complete, its status will not show up any more in the log file.

    For such exams, use the following procedure to get the latest status:

    1. Copy the UID and 2ndID from the output of the egrep command.

    2. The same exam number could have been sent out multiple times. Make sure the UID & 2ndID chosen is per the correct time stamp.

    3. Execute the following command using the copied UID and 2ndID:

      curl “https://<organization name as registered on Arterys>.organization.arterys.com:443/api/ge.0/upload/<UID>?filter=date:<2ndID>”

      Example output of this command for exam 646: curl "https://ge-reference.organization.arterys.com:443/api/ge.0/upload/1.2.840.113619.6.408.14786641920532410607184093538995956883?filter=date:1473968416307"

      ARTERYS_PROCESSED: 1473968416307:c192388242f3a0f385568af636cc7e670a1d3b53
Topic ID: id_15187782

Finalization

Finalization

  1. Perform a Save Info to save the PHI client configuration.

  2. Customer must configure the DICOM end points to receive processed images from Arterys.