Attachment_4_-_HAIMS_Auto_Store_Checklist.pdf

HAIMS Bulk Scan Component “AutoStore” Site Checklist Version 4.0

26 January 2013

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 1 of 10

2 | P a g e – AutoStore HAIMS Site Checklist 4.0

Contents

Introduction

AutoStore “Relay” Server Requirements

Virtualization

Communication Architecture

Default ports being used by AutoStore / Component Functions

MFD API Platforms

AutoStore MFD Questionnaire

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 2 of 10

3 | P a g e – AutoStore HAIMS Site Checklist 4.0

Introduction

The Department of Defense healthcare community has requested an ability to easily scan documents into HAIMS. In response to this demand, DHIMS is deploying an update to HAIMS to support both (a) traditional desktop scanners, with now (b) an ability to scan from Multi-Function Devices (MFDs) and some network scanners.

HAIMS has integrated with a Commercial-Off-The-Shelf (COTS) scanning solution called AutoStore to provide a capability to scan documents from Multi-Function Devices (MFDs) into the HAIMS system (i.e. scanning from a Xerox, Ricoh, HP, etc). DHIMS selected AutoStore due to its multi-brand support of MFDs, and AutoStore’s integration capabilities with CAC to support secure patient record scanning. The HAIMS MFD integration will essentially place a button on the MFD to make it easy for users to scan to HAIMS. An example screenshot from a Ricoh MFD is below:

The HAIMS integration on an MFD is very similar to deploying an “app” (or application) on a mobile phone – sometimes now referred to as smart-phones. In the smart-phone industry, there are various platforms such as iOS (Apple), Android (Google), Windows Phone 7 (Microsoft), webOS (HP/Palm), etc. Just like the smart-phone industry, the smart- MFD industry of Xerox, Ricoh, HP, etc has its own operating system/platform, with similar cryptic branding terms such as EIP (Xerox), ESA (Ricoh), OXP (HP), etc.

This document serves MTFs in understanding the procedures to help ensure their MFDs can meet the specific platform requirements to enable a HAIMS “app” on their MFD. An example of this “app” can be located at this website:

http://haims.smartmfp.net. Fortunately, AutoStore mitigates most of this complexity by allowing HAIMS to develop an MFD “app” universal of most MFD manufacturers.

AUTOSTORE-HAIMS ARCHITECTURE

Each MFD enabled with the HAIMS “app” communicates on different ports and protocols to the HAIMS server. To mitigate firewall issues, and reduce complexity, HAIMS has architected an approach to have an AutoStore “Relay” Server installed at each MTF. Therefore, communication will be from the local MFDs to the AutoStore “Relay” Server at the MTF which will then relay images and metadata to an AutoStore server at the HAIR. An example diagram is below:

AutoStore “relay” Server at MTF HAIMSAutoStore Server At HAIR

Pull communication from MTF to HAIR

It is the expectation that the MTF will provide the necessary hardware and Windows OS platform to support the

AutoStore “Relay” Server. Requirements for this server are outlined below.

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 3 of 10 http://haims.smartmfp.net/

4 | P a g e – AutoStore HAIMS Site Checklist 4.0

AutoStore General High Level Requirements This AutoStore Checklist must be complete, compliant and provided to Evolvent 2 weeks prior implementation.

All target MFDs being used for HAIMS AutoStore must be verified that they are both SSL enabled and AutoStore Ready 2 weeks prior to implementation; see “Being AutoStore Ready” section for more details.

Connectivity to include PPS updates complete and tested 2 weeks prior implementation; see “Facility Network/System

Technical Requirements” for more information.

AutoStore “Relay” Server Requirements

System requirements / limitations of AutoStore 5 and AutoStore 6 AutoStore 5 is used with HAIMS version 2.18.2.1 AutoStore 6 is used with HAIMS version 2.19.0.0

Supported Operating Systems Windows 2008 Server, 32 and 64-bit

Windows 2008 R2 Server, 32 and 64-bit

Windows 7 Ultimate or Enterprise, 32 and 64-bit***

The above OSs being virtualized on VMWare or other virtualization platform

*** Operating systems ONLY supported if not governed by end user device group policy object implementing firewall restrictions preventing port access. Treatment facilities normally have firewall restrictions for desktop operating systems that prevent the system from listening on ports to facilitate the network traffic between MTF Relay Server and the MFDs.

Non-Supported Operating Systems

Windows Server 2000

Windows Server 2003

Windows Server 2008 Domain Controller

