J-22 Contractor Furnished Property REDLINED for Amendment 2.docx

RFP-CMS-2010-0050

Attachment J-22: Contractor Furnished Property

The Application and Data Zones need to support:

· JVM (Java Virtual Machine) 1.6

· JMS (Java Messaging Service)

· Websphere MQ

· Websphere Message Broker

Application Server It is recommended that CEM run on a true application server. The following servers are supported:

· JBoss is the preferred server

· The following servers are also supported:

· Websphere

· Glassfish

· Weblogic

· JBoss

· Tomcat (does not support JMS out of the box – must be added)

Database System CEM requires an RDMS, and will be tested with the following:

· Oracle 10g and 11g

· DB2 (9)

· MS SQL Server 2005 and 2009

Operating System CEM will support :

· A variety of Unix platforms

· A variety of Linux platforms

· Windows Server 2003 and 2005?

The maintainer does not recommend running CEM in an IBM z/OS environment.

The CMS Technical Reference Architecture (TRA) recommends the following configuration to meet the above requirements:

· Websphere Application Server

· Websphere MQ

· Websphere Message Broker

· Oracle 10g

· z/Linux (Red Hat Enterprise Linux (RHEL) 5.2) on the mainframe or

· Solaris 10 Update 6, Windows 2000, Windows 2003 on the mid-tier The TRA recommendations are preferred but are not required for running the CEM at the MAC local data center.

Additional Software Needed:

Saxon 9.2

PART A HARDWARE REQUIREMENTS

CPUs and Memory:

The CEM Java application server must have a minimum of 8 GB Memory (2 GB based memory and 2 GB per concurrent process) available to the JVM.

The number of CPUs that the Application and Data servers contain will be directly related to the claims volume processed and the amount of multi-tasking and multi-threading anticipated. Recommended:

· CPU Speed: 1.8GHz – 3+ GHz

· Number of CPU: 1 - 8

· Number of Cores: 2 - 8

· Memory: 8 - 128 The greater the CPU speed, more CPUs, Cores, and memory, the faster the application will perform. More Memory will allow caching of some of the database tables and will increase throughput.

I/O Files and Disk Space:

· CEM Input files - Flat files used for input into the CEM can exist on a local path accessible to the CEM application on its host server. The files may physically exist elsewhere as long as they have a network mount on the host server. See example below.

· CEM Output files - Flat files created by the CEM will be placed on a local path accessible to the CEM application on its host server. See example below.

· CEM must have input, output, and error folders per FISS region for each transaction.

· Example:

5010 837 Input folder for 837 flat file from translator 5010 837 Output folder for 837 files from CEM to FISS 5010 837 Error Folder 837 file rejection from CEM for example, does not have a receipt date or missing CTR 5010 837 Folder 837 Receipt and Control 5010 837 Output Folder 277CA

· Edit files: (each file will be region specific, meaning for every region you will have a separate file) Zip code Claim Adjustment Reason Codes Country Codes Country Subdivision codes State codes DRG codes Group codes HCPCS codes HIPPS codes ICD-9 codes Modifier codes

NDC

Portion of NPI Crosswalk Remittance Advice Remark Codes Taxonomy Codes NOC codes Subsets of NUBC codes sets:

Admission Source Admission Type Type of Bills (In and Out) Type of Bill Frequency Patient Status Condition Codes Occurrence Codes Occurrence Span Codes Value Codes Revenue Codes Subset of Provider file

PART B SOFTWARE REQUIREMENTS

The Application and Data Zones need to support:

· JVM (Java Virtual Machine) 1.6

· JMS (Java Messaging Service)

· Websphere MQ

· Websphere Message Broker

Application Server It is recommended that CEM run on a true application server. The following servers are supported:

· Websphere

· Glassfish

· Weblogic

· JBoss

· Tomcat (does not support JMS out of the box – must be added)

Database System CEM requires an RDMS, and will be tested with the following:

· Oracle 10g and 11g

· DB2 (9)

· MS SQL Server 2005 and 2009

Operating System CEM will support :

· A variety of Unix platforms

· A variety of Linux platforms

· Windows Server 2003 and 2005 The maintainer does not recommend running CEM in an IBM z/OS environment.

The CMS Technical Reference Architecture (TRA) recommends the following configuration to meet the above requirements:

· Websphere Application Server

· Websphere MQ

· Websphere Message Broker

