Enterprise File Transfer (EFT) Setup Instructions

yompmulligrubsInternet και Εφαρμογές Web

31 Οκτ 2013 (πριν από 3 χρόνια και 1 μήνα)

92 εμφανίσεις




Enterprise File Transfer (EFT) Setup Instructions


1



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
EFT_ADMIN@cms.hhs.gov


** 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: EFT_ADMIN@cms.hhs.gov


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


James O’Kussick at
James.Okussick@cms.hhs.gov



Information Security

Each application is respon
sible 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 de
fined 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
Manage
d 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 spec
ify 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
Platfo
rm Server will convert the remote user ID and password to a CMS RACF user ID using encrypted MFT





Enterprise File Transfer (EFT) Setup Instructions



2

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 Ce
rtificates

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

Mainframe filename (What we create)

T#EFT.OG.TIFF.C%%%%%%.DYYMMDD.THHMMSST


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.



Enterprise File Transfer (EFT) Setup
Questionnaire


3



A.

CUSTOMER INFORMATION

Customer Name:








3
rd

Party Vendor:







B.

CONTACT INFORMATION

1.

CMS BUSINESS OWNER CONTACT

Full
Name:














First

Last


Phone:

(




)



-






Email Address:







2.

CMS GTL CONTACT

Full
Name:














First

Last


Phone:

(




)



-






Email Address:







3.

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

Full
Name:














First

Last


Phone:

(




)



-






Email Address:







C.
APPLICATION INFORMATION


What is the CMS Application name?
Example: MARx, MBD or EDB







D.

DATA TRANSFER INFORMATION

1.

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



MFT INTERNET SERVER



MFT PLATFORM SERVER (CYBERFUSION)




SI (GENTRAN)

CONNECT DIRECT (C:D)








Enterprise File Transfer (EFT) Setup Instructions


4


2.

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




Yes

No


3.

Please show the flow of data.


Example: External

server to CMS application
. Please update the following:



From To From

To


















4.

What is the frequency that the files will be sent?



Daily

Weekly

Monthly

Quarterly

Annually


What is the frequency that the files will be received?



Daily

Weekly

Monthly

Quarterly

Annually


5.

What is the total estimated file size(s)?



less than 1GB

1GB to 300GB

greate
r than 300GB


6.

How many files will be transmitted? Sent:






Received:







John Doe’s
Serv


NLR

Applica瑩on


CMS

Mai nframe






Enterprise File Transfer (EFT) Setup Instructions


5


7.

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


Special Requirements:





8.

For files going through the CMS Mainframe:


Please provide the logical record length, record format and block size for the new files.


Logical record length:







Record format:






Block size:







9.

Is there a current dataset at CMS for the file?




Yes

No




If yes, please provide the name:








If not, is there something EFT can put into the new name EFT
creates to help identify the file (some
required information)?

Suggested Identifier (maximum of 14 characters):








10.

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






11.

What is your expected Production Date?