IEHP EDI Outbound Response Files (Provider Connection)
IEHP EDI Outbound Response Files (reports) are placed on the SFTP server in the Response_Prod folder in the Provider’s folder. An example of the file naming convention for the report describing the reasons the interchange control structure was not valid is 01s0318h101_40605_201604122150.TA1.
A. 01s0318h101 identifies the original file name
1. (Reference the Provider Sub-ID Chart for your two (2)-character Submitter code.)
B. 40605 is the transmission ID assigned to the file by IEHP for tracking purposes
C. 201804122150 is a CCYYMMDDHHMM date stamp for when the report was generated
D. TA1 describes the type of report 999 Report from IEHP to Providers
An example of the file naming convention for the report describing the reasons the file structure was not valid is 1s0318h101_40605_201804122150.999.
A. 1s0318h101 identifies the original file name
1. (Reference the Provider Sub-ID Chart for your two (2)-character Submitter code.)
B. 40605 is the transmission ID assigned to the file by IEHP for tracking purposes
C. 201804122150 is a CCYYMMDDHHMM date stamp for when the report was generated
D. 999 describes the type of report EVR Report from IEHP to Providers.
An example of the file naming convention for the report describing the reasons the data elements were not valid is 01s0318h101_40605_EVR_201804122150.rph.
A. 01s identifies the original file name
1. (Reference the Provider Sub-ID Chart for your three (3)-character Submitter code.)
B. 40605 is the transmission ID assigned to the file by IEHP for tracking purposes
C. EVR (Encounter Validity Report) describes the type of report
D. 201804122150 is a CCYYMMDDHHMM date stamp for when the report was generated .rph defines a report file that lists all invalid hospital encounters within the submitted file (the h identifies a hospital encounter).