Functional Requirements Document

Project Identification

Functional Specification:

Requestor and/or the Functional Lead/Consultant should complete the Functional Description section. Once the functional specification is complete, there should be a functional spec review, including at a minimum the requestor/end user, functional spec author, and the assigned tech spec writer. If the requestor/end user is in agreement that the functional spec is complete and accurate, they should sign-off. At that point, the tech spec writer will complete a technical specification, consulting with the functional spec writer as needed.

FUNCTIONAL DESCRIPTION

General Description and Purpose of this Customization/Modification:

UHCL's Health Center will be transitioning from EMR system to PNC and a new data interface is requested to accommodate transfer of student and employee data from PeopleSoft to PNC.

Scope:

• Develop a process to produce a datafile that includes student and employee data.
• Establish an SFTP connection to transfer datafile from PeopleSoft to PNC.

FUNCTIONAL SPECIFICATION (Detail specifically what needs to be modified or created)

Data file:

1. File formatting : Please see attachment 1.
2. Approved student fields : Please see attachment 2.
3. Approved employee fields : Please see attachment 3.

Population:

All active UHCL employees and enrolled students.

Assumptions:

All data fields are required to be sent to PNC; However, the fields that are not approved will be sent as blanks.

Required security role to run the process:

UHCSC_CC_PNC_INTFC_PROC

SFTP configuration:

sftp setup FTP ID                                        = PNC
sftp setup FTP Address                             = sftp.pointnclick.com
sftp setup User Name                               = UHCLSFTP
sftp setup FTP Remote Directory            = Production/Import/Reg

Filenames:

PNC_Employee_Reg_UHCL_PROD.txt
PNC_Student_Reg_UHCL_PROD.txt

Current schedule:

Daily 10:00PM 

Revision Log