Enterprise File Transfer (EFT) Setup Instructions

Enterprise File Transfer (EFT) Setup Instructions

Introduction

The purpose of this Questionnaire is to collect the technical details needed to setup the EFT exchange process with the Centers for Medicare & Medicaid Services (CMS).

• Please provide as much detail as you can when completing this survey. Return the completed survey within 3 business days to

** An incomplete survey may cause a delay in the time it takes to complete this request. **

• Use the letter ‘x’ to mark your selection. All other fields enter the requested information. Not applicable information, please add N/A.

Contact Information

For technical questions, please contact the EFT group and a technician will contact you.

Department Email:

For application related questions, please contact your CMS GTL (Government Task Lead) or the CMS EFT GTL:

James O’Kussick at

Information Security

Each application is responsible for enforcing authorization to content and functionality within the application. Access Manager and RACF provide authorization to the applications as a whole by applying policies that have been defined for the application’s GTL to the user data. For example, the policy for the MARx UI requires that a user have either a Submitter or a Representative plan Role attribute or that a user requires access to a particular dataset.

Once the user has been authorized through Access Manager, the user is also defined in the IBM Sterling B2B Integrator Suite (formerly Gentran, also known as SI) or the Managed File Transfer Internet Server (MFT IS)applications or through RACF that the user has dataset access to manage file access for Connect:Direct (C:D) or Managed File Transfer Platform Server (MFT PS).

User Provisioning

IACS/System ID’s are required for SI and MFT IS. These ID’s are registered to individuals and expire every 60 days. Any issues related to your account or password, please contact the CMS IT Service Desk at 1-800-562-1963 or 410-786-2580 and request a trouble ticket to be opened for the IACS group.

RACF

The CMS business partners who use C:D to transmit files directly to the mainframe environment in the CMS data center will be required to specify a Secure Point of Entry (SPOE) in their C:D processes. This SPOE will be automatically converted to a CMS RACF user ID that will be used to authenticate the user.

The CMS business partners who use MFT Platform Server to transmit files directly to the mainframe environment in the CMS data center will be required to specify a remote user and password in their MFT processes. Typically, the remote user and password is stored encrypted on the remote node in a MFT initiator user profile. The CMS MFT Platform Server will convert the remote user ID and password to a CMS RACF user ID using encrypted MFT responder user profiles. This CMS RACF user ID will be used for user authentication and to determine the user’s authorization to files.

SSH keys or x.509 Certificates

The CMS business partners, who connect to the second instance of MFT Internet Server, must authenticate using an SSH2 key or an x.509 certificate.

Password Exchanges

For SSH keys and account passwords, if your site has a process for notifying the EFT group for an expiring password, please provide a contact and the procedure documentation. The Partner Server document will need to be updated and resubmitted to the EFT group.

File Naming Conventions

Please follow the guidelines for CMS file naming conventions:

• No more than 44 characters
• No more than 8 characters per qualifier
• The qualifiers cannot start with a number
• The last 2 qualifiers must be the date and time stamp (see above)
• Test files begin with a T#
• Production files begin with a P#

Additional Documentation Required

Internet Server

• Partner Server Information document (outbound to customer)*
• If using SSH servers, SPOE form*

Platform Server

• Partner Server Information document*
• SPOE form*
• VPN*
• ISA form

C:D

• Partner Server Information document*
• SPOE form*
• VPN*
• ISA form (new connection)

*Documents can be provided by Lockheed Martin if needed.

2

Enterprise File Transfer (EFT) Setup Instructions

1. CMS BUSINESS OWNER CONTACT

1. CMS GTL CONTACT

1. TECHNICAL CONTACT (This is the person that will be assisting with the setup)

1. Which electronic file transfer platform do you wish to setup? (Check only one)

1. Does the transferred file(s) contain PII (Personal Identifiable Information)?

1. Please show the flow of data.

1. What is the frequency that the files will be sent?

1. What is the total estimated file size(s)?

1. How many files will be transmitted? Sent: Received:

1. Are there any special handling requirements associated with the data? Example: Outbound files sent to multiple destinations or binary transfer.

1. For files going through the CMS Mainframe:

1. Is there a current dataset at CMS for the file?

1. Provide an estimated date when you would like to begin testing:

1. What is your expected Production Date?

1