HP Medical Archive Solution 17

HPMA User Guide

Architecture Overview

The HP Medical Archive architecture provides a secure, reliable, and high performance solution for the storage and distribution of very high volumes of fixed content health care data within a data center and optionally a disaster recovery (DR) site.

The term “grid computing” is inspired by the success of the interconnection of the electric power and communication network infrastructure in the late 1800s and early 1900s.

The power grid manages the available power resources and balances loads to ensure continuous operation. How and where the power originates is transparent to the consumer. During peak hours, available resources are automatically balanced and power is rerouted to where it is needed most. As demand increases, additional generating resources come online, and they are transparently utilized. Similarly, when stations go offline or get decommissioned, there are no consumer service disruptions. The grid automatically balances the available resources to changing demand; loss of a subset of resources does not result in degraded service.

Grid computing is based on the principle that access to computational resources (storage, processing power, and data) can be enhanced with high levels of reliability and scalability, analogous to obtaining electric power from the power grid. Grid storage is the application of grid computing principles to storage architecture: directories, query, resource management, and fault management.

The HP Medical Archive system is composed of multiple nodes, which form a unified archive. Each node consists of software services operating on a server that manages a limited capacity storage resource.

Within a given facility, all nodes are interconnected using standard TCP/IP networking, and communicate with local imaging modalities, PACS, and workstations. Wide Area Network (WAN) links extend the grid, enabling off-site replication of content for disaster recovery.

The HP Medical Archive deployment relies on open standards for interoperability with external hospital systems. Exchange of clinical data with external clinical systems, including PACS, viewing worksta- tions, and modalities, takes place over standardized network file system protocols (NFS/CIFS) or (optionally) via established imaging protocols, including DICOM.

2

HP Medical Archive

Contents