Windows Small Business Server 2003

Windows Small Business Server 2008

Windows Small Business Server 2011

Windows Vista Home Basic and Home Premium

Windows 7 Home Premium and Professional

Any operating system governed by end user device group policy object implementing firewall restrictions preventing port access.

Rights

AutoStore needs to run with local administrative rights for the following tasks:

Installation

Administration

Applying licenses

Runtime of the server Access to external network (communication with HAIMS AutoStore WSS Server at designated Regional HAIR)

Hardware Requirements

SMB: Desktop class CPU / 2 GB of RAM

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 4 of 10

5 | P a g e – AutoStore HAIMS Site Checklist 4.0

Standard: Desktop class /Server class CPU with 2 Cores / 4 GB RAM

Enterprise: Server class CPU with multiple cores / 4 GB or more RAM

100 MBit / 1 GB Network Connection

10 GB of free hard disk space

Other Software components

.NET Framework v3.5

.NET framework v4.0 Internet Information Server (IIS) for certain components

FTP and HTTP Server for certain components

CDO Message Objects for sending via MAPI

Virtualization

AutoStore supports virtualization deployments. Virtualization is the method of running AutoStore on a Virtual Machine

(VM) instead of directly on physical hardware e.g. on VMware or Microsoft Virtual Server. The VM runs AutoStore like a normally installed operating system, and the TCP/IP communication can happen without any interruption.

Facility Network/System Technical Requirements Requirements Compliant?

Workstation/server that is being provided for the MTF Relay needs a local administrator account which can access the Internet (without being prompted for domain account). This local administrator will also be used to install the Autostore MTF relay software and will be configured to run the Autostore application

Yes / No

Workstation/server should not have any local or group policy firewall restrictions that disallow service or network access to the MTF Relay Server. (MFDs will need to communicate to MTF Relay Server without restrictions; this is only for local site traffic)

Yes / No

Ensure there are no network connectivity restrictions exists between MFDs and MTF Relay Server Yes / No

Server must have a CAC reader for testing purposes Yes / No

Server must have a DVD-ROM to be able to copy data onto the server Yes / No

DNS A record must exist for the target HAIR AutoStore WSS (see test below) Yes / No Network connectivity from the MTF Relay Server to the WSS Server at the target HAIR over 443. This can be verified by launching Internet Explorer (using local administrator and should not be prompt for domain logon) from the MTF Relay Server and browsing to your dedicated HAIR AutoStore WSS URL. If you are prompted with a Windows username/password, test is successful.

Yes / No

Network connectivity from the MTF Relay Server to the HAIMS URL at the target HAIR over 443. This can be verified by launching Internet Explorer (using local administrator and should not be prompt for domain logon) from the MTF Relay Server and browsing to your dedicated HAIMS HAIR URL. If HAIMS banner is displayed, test is successful.

Yes / No

MTF Relay Server / workstation have a valid and current DoD certificate Yes / No

Any HBSS restrictions on MTF Relay Server that may block the AutoStore Service (batch.exe) Yes / No

A temporary workstation with network connectivity to test and troubleshoot issues with the MTF relay server Yes / No

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 5 of 10

6 | P a g e – AutoStore HAIMS Site Checklist 4.0

COMMUNICATION ARCHITECTURE

AutoStore uses a client/server communication when working with MFDs or network scanners. The AutoStore server provides the configuration to the MFD clients, who in turn display the menus for indexing/metadata and sends back the image and indexing/metadata information to the server system for further processing.

This web services-driven communication allows for central management. This is a flexible, near zero footprint on the

MFDs.

MFD Device

Menu Request

AutoStore/HAIMS

Image/Metadata

Autostore

Scan Tickets

NSI Autostore

Client

Menu Response

Image + DATA transport

High level overview on the communcation methods

Ports in AutoStore can be changed in the administration interface of the AutoStore “Relay” Server.

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 6 of 10

7 | P a g e – AutoStore HAIMS Site Checklist 4.0

Default ports being used by AutoStore / Component Functions

Component Port(s) Configurable Comment Encryptable Supports CAC

Fujitsu 3255 TCP YES SSL Check with Fujitsu

HP MFD/Digital Sender 3233 TCP YES SSL Yes (*)

HP OXPd 3233/3234 TCP Yes SSL Yes (*)

HP 9055/9065 MFD 3434 TCP YES NO Check with HP

HP 4100/9000 MFD 3232 TCP Partially 25 TCP is also needed for receiving files

NO Check with HP