· Oracle 10g

· z/Linux (Red Hat Enterprise Linux (RHEL) 5.2) on the mainframe or

· Solaris 10 Update 6, Windows 2000, Windows 2003 on the mid-tier The TRA recommendations are preferred but are not required for running the CEM at the MAC local data center.

PART B HARDWARE REQUIREMENTS

CPUs and Memory:

The number of CPUs that the Application and Data servers contain will be directly related to the claims volume processed and the amount of multi-tasking and multi-threading anticipated. Recommended:

· CPU Speed: 1.8GHz – 3+ GHz

· Number of CPU: 1 - 8

· Number of Cores: 2 - 8

· Memory: 3 - 128 The greater the CPU speed, more CPUs, Cores, and memory, the faster the application will perform. More Memory will allow caching of some of the database tables and will increase throughput.

I/O Files and Disk Space:

· CEM Input files – 837P and 276 flat files created by the EDI translator

· CEM requires TRIPLE the disk space usually required by these files

· CEM Output files – 837P and 276 flat files to be sent to the EDC, plus 277CA flat files to return to the EDI translator

· CEM Receipt/Control/Balancing module input from the EDC – 277 and 835 flat files

· CEM requires DOUBLE the disk space usually required by these files

· Edit Files – 3 gigabytes

· The following files will be extracted from the MCS EDC files and downloaded:

State Codes Zip Codes Adjustment Reason Codes Remarks Codes Taxonomy Codes NPI Crosswalk HCPCS Codes (Procedure Codes) POS Codes Mammography Certification Diagnosis Codes Modifier Codes Plan Information

· The following come from other sources:

Country Codes Country Sub-Divisions Codes NUBC Condition Codes NDC Codes NOC Procedure Codes

· The following are updated and maintained by the CEM:

ICN Control – similar in size to the MCS ICNI Receipt, Control, and Balancing (CTR table)

(1) Processor: 500 MHz Pentium III or comparable AMD; 800 MHz Celeron or comparable AMD

(2) Disk space: 100 MB available

(3) Memory: 288 MB for Windows XP

(4) Operating system: Windows XP Service Pack 2 or later

(5) Browser: Internet Explorer 6.0 - Service Pack 1 with Cumulative security update for SP 1 (KB867801) or above. If using Internet Explorer 8.0, MS10-002: Cumulative security update must be applied. NOTE: Each PC can have only one active NGD session per IE 8 instance.

(6) Java: Sun J2SE v1.5 or higher Java Runtime Environment (JRE). The Sun J2SE can be downloaded from Sun’s web site at http://java.sun.com/. Do not download the Software Development Kit (SDK). Installation instructions are on this site.

(7) Monitor: 21”

(8) Pointing device: mouse with scroll

(9) Network interface: network interface card compatible with the call center LAN, which will ultimately allow workstation access to CMSnet

(10) Word processor: Microsoft Word 2002 (or higher version)—required only for generating correspondence)

(11) Viewers: Microsoft Word Viewer (provided free by Microsoft) and Adobe Acrobat Reader (v4.05 or v5.0 free from Adobe)—required to view correspondence and some reference materials available in Next-Generation Desktop (NGD)

Processor: Intel CPU 2.0 GHz Processor (or equivalent). Significant performance improvements are achieved with faster 2.5 GHz + Dual Core Processor Disk Space: 2 GB Available Memory: 2 GB for Microsoft Windows Operating systems. For workstations using Windows NT4.0, Windows 2000, Windows XP or running multiple applications simultaneously with HIGLAS, 4 GB of RAM will provide improved performance.

Operating System: Windows XP, Windows 2000, Windows 98 SE, Windows NT Workstation 4.0 ( Service Pack 3.5, or later) Browser: Internet Explorer 5.5 / 6.0 / 7.0. Java Runtime Environment (JRE) version 1.6.0_11 or higher required for browser compatibility.

NOTE: Proxy Server must be bypassed in the end user Internet Explorer configurations. HIGLAS recommends using a Proxy Exceptions List Entry of “HIGLAS*.HIGLASIBM.GOV”.

Monitor: / Video: 15” (17” or larger is preferable, especially for workstations used for WBT training) Super VGA (800 x 600) or higher-resolution video adapter and monitor.

Pointing Device: Mouse Network Interface: Network Interface Card compatible with the call center LAN, which will ultimately allow workstation access to the MPLS.