HP Medical Archive Solutions User Guide Page HPMA User Guide DISCLAIMER http://www.openssl.org Copyright ©2005 by Bycast Inc. All rights reserved Proprietary and Confidential Contents Preface Purpose Currency Intended Audience Alarms System Status Overview Alarm Levels and Indicators Alarms Tab Alarm Handling Configuration Introduction to Configuration Alarm Configuration Service and Component Configuration ADC Configuration Troubleshooting Alarms Overview Alarm Reference Table Introduction to Server Manager Overview of Server Manager Glossary Index Page Preface version version 2.Use your operating system’s window close button to close the About dialog If you have an earlier version of NMS, contact HP technical support References PDF editions include hyperlinks to assist navigating the document not Using this Guide Chapters Conventions Terminology Numerics Numeric values are presented in decimal unless noted otherwise Fonts •Items upon which you act are shown in bold. These include: •Buttons or keys to click or press, such as Apply or <Tab Keyboard Input <Alt>+<F7 <space>Y<Enter Color www.hp.com Getting Started NMS and the HP Medical Archive Architecture Page Role of the Network Management System (NMS) It is a Network and Element Terminology •Locations •Nodes Capabilities At this time, the only supported browser is: •Microsoft Internet Explorer v6.0 SP2 (and above) •JavaScript and cookies must be enabled •Adobe SVG Viewer plug-in plug-in Log in Once you have accessed the NMS via your browser, the HP Medical Archive log in... window appears To log into the NMS: 1.Click in the username field to place the cursor in the field To log out: 1.Click on the Logout arrow button to log out Logged out 2.You may safely close the browser or continue using other applications At the time of installation, default user and group accounts are config Account Management Configuration Table 1: Account Configuration Controls Action Description Apply Table 1: Account Configuration Controls (cont.) Action Table 2: Account Management Attributes Attribute Type / Units Editing Your Account You may need to configure your browser to permit popups from this site Click the edit User Account 2.To change your password: Interface2 Components Navigating the NMS Interface The NMS interface is divided into three key sections or frames: •Header •Navigation Tree •Content Frame Every “page” of the NMS interface contains these three frames Refresh Time Information presented in the NMS interface is time-sensitive.Since the Updated Refreshing the Display To take a new “snapshot” of the grid status: System Status Indicator Grid Map Account Management Button changes to their password and the settings for their first and last names Only the Vendor maintenance user has Account permission to: Tree Structure Status Indicators Tabs Page Selectors Property Information (Overview) Text Color gray italics Immediate Reports Active Alarms Overview Alarms See Chapter 3 for a full description of the alarm capability Reports •The Chart page produces graphical data for the selected attribute •The Text page produces tables of data Notification Location and Node Maps Page page 16. Click a tab to display the related content and selection forms Page Alarms3 System Status and Notifications The NMS uses color-codingand icons for easy identification of alarm System Monitoring Notifications Indicators and Propagation Figure 16: “Sample Alarm Indicator Propagation” on page 30.) Table 3: Alarm Levels and Indicators Icon Color Level Meaning Page provides details of the current status Main Page The alarm data is listed in a table with the following headings: Table 4: Alarm Table Headings Heading Definition History Page Rows showing the green icon show either: Cleared —or— •“Normal”—anattribute has returned to normal state from the unknown state () and the description shows “State Change Unknown to Active” Tracing the Source of an Alarm Tracing an alarm follows these main steps (each is expanded later in the text): 1.Trace through the network tree to the specific node generating the alarm Use the information from the Troubleshoot the alarm by using the lookup table in Resolving Alarms Clearing Alarms Alarm states are self-correctingwhen the attribute value for an alarm You can perform queries to retrieve data for preventive analysis Page Reports4 Current and History Reporting Report Types The NMS provides three different ways to generate reports: •Immediate—generatedby the click of a button on the Overview page Immediate—generated by the click of a button on the Immediate Reports Table 5: Immediate Report Buttons Button Report Type Presentation Quick Reports Optionally deselect the Vertical Scaling Optionally select the Text page to obtain a text format report 4.Use the Attribute pull-downmenu to select the attribute to report Custom Reports To generate a custom report: Start Date End Date Custom Query Charts Interpreting Lines and Shading Charts use color and shading to convey specific information about the graph Table 6: Chart Colors and Shading Sample Meaning Reported attribute values are plotted using dark green lines Text Reports Window Using Microsoft® Internet Explorer: 1.Create the desired report (or other content page) 2.Right-clickin the Content frame to access the context menu Select either Print Print Options Page Services and Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Configuration Alarms and Services Each service’s Configuration tab has two pages: Configuration—NotificationPage Table 59: Notification Table Headings Table 59: Notification Table Headings (cont.) The alarm’s threshold value used to test (using Op) against the attribute’s actual value Value Type Active Alarms Page Changing Alarm Settings Enabling (or Disabling) an Alarm Setting an Alarm Threshold Secondary Message Value Configuration—MainPage Configuration changes entered in the form are not made until you select the than once. Wait for your browser to refresh the page Table 60: Main Page Configuration Settings Common to All Services Prompt Table 60: Main Page Configuration Settings Common to All Services (cont.) Page Table 61: CLB X DICOM Component Configuration Settings Table 62: CLB X DICOM Component Configuration Settings Page Table 63: FSG X Storage Component Configuration Settings Table 64: LDR Service Configuration Settings Table 65: LDR X Storage Component Configuration Settings counters to clear alarms Table 66: LDR X DICOM Component Configuration Settings Sets the component to be either: • Offline—NoDICOM transactions are allowed and any entity that tries to establish a DICOM Table 67: LDR X HTTP Component Configuration Settings Page Table 68: SSM X Events Component Configuration Settings ability to reset the error counters Table 69: SSM X Network Component Configuration Settings Clear Error Counts Resets all network component error and fault counters. This clears the “FERR” alarm Troubleshooting Alarms Attr Recommended Action Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Introduction to Page Page Page Operation Using the Local Console Header Error Service List Service Name Version Nominally these all report “Verified” or “Running”. As the services are Stopping Control Buttons Use of these buttons is described in detail in “Command Operations” on page Server Identification Node Type Host Name Prompt Line for more on using the buttons Display Updates Keyboard Input The interface only supports use of the command buttons shown in the Monitoring Services Starting Services Start All Stopping Services Stop All When maintenance tasks are finished, you can either: Shutting Down the Server If the server must be powered down for hardware maintenance Restart Glossary CMS FCS flywheeling FSG Grid Task latency LDR metadata Data that provides information about other data namespace NFS SATA SQL StorageGRID™ study SVG UTC UUID WAN Page Index