Section C Final - Attachment 18.docx

GSA SOLICITATION QMAD-JM-100001-N

August 23, 2010

GSA SOLICITATION QMAD-JM-10001-N

Attachment 1 – Customer Agency Profiles Release Date????

Attachment 18 Patient Travel (Separately Priced Mandatory Requirement) Purpose This attachment includes functional and performance requirements to enable Users to create, Patient Travel documents within ETS2.

The desired performance outcome is the delivery of comprehensive, streamlined, high quality, functionality to the NIH and other Federal agencies (if they choose) by ensuring all expectations are clearly understood.

Requirements The ETS2 shall meet or exceed the following requirements for Patient Travel:

Allow Agencies and their subordinate organizations to configure (i.e. turn off or on) ETS2 to claim Patient Travel on a Travel Authorization and Voucher. All Authorization and Voucher functionality required in ETS2 shall be made available for Authorizations and Vouchers used for Patient Travel;

Allow Agencies and their subordinate organizations to configure both the Trip Purpose Identifier and Trip Type to allow a User to indicate that a Travel Authorization is for Patient Travel. Users will be required to select the appropriate Trip Purpose Identifier and Trip Type as configured by their Agency;

Require the User to enter a Patient Protocol Number (minimum of 12 characters) on the Patient Travel Authorization. The Patient Protocol Number shall be transmitted via the standard ETS2 data input/output process to the Agency’s business system;

Display the Patient Protocol Number on the Travel Voucher when created from the Patient Travel Authorization. The User shall be prevented from changing the Patient Protocol Number on the Travel Voucher. All other Travel Voucher functionality shall function as required within ETS2; and Transmit the necessary data input/output files, once a Patient Travel Authorization is approved, to/from the Agency’s business system in less than 15 minutes at all times (this does not include the time it takes the Agency’s business system to process and submit back to ETS2 if required as part of the Interface). This requirement is included due to the nature of the business process for Patient Travel (i.e. Patients waiting in person to receive reimbursement for their expenses).