HP Digital Sender

9100c xxx NO Depending on the HP Digital

Sender Service/Link

NO Yes (*)

Konica Minolta 50001/3 TCP YES For incoming files: 21 TCP for

FTP / 80/443 for WebDAV

SSL and PKI Yes (*)

Kodak ScanStation 8787 TCP YES SSL Check with Kodak

Kyocera MFD 37169 TCP YES NO Check with Kyocera

Kyocera Hypass 3250 TCP YES Only requires SSL encrypted configurable port for the connection between the device and server

SSL Check with Kyocera

Lexmark 3233/3234 TCP YES Custom SSL certificates can be used for encryption

SSL Yes (*)

Ricoh SDKJ1 8085 TCP YES SSL Check with Xerox

Ricoh ESA 8084 TCP YES SSL Yes (*)

Sharp xxx NO 21 TCP for data transfer NO Check with Sharp

Sharp OSA YES 80 TCP is needed for displaying menus, 21 TCP

(FTP), 139&445 TCP (SMB)

are needed for retrieving files

NO Yes (*)

Xerox CentreConnect

(EIP)

3241 TCP YES 80 TCP is needed for displaying menus, 21 TCP

(FTP), 139&445 TCP (SMB)

are needed for retrieving files

NO Yes (*)

Xerox WorkCentre xxx YES 21 TCP (FTP), 139&445 TCP

(SMB) are needed for retrieving files – 161 UDP for

SMNP configuration

NO Check with Xerox

Canon (Europe only – end of 2012 – US)

8787 TCP YES SSL Check with Canon

Any “Yes” for CAC means that the platform supports CAC, but the specific device by the manufacturer may not.

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 7 of 10

8 | P a g e – AutoStore HAIMS Site Checklist 4.0

MFD API PLATFORMS

The following information is more specific details related to the API platform available for each manufacturer. The IT department of each MTF should contact their local MFD support representatives (usually a dealer or the manufacturer), and/or contact NSi, the manufacturer of AutoStore at the following email address (support.haims@nsiautostore.com) for more detailed information and/or question. A dealer or support organization should know how to deploy the appropriate API, and with most modern devices this capability is pre-installed.

Additionally there are some implied requirements, such as (a) the MFD must be connected to the network, (b) the MFD must have a static IP address, (c) the MFD must have scanning capabilities.

The details below are for the most current API information per manufacturer. AutoStore supports an even wider range of devices with older API capabilities. As an example, the most recent API platform from Xerox is called EIP, however previously there was an XML output capability called “Template Based Scanning”. Template scanning is also still in use today by Xerox, and is sometimes only available on smaller MFD models.

Once the MFD devices are configured to support the AutoStore client/HAIMS “app”, the MFD will need to be configured which in most cases simply means telling it where the IP address of the AutoStore “Relay” Server is located. This configuration will be done by the HAIMS deployment team. There are various tools to push out this configuration based on the MFD manufacturer.

For each listing below, more information can be found specific to the AutoStore support at this link:

http://haims.smartmfp.net/mfpList.html (and then click on the applicable icon)

Additional information regarding API prerequisites can be followed at this link: http://haims.smartmfp.net/mfpapi.html

Manufacturer Xerox

Latest API Platform EIP

MFD Configuration Information

EIP is a “web” platform where once installed on the device, the only configuration it needs is to know the URL of the AutoStore “Relay” Server. There is an administrative tool on the AutoStore Server to enter the MFD IP addresses to automate this process to push out the URLs to each MFD. More specific documentation can be provided upon request, and is in the help files on the AutoStore Server.

Manufacturer Ricoh

Latest API Platform ESA

MFD Configuration Information

ESA is a java platform, requiring an AutoStore java client to be installed. There is an administrative tool on the AutoStore Server to enter the MFD IP addresses to automate this process to push out the java client to each MFD. More specific documentation can be provided upon request, and is in the help files on the AutoStore Server.

Manufacturer Sharp

Latest API Platform OSA

Configuration Information

OSA is a “web” platform where once installed on the device, the only configuration it needs is to know the URL of the AutoStore Server. This is a manual process to log into the Sharp web interface of each MFD to specify the URL of the AutoStore Server. More specific documentation can be provided upon request, and is in the help files on the AutoStore Server.

HP

Latest API Platform OXP

MFD Configuration Information

OXP is a java platform, requiring an AutoStore java client to be installed. This is a manual process to log into the HP web interface of each MFD to upload the AutoStore client. More specific documentation can be provided upon request, and is in the help files on the AutoStore Server.

Kyocera

Latest API Platform Hypas

MFD Configuration Information

Hypas is a java platform, requiring an AutoStore java client to be installed. This is a manual process to log into the physical device interface of each MFD to upload the AutoStore client. More specific documentation can be provided upon request, and is in the help files on the AutoStore Server.

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 8 of 10 mailto:support.haims@nsiautostore.com http://haims.smartmfp.net/mfpList.html http://haims.smartmfp.net/mfpapi.html

9 | P a g e – AutoStore HAIMS Site Checklist 4.0

Fujitsu (Network Scanners) Latest API Platform N/A

MFD Configuration Information

Fujitsu’s API is a client/server platform, requiring an AutoStore client to be installed. This is a manual process to log into the web device interface of each Fujitsu to upload the AutoStore client. More specific documentation can be provided upon request, and is in the help files on the AutoStore Server.

Kodak (Network Scanners)

Latest API Platform N/A

MFD Configuration Information

Kodak’s API is a client/server platform, requiring an AutoStore client to be installed. This is a manual process to log into the physical device interface of each Kodak to upload the AutoStore client. More specific documentation can be provided upon request, and is in the help files on the AutoStore Server.

Lexmark

Latest API Platform Embedded Solution Framework (ESF)

MFD Configuration Information

ESF is a java platform, requiring an AutoStore java client to be installed. This is a manual process to log into the Lexmark web interface of each MFD to upload the AutoStore client. More specific documentation can be provided upon request, and is in the help files on the AutoStore Server.

Canon

NSi Supported Devices Under Development

Latest API Platform MEAP Web

MFD Configuration Information

Canon has placed restrictions on using AutoStore in the US, and therefore any HAIMS button on the MFD can only be deployed in Europe. However, a new technology called MEAP Web is being developed and may be available as early as the summer of 2012. MEAP Web eliminates this restriction.

Konica Minolta

Latest API Platform OpenAPI

MFD Configuration Information

OpenAPI is a “web” platform where once installed on the device, the only configuration it needs is to know the URL of the AutoStore Server. There is an administrative tool on the AutoStore Server to enter the MFD IP addresses to automate this process to push out the URLs to each MFD. More specific documentation can be provided upon request, and is in the help files on the AutoStore Server.

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 9 of 10

10 | P a g e – AutoStore HAIMS Site Checklist 4.0

AUTOSTORE MFD QUESTIONNAIRE

Does your site/MTF already have AutoStore in use? AutoStore is also rebranded by various manufacturers to include Xerox SMARTdocument Travel, Kyocera KyoCapture, and IKON/Ricoh DocAccel. If checked, please specify the version being used:

Version of AutoStore in use today: ______________________________________________

Please list the make/model of devices at your site/MTF that you would like to use to scan into HAIMS. Please include the IP address, if the device is using CAC, and if the device is currently configured for scanning. Please ensure you have web admin access to the MFDs listed below; this means you have the web URL for the MFD and the admin username and password to login. Additionally we request that you specify if the MFD is “AutoStore Ready” by meaning that it has the necessary API platform installed (i.e. Xerox=EIP, etc). Additional information about being AutoStore ready is provided below.

Manufacturer Model IP Address SSL

Enabled

Using

CAC

Scanning Web

Admin

Access

AutoStore

Ready (*)

Example HP (example) 9200c 192.168.10.9 Yes Yes Yes Yes Yes – has

OXPd

Please specify who your support vendor is for your MFDs and a contact number, this may include a local dealer, direct with the manufacturer, etc.

Contact information for local dealer: ___________________________________________

Please have the username/password available to access the MFDs.

(*) Being "AutoStore Ready" The AutoStore technology is well known throughout the MFD community with relationships with most of the major MFD manufacturers. By having an MFD leveraging AutoStore, the MTF can have a “HAIMS” button on the MFD to enable easy and secure scanning. Additional information about being AutoStore Ready and the prerequisite API platforms needed are covered in more detail previously in this document. The MTF site will need to ensure the MFD is AutoStore ready as this is a prerequisite for the installation of the HAIMS bulk scanning capability. Being AutoStore ready also requires SSL to be enabled but may vary based on manufacturer. Ensuring the MFD is both SSL enabled and AutoStore Ready must happen two weeks prior to the installation date as previously mentioned.

SP7000-16-Q-0008 Attachment 4 - HAIMS Auto Store Site Checklist Page 10 of 10